ispCP - Board - Support
ispCP don't "work" - Printable Version

+- 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)

Pages: 1 2 3


RE: ispCP don't "work" - joximu - 03-25-2009 09:05 AM

now:
is the problem betwen ispcp-gui and the daemon or between the daemon and the request manager?

/J


RE: ispCP don't "work" - santerref - 03-25-2009 11:14 PM

I don't know ... Tongue I think that this is why I need your help... I do not really know where I have to look at..
When I try to use ispcp-dmn-mngr this is what I have :

Quote:DEBUG: push_el() sub_name: dmn_mngr_start_up(), msg: Starting...
DEBUG: push_el() sub_name: check_master(), msg: Starting...
DEBUG: push_el() sub_name: sys_command(), msg: Starting...
DEBUG: push_el() sub_name: sys_command('export COLUMNS=120;/bin/ps auxww | awk '$0 ~ /ispcp-rqst-mngr/ && $0 !~ /awk/ { print $2 ;}' 1>/tmp/ispcp-cc.stdout 2>/tmp/ispcp-cc.stderr'), msg: Ending...
DEBUG: push_el() sub_name: del_file(), msg: Starting...
DEBUG: push_el() sub_name: del_file(), msg: Ending...
DEBUG: push_el() sub_name: del_file(), msg: Starting...
DEBUG: push_el() sub_name: del_file(), msg: Ending...
DEBUG: push_el() sub_name: check_master(), msg: ERROR: Master manager process is not running !
DEBUG: pop_el() sub_name: check_master(), msg: ERROR: Master manager process is not running !
DEBUG: pop_el() sub_name: del_file(), msg: Ending...
DEBUG: pop_el() sub_name: del_file(), msg: Starting...
DEBUG: pop_el() sub_name: del_file(), msg: Ending...
DEBUG: pop_el() sub_name: del_file(), msg: Starting...
DEBUG: pop_el() sub_name: sys_command('export COLUMNS=120;/bin/ps auxww | awk '$0 ~ /ispcp-rqst-mngr/ && $0 !~ /awk/ { print $2 ;}' 1>/tmp/ispcp-cc.stdout 2>/tmp/ispcp-cc.stderr'), msg: Ending...
DEBUG: pop_el() sub_name: sys_command(), msg: Starting...
DEBUG: pop_el() sub_name: dmn_mngr_start_up(), msg: Starting...
DEBUG: pop_el() sub_name: get_conf(), msg: Ending...
DEBUG: pop_el() sub_name: setup_main_vars(), msg: Ending...
DEBUG: pop_el() sub_name: decrypt_db_password(), msg: Ending...
DEBUG: pop_el() sub_name: decrypt_db_password(), msg: Starting...
DEBUG: pop_el() sub_name: setup_main_vars(), msg: Starting...
DEBUG: pop_el() sub_name: get_file(), msg: Ending...
DEBUG: pop_el() sub_name: get_file(), msg: Starting...
DEBUG: pop_el() sub_name: get_conf(), msg: Starting...
DEBUG: pop_el() Empty 'EL' Stack !

What does it mean : Empty 'EL' Stack !


RE: ispCP don't "work" - ephigenie - 03-25-2009 11:33 PM

please create a <? phpinfo() ?> page and take a look if
sockets are in the list of supported file streams.
We use a socket to communicate with the daemon and sometimes there's a problem
that socket support was left out when compiling ...

Please check this.
It'll be a good thing if you could provide us with the output of your phpinfo somehow as an attachement maybe to a post.


RE: ispCP don't "work" - santerref - 03-25-2009 11:39 PM

For the socket I look on which domain? If I took a look at my principal domain :

Quote:sockets
Sockets Support enabled

If you want to look : http://h3berg.com/phpinfo.php


RE: ispCP don't "work" - joximu - 03-25-2009 11:58 PM

if you want to run the request manager manually:

ispcp_rqst_mngr (or something like this - it's in the engine folder).

I wonder, if the request manager is started if you do the "telnet 9876" thing from above.

Test: do some change in ispcp (they are not done because of your problem).
Do the "telnet 9876" thing and see if the changes are made in the system (eg. if there is no more to do in ispcp-debugger...)

/J


RE: ispCP don't "work" - santerref - 03-26-2009 12:03 AM

When I run the rqst-mngr it's ok (manually). It's the panel that do not execute the request so I think that the problem is with the GUI...


RE: ispCP don't "work" - joximu - 03-26-2009 08:41 AM

Does it work if you run the request manager by connecting to port 9876 and do a "execute request" (as above)????????

I just want to be sure...

If the gui has problems doing this connecting thing then we can really focus on that.

/J


RE: ispCP don't "work" - santerref - 03-26-2009 11:15 PM

Yes, when i make a telnet on the daemon and I execute request, he says to me Ok. Like in the precedent post :

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.

But I think that you want to I try to had a subdomain and after I run this and look if it do it...

I will try.


RE: ispCP don't "work" - joximu - 03-27-2009 12:42 AM

exactly - does it really run the request manager or does it only write down "OK ... being processed"...

/J


RE: ispCP don't "work" - kserxes - 05-08-2009 07:41 AM

Hi,

I would like to add myself to the discussion because I seem to have the exact same problem.

After changing something in the gui (e.g. adding an email address) I have to manually start the request manager and everything is fine, but if I wait for automatic execution I could wait for eternity Wink.

Telnet'ing on port 9876 I have the exact same output, so it says "250 OK ..." but actually it seems that the request manager isn't called. When using the ispCP debugger I see that there are "Execute requests". When I click on them I also get the "Daemon returned 250..." but the requests are still there.

I am running on an OpenSuse 10.1 system. Did a fresh install and had to use mod_php5 because I couldn't get fcgid to work properly.

In another post I read something about adding ispcp.lock (which now resides in /tmp folder right?) to the open_basedir value in 00_master.conf but that one is already added. By the way when is this lock file supposed to be existing because I haven't seen it so far?

Hope somebody can help. Thanks in advance!

Cheers,
Juergen