Can anyone tell me how to make the postgresql code in the xmlrpc engine not spew all over my httpd error log? In less than 1 week I have in excess of 500MB of stuff like this:
Execute operation completed in 0.0001 seconds fetchall operation completed in 0.0000 seconds SELECT tag_id FROM group_config WHERE create_event > 4160 OR revoke_event > 4160
Execute operation completed in 0.0002 seconds fetchall operation completed in 0.0000 seconds
SELECT user_id,authtype,expired,start_time,update_time,master,exclusive,callnum FROM sessions WHERE id = 7475 AND key = '3-GvtCW6UIMQ17LbWlnlJ' AND hostip = '172.31.0.1' FOR UPDATE
Execute operation completed in 0.0004 seconds fetchone operation completed in 0.0001 seconds SELECT name,status,usertype FROM users WHERE id=3 Execute operation completed in 0.0002 seconds fetchone operation completed in 0.0000 seconds UPDATE sessions SET update_time=NOW() WHERE id = 7475 Execute operation completed in 0.0002 seconds UPDATE sessions SET callnum=158074 WHERE id = 7475 Execute operation completed in 0.0002 seconds SELECT id, name, perm_id, arches, locked FROM tag_config JOIN tag ON tag_config.tag_id = tag.id WHERE tag_config.active = TRUE AND tag.name = 'dist-F9-SCM-build' Execute operation completed in 0.0004 seconds fetchall operation completed in 0.0000 seconds
SELECT user_id,authtype,expired,start_time,update_time,master,exclusive,callnum FROM sessions WHERE id = 7475 AND key = '3-GvtCW6UIMQ17LbWlnlJ' AND hostip = '172.31.0.1' FOR UPDATE
Execute operation completed in 0.0004 seconds fetchone operation completed in 0.0001 seconds SELECT name,status,usertype FROM users WHERE id=3 Execute operation completed in 0.0002 seconds fetchone operation completed in 0.0000 seconds UPDATE sessions SET update_time=NOW() WHERE id = 7475 Execute operation completed in 0.0002 seconds UPDATE sessions SET callnum=158075 WHERE id = 7475 Execute operation completed in 0.0002 seconds SELECT id, name, perm_id, arches, locked FROM tag_config JOIN tag ON tag_config.tag_id = tag.id WHERE tag_config.active = TRUE AND tag.name = 'dist-F10-SCM-build' Execute operation completed in 0.0004 seconds fetchall operation completed in 0.0000 seconds
On Thu, 2008-08-07 at 12:06 -0400, Mike McLean wrote:
Doug Ledford wrote:
Can anyone tell me how to make the postgresql code in the xmlrpc engine not spew all over my httpd error log? In less than 1 week I have in excess of 500MB of stuff like this:
edit /etc/httpd/conf.d/kojihub.conf, ensure KojiDebug is not set
Yeah, did that already...no change.
Doug Ledford wrote:
On Thu, 2008-08-07 at 12:06 -0400, Mike McLean wrote:
Doug Ledford wrote:
Can anyone tell me how to make the postgresql code in the xmlrpc engine not spew all over my httpd error log? In less than 1 week I have in excess of 500MB of stuff like this:
edit /etc/httpd/conf.d/kojihub.conf, ensure KojiDebug is not set
Yeah, did that already...no change.
Is KojiDebug set to any value at all (e.g. 'no')? It appears that one part of the code may misinterpret a non-null value as enabled. A bug, to be sure, but in the meantime, best to make sure there is no uncommented 'KojiDebug' value of any sort.
On Thu, 2008-08-07 at 16:09 -0400, Mike McLean wrote:
Doug Ledford wrote:
On Thu, 2008-08-07 at 12:06 -0400, Mike McLean wrote:
Doug Ledford wrote:
Can anyone tell me how to make the postgresql code in the xmlrpc engine not spew all over my httpd error log? In less than 1 week I have in excess of 500MB of stuff like this:
edit /etc/httpd/conf.d/kojihub.conf, ensure KojiDebug is not set
Yeah, did that already...no change.
Is KojiDebug set to any value at all (e.g. 'no')? It appears that one part of the code may misinterpret a non-null value as enabled. A bug, to be sure, but in the meantime, best to make sure there is no uncommented 'KojiDebug' value of any sort.
Yeah, it's set to no....I'll comment it out and see if that helps.
On Thu, 2008-08-07 at 20:34 -0400, Doug Ledford wrote:
On Thu, 2008-08-07 at 16:09 -0400, Mike McLean wrote:
Doug Ledford wrote:
On Thu, 2008-08-07 at 12:06 -0400, Mike McLean wrote:
Doug Ledford wrote:
Can anyone tell me how to make the postgresql code in the xmlrpc engine not spew all over my httpd error log? In less than 1 week I have in excess of 500MB of stuff like this:
edit /etc/httpd/conf.d/kojihub.conf, ensure KojiDebug is not set
Yeah, did that already...no change.
Is KojiDebug set to any value at all (e.g. 'no')? It appears that one part of the code may misinterpret a non-null value as enabled. A bug, to be sure, but in the meantime, best to make sure there is no uncommented 'KojiDebug' value of any sort.
Yeah, it's set to no....I'll comment it out and see if that helps.
That appears to have worked.
buildsys@lists.fedoraproject.org