Description of problem: In /var/log/tomcat5/catalina.out the following massages are logged: 2010-03-16 17:03:59,965 [TP-Processor2] WARN com.redhat.rhn.frontend.servlets.LocalizedEnvironmentFilter - timezone still null In only five days, this message is logged 24001 times, which makes the log increase in size very fast: # grep "timezone still null" /var/log/tomcat5/catalina.out | wc -l 24001 This is probably caused by not finding a specific timezone in db: spacewalk-java-0.5.44/code/src/com/redhat/rhn/domain/user/UserFactory.java: === snip === public static RhnTimeZone getTimeZone(String olsonName) { Session session = null; try { session = HibernateFactory.getSession(); return (RhnTimeZone) session .getNamedQuery("RhnTimeZone.loadTimeZoneByOlsonName") .setString("ton", olsonName) //Retrieve from cache if there .setCacheable(true) .uniqueResult(); === snip === the codepath to the above code is: spacewalk-java-0.5.44/code/src/com/redhat/rhn/frontend/servlets/LocalizedEnvironmentFilter.java:setTimeZone() -> UserManager.getTimeZone() Version-Release number of selected component (if applicable): spacewalk-java-0.5.44-69.el5sat How reproducible: not for all, but specific timezones set in /etc/sysconfig/clock e.g. "Europe/Prague" Steps to Reproduce: 1. set the specific e.g. "Europe/Prague" in /etc/sysconfig/clock 2. try to login through webui, this will produce the messages Actual results: a lot of the same messages in /var/log/tomcat5/catalina.out: 2010-03-16 17:03:59,965 [TP-Processor2] WARN com.redhat.rhn.frontend.servlets.LocalizedEnvironmentFilter - timezone still null Expected results: it shouldn't print the messages so often Additional info: This has been already fixed, but not yet in the current/stable spacewalk: https://fedorahosted.org/spacewalk/changeset/e741830fc233b790690f5ded01bf47fb10192305#file0
Hey martin, Actually that component is correct. Also, this was fixed in spacewalk in commit: e741830fc233b790690f5ded01bf47fb10192305 We just need to backport it. Moving to modified and aligning to sat531-triage for possible errata inclusion. -Justin
The 5.4.0 RHN Satellite and RHN Proxy release has occurred. This issue has been resolved with this release. RHEA-2010:0801 - RHN Satellite Server 5.4.0 Upgrade https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10332 RHEA-2010:0803 - RHN Tools enhancement update https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10333 RHEA-2010:0802 - RHN Proxy Server 5.4.0 bug fix update https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10334 RHEA-2010:0800 - RHN Satellite Server 5.4.0 https://rhn.redhat.com/rhn/errata/details/Details.do?eid=10335 Docs are available: http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/index.html Regards, Clifford