← Back to team overview

touch-packages team mailing list archive

[Bug 1412719] Re: wait-for-state restarts whoopsie every 30sec

 

The second part of the patch proposed to upstart's wait-for-state job is
reasonable, but has nothing to do with the behavior shown here.  And the
first part of the patch is wrong.  It's not appropriate to change the
default wait-for-state behavior that other packages are relying on.

/etc/init/whoopsie.conf has:

    status network-manager >/dev/null 2>&1 && start wait-for-state
WAITER=whoopsie WAIT_FOR=network-manager GOAL=start || :

- 'GOAL' is incorrect; the variable name is 'TARGET_GOAL', but start is the default so this is a cosmetic issue.
- because network-manager runs a service, WAIT_STATE=running needs to be specified here.
- changing any of this will not cause whoopsie to stop respawning.  All of the wait-for-state handling happens in a *pre-start* script which has been written to ignore any failure from wait-for-state.  The logs in this bug clearly show that there is a main process which is exiting.

[14103.317598] init: whoopsie main process ended, respawning

This means that whoopsie itself is exiting for some reason and then
being respawned.  wait-for-state is in no way causing whoopsie to be
restarted; the only thing wait-for-state is doing is causing enough of a
delay in the pre-start that the respawn limit is never hit, causing this
to loop indefinitely.  But the real issue is whatever is causing
whoopsie to exit in the first place.


** Changed in: upstart (Ubuntu)
   Importance: High => Wishlist

** Also affects: whoopsie (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: whoopsie (Ubuntu)
       Status: New => Triaged

** Changed in: whoopsie (Ubuntu)
     Assignee: (unassigned) => Didier Roche (didrocks)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1412719

Title:
  wait-for-state restarts whoopsie every 30sec

Status in One Hundred Papercuts:
  Confirmed
Status in Upstart:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed
Status in whoopsie package in Ubuntu:
  Triaged

Bug description:
  wait-for-state is restarting whoopsie every 30sec:

  [14103.317598] init: whoopsie main process ended, respawning
  [14133.330315] init: wait-for-state (whoopsienetwork-manager) main process (10221) terminated with status 100
  [14133.396185] init: whoopsie main process (10227) terminated with status 1
  [14133.396205] init: whoopsie main process ended, respawning
  [14163.409765] init: wait-for-state (whoopsienetwork-manager) main process (10231) terminated with status 100
  [14163.468346] init: whoopsie main process (10237) terminated with status 1
  [14163.468366] init: whoopsie main process ended, respawning
  [14193.485204] init: wait-for-state (whoopsienetwork-manager) main process (10241) terminated with status 100
  [14193.560511] init: whoopsie main process (10249) terminated with status 1
  [14193.560531] init: whoopsie main process ended, respawning

  
  The problem in wait-for-state.conf is this line:
  status $WAIT_FOR | grep -q "$TARGET_GOAL/$WAIT_STATE" && exit 0

  TARGET_GOAL is either "start" or "stop".
  WAIT_STATE by default is "started", but there is no job status like "start/started".

  so WAIT_STATE needs to be something like "running" (or "waiting" for
  goal of "stop").

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: upstart 1.13.2-0ubuntu6
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 20 20:59:02 2015
  InstallationDate: Installed on 2014-09-03 (139 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140902)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic root=UUID=93e046a8-7604-4f60-a5f8-b3be22f948aa ro quiet splash vt.handoff=7
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemVersion: init (upstart 1.13.2)
  modified.conffile..etc.init.wait.for.state.conf: [modified]
  mtime.conffile..etc.init.wait.for.state.conf: 2015-01-20T20:02:17.598668

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1412719/+subscriptions


References