SystemImager® v4.0.2 Manual | ||
---|---|---|
<<< Previous | Monitoring clients installation with SystemImager | Next >>> |
If you don't see the clients in the monitoring interface when they boot-up check the following issues:
Do you have a firewall in your image server that filter the port 8181? The clients use that port to contact the image server.
Try to use the IP address of the monitor server instead of the hostname.
Are you sure the clients are using the correct boot parameters? (remember that you can check the parameters directly from the clients if you have the access to the real console looking in /proc/cmdline)
Try to increase the verbosity of the si_monitor log changing the value LOGLEVEL=2 into LOGLEVEL=3 in /etc/init.d/systemimager-server-monitord and restart the monitor daemon (/etc/init.d/systemimager-server-monitord restart); all the logs are stored in /var/log/systemimager/si_monitor.log).
Clients can be monitored also if an X server is not available, for example if you're connected remotely via ssh on the image server and you've not enabled the X11 forwarding. In this case simply look at the file /var/lib/systemimager/clients.xml. It's an XML, but the clients and the attribute names are quite nmemonic. You can periodically cat the file or write your own console monitoring scripts. If you wrote a nice ncurses or a console interface feel free to post the patch to the sisuite-devel list.
<<< Previous | Home | Next >>> |
Enabling clients to send monitoring data | Up | HOWTO Distribute configuration file across a SystemImager cluster |