I see this in /var/log/cobbler/cobbler.log:
Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE expiring token; user(<DIRECT>) Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE expiring token; user(<DIRECT>) Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE expiring token; user(cobbler) Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE expiring token; user(cobbler) Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE expiring token; user(<DIRECT>) Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE expiring token; user(<DIRECT>) Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE expiring token; user(<DIRECT>) Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE expiring token; user(<DIRECT>) Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE expiring token; user(<DIRECT>) Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE expiring token; user(<DIRECT>) Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE expiring token; user(<DIRECT>) Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE expiring token; user(<DIRECT>) Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE expiring token; user(<DIRECT>) Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE CLI Authorized; user(?) Fri Jan 15 13:06:05 2016 - DEBUG | REMOTE CLI Authorized; user(?) Fri Jan 15 13:06:05 2016 - INFO | REMOTE start_task(Power management (status)); event_id(2016-01-15_130605_power); user(?) Fri Jan 15 13:06:06 2016 - DEBUG | get_item; ['system', 'c1101'] Fri Jan 15 13:06:06 2016 - DEBUG | done with get_item; ['system', 'c1101'] Fri Jan 15 13:06:06 2016 - DEBUG | get_item; ['system', 'c1101'] Fri Jan 15 13:06:06 2016 - DEBUG | done with get_item; ['system', 'c1101'] Fri Jan 15 13:06:06 2016 - DEBUG | REMOTE CLI Authorized; user(?)
And in the tasks/power.log:
Fri Jan 15 13:06:06 2016 - INFO | cobbler power configuration is: Fri Jan 15 13:06:06 2016 - INFO | type : ipmilan Fri Jan 15 13:06:06 2016 - INFO | address: [redacted] Fri Jan 15 13:06:06 2016 - INFO | user : root Fri Jan 15 13:06:06 2016 - INFO | id : Fri Jan 15 13:06:06 2016 - INFO | running: /sbin/fence_ipmilan Fri Jan 15 13:06:15 2016 - INFO | received on stdout: Fri Jan 15 13:06:15 2016 - DEBUG | received on stderr: Failed: Unable to obtain correct plug status or plug is not available
Fri Jan 15 13:06:17 2016 - INFO | running: /sbin/fence_ipmilan Fri Jan 15 13:06:25 2016 - INFO | received on stdout: Fri Jan 15 13:06:25 2016 - DEBUG | received on stderr: Failed: Unable to obtain correct plug status or plug is not available
Fri Jan 15 13:06:27 2016 - INFO | running: /sbin/fence_ipmilan Fri Jan 15 13:06:35 2016 - INFO | received on stdout: Fri Jan 15 13:06:35 2016 - DEBUG | received on stderr: Failed: Unable to obtain correct plug status or plug is not available
Fri Jan 15 13:06:37 2016 - INFO | running: /sbin/fence_ipmilan Fri Jan 15 13:06:45 2016 - INFO | received on stdout: Fri Jan 15 13:06:45 2016 - DEBUG | received on stderr: Failed: Unable to obtain correct plug status or plug is not available
Fri Jan 15 13:06:47 2016 - INFO | running: /sbin/fence_ipmilan Fri Jan 15 13:06:55 2016 - INFO | received on stdout: Fri Jan 15 13:06:55 2016 - DEBUG | received on stderr: Failed: Unable to obtain correct plug status or plug is not available
Fri Jan 15 13:06:57 2016 - INFO | Exception occured: <class 'cobbler.cexceptions.CX'> Fri Jan 15 13:06:57 2016 - INFO | Exception value: 'command failed (rc=1), please validate the physical setup and cobbler config' Fri Jan 15 13:06:57 2016 - INFO | Exception Info: File "/usr/lib/python2.7/site-packages/cobbler/utils.py", line 126, in die raise CX(msg)
Fri Jan 15 13:06:57 2016 - WARNING | failed to execute power task on c1101 Fri Jan 15 13:06:57 2016 - INFO | ### TASK COMPLETE ###
Mike Waldron Systems Specialist ITS - Research Computing Center University of North Carolina at Chapel Hill
________________________________ From: Waldron, Michael H Sent: Friday, January 15, 2016 10:39 AM To: cobbler@lists.fedorahosted.org Subject: Power management problem
I'm trying to use the power management feature in cobbler, but when I run any of the power commands, such as 'cobbler system powerstatus', I get the error:
Failed: Unable to obtain correct plug status or plug is not available
It is calling the fence_ipmilan agent, and I have verified that this works from the command line:
fence_ipmilan -a 172.26.145.151 -P -l root -p password -o status
Has anyone else seen this issue?
Mike Waldron Systems Specialist ITS - Research Computing Center University of North Carolina at Chapel Hill