logresolvemerge.pl does not reap its children

Bug #542062 reported by Chris Jones
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AWStats
Unknown
Unknown
awstats (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: awstats

It seems that logresolvemerge.pl forks gzip for each of the zipped logfiles it's reading, but does not reap them when they have finished, leading to as many zombie processes as there were log files.

While this is not directly harmful, it does make system monitoring trickier.

Revision history for this message
Chuck Short (zulcss) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

Changed in awstats (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Chris Jones (cmsj) wrote :

Chuck: It's completely reproducible, you just need to run an awstats job:

a) on a busy website's logs
b) using logresolvemerge.pl to bring together the logs from multiple hosts, e.g. LogFile="/usr/share/doc/awstats/examples/logresolvemerge.pl /path/to/server1/access.log* /path/to/server2/access.log* |"

What seems to happen is that the gzip processes used to unpack the logs and feed into logresolvemerge.pl exit, but are not acknowledged while awstats.pl works, so they are technically zombies.

Changed in awstats (Ubuntu):
status: Incomplete → New
Revision history for this message
Chuck Short (zulcss) wrote :

Thanks for the info Chris.

chuck

Changed in awstats (Ubuntu):
status: New → Triaged
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.