Did you ask same question on another thread? Please show directory listing of the sess_* files. Like Code: ls -lht tmp/sess* | tail -20 If cron jobs are not running, debug instructions are in https://www.howtoforge.com/community/threads/please-read-before-posting.58408/
I bet the built in cleanup has the same "too many args" problem you saw on the cli, well need to change the commands run to avoid that.
I dont think so, or if i did then it would have been a very very long time ago the cron is working, so that part is not the issue, its something else Code: user@server1:/var/www/clients/client0/web40# ls -lht tmp/sess* | tail -20 -rw------- 1 web40 client0 21 May 24 12:32 tmp/sess_fe6lbrvirvvgp9h51v2sadscgv -rw------- 1 web40 client0 21 May 24 12:31 tmp/sess_iikeuiqt1351tlq2n8jtqgbjbt -rw------- 1 web40 client0 21 May 24 12:31 tmp/sess_fe24fh6gs5adhisj5b9vii8qfn -rw------- 1 web40 client0 21 May 24 12:31 tmp/sess_vh5qn4ithus3og7atvbpak8vlp -rw------- 1 web40 client0 21 May 24 12:31 tmp/sess_gfus900qm51e9v12tl4ngkf9eg -rw------- 1 web40 client0 21 May 24 12:30 tmp/sess_0nsi1lm2io9vchsqk5rb6p54qo -rw------- 1 web40 client0 21 May 24 12:30 tmp/sess_6v0s1a7gp0lbnmdbi2sskrhptm -rw------- 1 web40 client0 21 May 24 12:30 tmp/sess_us2jgfu9vgijg476k8su6qskp0 -rw------- 1 web40 client0 21 May 24 12:30 tmp/sess_gg5gv34tsmltkf9c3tmc7s4s6e -rw------- 1 web40 client0 21 May 24 12:30 tmp/sess_r73d9aqv2kbbgeolrt7sieeo21 -rw------- 1 web40 client0 21 May 24 12:29 tmp/sess_38b6vmttt873k5n0o9rsbeurlm -rw------- 1 web40 client0 21 May 24 12:29 tmp/sess_kmdecuk040i4avrubbna03su9r -rw------- 1 web40 client0 21 May 24 12:29 tmp/sess_o3f0rq0p48tev0onjd2almi3l1 -rw------- 1 web40 client0 21 May 24 12:29 tmp/sess_voj2sj6mbqhh54r6bpgdgnlpdk -rw------- 1 web40 client0 21 May 24 12:29 tmp/sess_vf8se3d1b7bipr0j031lqo1gk8 -rw------- 1 web40 client0 21 May 24 12:29 tmp/sess_od468r5ojob8vti669ad58l3ih -rw------- 1 web40 client0 21 May 24 12:29 tmp/sess_qh8s6725pkphdnavefve1p7s9m -rw------- 1 web40 client0 0 May 24 12:27 tmp/sess_kvntfohjp4plmljojmcbtd8r9j -rw------- 1 web40 client0 0 May 24 12:27 tmp/sess_ijc603q86g08nmp5gdj06kes8v -rw------- 1 web40 client0 21 May 24 12:24 tmp/sess_2msmb44fv5choifcelediqu8gq
Code: w------- 1 web40 client0 0 May 24 12:27 tmp/sess_kvntfohjp4plmljojmcbtd8r9j -rw------- 1 web40 client0 0 May 24 12:27 tmp/sess_ijc603q86g08nmp5gdj06kes8v -rw------- 1 web40 client0 21 May 24 12:24 tmp/sess_2msmb44fv5choifcelediqu8gq Those are new files, that is why the automatic remove does not remove them. They would get removed eventually if you wait. How many files are there? Show Code: ls -lht tmp/sess* | wc -l
Code: :/var/www/clients/client0/web40# ls -lht tmp/sess* | tail -20 -rw------- 1 web40 client0 21 May 24 12:32 tmp/sess_fe6lbrvirvvgp9h51v2sadscgv -rw------- 1 web40 client0 21 May 24 12:31 tmp/sess_iikeuiqt1351tlq2n8jtqgbjbt -rw------- 1 web40 client0 21 May 24 12:31 tmp/sess_fe24fh6gs5adhisj5b9vii8qfn -rw------- 1 web40 client0 21 May 24 12:31 tmp/sess_vh5qn4ithus3og7atvbpak8vlp -rw------- 1 web40 client0 21 May 24 12:31 tmp/sess_gfus900qm51e9v12tl4ngkf9eg -rw------- 1 web40 client0 21 May 24 12:30 tmp/sess_0nsi1lm2io9vchsqk5rb6p54qo -rw------- 1 web40 client0 21 May 24 12:30 tmp/sess_6v0s1a7gp0lbnmdbi2sskrhptm -rw------- 1 web40 client0 21 May 24 12:30 tmp/sess_us2jgfu9vgijg476k8su6qskp0 -rw------- 1 web40 client0 21 May 24 12:30 tmp/sess_gg5gv34tsmltkf9c3tmc7s4s6e -rw------- 1 web40 client0 21 May 24 12:30 tmp/sess_r73d9aqv2kbbgeolrt7sieeo21 -rw------- 1 web40 client0 21 May 24 12:29 tmp/sess_38b6vmttt873k5n0o9rsbeurlm -rw------- 1 web40 client0 21 May 24 12:29 tmp/sess_kmdecuk040i4avrubbna03su9r -rw------- 1 web40 client0 21 May 24 12:29 tmp/sess_o3f0rq0p48tev0onjd2almi3l1 -rw------- 1 web40 client0 21 May 24 12:29 tmp/sess_voj2sj6mbqhh54r6bpgdgnlpdk -rw------- 1 web40 client0 21 May 24 12:29 tmp/sess_vf8se3d1b7bipr0j031lqo1gk8 -rw------- 1 web40 client0 21 May 24 12:29 tmp/sess_od468r5ojob8vti669ad58l3ih -rw------- 1 web40 client0 21 May 24 12:29 tmp/sess_qh8s6725pkphdnavefve1p7s9m -rw------- 1 web40 client0 0 May 24 12:27 tmp/sess_kvntfohjp4plmljojmcbtd8r9j -rw------- 1 web40 client0 0 May 24 12:27 tmp/sess_ijc603q86g08nmp5gdj06kes8v -rw------- 1 web40 client0 21 May 24 12:24 tmp/sess_2msmb44fv5choifcelediqu8gq This output looks the same as last but its much more is thieir, and also should this be all removed by now? i think so, and also afew post before when i said their was 5000+ sess_ file, i have not touch or removed any myself see the outcome, and now i have 20000+ so something is very wrong with my system with sess_ files and updating to isp 3.2.4 last week did not resolve the issue, but crontab is working so i dont know where the blockage is?
These are all new files, so it's expected that they are there and they shall not get removed. Only old session files get removed, old means 3 days and older. The number of session files depends on the activity of the website, so it is normal that there are thousands of them and large sites can even have millions of sessions, but such sites normally don't use a file-based session handler. To sum it up, your system seems to be fine, nothing unusual, and session cleanup works as well as you don't have old sessions there according to your posts.
Thamks for that insight, I will wait two more days to see if this infact gets removed. I do wonder if their is a limit on the amount that isp can clean before command may timeout because of file handing is too large?
