sealert and setroubleshoutd

[Eric Tanguy]

I have setroubleshoutd running as a service but i can't run sealert.
When i try to run it nothing happen so i tried to run it from root
command line with -v : 
Traceback (most recent call last):
  File "/usr/bin/sealert", line 440, in ?
    print s
NameError: name 's' is not defined

What's the problem ?
Thanks

Eric

[Eric Tanguy]

Le dimanche 19 novembre 2006 à 09:20 +0100, Tanguy Eric a écrit :
>  I have setroubleshoutd running as a service but i can't run
> sealert.
>  When i try to run it nothing happen so i tried to run it from root
>  command line with -v : 
>  Traceback (most recent call last):
>    File "/usr/bin/sealert", line 440, in ?
>      print s
>  NameError: name 's' is not defined
>  
>  What's the problem ?
>  Thanks
>  
>  Eric
>   
In fact, it seems i have the same problem in
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=214218 but this
seems not fixed yet.

Eric

[John Dennis]

On Sun, 2006-11-19 at 11:35 +0100, Tanguy Eric wrote:
>  Le dimanche 19 novembre 2006 à 09:20 +0100, Tanguy Eric a écrit :
>  > I have setroubleshoutd running as a service but i can't run sealert.
>  > When i try to run it nothing happen so i tried to run it from root
>  > command line with -v : 
>  > Traceback (most recent call last):
>  >   File "/usr/bin/sealert", line 440, in ?
>  >     print s
>  > NameError: name 's' is not defined
>  > 
>  > What's the problem ?
>  > Thanks
>  > 
>  > Eric
>  > 
>  
>  In fact, it seems i have the same problem in
>  http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=214218 but this
>  seems not fixed yet. 
We'll probably be putting a new package in rawhide at the end of today
or tomorrow which will fix these problems.

BTW, if you want verbose output to diagnose problems you can change the
logging configuration in the config file
(/etc/setroubleshoot/setroubleshoot.cfg). The daemon (setroubleshootd)
and the GUI component (sealert) each have their own logging section in
the config file, setroubleshootd_log, sealert_log respectively. There
are two values in each section you might want to change, the level value
defines what messages get emitted, you probably want 'debug' if you're
trying to track a problem down. Normally the logging goes to the log
files (/var/log/setroubleshoot/setroubleshoot.log and /tmp/sealert.log),
but if you set the 'console' flag to true what is being written to the
log file will also be echoed to the console. HTH, new package coming
soon...
-- 
John Dennis <jdennis(a)redhat.com&gt;
Red Hat Inc.

[Eric Tanguy]

Le lundi 20 novembre 2006 à 11:24 -0500, John Dennis a écrit :
>  On Sun, 2006-11-19 at 11:35 +0100, Tanguy Eric wrote: 
>  > Le dimanche 19 novembre 2006 à 09:20 +0100, Tanguy Eric a écrit :
>  > > I have setroubleshoutd running as a service but i can't run sealert.
>  > > When i try to run it nothing happen so i tried to run it from root
>  > > command line with -v : 
>  > > Traceback (most recent call last):
>  > >   File "/usr/bin/sealert", line 440, in ?
>  > >     print s
>  > > NameError: name 's' is not defined
>  > > 
>  > > What's the problem ?
>  > > Thanks
>  > > 
>  > > Eric
>  > > 
>  > 
>  > In fact, it seems i have the same problem in
>  > http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=214218 but this
>  > seems not fixed yet.
>  
>  We'll probably be putting a new package in rawhide at the end of today
>  or tomorrow which will fix these problems.
>  
>  BTW, if you want verbose output to diagnose problems you can change
>  the logging configuration in the config file
>  (/etc/setroubleshoot/setroubleshoot.cfg). The daemon (setroubleshootd)
>  and the GUI component (sealert) each have their own logging section in
>  the config file, setroubleshootd_log, sealert_log respectively. There
>  are two values in each section you might want to change, the level
>  value defines what messages get emitted, you probably want 'debug' if
>  you're trying to track a problem down. Normally the logging goes to
>  the log files (/var/log/setroubleshoot/setroubleshoot.log
>  and /tmp/sealert.log), but if you set the 'console' flag to true what
>  is being written to the log file will also be echoed to the console.
>  HTH, new package coming soon... 
Thanks for the answer John, but putting a new package in rawhide is good
for rawhide but useless for Fedora Core 6 users. Can you put also this
new package in updates-testing and after in updates ?
Eric