"open3: exec of /usr/local/cpanel/whostmgr/bin/whostmgr ./servup failed at whostmgr/bin/whostmgrd.pl "
On my "server status" page I just got -
"/usr/local/apache/bin/httpd: error while loading shared libraries: libgssapi_krb5.so.2: cannot open shared object file: No such file or directory"
"exim: Cannot allocate memory"
Cpanel shows "[an error occurred while processing this directive]" in some of the feature allocations.
Many of the errors seem to be related to memory allocation as well.
A cPanel tech that took a look at it asked - "I'm able to get into WHM now but I am still getting random "Cannot allocate memory" errors. Was anything done to the main VPS recently that could be affecting the OS's ability to tap into the free ram on the server ? I can't see anything from `dmesg` or anything on the console `cat /dev/vcs1` to check for system errors, can you find out from the server owner if they see anything odd ?"
I'm still trying to work with cPanel and the host regarding his questions.
My VPS provider has upgraded the versions of cPanel / WHM and the error continues to occur. The only "fix" has been a restart of the virtuozzo VPS session.
After a session restart the error goes away for between three and twenty hours before returning.
I'm taking the big step to a more professional server provider soon, but I really need the current VPS at least up for a little while so I can smoothly transition.
Any suggestions will be very, very, greatly apreciated.
Last edited by ServersInSeconds; 03-01-2004 at 01:05 AM.
I just got this response from the host:
> The VPS administrator is aware of the "cannot allocate memory" problems and is working with the VPS software vendor to get those resolved. It looks like it's a bug in the VPS software.
The software is Vituozzo.
I think I'll try to get this moved to a more appropriate forum now that I think it isn't cPanel related.