Bernard Li wrote:
> Dear all:
>
> I just noticed that the file /var/lib/systemimager/clients.xml's
> timestamp is updated constantly if systemimager-server-monitord is
> running even though there are no new data (i.e. no image process going
> on).
>
> I think it would be better to not update this file unless there is new
> information to write to the file.
>
> This way we can figure out the last activity (eg. when a server was
> last imaged) by looking at the last modification timestamp of that
> file.
>
Interesting point. The timestamp for a client is updated only when that client
performs a connection to the si_monitor daemon that runs on the image server.
If you look at the code:
while (accept(CLIENT, IN)) {
...
# Update the database.
update_db($other_host, $_);
...
}
This means that if a client has a recent timestamp (and if the state is not
"rebooting" or "REBOOTED") the network is working fine for that client.
OTOH if you see a client that is not able to finish the installation and the
timestamp is not so recent, maybe there're problems in the network connection
and you should check the cables, switches and so on...
So, I think that the approach to save the timestamp for each client connection
is useful to debug this kind of problem, maybe we could even make concrete this
thought and introduce the TIMED-OUT state, or something similar...
Opinions?
-Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
sisuite-devel mailing list
sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
