Description of problem: Logrotate segfaults when run. Version-Release number of selected component (if applicable): logrotate-3.7.4-7 How reproducible: Every time Steps to Reproduce: 1. /usr/sbin/logrotate /etc/logrotate.conf Actual results: Logrotate crashes. Expected results: Logrotate should rotate logs Additional info: This happen with any file in /etc/logrotate.d: gdb /usr/sbin/logrotate GNU gdb Red Hat Linux (6.5-14.fc7rh) Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run /etc/logrotate.conf Starting program: /usr/sbin/logrotate /etc/logrotate.conf Program received signal SIGSEGV, Segmentation fault. 0x0804df86 in readConfigFile (configFile=0x84bd720 "httpd", defConfig=0xbfbe2658, logsPtr=0xbfbe2858, numLogsPtr=0xbfbe2860) at config.c:1042 1042 if (!strcmp((*logsPtr)[j].files[k],
I can't reproduce it. :-( Could you install debuginfo package and run it in valgrind.
Created attachment 140758 [details] valgrind output Valgrind output attached. This has been happening for quite some time prior to FC6 - I had just hoped that FC6 would fix it.
Created attachment 140759 [details] GDB output, showing back trace and a couple of variable values. If there's anything else I can show, let me know
I need to reproduce it on same configuration as you have. Send me your logrotate configuration, please. #tar cvzf logConfig.tgz /etc/logrotate.d /etc/logrotate.conf
Created attachment 140764 [details] logrotate config files Per request, here are the config files
I still can't reproduce it. Send me #ll -R /var/log/ output.
Created attachment 140775 [details] ll -l /var/log output Per request, var log output
I can't reproduce it. Does it happend on clean FC6 installation?
I'm not sure I understand - do you mean "A clean *update* from the FC6 release disk onto the machine with the other files intact", or do you really mean "a clean install from zero, preserving no data"? If the latter, then I doubt very much it is happening since this bug would be being flooded with "Me Too"'s. I know *something* is screwy with this machine, as my other FC6 machine is not showing this symptom - I just am at a loss to determine what would have gone wrong. I'll see if I can step through with the debugger and see where things go wrong.
I meant clean installation from zero.
Somehow the executable was corrupted, and that fact was not being detected.