Jump to content

Excess Use Of Inodes by composer folder inside vendor.


IamAQ

Recommended Posts

Hello,

I am facing a problem with updating WHMCS. It says to check memory limits and execution time but both of them are set as recommended values. I think the problem lies with the cache. As my c-panel indicates excessive use of inodes. Inode has crossed its max value. Maybe that is the reason for updating failure. As because of max node usage cache is not enough for the updating process. 
My website is in the initial phases, and don't have much client's data.

I have seen that folder named 'composer' inside vendor folder consuming the majority of Inodes. 
Why it is so, What these folders contain? and how I can reduce it.

Is my website having spam or something?

Please help.

thanks,

Link to comment
Share on other sites

  • WHMCS Support Manager

Hi @IamAQ,

My installation's /vendor directory contains 7697 files. Whilst auto-updating, this will double as the new files are extracted before being copied across.

If this is hitting a limit of your hosting, you can apply incremental updates manually: https://docs.whmcs.com/Updating#For_a_Patch_Set

However you cannot apply patch sets to update between major versions, (eg. 7.6 > 7.7) so in the intervening period I recommend working with your hosting provider to increase this limit, or seek a different provider.

Link to comment
Share on other sites

5 hours ago, WHMCS John said:

My installation's /vendor directory contains 7697 files. Whilst auto-updating, this will double as the new files are extracted before being copied across.

 

In my case, it contains 177317 files. Can't I reduce them?
I don't want to transfer to another hosting.

Link to comment
Share on other sites

  • WHMCS Support Manager

Hi @IamAQ,

This indicates that the files from an unsuccessful auto-update attempt are present on your server.

It sounds like the new files have been partially extracted, but not yet copied to the new location. The auto-updater failed at this point because it couldn't extract all the new files.

The files are located at /vendor/whmcs/whmcs/ and can be safely removed.

Link to comment
Share on other sites

4 hours ago, WHMCS John said:

sounds like the new files have been partially extracted, but not yet copied to the new location. The auto-updater failed at this point because it couldn't extract all the new files.

Yeah, that's right! 

 

It do have many folders thats contains whmcs files, like admin, assets, downloads, vendor, attachments etc. 

 

May I remove that? Is it save if I remove these files?

Link to comment
Share on other sites

11 hours ago, larryjhammondd said:

Hi,

tell me ,   The files are located at /vendor/whmcs/whmcs/ and can be safely removed  ?????
  

Yes, The files located at vendor/whmcs/whmcs can be removed safely. I have done that and it didn't harm other files. 

Link to comment
Share on other sites

12 hours ago, IamAQ said:

What if I face the same problem again! 

u can compare your directory and default, just remove it.. to get more inodes space

remember : don't forget to backup before u do this..

if u user auto update please check your Temporary Path == Utility >> update WHMCS.  The temporary path is used for staging files during an update. It is recommended that this directory be located outside the public doc root.

Edited by lims
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated