Power Management - Scheduled WOL causes shutdown

Wayne Workman

Server

Version: 1.3.0 RC-10
OS: Fedora 21

Client

Version: 0.11.5
OS: Win10 x64 LTSB

Description

@Tom-Elliott
We’ve had two Power Management tasks scheduled for every computer forever, a picture of them is in here: https://forums.fogproject.org/topic/8402/power-management-rc-8-json-issue
This morning was my building’s first morning on RC-10. There was a WOL task scheduled for 7:30. When 7:30 came around, my computer wanted to shutdown! I clicked abort, here are the logs from that. Because of this, I’ve deleted all power management tasks from all computers because I didn’t want any more unexpected behavior.

------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 9/12/2016 7:27 AM Client-Info Client Version: 0.11.5
 9/12/2016 7:27 AM Client-Info Client OS:      Windows
 9/12/2016 7:27 AM Client-Info Server Version: 1.3.0-RC-10
 9/12/2016 7:27 AM Middleware::Response Success
------------------------------------------------------------------------------

 9/12/2016 7:27 AM Middleware::Communication URL: http://10.2.1.11/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 9/12/2016 7:27 AM Middleware::Response Success
 9/12/2016 7:27 AM Service Sleeping for 113 seconds
 9/12/2016 7:29 AM Middleware::Communication URL: http://10.2.1.11/fog/management/index.php?sub=requestClientInfo&mac=90:B1:1C:98:03:8C||00:00:00:00:00:00:00:E0&newService&json
 9/12/2016 7:29 AM Middleware::Response Success
 9/12/2016 7:29 AM Middleware::Communication URL: http://10.2.1.11/fog/service/getversion.php?clientver&newService&json
 9/12/2016 7:29 AM Middleware::Communication URL: http://10.2.1.11/fog/service/getversion.php?newService&json

 9/12/2016 7:29 AM Service Creating user agent cache
 9/12/2016 7:29 AM Middleware::Response Invalid time
 9/12/2016 7:29 AM Middleware::Response Success
 9/12/2016 7:29 AM Middleware::Response Module is disabled globally on the FOG server

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 9/12/2016 7:29 AM Client-Info Client Version: 0.11.5
 9/12/2016 7:29 AM Client-Info Client OS:      Windows
 9/12/2016 7:29 AM Client-Info Server Version: 1.3.0-RC-10
 9/12/2016 7:29 AM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------TaskReboot----------------------------------
------------------------------------------------------------------------------
 9/12/2016 7:29 AM Client-Info Client Version: 0.11.5
 9/12/2016 7:29 AM Client-Info Client OS:      Windows
 9/12/2016 7:29 AM Client-Info Server Version: 1.3.0-RC-10
 9/12/2016 7:29 AM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 9/12/2016 7:29 AM Client-Info Client Version: 0.11.5
 9/12/2016 7:29 AM Client-Info Client OS:      Windows
 9/12/2016 7:29 AM Client-Info Server Version: 1.3.0-RC-10
 9/12/2016 7:29 AM Middleware::Response Success
 9/12/2016 7:29 AM HostnameChanger Checking Hostname
 9/12/2016 7:29 AM HostnameChanger Hostname is correct
 9/12/2016 7:29 AM HostnameChanger Attempting to join domain
 9/12/2016 7:29 AM HostnameChanger Host is already joined to target domain
------------------------------------------------------------------------------


