Suggestions for next hobbit release
Hello Henrik!
I have some suggestions for the next hobbit release:
- reports from hosts which are not known by the server should appear in the error report of the hobbitd. That would make it easier to find misconfiguration especially with the hostname the client sends.
- Succesfully sent messages should be logged to ensure that the client works correctly. It would be enough to log the last sent message for having a static small size of the logfile
- Bugfix: The Linux client does not stop the vmstat-process by stopping hobbitclient. See the shell-output below:
[root@*** /]# ps -ef | grep hobbit hobbit 28837 1 0 14:21 ? 00:00:00 /usr/local/hobbit/client/bin/hobbitlaunch --config=/usr/local/hobbit/client/etc/clientlaunch.cfg --log=/usr/local/hobbit/client/logs/clientlaunch.log --pidfile=/usr/local/hobbit/client/logs/clientlaunch.pid hobbit 28917 1 0 14:36 ? 00:00:00 sh -c vmstat 300 2 1>/usr/local/hobbit/client/tmp/hobbit_vmstat.28907 2>&1; mv /usr/local/hobbit/client/tmp/hobbit_vmstat.28907 /usr/local/hobbit/client/tmp/hobbit_vmstat hobbit 28919 28917 0 14:36 ? 00:00:00 vmstat 300 2 root 28938 27515 0 14:38 pts/2 00:00:00 grep hobbit [root@*** /]# /etc/init.d/hobbitc stop Hobbit client stopped [root@*** /]# ps -ef | grep hobbit hobbit 28917 1 0 14:36 ? 00:00:00 sh -c vmstat 300 2 1>/usr/local/hobbit/client/tmp/hobbit_vmstat.28907 2>&1; mv /usr/local/hobbit/client/tmp/hobbit_vmstat.28907 /usr/local/hobbit/client/tmp/hobbit_vmstat hobbit 28919 28917 0 14:36 ? 00:00:00 vmstat 300 2 root 28960 27515 0 14:38 pts/2 00:00:00 grep hobbit
I hope you think these features could be useful and implement them into the next release. Thanks and best regards Christian
Hi Christian,
On Thu, Sep 15, 2005 at 02:56:46PM +0200, Christian Schlüter wrote:
Hello Henrik!
I have some suggestions for the next hobbit release:
- reports from hosts which are not known by the server should appear in the error report of the hobbitd. That would make it easier to find misconfiguration especially with the hostname the client sends.
You can already do that - in your hobbitserver.cfg, change BBGHOSTS:
BBGHOSTS="1" # How to handle status messages from unknown hosts. # 0=accept message, 1=discard message, # 2=discard message and log the event
Set it to "2", and the "hobbitd" column will list the hostnames and IP's of all hosts whose messages were discarded.
- Succesfully sent messages should be logged to ensure that the client works correctly. It would be enough to log the last sent message for having a static small size of the logfile
Do you mean "logged on the client host", or "logged on the Hobbit server" ? And the entire message, or just that it was sent ? Big difference ...
On clients, the latest message is in ~hobbit/client/tmp/msg.txt . On the Hobbit server, I do not want to log incoming messages for performance reasons.
- Bugfix: The Linux client does not stop the vmstat-process by stopping hobbitclient.
Right ... the vmstat is started as with "nohup" to let it run independently of all the other client tasks (it's the only one that takes a long time). So this is a bit harder to do than it seems - hobbitlaunch which is the only other job running doesn't know the process-id of the vmstat process.
Henrik
Christian Schlüter wrote:
- Bugfix: The Linux client does not stop the vmstat-process by stopping hobbitclient. See the shell-output below
I can confirm this.
I also got script errors and weird client behavior from the 4.1.2 snapshots because of a missing hobbitclient-rhel3.sh script (which happens when you use "runclient.sh --os=rhel3"
Tom
participants (3)
-
henrik＠hswn.dk
-
kiki＠mpgabi2004.de
-
tomg＠mcclatchyinteractive.com