moved server, the server itself is not reporting?
list Mike Eggleston
I recently moved the hobbit server from one box to another. I changed DNS entries, firewall entries, etc., and now today everything except one box is reporting. The new hobbit server itself is not report its own status. I start the hobbit server with: # su - hobbit $ ~/current/server/hobbit.sh start The daemon does start, things updating, etc., just not the server box itself. In /var/log/hobbit/hobbitclient.log I have lots of messages: ... 2007-12-20 09:04:00 Whoops ! bb failed to send message - Connection failed 2007-12-20 09:09:01 Could not connect to bbd at 10.1.2.89:1984 - Connection refused 2007-12-20 09:09:01 Whoops ! bb failed to send message - Connection failed 2007-12-20 09:14:02 Could not connect to bbd at 10.1.2.89:1984 - Connection refused 2007-12-20 09:14:02 Whoops ! bb failed to send message - Connection failed 2007-12-20 09:19:03 Could not connect to bbd at 10.1.2.89:1984 - Connection refused ... Looks like the client daemon did not start. What more do I need to add starting the server to start the client? Ideas? Mike
list Josh Luthman
Is the new server listening on 10.1.2.89:1984? Do a netstat -an|grep 1984 and paste what you see, please.
▸
On 12/20/07, Mike Eggleston <user-4ff7b7cae5b8@xymon.invalid> wrote:I recently moved the hobbit server from one box to another. I changed DNS entries, firewall entries, etc., and now today everything except one box is reporting. The new hobbit server itself is not report its own status. I start the hobbit server with: # su - hobbit $ ~/current/server/hobbit.sh start The daemon does start, things updating, etc., just not the server box itself. In /var/log/hobbit/hobbitclient.log I have lots of messages: ... 2007-12-20 09:04:00 Whoops ! bb failed to send message - Connection failed 2007-12-20 09:09:01 Could not connect to bbd at 10.1.2.89:1984 - Connection refused 2007-12-20 09:09:01 Whoops ! bb failed to send message - Connection failed 2007-12-20 09:14:02 Could not connect to bbd at 10.1.2.89:1984 - Connection refused 2007-12-20 09:14:02 Whoops ! bb failed to send message - Connection failed 2007-12-20 09:19:03 Could not connect to bbd at 10.1.2.89:1984 - Connection refused ... Looks like the client daemon did not start. What more do I need to add starting the server to start the client? Ideas? Mike
--
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
Those who don't understand UNIX are condemned to reinvent it, poorly.
--- Henry Spencer
list Mike Eggleston
On Thu, 20 Dec 2007, Josh Luthman might have said:
▸
Is the new server listening on 10.1.2.89:1984? Do a netstat -an|grep 1984 and paste what you see, please.
No, the new server is 10.1.2.84. So, maybe there are two parts to this. Something is sending to 10.1.2.89 (the old server) and something is not listening on 10.1.2.84 (the new server). Mike
list Chris Ss-is Morris
Check in ~/client/etc/hobbitclient.cfg to see what the IP address of your server is - I fell in this trap once.
▸
-----Original Message-----
From: Mike Eggleston [mailto:user-4ff7b7cae5b8@xymon.invalid]
Sent: 20 December 2007 16:45
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] moved server, the server itself is not reporting?
On Thu, 20 Dec 2007, Josh Luthman might have said:
Is the new server listening on 10.1.2.89:1984? Do a netstat -an|grep 1984 and paste what you see, please.
No, the new server is 10.1.2.84. So, maybe there are two parts to this. Something is sending to 10.1.2.89 (the old server) and something is not listening on 10.1.2.84 (the new server). Mike **********************************************************************
We would like to take this opportunity to wish all our customers, suppliers and colleagues a peaceful Christmas and a prosperous New Year.
We will not be sending corporate Christmas cards this year. Instead, we will be making a donation to our chosen corporate charity Macmillan Cancer Support.
**********************************************************************
This e-mail including any attachments is provided for general information purposes only and does not constitute advice except to the addressee if expressly stated in this email. For the avoidance of doubt the contents of this email and any attachments are subject to contract and are not intended to and will not constitute a legally binding contract or any part of a legally binding contract.
The information contained in this email and any attachments is confidential. It is intended only for the use of the intended recipient at the email address to which it has been addressed. If the reader of this message is not an intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution or copying of the message or associated attachments is strictly prohibited.
If you have received this e-mail in error, please notify user-36fa688b57c1@xymon.invalid and permanently delete the email and any attachments immediately from your system. You should not retain, copy or use this email or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you for your co-operation.
Neither RWE Systems UK Ltd nor any of the other companies in the RWE Group from whom this e-mail originates accept any responsibility for losses or damage as a result of any viruses and it is your responsibility to check attachments (if any) for viruses.
RWE Systems UK Ltd Registered office: Mistral, Westlea Campus, Chelmsford Road, Swindon, Wiltshire, SN5 7EZ. Registered in England and Wales: company number 6052966.
*******************************************
list Ralph Mitchell
▸
On Dec 20, 2007 10:44 AM, Mike Eggleston <user-4ff7b7cae5b8@xymon.invalid> wrote:
On Thu, 20 Dec 2007, Josh Luthman might have said:Is the new server listening on 10.1.2.89:1984? Do a netstat -an|grep 1984 and paste what you see, please.No, the new server is 10.1.2.84. So, maybe there are two parts to this. Something is sending to 10.1.2.89 (the old server) and something is not listening on 10.1.2.84 (the new server).
When you moved the hobbit server, did you change anything in it's config??
When you install Hobbit, it asks for the server's IP, and stashes it in
server/etc/hobbitserver.cfg as
BBSERVERIP=a.b.c.d
I guess that's so that it doesn't have to rely on DNS lookups working for it
to be able to send status.
Ralph Mitchell
list Mike Eggleston
On Thu, 20 Dec 2007, Morris, Chris (SS-IS) might have said:
▸
Check in ~/client/etc/hobbitclient.cfg to see what the IP address of your server is - I fell in this trap once.
That was it, thanks. Works great now. Mike
list Mike Eggleston
On Thu, 20 Dec 2007, Ralph Mitchell might have said:
▸
On Dec 20, 2007 10:44 AM, Mike Eggleston <user-4ff7b7cae5b8@xymon.invalid> wrote:On Thu, 20 Dec 2007, Josh Luthman might have said:Is the new server listening on 10.1.2.89:1984? Do a netstat -an|grep 1984 and paste what you see, please.No, the new server is 10.1.2.84. So, maybe there are two parts to this. Something is sending to 10.1.2.89 (the old server) and something is not listening on 10.1.2.84 (the new server).When you moved the hobbit server, did you change anything in it's config?? When you install Hobbit, it asks for the server's IP, and stashes it in server/etc/hobbitserver.cfg as BBSERVERIP=a.b.c.d I guess that's so that it doesn't have to rely on DNS lookups working for it to be able to send status.
I missed changing ~/current/client/etc/hobbitclient.cfg for the new IP address. All is working now, thanks to everyone. Mike