[not solved] Failed to obtain or reinitialize VMemBuf
 

titile: Failed to obtain or reinitialize VMemBuf. possibly running out of swap space.

have been getting these errors on file uploads to litespeed webserver 4.1.4.

its happened three times so far, several days between incidents. haven't been able to work out what causes it.
once it starts happening it seems to happen to everyone if the upload is above a certain size (i haven't worked out what size exactly).

restarting litespeed solves the problem.

/tmp has plenty of space
and /tmp/lshttpd's permissions appear to be fine

please refer:
http://www.litespeedtech.com/support...ead.php?t=5284
see if /tmp/lshttpd/swap related?

i found that last week when looking into the first occurrence but it didnt seem to help
/tmp/lshttpd/swap's permissions are ok. owned by lsws, the same user as litespeed is running as.

there are no other errors in any log files at the same time of each error.
the upload is not even attempted by the browser, a connection reset error is seen in the browser instantly.

as restarting lsws fixes the bug it also seems to suggest its not a file permission error.

the problem has happened again.
6 hours of errors over night preventing all file uploads to our sites.

i've rolled back to 4.1.3

just now I experienced same issue
it's 4.0.20. lsphp 5.1.2 with Server API : LiteSpeed 4.10

so it's not likely an issue between 4.1.3 and 4.1.4

I did a change in php.ini:
upload_tmp_dir = /tmp
(it's not set before.) and restarted lsws.

my test shows upload 1M file was ok, but failed for a 1.8M file.

maybe restart lsws resolved the issue as you observed.
just put more info here.

upload_tmp_dir is not set in my php.ini either. sys_get_temp_dir() returns /tmp
should i set it anyway?

/tmp has 4.2gig free. according to graphs it got as low as 3.9gig yesterday.

restarting lsws means that the problem goes away for some time. seems to come back on its own for no reason.

for example, I just uploaded a 10mb file with no problem. while it was uploading I could see /tmp/phpnMUhZ6 getting filled.

This problem has returned again today.
Strange that only yesterday I upgraded to lsws 4.1.10.

any suggestion as to what might be the cause?

does it happen once just after upgrade, or does it happen times(can check the error log) after upgrade ?

I don't know what triggered it last time (perhaps an upgrade that I had forgotten), but this time it seems it probably was the upgrade that caused it.
It happened on every website accepting file uploads until i ran "lswsctrl restart".
so far for the last 2 days no error has been reported.

I have similar experience on another website. if it happens again, please report it here to trace it.