+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Usage (/forum-34.html)
+--- Thread: ispCP locks up when adding/deleting domains (/thread-7286.html)
ispCP locks up when adding/deleting domains - corra - 07-23-2009 07:58 AM
Hi Everyone,
Think ispCP is absolutely brilliant and think the devs have done an awesome job. I've only just started using it though and I'm having a few issues.
FreeBSD 7.2 Jail, followed the FreeBSD tutorial exactly.
Firstly ispcp_daemon wouldn't start up and I didn't change a thing and now it does.
Now every time I add a domain or delete a domain / do anything else involving ispcp_daemon I suspect I start getting 500 errors and max execution time exceeded errors. And when looking in top php-cgi is running at 100% cpu, I then need to do a killall -9 php-cgi to enable Apache to respond again.
Any help would be much appreciated
RE: ispCP locks up when adding/deleting domains - corra - 07-24-2009 03:14 PM
I have investigated further and discovered the only way to sucessfully add/remove domains is to killall -9 php-cgi after adding and then run ispcp-rqst-mngr to complete the domain addition.
RE: ispCP locks up when adding/deleting domains - kilburn - 07-24-2009 04:22 PM
Can you strace the 100% cpu usage php5-cgi to see what is it doing? I suspect that it's a trashing problem (out of ram, machine begins swapping, I/O is killed and you get an unresponsive server), but I may be wrong...
RE: ispCP locks up when adding/deleting domains - corra - 07-24-2009 05:55 PM
Does strace have an amd64 equivalent because I can't make the port :
===> strace-4.5.18_1 is only for i386, while you are running amd64.
This machine is a dual 3.6ghz xeon with 5gb of ram and plenty available.
RE: ispCP locks up when adding/deleting domains - kilburn - 07-25-2009 02:01 AM
I'm just a linux guy, this should serve the same purpose in the BSD world
RE: ispCP locks up when adding/deleting domains - vlad.gladin - 07-25-2009 02:06 AM
Exacly the same configuration here.... exactly the same error.
freebsd amd64, 7.2 inside a jail.
I think it's something to do with the daemon locking when adding a domain or doing some conf work.
I am still investigating.
It might be a permission problem somewhere.