Ubuntu
powernap package

Powernap systemd setup is broken

Bug #1460712 reported by Ben on 2015-06-01

30

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	One Hundred Papercuts	Confirmed	High	Unassigned
	powernap (Ubuntu)	Triaged	High	Dustin Kirkland 

Bug Description

After upgrading my server to 15.04, I noticed that the powernap service was failing to start. To get it working, I had to make the following changes:

/lib/systemd/system/powernap.service :
Change 'network.service' on the Requires/After lines to 'network.target'

(n.b. no idea if this is correct, I am a systemd newbie, but systemd was complaining about the use of network.service)

/usr/share/powernap/powernap-ethtool :
Fix the path of ethtool - this file refers to /usr/sbin/ethtool but it exists in /sbin/ethtool on my server

After these changes, powernap now seems to start up correctly.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: powernap 2.21-0ubuntu1 [modified: lib/systemd/system/powernap.service usr/share/powernap/powernap-ethtool]
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Mon Jun 1 16:36:03 2015
InstallationDate: Installed on 2014-02-26 (460 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016)
PackageArchitecture: all
SourcePackage: powernap
UpgradeStatus: Upgraded to vivid on 2015-06-01 (0 days ago)
modified.conffile..etc.init.powernap.override:
mtime.conffile..etc.init.powernap.override: 2015-06-01T15:30:32.755206
mtime.conffile..etc.powernap.config: 2014-02-26T15:33:58.282474
upstart.powernap.override:

Tags:

Revision history for this message

Ben (f-ubunqu-k) wrote on 2015-06-01:

#1

Dependencies.txt Edit (3.3 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (8.8 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (112 bytes, text/plain; charset="utf-8")
modified.conffile..etc.powernap.config.txt Edit (7.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-07-04:

#2

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in powernap (Ubuntu):
status:	New → Confirmed

Alberto Salvia Novella (es20490446e) on 2015-07-07

Changed in powernap (Ubuntu):
importance:	Undecided → High
no longer affects:	powernap
Changed in hundredpapercuts:
importance:	Undecided → High
status:	New → Confirmed

Revision history for this message

zeke2135 (dlbrewe-2) wrote on 2015-11-03:

#3

In addition to the indicated changes to I had to add PIDFile=/var/run/powernap.pid to get it to run properly.

Robie Basak (racb) on 2015-11-05

tags:

added: systemd-boot

Revision history for this message

Martin Pitt (pitti) wrote on 2016-02-01:

#4

The two suggested changes make sense; please drop "Requires=network" completely, you only need the After=network.target.

But I can't get powernap to run at all in current xenial -- running "sudo /usr/sbin/powernapd" in a VM or a container immediately exits. It just writes the pid file and then exits with 0.

Changed in powernap (Ubuntu):
assignee:	nobody → Dustin Kirkland  (kirkland)
status:	Confirmed → Triaged

Revision history for this message

Ben (f-ubunqu-k) wrote on 2016-02-01:

#5

Martin, as you are running a later system, perhaps you are hitting bug 1497782 - https://bugs.launchpad.net/powernap/+bug/1497782

Do you see any errors in /var/log/powernap.err ?

Revision history for this message

Zak Kipling (zak-k) wrote on 2016-07-22:

#6

This affects me following an LTS upgrade from Trusty to Xenial.

The workaround described here seems to fix the problem though.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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