etherwake does not wake up machines
Bug #1396740 reported by
Daniel Bidwell
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Low
|
Unassigned | ||
maas (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
wakeonlan uses a tcp socket to wake up the server and can run as the maas user. ether_wake uses a udp socket to wake up the server and must run as root for it to work.
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in maas (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in maas: | |
status: | Invalid → Confirmed |
To post a comment you must log in.
The fix for this is ato add the following line to /etc/sudoers. d/99-maas- sudoers:
maas ALL= NOPASSWD: /usr/sbin/etherwake
and edit /etc/maas/ templates/ power/ether_ wake.template to change:
/usr/sbin/etherwake $mac_address
to:
sudo /usr/sbin/etherwake $mac_address
If the network that you need to send to is not eth0 then you need to use the following instead:
sudo /usr/sbin/etherwake -i ethx $mac_address