[Spacewalk-list] Internal 500 errors generated by yum and somerhn_check procedures

[Czerak, Jason]

Interesting observation today. I came across bug 483156, it was closed
as not a bug. However, it's the exact same problem I'm having.

I enabled debug=5, and bounced the entire set of services. And the error
Is now gone again. Why is this? Since the error is around logging of the
problem, I think it may be related.

After a few guest kickstarts, I reset things, removed the debug=5 line
and now the issues is no longer present!

There were no new packages uploaded short of the failed attempts at
getting VMwareTools uploaded.

There were no configuration file changes short of the debug =5.

My guess here is that a combination of itmes in the DB is tripping these
errors. The DB  only component with constant change. 

I'm going to start importing other systems into spacewalk today. So
we'll see lots of change other then the two basic sandbox vm's being
re-installed over and over.





-----Original Message-----
From: spacewalk-list-bounces at redhat.com
[mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Czerak, Jason
Sent: Monday, June 01, 2009 2:08 PM
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Internal 500 errors generated by yum and
somerhn_check procedures

http://pastebin.com/m491d9482

For some reason, these errors stopped last week with an upgrade to
tomcat.  This morning, just finishing up some final testing on my KS and
configuration channels, they started to pop up again. Now I can't even
get a clean install done.

I'm open to a webex since It's rather repeatable, somewhat if developers
are interested in digging.

--
Jason



_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list