A couple other things:
I read this item to check from the wiki page:
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/)
But the page doesn't mention what the correct boot parameters are
though. I remember something like "MONITOR_SERVER=xyz" or something maybe?
http://wiki.systemimager.org/index.php/Monitoring
Also, the page above seems to have gotten infected with paragraphs of
spam inserted randomly in it. Might be worth checking out.
Jeremy
On 9/7/2010 4:08 PM, Jeremy Enos wrote:
I'm trying to figure out why si_monitortk isn't showing me anything.
The clients.xml file is empty. The si_monitor.log file is empty (on log
level 3, debug). Port 8181 is open and accessible from the clients.
I can't seem to find out what writes to 8181 on the clients at various
boot and build stages to try to figure out what's wrong. Any hints?
I'm using si version 4.1.7.
thx-
Jeremy
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
