On Tue, Dec 1, 2009 at 1:21 PM, Andy Speagle <[email protected]> wrote:
Hi all...I've had a problem rear its ugly head today.. and I'm loathe to explain it. Essentially, nearly anything I do in the WebUI times out. I've tracked it to a database issue. It seems that I'm running into table contention because anything I try fires up two queries... one SELECT and one UPDATE... the offensive one I believe is the UPDATE.. which is: update PXTSessions set value=:1, web_user_id=:2, expires=:3 where id=:4
PXTSessions is the way the perl webui handles logged in sessions. It is shared with the java webui as well. If you login with no cookies, we will create a new entry, each request updates the table to keep the expires date updated. If your login times out, but we get presented with the same cookie value, we simply update the record again to re-establish the session (if the row exists). So the update above is quite normal. Are you seeing an error?
Can anyone speak to this issue? I don't see anything in the archives regarding this. What I think happened is this: I have some automated jobs that run via cron on the Spacewalk server as the "admin" user... while one of those was running, I logged into the WebUI as the same user... I suspect that somehow these logins were in contention for session info...
Are these cron jobs using the API? or are they screen scraping the webui? In theory, you should be able to login as many times as you want with the same user from different locations. It shouldn't affect anything. Are all the jobs presenting the same cookie? That would cause them all to use the same sessions which would probably cause some bizarre issues. Is there an error log in either /var/log/tomcat5/catalina.out or /var/log/httpd/error_log? Sincerely, jesus
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
