Current time: 11-16-2024, 11:28 AM Hello There, Guest! (LoginRegister)


Post Reply 
Update to latest trunk caused a 250 Error in ispCP gui debugger
Author Message
c0urier Offline
Junior Member
*

Posts: 89
Joined: Jun 2007
Reputation: 1
Post: #1
Update to latest trunk caused a 250 Error in ispCP gui debugger
Hi again,

I just updated to the lastest trunk from today 09-01-02 and I just for fun had a look in the admin panel/ispCP debugger and saw under ispCP Daemon tools that it wanted me to excute a command:
I clicked it and got this error: Daemon returned 250 as status code

A screen dump is attached

System Info:
Debian Lenny - Fully updated
Latest ispCP Trunk (2009-01-02)
Only a few modifications to the ispcp.conf file = Timestamp of version.

The error comes when you ex. try to modify a domain status (Delete/Create). And the amout of requests raises, like on the image there is only 1, but 4 now, after I tried to delete a test domain)


Attached File(s) Thumbnail(s)
   
(This post was last modified: 01-03-2009 02:47 AM by c0urier.)
01-03-2009 01:18 AM
Visit this user's website Find all posts by this user Quote this message in a reply
sci2tech Away
Senior Member
****

Posts: 1,285
Joined: Jan 2007
Reputation: 23
Post: #2
RE: Update to latest trunk caused a 250 Error in ispCP gui debugger
250 status code mens everything is ok, daemon is listening. When you delete a domain, all associated mails/ subdomains etc are marked for deletion. Until requests are executed, number of these request is displayed.
01-03-2009 04:31 AM
Visit this user's website Find all posts by this user Quote this message in a reply
c0urier Offline
Junior Member
*

Posts: 89
Joined: Jun 2007
Reputation: 1
Post: #3
RE: Update to latest trunk caused a 250 Error in ispCP gui debugger
(01-03-2009 04:31 AM)sci2tech Wrote:  250 status code mens everything is ok, daemon is listening. When you delete a domain, all associated mails/ subdomains etc are marked for deletion. Until requests are executed, number of these request is displayed.

That's true, but I have run into the old problem which we talked about in PM that nothing happens until I run the daemon manually. Strange!
01-03-2009 05:38 AM
Visit this user's website Find all posts by this user Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 2 Guest(s)