ok, I just tried your command below though I would have never guess 
that's the filename the --db switch would want.  Anyhow, I'm doing 
another install while doing monitortk on one terminal and a tail -f of 
si_monitor.log.  I see records showing up in the log and nothing coming 
out of monitortk.  Is monitortk supposed to be doing graphics?   The 
reason  ask is because I'm not running X!

Ahh!  Case Solved!

I just started an X server and exported the display to my laptop and NOW 
I'm seeing something.  Very cool, but I'm curious as to why I did't get 
any "can't open display" errors from the script.  I have perl scripts 
that use TK and I thought they always gave me that error but when I went 
to try and generate it so I could send a sample, it didn't!  Now I'm 
confused because I know that at least under some circumstances that 
occurs.  btw - is it a valid assumption that everyone will always have 
an X display running?  Would it be a royal pain to support a non-X 
mode?  In any event, if someone could figure out how to tell if there is 
an X server running and generate an error if one isn't, that could save 
a lot of time for everyone.   I suppose at the very least in the 
Troubleshooting section one could enter the problem that monitortk isn't 
generating output and the recommended solution is to see if X is 
running.  Also, is that -db switch needed?

-mark

Bernard Li wrote:

>What happens if you run:
> 
># si_monitortk --db /var/lib/systemimager/clients.xml
> 
>?
> 
>Anyways ping me on IRC next time you're around.
> 
>Cheers,
> 
>Bernard
>
>________________________________
>
>From: Mark Seger [mailto:[EMAIL PROTECTED]
>Sent: Wed 02/08/2006 17:29
>To: Bernard Li
>Cc: sisuite-devel@lists.sourceforge.net; Andrea Righi
>Subject: Re: [Sisuite-devel] Atomic write in si_monitor
>
>
>
>yes, I run si_monitortk and see nothing.  I do see data in
>/var/log/systemimager/si_monitor.log so I know it's arriving at the
>image server though.  I'm certainly willing to spend some time trying to
>track this down, perhaps on chat, but right now we're in a heat wave and
>I'm hiding in the basement only occasionally checking email.
>-mark
>
>Bernard Li wrote:
>
>  
>
>>And you get nothing when you run the si_monitortk widget?
>>
>>Note this is _not_ si_monitor, this is a Tk widget:
>>
>># which si_monitortk
>>/usr/sbin/si_monitortk
>>
>>According the file, your nodes are currently rsyncing overrides, which
>>is close to completion...
>>
>>Cheers,
>>
>>Bernard
>>
>>
>>
>>    
>>
>>>-----Original Message-----
>>>From: Mark Seger [mailto:[EMAIL PROTECTED]
>>>Sent: Wednesday, August 02, 2006 16:22
>>>To: Bernard Li
>>>Cc: sisuite-devel@lists.sourceforge.net; Andrea Righi
>>>Subject: Re: [Sisuite-devel] Atomic write in si_monitor
>>>
>>><opt>
>>> <client tmpfs="1%" cpu="AMD Opteron (tm) Processor 848
>>>(2197.163 MHz)"
>>>status="101" ip="192.168.253.211" time="3" name="00.0F.20.FC.B4.7F"
>>>ncpus="1" first_timestamp="1153502356" host="sandbox211"
>>>os="rhel4-U3-dl585" timestamp="1153662846"
>>>kernel="2.6.16-boel_v3.7.3"
>>>speed="0" mem="6974" log="rsync -av --numeric-ids
>>>192.168.253.223\x3a\x3aoverrides/dl585-2disk/ /a/" />
>>> <client tmpfs="1%" cpu="Dual Core AMD Opteron(tm) Processor 275
>>>(2210.193 MHz)" status="102" time="3" ip="192.168.253.174"
>>>name="00.14.C2.54.C5.A1" first_timestamp="1154548378" ncpus="1"
>>>os="rhel4-U2-dl145" host="sandbox174" timestamp="1154551040"
>>>kernel="2.6.16-boel_v3.7.3" speed="0" log="Imaging completed"
>>>mem="3950" />
>>></opt>
>>>-mark
>>>
>>>Bernard Li wrote:
>>>
>>>  
>>>
>>>      
>>>
>>>>So what is in your /var/lib/systemimager/clients.xml file?
>>>>
>>>>Cheers,
>>>>
>>>>Bernard
>>>>
>>>>
>>>>-----Original Message-----
>>>>From: Mark Seger [mailto:[EMAIL PROTECTED]
>>>>Sent: Wed 02/08/2006 13:34
>>>>To: Bernard Li
>>>>Cc: sisuite-devel@lists.sourceforge.net; Andrea Righi
>>>>Subject: Re: [Sisuite-devel] Atomic write in si_monitor
>>>>
>>>>Actually it's all coming back to me.  I've done exactly what you
>>>>described and am getting no output from monitortk.  It was
>>>>    
>>>>
>>>>        
>>>>
>>>at this point
>>>  
>>>
>>>      
>>>
>>>>last week that I ran my own monitor and verified data was getting to
>>>>this system.  I had also earlier verified data was getting into
>>>>/var/log/systemimager/si_monitor.log so clearly the problem is how
>>>>monitortk is [not] picking up the data to display.
>>>>-mark
>>>>
>>>>Bernard Li wrote:
>>>>
>>>>
>>>>
>>>>    
>>>>
>>>>        
>>>>
>>>>>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

Reply via email to