Setting MAX_*_LOG to 2147483648 or greater causes problems with logs. The problem may be due to int usage condor_util_lib/dprintf.c int MaxLog[D_NUMLEVELS+1] = { 0 }; upstream ticket: http://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=823
Created attachment 364029 [details] patch to fix log size Since 2GB true logfile is hard to generate, I tested rotation by using a 3.8 GB file that was just a cat of some isos and set max log to some number of bytes above 3.8 GB. It successfully adds log entries to the tail of the file and rotates the file when it reached the max log value.
Created attachment 364039 [details] small change to above
was pushed upstream fix is in 7.4.0-0.6
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Log files are no longer limited to 2GB size (527801)
The issue has been fixed verified on RHEL 4.8 / 5.4 i386 / x86_64 on packages: [root@mrg-qe-01 qpid_ptest_cluster_tsxtest]# rpm -qa | grep condor condor-remote-configuration-server-1.0-21.el5 condor-7.4.1-0.2.el5 condor-qmf-plugins-7.4.1-0.2.el5 condor-remote-configuration-1.0-21.el5 ->VERIFIED
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1,3 @@ +Grid Bug Fix + Log files are no longer limited to 2GB size (527801)
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,3 +1,3 @@ -Grid Bug Fix +Grid Enhancement -Log files are no longer limited to 2GB size (527801)+Log files are no longer limited to 2GB size
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1633.html