Domains stuck in "Addition in progress"

[olindata]

Hey guys,

well, as the title says, teh domains are stuck in that mode. The daemon is running and i even restarted it.
On the ispcp debugger page in the admin interface, it says 17 requests pending. When I click on it, I get a message saying "Daemon returned 0 as status code"

I'm using 1.0.2 on CentOS 5.3. Any help would be highly appreciated!

[kilburn]

You should test 2 things:

1- Manually connect to the daemon using telnet and tell it to "execute request". See what happens.

2- Manually run the ispcp-rqst-mngr and see what happens.

[olindata]

Thanks! See my results below:

(09-08-2009 09:15 PM)kilburn Wrote:  You should test 2 things:

1- Manually connect to the daemon using telnet and tell it to "execute request". See what happens.

Code:

[root@web01 ~]# netstat -lepn | grep ispcp
tcp        0      0 127.0.0.1:9876              0.0.0.0:*                   LISTEN      0          286925     13197/ispcp_daemon  
unix  2      [ ACC ]     STREAM     LISTENING     102927 19239/master        private/ispcp-arpl
[root@web01 ~]# telnet 127.0.0.1 9876
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: No route to host
telnet: Unable to connect to remote host: No route to host
[root@web01 ~]#

2- Manually run the ispcp-rqst-mngr and see what happens.
[/quote]

Code:

[root@web01 ~]# ispcp-rqst-mngr
-bash: ispcp-rqst-mngr: command not found
[root@web01 ~]# whereis ispcp-rqst-mngr
ispcp-rqst-mngr:
[root@web01 ~]# find / -type f -name ispcp-rqst-mngr
/var/www/ispcp/engine/ispcp-rqst-mngr
[root@web01 ~]# cd /var/www/ispcp/engine/
[root@web01 engine]# ./ispcp-rqst-mngr
[root@web01 engine]#

[kilburn]

Quote:

Code:

[root@web01 ~]# telnet 127.0.0.1 9876
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: No route to host
telnet: Unable to connect to remote host: No route to host

So your server doesn't know how to route to localhost? Something is really wrong here. Do you have a "127.0.0.1 localhost" line in /etc/hosts? If not, add it....

Quote:

Code:

[root@web01 engine]# ./ispcp-rqst-mngr
[root@web01 engine]#

... and your domains got configured properly, right?

[olindata]

(09-08-2009 10:43 PM)kilburn Wrote:  

Quote:

Code:

[root@web01 ~]# telnet 127.0.0.1 9876
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: No route to host
telnet: Unable to connect to remote host: No route to host

So your server doesn't know how to route to localhost? Something is really wrong here. Do you have a "127.0.0.1 localhost" line in /etc/hosts? If not, add it....

Quote:

Code:

[root@web01 engine]# ./ispcp-rqst-mngr
[root@web01 engine]#

... and your domains got configured properly, right?

Hmm.. apparently there was something wrong with the ProFTPd config that was causing this. For some reason, there were two lines in the config file that were routing authorisation to PAM. Strange though, since I just followed the guidelines with the install and didn't use it beforehand. Anyway, once that was all good and done, the requests were processed and everything seems to be peachy.

As a general comment though, I can say that this whole thing would be much easier to setup if there was proper logging and error messages. Now, stuff is all over the place, which makes it really hard to figure out what is wrong for an ispCp n00b (not a linux n00b at all, just ispCp).

On to making my smtp work

[olindata]

(09-08-2009 10:49 PM)olindata Wrote:  

(09-08-2009 10:43 PM)kilburn Wrote:  

Quote:

Code:

[root@web01 ~]# telnet 127.0.0.1 9876
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: No route to host
telnet: Unable to connect to remote host: No route to host

So your server doesn't know how to route to localhost? Something is really wrong here. Do you have a "127.0.0.1 localhost" line in /etc/hosts? If not, add it....

Quote:

Code:

[root@web01 engine]# ./ispcp-rqst-mngr
[root@web01 engine]#

... and your domains got configured properly, right?

Hmm.. apparently there was something wrong with the ProFTPd config that was causing this. For some reason, there were two lines in the config file that were routing authorisation to PAM. Strange though, since I just followed the guidelines with the install and didn't use it beforehand. Anyway, once that was all good and done, the requests were processed and everything seems to be peachy.

As a general comment though, I can say that this whole thing would be much easier to setup if there was proper logging and error messages. Now, stuff is all over the place, which makes it really hard to figure out what is wrong for an ispCp n00b (not a linux n00b at all, just ispCp).

On to making my smtp work

Apparently something is still wrong here, daemon still returns 0 as its status code. Even when I stop and start the daemon, this remains the same.
I have a feeling it might have something to do with us not having installed dovecot and a bunch of other services.

The problem here is: how can I see what is going on? where does that daemon log what it is doing, and where do errors go?

[sci2tech]

You need to kill daemon by pid with sigkill signal. Then start it again. Or reboot server.

[olindata]

(09-23-2009 03:33 AM)sci2tech Wrote:  You need to kill daemon by pid with sigkill signal. Then start it again. Or reboot server.

Isn't the following enough?

~: /etc/init.d/ispcp_daemon stop
~: /etc/init.d/ispcp_daemon start

[sci2tech]

In your case no. To check:

Code:

/etc/init.d/ispcp_daemon stop
ps aux | grep ispcp_daemon

Next time please use search. This was discussed over and over again.

[olindata]

(09-23-2009 03:40 AM)sci2tech Wrote:  In your case no. To check:

Code:

/etc/init.d/ispcp_daemon stop
ps aux | grep ispcp_daemon

Code:

[olindata@web01 ~]$ sudo /etc/init.d/ispcp_daemon stop
Password:
audit_log_user_command(): Connection refused
Shutting down ISPCP services:                              [  OK  ]

[olindata@web01 ~]$ ps aux | grep isp
root     21276  0.0  4.2  89924 15756 ?        S    13:16   0:00 /usr/bin/perl /var/www/ispcp/engine/ispcp-apache-logger -e
root     21285  0.0  4.2  90052 15836 ?        S    13:16   0:00 /usr/bin/perl /var/www/ispcp/engine/ispcp-apache-logger
olindata 21829  0.0  0.2  61176   748 pts/0    S+   14:00   0:00 grep isp
[olindata@web01 ~]$

(09-23-2009 03:40 AM)sci2tech Wrote:  Next time please use search. This was discussed over and over again.

Oh, sorry! I continued my own thread for two reasons:
- it is a continuation of this problem that was never really solved, it just seemed liek it was.
- googling with "Daemon returned 0 as status code" led me straight here