[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [hobbit] Solaris clients don't report
- To: "hobbit (at) hswn.dk" <hobbit (at) hswn.dk>
- Subject: RE: [hobbit] Solaris clients don't report
- From: "Everett, Vernon" <Vernon.Everett (at) woodside.com.au>
- Date: Sun, 2 Nov 2008 21:03:07 +0900
- Accept-language: en-US, en-AU
- Acceptlanguage: en-US, en-AU
- Thread-index: Ack83htYQlbsC8AgQH+Jr4idb07HEwABLAGw
- Thread-topic: [hobbit] Solaris clients don't report
And if those all turn up OK, have you checked tha basics?
Have you looked for the host names in the ghost client report?
Sometimes, if the host name is not as specified in the bb-hosts, From: T.J. Yang [mailto:tj_yang (at) hotmail.com]
Sent: Sunday, 2 November 2008 8:26 PM
To: hobbit (at) hswn.dk
Subject: Re: [hobbit] Solaris clients don't report
2. check if hobbit client procesess are running fine ?
ps -eaf |grep hobbit
bash-3.00# ps -eaf |grep hobbitc
hobbitc 634 1 0 Oct 31 ? 0:01 /opt/hobbitclient42/bin/hobbitlaunch --config=/etc/opt/moto/hobbitclient42
hobbitc 1753 1 0 05:20:09 ? 0:00 sh -c iostat -c 300 2 1>/var/opt/hobbitclient42/tmp/hobbit_iostatcpu.netin
hobbitc 1752 1751 0 05:20:09 ? 0:00 vmstat 300 2
hobbitc 1754 1753 0 05:20:09 ? 0:00 iostat -c 300 2
hobbitc 1751 1 0 05:20:09 ? 0:00 sh -c vmstat 300 2 1>/var/opt/hobbitclient42/tmp/hobbit_vmstat.netinstall.
hobbitc 1756 1755 0 05:20:09 ? 0:00 iostat -dxsrP 300 2
hobbitc 1755 1 0 05:20:09 ? 0:00 sh -c iostat -dxsrP 300 2 1>/var/opt/hobbitclient42/tmp/hobbit_iostatdisk.
bash-3.00#
3. check hobbitclient.cfg,following is an example sending hb message to two hb servers.
BBDISP="0.0.0.0" # IP address of the Hobbit server
BBDISPLAYS="192.168.1.3 192.168.1.2" # IP address of the Hobbit server
tj
From: Hanrahan, Kevin<mailto:Kevin.Hanrahan (at) elavon.com>
Sent: Saturday, November 01, 2008 9:03 PM
To: 'hobbit (at) hswn.dk'<mailto:'hobbit (at) hswn.dk'>
Subject: RE: [hobbit] Solaris clients don't report
there is not much there:
bash-3.00$ tail clientlaunch.log
2008-10-30 17:14:57 hobbitlaunch starting
2008-10-30 17:14:57 Loading tasklist configuration from /home/sysmon/client/etc/clientlaunch.cfg
the other log is completely empty...zero bytes
ideas?
From: T.J. Yang [mailto:tj_yang (at) hotmail.com]
Sent: Saturday, November 01, 2008 6:37 PM
To: hobbit (at) hswn.dk<mailto:hobbit (at) hswn.dk>
Subject: Re: [hobbit] Solaris clients don't report
please check your hobbit client log files.
bash-3.00# ls
clientlaunch.log hobbitclient.log
bash-3.00#
From: Hanrahan, Kevin<mailto:Kevin.Hanrahan (at) elavon.com>
Sent: Saturday, November 01, 2008 9:52 AM
To: 'hobbit (at) hswn.dk'<mailto:'hobbit (at) hswn.dk'>
Subject: [hobbit] Solaris clients don't report
Hi all,
I can't get any solaris clients to report to the Hobbit server. I build the clients on the servers like I have with the all my linux clients, but none seem to report. They are all running solaris 10. There isn't anything blocking port 1984 between the boxes. The only difference I see is that I am using "gmake" instead of "make" to build the client. Could that be the problem? Can anybody offer suggestions?
thanks
kh
----------------------------------------- Note: The information contained in this e-mail and in any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. The recipient should check this e-mail and any attachments for the presence of viruses. Sender accepts no liability for any damages caused by any virus transmitted by this e-mail. If you have received this e-mail in error, please notify us immediately by replying to the message and delete the e-mail from your computer. Elavon (formerly NOVA Information Systems)
NOTICE: This email and any attachments are confidential.
They may contain legally privileged information or
copyright material. You must not read, copy, use or
disclose them without authorisation. If you are not an
intended recipient, please contact us at once by return
email and then delete both messages and all attachments.