------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 9/12/2016 7:29 AM Client-Info Client Version: 0.11.5
 9/12/2016 7:29 AM Client-Info Client OS:      Windows
 9/12/2016 7:29 AM Client-Info Server Version: 1.3.0-RC-10
 9/12/2016 7:29 AM Middleware::Response No snapins
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------PrinterManager--------------------------------
------------------------------------------------------------------------------
 9/12/2016 7:29 AM Client-Info Client Version: 0.11.5
 9/12/2016 7:29 AM Client-Info Client OS:      Windows
 9/12/2016 7:29 AM Client-Info Server Version: 1.3.0-RC-10
 9/12/2016 7:29 AM Middleware::Response Success
 9/12/2016 7:29 AM PrinterManager Getting installed printers
 9/12/2016 7:29 AM PrinterManager Adding printers
 9/12/2016 7:29 AM PrinterManager SSD 1075 already exists
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------PowerManagement-------------------------------
------------------------------------------------------------------------------
 9/12/2016 7:29 AM Client-Info Client Version: 0.11.5
 9/12/2016 7:29 AM Client-Info Client OS:      Windows
 9/12/2016 7:29 AM Client-Info Server Version: 1.3.0-RC-10
 9/12/2016 7:29 AM Middleware::Response Success
 9/12/2016 7:29 AM PowerManagement Calculating tasks to unschedule
 9/12/2016 7:29 AM PowerManagement Calculating tasks to schedule
 9/12/2016 7:29 AM PowerManagement --> A wol at 30 7 * * 1-5 is already scheduled
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 9/12/2016 7:29 AM Client-Info Client Version: 0.11.5
 9/12/2016 7:29 AM Client-Info Client OS:      Windows
 9/12/2016 7:29 AM Client-Info Server Version: 1.3.0-RC-10
 9/12/2016 7:29 AM Middleware::Response Success
------------------------------------------------------------------------------

 9/12/2016 7:29 AM Middleware::Communication URL: http://10.2.1.11/fog/management/index.php?sub=requestClientInfo&configure&newService&json
 9/12/2016 7:29 AM Middleware::Response Success
 9/12/2016 7:29 AM Service Sleeping for 46 seconds
 9/12/2016 7:30 AM Power Creating shutdown command in 60 seconds
 9/12/2016 7:30 AM Bus {
  "self": true,
  "channel": "Power",
  "data": "{\r\n  \"action\": \"request\",\r\n  \"period\": 60,\r\n  \"options\": 1,\r\n  \"command\": \"/s /c \\\"FOG PowerManagement\\\" /t 0\",\r\n  \"message\": \"This computer needs to perform maintenance.\"\r\n}"
}
 9/12/2016 7:30 AM Bus Emmiting message on channel: Power
 9/12/2016 7:30 AM Middleware::Communication URL: http://10.2.1.11/fog/management/index.php?sub=requestClientInfo&mac=90:B1:1C:98:03:8C||00:00:00:00:00:00:00:E0&newService&json
 9/12/2016 7:30 AM Middleware::Response Success
 9/12/2016 7:30 AM Middleware::Communication URL: http://10.2.1.11/fog/service/getversion.php?clientver&newService&json
 9/12/2016 7:30 AM Middleware::Communication URL: http://10.2.1.11/fog/service/getversion.php?newService&json

 9/12/2016 7:30 AM Service Creating user agent cache
 9/12/2016 7:30 AM Middleware::Response Invalid time
 9/12/2016 7:30 AM Middleware::Response Success
 9/12/2016 7:30 AM Middleware::Response Module is disabled globally on the FOG server
 9/12/2016 7:30 AM Service Power operation being requested, checking back in 30 seconds
 9/12/2016 7:30 AM Bus Emmiting message on channel: Power
 9/12/2016 7:30 AM Power Aborting shutdown
 9/12/2016 7:30 AM Bus {
  "self": true,
  "channel": "Power",
  "data": "{\r\n  \"action\": \"abort\"\r\n}"
}
 9/12/2016 7:30 AM Bus Emmiting message on channel: Power
 9/12/2016 7:30 AM Power Aborting shutdown
 9/12/2016 7:30 AM Bus {
  "self": true,
  "channel": "Notification",
  "data": "{\r\n  \"title\": \"Shutdown Aborted\",\r\n  \"message\": \"Shutdown has been aborted\"\r\n}"
}
 9/12/2016 7:30 AM Bus Emmiting message on channel: Notification

Tom Elliott

@Joe-Schmitt this was an accidental issue I think on my side as it was sending wol tasks. Just for confirmation the client is simply checking if a task is reboot, if not it sets up as shutdown?

I’ve removed wol tasks from the client sender for RC 11 just would be good to know for sure.

Power Management - Scheduled WOL causes shutdown

Server

Client

Description

156

12.1k

17.3k

155.4k