Re: Add another one: the same sealert problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/31/2012 02:37 PM, m.roth@xxxxxxxxx wrote:
> I hadn't paid attention when one or two folks recently posted this (that 
> may have been on the CentOS list), but it's hit us, also: $ sealert -l
> d1655210-f43c-4737-98dc-86b6aac82bb6 Entity: line 53: parser error : Input
> is not proper UTF-8, indicate encoding ! Bytes: 0x99 0x3C 0x2F 0x74 
> <tpath>`</tpath> ^ failed to connect to server: xmlParseDoc() failed
> 
> I tried reinstalling sealert-server, but no joy. I can't really reboot this
> server on a blind hope that doing so would fix it. Anyone have a clue for a
> way to solve this?
> 
> Here's the report from the abrt full crash report: 
> analyze.py:426:lookup_signature:ProgramError: [Errno 1001] signature not 
> found
> 
> Traceback (most recent call last): File
> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 401,
> in auto_save_callback self.save() File
> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 377,
> in save self.prune() File
> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 340,
> in prune self.delete_signature(sig, prune=True) File
> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 471,
> in delete_signature siginfo = self.lookup_signature(sig) File
> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 426,
> in lookup_signature raise ProgramError(ERR_NO_SIGNATURE_MATCH) 
> ProgramError: [Errno 1001] signature not found
> 
> Local variables in innermost frame: matches: [] siginfo: None self:
> <setroubleshoot.analyze.SETroubleshootDatabase object at 0x1de8350> sig:
> <setroubleshoot.signature.SEFaultSignature object at 0x6386950>
> 
> What signature is it looking for, and where?
> 
> mark
> 
> 
> 
> -- selinux mailing list selinux@xxxxxxxxxxxxxxxxxxxxxxx 
> https://admin.fedoraproject.org/mailman/listinfo/selinux
Best to make sure the setroubleshootd is not running.

Then go and edit the xml.

and remove the `

vi /var/lib/setroubleshoot/setroubleshoot_database.xml

Do you have the AVC that created that content.  I would like see how it got
into the database.  I would really like to get rid of the XML database
altogher but maybe in F18 or 19


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/Hu9QACgkQrlYvE4MpobMeowCfX/WU6zhlTcSKndpdAB5+NK3N
qEMAoNPLm5sxmIkqcfQMidn99IIWrYSz
=369T
-----END PGP SIGNATURE-----
--
selinux mailing list
selinux@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/selinux



[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux