Upstart configuration for aiccu does not track aiccu process correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
aiccu (Ubuntu) |
Fix Released
|
Medium
|
James Page |
Bug Description
I discovered this while debugging a race condition between the DHCP services and aiccu (they reside of the same server).
aiccu start forks 4 times - so upstart is not able to track it in any way.
This needs to be addressed by starting aiccu in the pre-start script and stopping it in the pre-stop script and dropping the script..end script section altogether.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: aiccu 20070115-
ProcVersionSign
Uname: Linux 3.2.0-20-generic x86_64
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Wed Mar 28 13:26:55 2012
InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Beta amd64 (20110413)
SourcePackage: aiccu
UpgradeStatus: Upgraded to precise on 2012-03-02 (25 days ago)
Related branches
Changed in aiccu (Ubuntu): | |
importance: | Undecided → Medium |
assignee: | nobody → James Page (james-page) |
status: | New → In Progress |
This bug was fixed in the package aiccu - 20070115- 14.1ubuntu2
--------------- 14.1ubuntu2) precise; urgency=low
aiccu (20070115-
* debian/ aiccu.upstart:
- Use pre-start, post-stop scripts to start and stop aiccu as upstart
cannot track aiccu in any meaningful way (LP: #967090).
- Check access to IPv6 endpoint before starting aiccu to avoid race
conditions with local DNS services (LP: #967095).
Thanks to Lars Düsing for this fix.
- Updated start on stanza to include local-filesystems.
- General tidy of upstart configuration including placing logfile in
/var/log and generating log entry timestamps.
-- James Page <email address hidden> Fri, 30 Mar 2012 12:50:10 +0100