Hello Jim,
sorry for the lag. Here is the .mp_sess.lck info:
/tmp/mp_sess # ll /tmp/mp_sess/.mp_sess.lck
-rw-r----- 1 httpd sys 0 Oct 12 01:56
/tmp/mp_sess/.mp_sess.lck
I didn' touched anything in /tmp after my last email but I have had to
add a cronjob with the find line.
If I can do anything more to help debug this tell me.
Jim Gallacher wrote:
dharana wrote:
I think there is a problem with the autocleaning function in
FileSession. I'm using Mod_Python 3.2.2b in a live server and I today
I noticed this:
/tmp/mp_sess # df -h /tmp
Filesystem Size Used Avail Use% Mounted on
/dev/sda7 989M 544M 395M 58% /tmp
/tmp/mp_sess # df -i /tmp
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda7 128768 128768 0 100% /tmp
/tmp/mp_sess # ll /tmp/
total 24
drwxrwxrwt 2 root root 4096 Oct 6 11:43 .ICE-unix/
drwx------ 2 root root 16384 Jun 14 22:30 lost+found/
drwxr-x--- 258 httpd sys 4096 Oct 6 06:04 mp_sess/
And, after executing this:
/tmp/mp_sess # find ./ -mmin +1440 -exec rm {} \;
I get this:
/tmp/mp_sess # df -i /tmp
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda7 128768 23857 104911 19% /tmp
So I think FileSession isn't doing its work. Any ideas?
Could you check:
ls -l /tmp/mp_sess/.mp_sess.lck
It should only exist when a cleanup is running.
.mp_sess.lck is a lock file to ensure only one cleanup process/thread is
running at one time. If something went wrong during a cleanup
(segfault?) then this lock file might not have been deleted. If an stale
lock file exists any subsequent cleanup will exit without doing
anything. If it exists delete it and see if the cleanup will run to
completion.
If this lock file looks like it might create problems I can add a check
to see if it's stale.
Regards,
Jim
--
dharana
