Hi Mark: You do not run si_monitor manually, there is an init script for starting it.
First of all, check the pid of running si_monitor process and kill it: # ps -ef | grep si_monitor Then start the monitord script: /etc/init.d/systemimager-server-monitord start si_monitortk is the Tk widget you will run to view the status. clients.xml will have information stored there once your clients talk to the monitord. Add the following to /tftpboot/pxelinux.cfg/default's APPEND line: MONITOR_SERVER=<IP_OF_IMAGESERVER> MONITOR_CONSOLE=yes or via si_mkautoinstallcd --append That should do the trick. Cheers, Bernard P.S. I thought Andrea already has this nicely documented but I couldn't find it in either wiki.sisuite.org nor wiki.systemimager.org. > -----Original Message----- > From: Mark Seger [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 02, 2006 13:06 > To: Bernard Li > Cc: sisuite-devel@lists.sourceforge.net; Andrea Righi > Subject: Re: [Sisuite-devel] Atomic write in si_monitor > > I went back to look at things and decided I have no idea how to run > si_monitor. -help doesn't tell me what's required, though I > suspect -db > may be? I guess I assumed you just run it and would > interactively see > the output from the clients. That what I'm doing with my monitoring > code. I do see a couple of entries in > /var/lib/systemimager/clients.xml, but only a couple. I > don't know if > this is right or wrong. > > When I try running si_monitor it tells me: > [EMAIL PROTECTED] sbin]# ./si_monitor -db /tmp/test > warning: log file was not specified: ignoring log level: 2. > > Then I tried: > ./si_monitor -db /tmp/test -log /tmp/log > which seemed to work but when I looked at /tmp/log all it had > in it was: > > [EMAIL PROTECTED] sbin]# cat /tmp/log > Wed Aug 2 20:02:31 2006: error: could not bind to port 8181 > : Address > already in use > > Is it a correct assumption on my part that once everything is > configured > I should be able to run si_monitor and see messages displayed on my > terminal as they occur on the client? If so, what is the > magic set of > switches that will do that? > > btw - I'll be happy to share my code but I'm not sure what it will do > that this doesn't already do, once I figure out how to use it. 8-) > > -mark > > Bernard Li wrote: > > >Hi Mark: > > > >If you have monitoring working, then client information will > be stored > >in /var/lib/systemimager/clients.xml. > > > >We should try to figure out how to get your si_monitor(tk) working. > >Also we would welcome your monitoring code to further enhance what we > >already have! > > > >Thanks, > > > >Bernard > > > > > > > >>-----Original Message----- > >>From: Mark Seger [mailto:[EMAIL PROTECTED] > >>Sent: Wednesday, August 02, 2006 11:07 > >>To: sisuite-devel@lists.sourceforge.net > >>Cc: Andrea Righi; Bernard Li > >>Subject: Re: [Sisuite-devel] Atomic write in si_monitor > >> > >>As andrea knows I never got the monitoring code to work at all. > >>However, I threw together some socket code I had lying around > >>and it was > >>very happy to receive data from the clients. I guess I'm not > >>sure what > >>people are talking about with respect to XML becuase I don't recall > >>seeing any coming from the client. > >>-mark > >> > >> > >> > >> > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sisuite-devel mailing list Sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
