m.roth@5-cent.us wrote:
I hadn't paid attention when one or two folks recently posted this, 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?
Following myself up, 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