Domain status is not OK... after any modification

Domain status is not OK... after any modification - 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: Domain status is not OK... after any modification (/thread-1811.html)

Pages: 1 2

Domain status is not OK... after any modification - bulforce - 11-19-2007 07:40 AM

I have this issue now... every time i made some change to domain.. ex. modify disk space or bandwidth. I am getting domain status is not OK

I am going out of this situation by runnung:

Code:

/var/www/ispcp/engine/ispcp-rqst-mngr

Anybody have idea what can cause this problem

RE: Domain status is not OK... after any modification - joximu - 11-19-2007 07:50 AM

is the ispcp_daemon running?

"/etc/init.d/ispcp_daemon restart"

/J

RE: Domain status is not OK... after any modification - bulforce - 11-19-2007 08:10 AM

Code:

# ps aux | grep ispcp_daemon

root      3466  0.0  0.0   1560   408 ?        S    Nov06   0:00 /var/www/ispcp/daemon/ispcp_daemon -- -p /var/run/ispcp_daemon.pid

It looks like is running

RE: Domain status is not OK... after any modification - joximu - 11-19-2007 08:50 AM

If a restart of the daemon does not solve the problem - hm, then maybe you could enable the debug mode... and then see what's in the log files.

/J

RE: Domain status is not OK... after any modification - bulforce - 11-19-2007 09:30 AM

I restarted the main daemon proccess... but it doesnt fix the problem.

here is the output of:

Code:

./ispcp-dmn-mngr

Code:

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 !

DEBUG: push_el() sub_name: dmn_mngr_shut_down(), msg: Starting...

DEBUG: push_el() sub_name: dmn_mngr_shut_down(), msg: Ending...

Also i have notice that this problem only appear if i change the disk size or bandwith of domains that are under reseller that has limit on those resources. If the reseller has unlimited bandwidth and disk spase, there are no problems to make any changes. Please not that the reseller has NOT reached the limit.

Here is the output of:

Code:

./ispcp-rqst-mngr

Code:

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: mngr_engine(), msg: processing 18, bgpriut.info, change.

DEBUG: push_el() sub_name: sys_command(), msg: Starting...

DEBUG: push_el() sub_name: sys_command('/var/www/ispcp/engine/ispcp-dmn-mngr 18 1>/var/log/ispcp/ispcp-dmn-mngr.stdout 2>/var/log/ispcp/ispcp-dmn-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: sys_command(), msg: Starting...

DEBUG: push_el() sub_name: sys_command('/var/www/ispcp/engine/ispcp-serv-mngr 1 0 0 0 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: 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...

This command is fixing the situation.

RE: Domain status is not OK... after any modification - joximu - 11-19-2007 09:35 AM

well, you only should run
/var/www/ispcp/engine/ispcp-rqst-mngr
manually...

BUT: which version of ispcp do you have? (from when?)

I think there was something similar in the last weeks - should be fixed...

/Joximu

RE: Domain status is not OK... after any modification - bulforce - 11-19-2007 09:39 AM

ispCP 1.0rc3 OMEGA
build: 2007-10-15
Priamos

I grab the latest snapshot at that time.

RE: Domain status is not OK... after any modification - joximu - 11-19-2007 10:18 AM

http://www.isp-control.net/ispcp/ticket/853

fixed november 3rd... - a newer ispcp version should fix this.

/J

RE: Domain status is not OK... after any modification - bulforce - 11-19-2007 12:18 PM

thanks for your response(s).
Howver i dont want to risk with complete upgrade since the server is already in a production stage. Also in the ticket 853 ... i am not seeing any instruction for removing the bug... except link to the german corner forum... unfortunatelly i dont speak german.

Can you please go further and post some more information about this bug.

Thank you

RE: Domain status is not OK... after any modification - joximu - 11-19-2007 08:50 PM

Have a look here

http://www.isp-control.net/ispcp/changeset/897

the changes on trunk/gui/reseller/edit_domain.php
just add the two lines - then you should be fine.

/Joximu