Advertisement
Guest User

Untitled

a guest
Nov 16th, 2017
222
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.08 KB | None | 0 0
  1. root@node:~# systemctl status pvedaemon.service
  2. ● pvedaemon.service - PVE API Daemon
  3. Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled)
  4. Active: failed (Result: timeout) since czw 2017-11-16 14:38:26 CET; 4min 15s ago
  5. Process: 702 ExecStop=/usr/bin/pvedaemon stop (code=exited, status=0/SUCCESS)
  6. Process: 21317 ExecStart=/usr/bin/pvedaemon start (code=exited, status=255)
  7. Main PID: 15217 (code=exited, status=0/SUCCESS)
  8.  
  9. lis 16 14:35:26 node pvedaemon[21317]: start failed - unable to create socket - Address already in use
  10. lis 16 14:35:26 node pvedaemon[21317]: start failed - unable to create socket - Address already in use
  11. lis 16 14:35:26 node systemd[1]: pvedaemon.service: control process exited, code=exited status=255
  12. lis 16 14:36:56 node systemd[1]: pvedaemon.service stop-final-sigterm timed out. Killing.
  13. lis 16 14:38:26 node systemd[1]: pvedaemon.service still around after final SIGKILL. Entering failed mode.
  14. lis 16 14:38:26 node systemd[1]: Failed to start PVE API Daemon.
  15. lis 16 14:38:26 node systemd[1]: Unit pvedaemon.service entered failed state.
  16. root@node:~#
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement