+- ispCP - Board - Support (http://www.isp-control.net/forum)
+-- Forum: ispCP Omega Support Area (/forum-30.html)
+--- Forum: Usage (/forum-34.html)
+--- Thread: ispCP don't "work" (/thread-6146.html)
ispCP don't "work" - santerref - 03-21-2009 10:24 PM
Hello, I setup ispCP 1.0 and now it don't work... All the request that he has to do he do not do it.
If i had a subdomain, the panel do not creat it and in ispcp debugger we see all the request that the panel have to do.
I have to execute the request engine...
And when the panel has to many request it makes error 500.
RE: ispCP don't "work" - gOOvER - 03-22-2009 06:49 PM
Please give us some more Informations about your used Distro, etc and don't forget to post your logs. !!!
RE: ispCP don't "work" - ceco91 - 03-23-2009 04:54 AM
Is ispCP daemon working ? Have you started ? Try to connect using telnet to 127.0.0.1:9876
RE: ispCP don't "work" - santerref - 03-23-2009 05:34 AM
First, is it possible to know where are the logs... I found /var/log/ispcp but there is like 1000 files with many numbers and 2 or 3 ispcp-xxx-xxx (engine program).
My ispcp_deamon work :
Code:
h3berg:~# telnet 127.0.0.1 9876
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
250 OK ispCP Daemon v1.1 Welcomes You!And i have an other problem... Why when ispCP have to many request to do he makes an error 500 and why when i lunch ispcp-rqst-mngr my apache cut/stop 1 minutes and after he becomes up again?
I have 340 clients.
RE: ispCP don't "work" - santerref - 03-24-2009 11:53 PM
Nobody can help me? I think that this is a big problem because the task don't work ! Everything are : Please wait ... I have to start on my server the ispcp-rqst-mngr ... I hate to do this everytime !
RE: ispCP don't "work" - BeNe - 03-25-2009 12:06 AM
Please enable the Debug
--> http://www.isp-control.net/ispcp/wiki/howto_debug
Greez BeNe
RE: ispCP don't "work" - joximu - 03-25-2009 12:20 AM
the interesting log files are:
/var/log/ispcp/*err* (the ones with size > 0)
/J
RE: ispCP don't "work" - santerref - 03-25-2009 02:26 AM
Ok i will look at the log and for the debug mod there is nothing.... And if I activate de debug mode... Witch script do you want that i start ( ispcp-rqst... ) ?
The last log that I have its :
drwxr-xr-x 2 vmail mail 4096 2009-03-24 09:29 ispcp-arpl-msgr
And in this folder I look at this file : ispcp-arpl-msgr.stderr and I see this :
Quote:Can't call method "address" on an undefined value at /var/www/ispcp/engine/messager/ispcp-arpl-msgr line 700.
If i activate the DEBUG in the ispcp.conf file and i start rqst-mngr :
Quote:DEBUG: push_el() sub_name: mngr_start_up(), msg: Starting...
DEBUG: push_el() sub_name: lock_system(), msg: Starting...
DEBUG: push_el() sub_name: sys_command(), msg: Starting...
DEBUG: push_el() sub_name: sys_command('`which touch` /var/run/ispcp.lock'), msg: Ending...
DEBUG: push_el() sub_name: lock_system(), msg: Ending...
DEBUG: push_el() sub_name: get_conf(), msg: Starting...
DEBUG: push_el() sub_name: get_file(), msg: Starting...
DEBUG: push_el() sub_name: get_file(), msg: Ending...
DEBUG: push_el() sub_name: setup_main_vars(), msg: Starting...
DEBUG: push_el() sub_name: decrypt_db_password(), msg: Starting...
DEBUG: push_el() sub_name: decrypt_db_password(), msg: Ending...
DEBUG: push_el() sub_name: setup_main_vars(), msg: Ending...
DEBUG: push_el() sub_name: get_conf(), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: mngr_start_up(), msg: Ending...
DEBUG: push_el() sub_name: mngr_engine(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: mngr_engine(), msg: processing 54, actualitesncis, change.
DEBUG: push_el() sub_name: sys_command(), msg: Starting...
DEBUG: push_el() sub_name: sys_command('/var/www/ispcp/engine/ispcp-sub-mngr 54 1>/var/log/ispcp/ispcp-sub-mngr.stdout 2>/var/log/ispcp/ispcp-sub-mngr.stderr'), msg: Ending...
DEBUG: push_el() sub_name: mngr_engine(), msg: processing 61, site, change.
DEBUG: push_el() sub_name: sys_command(), msg: Starting...
DEBUG: push_el() sub_name: sys_command('/var/www/ispcp/engine/ispcp-sub-mngr 61 1>/var/log/ispcp/ispcp-sub-mngr.stdout 2>/var/log/ispcp/ispcp-sub-mngr.stderr'), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: mngr_engine(), msg: processing 49, actualitesncis.forum-actif.net, change.
DEBUG: push_el() sub_name: sys_command(), msg: Starting...
DEBUG: push_el() sub_name: sys_command('/var/www/ispcp/engine/ispcp-als-mngr 49 1>/var/log/ispcp/ispcp-als-mngr.stdout 2>/var/log/ispcp/ispcp-als-mngr.stderr'), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: mngr_engine(), msg: processing 1, dev, change.
DEBUG: push_el() sub_name: sys_command(), msg: Starting...
DEBUG: push_el() sub_name: sys_command('/var/www/ispcp/engine/ispcp-alssub-mngr 1 1>/var/log/ispcp/ispcp-alssub-mngr.stdout 2>/var/log/ispcp/ispcp-alssub-mngr.stderr'), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: sys_command(), msg: Starting...
DEBUG: push_el() sub_name: sys_command('/var/www/ispcp/engine/ispcp-serv-mngr 0 2 0 0 3 1>/var/log/ispcp/ispcp-serv-mngr.stdout 2>/var/log/ispcp/ispcp-serv-mngr.stderr'), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: doSQL(), msg: Starting...
DEBUG: push_el() sub_name: doSQL(), msg: Ending...
DEBUG: push_el() sub_name: mngr_engine(), msg: Ending...
DEBUG: push_el() sub_name: mngr_shut_down(), msg: Starting...
DEBUG: push_el() sub_name: unlock_system(), msg: Starting...
DEBUG: push_el() sub_name: sys_command(), msg: Starting...
DEBUG: push_el() sub_name: sys_command('`which rm` -rf /var/run/ispcp.lock'), msg: Ending...
DEBUG: push_el() sub_name: unlock_system(), msg: Ending...
DEBUG: push_el() sub_name: mngr_shut_down(), msg: Ending...
And after in /var/log/ispcp/ispcp-als-mngr.stderr
Quote:Use of uninitialized value in string eq at /var/www/ispcp/engine/ispcp-als-mngr line 2968.
Use of uninitialized value in string eq at /var/www/ispcp/engine/ispcp-als-mngr line 2968.
Use of uninitialized value in string eq at /var/www/ispcp/engine/ispcp-als-mngr line 2968.
And in the manager there is always 4 "bug" and ispcp never make them ... I click and the link it's says : the .... return 250 and nothing happen...
RE: ispCP don't "work" - joximu - 03-25-2009 02:49 AM
arpl is the automated mail responder - this is not the right engine script...
there are other engine scripts which are invoced by the daemon:
/var/www/ispcp/engine/*-mngr
dmn = domain, msg = mail etc. depending on what has to be done the corresponding engine script should be run by the top mngr: ispcp-rqst-mngr
e.g.
daemon -> ispcp-rqst-mngr -> the right "*-mngr" script
Hope this helps finding the point...
You also can check if the connection daemon -> request manager is ok?:
telnet localhost 9876
helo 1234
execute query
bye
this should start the request manager...
/J
RE: ispCP don't "work" - santerref - 03-25-2009 03:07 AM
The problem is : the panel do not execute the engine when a user try to make something ...
Quote:Trying 127.0.0.1...
Connected to ks365184.kimsufi.com.local.
Escape character is '^]'.
250 OK ispCP Daemon v1.1 Welcomes You!
helo 1234
250 OK 127.0.0.1/1234
execute query
250 OK request is being processed.
bye
250 OK Good Bye!
Connection closed by foreign host.