FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > CentOS > CentOS

 
 
LinkBack Thread Tools
 
Old 05-31-2012, 06:22 PM
 
Default Add another one: the same sealert problem

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?

mark

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 05-31-2012, 06:25 PM
 
Default Add another one: the same sealert problem

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

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 05-31-2012, 06:37 PM
 
Default Add another one: the same sealert problem

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@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/selinux
 
Old 05-31-2012, 06:43 PM
Daniel J Walsh
 
Default Add another one: the same sealert problem

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

On 05/31/2012 02:37 PM, m.roth@5-cent.us 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@lists.fedoraproject.org
> 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@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/selinux
 
Old 05-31-2012, 09:22 PM
 
Default Add another one: the same sealert problem

Well, this is getting more and more unpleasant. Turned out my manager and
the other admin were also working on this. One of the times they restarted
*something*, or maybe my reinstall, took care of the first problem.

Now, however, we're seeing a ton of exceptions... and what's struck me is
that I'm *not* getting the normal output from sealert. For example,
sealert -v -l 42f9d4f6-6327-4030-b927-d17ab9f4f0d6
2012-05-31 16:52:13,387 [plugin.INFO] importing
/usr/share/setroubleshoot/plugins/__init__ as plugins
SELinux is preventing /bin/chmod from using the fowner capability.

I used the -v to try to get more; I'm not seeing the screenful that
usually has more useful info. Could something have been screwed up with
selinux, in some way? I know that the other admin installed something, but
that was via a ruby-on-rails utility, and shouldn't have looked at
anything, much less modified anything....

mark



_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 05-31-2012, 09:22 PM
 
Default Add another one: the same sealert problem

Well, this is getting more and more unpleasant. Turned out my manager and
the other admin were also working on this. One of the times they restarted
*something*, or maybe my reinstall, took care of the first problem.

Now, however, we're seeing a ton of exceptions... and what's struck me is
that I'm *not* getting the normal output from sealert. For example,
sealert -v -l 42f9d4f6-6327-4030-b927-d17ab9f4f0d6
2012-05-31 16:52:13,387 [plugin.INFO] importing
/usr/share/setroubleshoot/plugins/__init__ as plugins
SELinux is preventing /bin/chmod from using the fowner capability.

I used the -v to try to get more; I'm not seeing the screenful that
usually has more useful info. Could something have been screwed up with
selinux, in some way? I know that the other admin installed something, but
that was via a ruby-on-rails utility, and shouldn't have looked at
anything, much less modified anything....

mark



_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 

Thread Tools




All times are GMT. The time now is 07:37 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org