Advertisement
ginsul

Untitled

Apr 6th, 2018
181
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.43 KB | None | 0 0
  1. #After triggering the 'delete server' event via Rackspace's Web interface, I can see in the logs a failing "poweroff" command.
  2. core@fixed-updated-1 ~ $ journalctl -f
  3. Apr 06 12:05:12 fixed-updated-1 systemd[1]: Created slice system-systemd\x2dcoredump.slice.
  4. Apr 06 12:05:12 fixed-updated-1 systemd[1]: Started Process Core Dump (PID 1042/UID 0).
  5. Apr 06 12:05:12 fixed-updated-1 systemd-coredump[1043]: Resource limits disable core dumping for process 1041 (poweroff).
  6. Apr 06 12:05:12 fixed-updated-1 systemd-coredump[1043]: Process 1041 (poweroff) of user 0 dumped core.
  7. Apr 06 12:05:28 fixed-updated-1 update_engine[700]: I0406 12:05:28.907824 700 update_attempter.cc:493] Updating boot flags...
  8.  
  9. #The coredump meta is present, but no core dump file ("none")
  10. core@fixed-updated-1 ~ $ coredumpctl list
  11. Fri 2018-04-06 12:05:12 UTC 1041 0 0 6 none /usr/bin/systemctl
  12.  
  13. #Read coredump meta.
  14. core@fixed-updated-1 ~ $ coredumpctl info 1041
  15. PID: 1041 (poweroff)
  16. UID: 0 (root)
  17. GID: 0 (root)
  18. Signal: 6 (ABRT)
  19. Timestamp: Fri 2018-04-06 12:05:12 UTC (19s ago)
  20. Command Line: /sbin/poweroff
  21. Executable: /usr/bin/systemctl
  22. Control Group: /
  23. Slice: -.slice
  24. Boot ID: ce73beca5cc143be8bb7b77cee8840eb
  25. Machine ID: f2c4f6b3ef2443db91d02b4f7f44cd68
  26. Hostname: fixed-updated-1
  27. Storage: none
  28. Message: Process 1041 (poweroff) of user 0 dumped core.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement