vzfs disk space usage over 80%

[vps-vince]

Hi all,
I see over 80% usage for vzfs, should I worry?
Only had this VPS for less than 2 weeks.


Current Disk Usage
Filesystem Size Used Avail Use% Mounted on

vzfs 308M 251M 57M 82% /tmp


Thanks,

- V

[elix]

That appears to be your /tmp partition only. Might want to look at that directory and clean it out a bit.

[charles]

Thats correct. We provide a 300M /tmp which is mounted without execute permissions for security. If you have something generating a lot of temp files you can always configure it to put them in another directory outside of /tmp to avoid it filling up.

hth
charles

[vps-vince]

I'm trying to FTP into my main account to view /tmp using root username and password, but getting ''authentication failed' message. I don't want to venture into the world of SSH yet - not until I get used to all the new VPS power I have. :)

My suspicion is it may be eAccelerator?

- V

P.S. nice to see you here elix ;-)

[charles]

No, root ftp is disallowed for security reasons - it passes the password in plain text. Use an sftp client, like filezilla for example.

hth
charles

[vps-vince]

OK, I have WS_FTP Pro which also has sftp.
As suspected, it is the /tmp/eaccelerator/ directory, with 5205 files, 251Meg

Charles, what is the best way to deal with this? My client accounts don't get that much traffic yet, so it could get worse. Is there a setting for eAccelerator to flush older cache files or a better way you suggest?

Thanks

[charles]

The better way is to store them somewhere else as they do not pose a security risk. In php.ini change

eaccelerator.cache_dir="/tmp/eaccelerator"

to something like

eaccelerator.cache_dir="/tmp_eaccelerator"

and create that of course

mkdir /tmp_eaccelerator
chown apache.apache /tmp_eaccelerator


hth
charles

[Hostultrix]

Hmm that's a good idea. But do you mean to chown it to nobody?

[charles]

chown it to whatever user apache runs as on your system (typically its apache or nobody). To see what it is on your system run

ps auxwww | grep httpd

and you'll see the owner in the first column for the httpd processes.


charles

[vps-vince]

Moving to a new directory will solve the 300MB limit, but still don't want it running wild and filling up my hard disk space.

Is there a setting for eAccelerator to flush older cache files ...?


Cheers,

- V

[charles]

Just setup a cron job to clean them up periodically. I'd just try do this as infrequently as possible just to keep it effective (or your defeating the point of caching). So move the dir and cron it daily or weekly.

charles

[vps-vince]

Thanks Charles.
Do you (or anybody else) have a script I can use, preferably with a "delete files older than ..." setting, so as not to delete all and indeed defeat the whole purpose?

Cheers,

[BornOnline]

Enable a pruning period... I think this cleans it up, but it may be only memory and not disk. You can always delete the files using eaccelerator.php.

http://eaccelerator.net/IniSettingsUk

eaccelerator.enable="1"
eaccelerator.optimizer="1"
eaccelerator.check_mtime="1"
eaccelerator.debug="0"
eaccelerator.filter=""
eaccelerator.shm_max="0"
eaccelerator.shm_ttl="900"
eaccelerator.shm_prune_period="1800"
eaccelerator.shm_only="0"
eaccelerator.compress="1"
eaccelerator.compress_level="9"