Powernap systemd setup is broken

Bug #1460712 reported by Ben on 2015-06-01
This bug affects 6 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
powernap (Ubuntu)
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)
mtime.conffile..etc.init.powernap.override: 2015-06-01T15:30:32.755206
mtime.conffile..etc.powernap.config: 2014-02-26T15:33:58.282474

Ben (f-ubunqu-k) wrote :
Launchpad Janitor (janitor) wrote :

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

Changed in powernap (Ubuntu):
status: New → Confirmed
Changed in powernap (Ubuntu):
importance: Undecided → High
no longer affects: powernap
Changed in hundredpapercuts:
importance: Undecided → High
status: New → Confirmed
zeke2135 (dlbrewe-2) wrote :

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
Martin Pitt (pitti) wrote :

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
Ben (f-ubunqu-k) wrote :

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 ?

Zak Kipling (zak-k) wrote :

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

The workaround described here seems to fix the problem though.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers