logrotate crashed with SIGSEGV

Bug #150715 reported by ValleyRat
6
Affects Status Importance Assigned to Milestone
logrotate (Ubuntu)
Invalid
Medium
Basilio Kublik

Bug Description

Binary package hint: logrotate

my syslog's seem to be getting large.
-rw-r----- 1 syslog adm 14604789 2007-10-08 14:20 syslog
-rw-r----- 1 syslog adm 72816275 2007-10-08 07:41 syslog.0
-rw-r----- 1 syslog adm 2201653 2007-10-07 07:16 syslog.1.gz
-rw-r----- 1 syslog adm 1995928 2007-10-06 07:20 syslog.2.gz
-rw-r----- 1 syslog adm 3018006 2007-10-05 06:45 syslog.3.gz
-rw-r----- 1 syslog adm 1870461 2007-10-04 09:13 syslog.4.gz
-rw-r----- 1 syslog adm 46883 2007-10-03 14:39 syslog.5.gz

my last command was
sudo logrotate -f syslog

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Oct 8 14:20:36 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/sbin/logrotate
NonfreeKernelModules: cdrom
Package: logrotate 3.7.1-3
PackageArchitecture: i386
ProcCmdline: logrotate -f /var/log/syslog.0
ProcCwd: /home/homer
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: logrotate
Stacktrace: #0 0x0804d27d in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 5735):
 #0 0x0804d27d in ?? ()
Title: logrotate crashed with SIGSEGV
Uname: Linux Duff 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 GNU/Linux
UserGroups:

Revision history for this message
ValleyRat (jamesfromburbank-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Thanks in advance

Changed in logrotate:
assignee: nobody → sourcercito
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in logrotate:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.