[Bug 1015223] Re: cloud-init-nonet main process killed by TERM signal
Clint Byrum
clint at fewbar.com
Tue Jun 19 21:28:42 UTC 2012
I'm adding an upstart task. I'm wondering if its even valid for upstart
to log these at the default log priority. Perhaps they should be dropped
to 'info' level. Killing a process as part of stopping the job is a
perfectly normal situation and doesn't really seem to warrant logs. The
only time I think it might be useful is when debugging issues with boot
ordering, which would seem to be a good time to lower log priority to
info anyway.
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1015223
Title:
cloud-init-nonet main process killed by TERM signal
Status in “cloud-init” package in Ubuntu:
Triaged
Status in “upstart” package in Ubuntu:
New
Bug description:
it has been reported in maas (and i think i've seen it other places) that the console may include:
init: cloud-init-nonet main process (307) killed by TERM signal
This message is scary to users, even though it is not fatal or even an
indication of a problem.
It occurs because the cloud-init-nonet's purpose in life is to block
the running of cloud-init until the network devices are up. when
upstart recognizes that 'static-network-up' it kills cloud-init-nonet,
which allows cloud-init to start.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: cloud-init 0.6.3-0ubuntu1
ProcVersionSignature: User Name 3.2.0-25.40-virtual 3.2.18
Uname: Linux 3.2.0-25-virtual x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Tue Jun 19 17:41:24 2012
Ec2AMI: ami-b2288bdb
Ec2AMIManifest: ubuntu-us-east-1/images-testing/ubuntu-precise-daily-amd64-server-20120616.manifest.xml
Ec2AvailabilityZone: us-east-1c
Ec2InstanceType: m1.small
Ec2Kernel: aki-825ea7eb
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
TERM=screen-bce
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1015223/+subscriptions
More information about the foundations-bugs
mailing list