API tools faq
paste
ravecat

systemctl

ravecat
Nov 8th, 2020
249
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Bash 12.36 KB | None | 0 0
raw download clone embed print report
  1. root@node-0:/home/admin# systemctl status 'pve*'
  2. ● pve-ha-lrm.service - PVE Local HA Ressource Manager Daemon
  3.    Loaded: loaded (/lib/systemd/system/pve-ha-lrm.service; enabled; vendor preset: enabled)
  4.    Active: failed (Result: exit-code) since Sun 2020-11-08 18:20:56 MSK; 2h 44min ago
  5.       CPU: 401ms
  6.  
  7. Nov 08 18:20:56 node-0 pve-ha-lrm[1918]: ipcc_send_rec[1] failed: Connection refused
  8. Nov 08 18:20:56 node-0 pve-ha-lrm[1918]: ipcc_send_rec[2] failed: Connection refused
  9. Nov 08 18:20:56 node-0 pve-ha-lrm[1918]: ipcc_send_rec[2] failed: Connection refused
  10. Nov 08 18:20:56 node-0 pve-ha-lrm[1918]: ipcc_send_rec[3] failed: Connection refused
  11. Nov 08 18:20:56 node-0 pve-ha-lrm[1918]: ipcc_send_rec[3] failed: Connection refused
  12. Nov 08 18:20:56 node-0 pve-ha-lrm[1918]: Unable to load access control list: Connection refused
  13. Nov 08 18:20:56 node-0 systemd[1]: pve-ha-lrm.service: Control process exited, code=exited status=111
  14. Nov 08 18:20:56 node-0 systemd[1]: Failed to start PVE Local HA Ressource Manager Daemon.
  15. Nov 08 18:20:56 node-0 systemd[1]: pve-ha-lrm.service: Unit entered failed state.
  16. Nov 08 18:20:56 node-0 systemd[1]: pve-ha-lrm.service: Failed with result 'exit-code'.
  17.  
  18. ● pve-ha-crm.service - PVE Cluster Ressource Manager Daemon
  19.    Loaded: loaded (/lib/systemd/system/pve-ha-crm.service; enabled; vendor preset: enabled)
  20.    Active: failed (Result: exit-code) since Sun 2020-11-08 18:20:56 MSK; 2h 44min ago
  21.       CPU: 401ms
  22.  
  23. Nov 08 18:20:56 node-0 pve-ha-crm[1900]: ipcc_send_rec[1] failed: Connection refused
  24. Nov 08 18:20:56 node-0 pve-ha-crm[1900]: ipcc_send_rec[2] failed: Connection refused
  25. Nov 08 18:20:56 node-0 pve-ha-crm[1900]: ipcc_send_rec[2] failed: Connection refused
  26. Nov 08 18:20:56 node-0 pve-ha-crm[1900]: ipcc_send_rec[3] failed: Connection refused
  27. Nov 08 18:20:56 node-0 pve-ha-crm[1900]: ipcc_send_rec[3] failed: Connection refused
  28. Nov 08 18:20:56 node-0 pve-ha-crm[1900]: Unable to load access control list: Connection refused
  29. Nov 08 18:20:56 node-0 systemd[1]: pve-ha-crm.service: Control process exited, code=exited status=111
  30. Nov 08 18:20:56 node-0 systemd[1]: Failed to start PVE Cluster Ressource Manager Daemon.
  31. Nov 08 18:20:56 node-0 systemd[1]: pve-ha-crm.service: Unit entered failed state.
  32. Nov 08 18:20:56 node-0 systemd[1]: pve-ha-crm.service: Failed with result 'exit-code'.
  33.  
  34. ● pvefw-logger.service - Proxmox VE firewall logger
  35.    Loaded: loaded (/lib/systemd/system/pvefw-logger.service; static; vendor preset: enabled)
  36.    Active: active (running) since Sun 2020-11-08 18:20:50 MSK; 2h 44min ago
  37.  Main PID: 925 (pvefw-logger)
  38.     Tasks: 2 (limit: 4915)
  39.    Memory: 1.6M
  40.       CPU: 239ms
  41.    CGroup: /system.slice/pvefw-logger.service
  42.            └─925 /usr/sbin/pvefw-logger
  43.  
  44. Nov 08 18:20:50 node-0 systemd[1]: Starting Proxmox VE firewall logger...
  45. Nov 08 18:20:50 node-0 pvefw-logger[925]: starting pvefw logger
  46. Nov 08 18:20:50 node-0 systemd[1]: Started Proxmox VE firewall logger.
  47.  
  48. ● pve-cluster.service - The Proxmox VE cluster filesystem
  49.    Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
  50.    Active: failed (Result: exit-code) since Sun 2020-11-08 18:20:55 MSK; 2h 44min ago
  51.       CPU: 6ms
  52.  
  53. Nov 08 18:20:55 node-0 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
  54. Nov 08 18:20:55 node-0 systemd[1]: pve-cluster.service: Service hold-off time over, scheduling restart.
  55. Nov 08 18:20:55 node-0 systemd[1]: Stopped The Proxmox VE cluster filesystem.
  56. Nov 08 18:20:55 node-0 systemd[1]: pve-cluster.service: Start request repeated too quickly.
  57. Nov 08 18:20:55 node-0 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
  58. Nov 08 18:20:55 node-0 systemd[1]: pve-cluster.service: Unit entered failed state.
  59. Nov 08 18:20:55 node-0 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
  60.  
  61. ● pve-storage.target - PVE Storage Target
  62.    Loaded: loaded (/lib/systemd/system/pve-storage.target; static; vendor preset: enabled)
  63.    Active: active since Sun 2020-11-08 18:20:53 MSK; 2h 44min ago
  64.  
  65. Nov 08 18:20:53 node-0 systemd[1]: Reached target PVE Storage Target.
  66.  
  67. ● pveproxy.service - PVE API Proxy Server
  68.    Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
  69.    Active: active (running) since Sun 2020-11-08 18:20:56 MSK; 2h 44min ago
  70.  Main PID: 1942 (pveproxy)
  71.     Tasks: 4 (limit: 4915)
  72.    Memory: 121.7M
  73.       CPU: 2min 10.555s
  74.    CGroup: /system.slice/pveproxy.service
  75.            ├─ 1942 pveproxy
  76.            ├─12423 pveproxy worker
  77.            ├─12424 pveproxy worker
  78.            └─12425 pveproxy worker
  79.  
  80. Nov 08 21:05:39 node-0 pveproxy[12421]: worker exit
  81. Nov 08 21:05:39 node-0 pveproxy[1942]: worker 12421 finished
  82. Nov 08 21:05:39 node-0 pveproxy[1942]: starting 1 worker(s)
  83. Nov 08 21:05:39 node-0 pveproxy[1942]: worker 12424 started
  84. Nov 08 21:05:39 node-0 pveproxy[12424]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServ
  85. Nov 08 21:05:40 node-0 pveproxy[12422]: worker exit
  86. Nov 08 21:05:40 node-0 pveproxy[1942]: worker 12422 finished
  87. Nov 08 21:05:40 node-0 pveproxy[1942]: starting 1 worker(s)
  88. Nov 08 21:05:40 node-0 pveproxy[1942]: worker 12425 started
  89. Nov 08 21:05:40 node-0 pveproxy[12425]: /etc/pve/local/pve-ssl.key: failed to load local private key (key_file or key) at /usr/share/perl5/PVE/APIServ
  90.  
  91. ● pve-daily-update.timer - Daily PVE download activities
  92.    Loaded: loaded (/lib/systemd/system/pve-daily-update.timer; enabled; vendor preset: enabled)
  93.    Active: active (waiting) since Sun 2020-11-08 18:20:53 MSK; 2h 44min ago
  94.  
  95. Nov 08 18:20:53 node-0 systemd[1]: pve-daily-update.timer: Adding 1h 45min 53.695839s random time.
  96. Nov 08 18:20:53 node-0 systemd[1]: Started Daily PVE download activities.
  97. Nov 08 18:21:21 node-0 systemd[1]: pve-daily-update.timer: Adding 25min 37.501896s random time.
  98.  
  99. ● pve-guests.service - PVE guests
  100.    Loaded: loaded (/lib/systemd/system/pve-guests.service; enabled; vendor preset: enabled)
  101.    Active: failed (Result: exit-code) since Sun 2020-11-08 18:20:57 MSK; 2h 44min ago
  102.  Main PID: 1978 (code=exited, status=111)
  103.       CPU: 525ms
  104.  
  105. Nov 08 18:20:56 node-0 systemd[1]: Starting PVE guests...
  106. Nov 08 18:20:57 node-0 pvesh[1978]: ipcc_send_rec[1] failed: Connection refused
  107. Nov 08 18:20:57 node-0 pvesh[1978]: ipcc_send_rec[2] failed: Connection refused
  108. Nov 08 18:20:57 node-0 pvesh[1978]: ipcc_send_rec[3] failed: Connection refused
  109. Nov 08 18:20:57 node-0 pvesh[1978]: Unable to load access control list: Connection refused
  110. Nov 08 18:20:57 node-0 systemd[1]: pve-guests.service: Main process exited, code=exited, status=111/n/a
  111. Nov 08 18:20:57 node-0 systemd[1]: Failed to start PVE guests.
  112. Nov 08 18:20:57 node-0 systemd[1]: pve-guests.service: Unit entered failed state.
  113. Nov 08 18:20:57 node-0 systemd[1]: pve-guests.service: Failed with result 'exit-code'.
  114.  
  115. ● pvebanner.service - Proxmox VE Login Banner
  116.    Loaded: loaded (/lib/systemd/system/pvebanner.service; enabled; vendor preset: enabled)
  117.    Active: active (exited) since Sun 2020-11-08 18:20:51 MSK; 2h 44min ago
  118.  Main PID: 791 (code=exited, status=0/SUCCESS)
  119.     Tasks: 0 (limit: 4915)
  120.    Memory: 0B
  121.       CPU: 0
  122.    CGroup: /system.slice/pvebanner.service
  123.  
  124. Nov 08 18:20:50 node-0 systemd[1]: Starting Proxmox VE Login Banner...
  125. Nov 08 18:20:51 node-0 systemd[1]: Started Proxmox VE Login Banner.
  126.  
  127. ● pvesr.service - Proxmox VE replication runner
  128.    Loaded: loaded (/lib/systemd/system/pvesr.service; static; vendor preset: enabled)
  129.    Active: failed (Result: exit-code) since Sun 2020-11-08 21:05:00 MSK; 40s ago
  130.   Process: 12385 ExecStart=/usr/bin/pvesr run --mail 1 (code=exited, status=111)
  131.  Main PID: 12385 (code=exited, status=111)
  132.       CPU: 335ms
  133.  
  134. Nov 08 21:05:00 node-0 systemd[1]: Starting Proxmox VE replication runner...
  135. Nov 08 21:05:00 node-0 pvesr[12385]: ipcc_send_rec[1] failed: Connection refused
  136. Nov 08 21:05:00 node-0 pvesr[12385]: ipcc_send_rec[2] failed: Connection refused
  137. Nov 08 21:05:00 node-0 pvesr[12385]: ipcc_send_rec[3] failed: Connection refused
  138. Nov 08 21:05:00 node-0 pvesr[12385]: Unable to load access control list: Connection refused
  139. Nov 08 21:05:00 node-0 systemd[1]: pvesr.service: Main process exited, code=exited, status=111/n/a
  140. Nov 08 21:05:00 node-0 systemd[1]: Failed to start Proxmox VE replication runner.
  141. Nov 08 21:05:00 node-0 systemd[1]: pvesr.service: Unit entered failed state.
  142. Nov 08 21:05:00 node-0 systemd[1]: pvesr.service: Failed with result 'exit-code'.
  143.  
  144. ● pvedaemon.service - PVE API Daemon
  145.    Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
  146.    Active: active (running) since Sun 2020-11-08 18:20:55 MSK; 2h 44min ago
  147.  Main PID: 1886 (pvedaemon)
  148.     Tasks: 4 (limit: 4915)
  149.    Memory: 123.8M
  150.       CPU: 877ms
  151.    CGroup: /system.slice/pvedaemon.service
  152.            ├─1886 pvedaemon
  153.            ├─1889 pvedaemon worker
  154.            ├─1890 pvedaemon worker
  155.            └─1891 pvedaemon worker
  156.  
  157. Nov 08 18:20:54 node-0 systemd[1]: Starting PVE API Daemon...
  158. Nov 08 18:20:55 node-0 pvedaemon[1886]: starting server
  159. Nov 08 18:20:55 node-0 pvedaemon[1886]: starting 3 worker(s)
  160. Nov 08 18:20:55 node-0 pvedaemon[1886]: worker 1889 started
  161. Nov 08 18:20:55 node-0 pvedaemon[1886]: worker 1890 started
  162. Nov 08 18:20:55 node-0 pvedaemon[1886]: worker 1891 started
  163. Nov 08 18:20:55 node-0 systemd[1]: Started PVE API Daemon.
  164.  
  165. ● pvestatd.service - PVE Status Daemon
  166.    Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
  167.    Active: failed (Result: exit-code) since Sun 2020-11-08 18:20:55 MSK; 2h 44min ago
  168.       CPU: 369ms
  169.  
  170. Nov 08 18:20:55 node-0 pvestatd[1722]: ipcc_send_rec[1] failed: Connection refused
  171. Nov 08 18:20:55 node-0 pvestatd[1722]: ipcc_send_rec[2] failed: Connection refused
  172. Nov 08 18:20:55 node-0 pvestatd[1722]: ipcc_send_rec[2] failed: Connection refused
  173. Nov 08 18:20:55 node-0 pvestatd[1722]: ipcc_send_rec[3] failed: Connection refused
  174. Nov 08 18:20:55 node-0 pvestatd[1722]: ipcc_send_rec[3] failed: Connection refused
  175. Nov 08 18:20:55 node-0 pvestatd[1722]: Unable to load access control list: Connection refused
  176. Nov 08 18:20:55 node-0 systemd[1]: pvestatd.service: Control process exited, code=exited status=111
  177. Nov 08 18:20:55 node-0 systemd[1]: Failed to start PVE Status Daemon.
  178. Nov 08 18:20:55 node-0 systemd[1]: pvestatd.service: Unit entered failed state.
  179. Nov 08 18:20:55 node-0 systemd[1]: pvestatd.service: Failed with result 'exit-code'.
  180.  
  181. ● pvenetcommit.service - Commit Proxmox VE network changes
  182.    Loaded: loaded (/lib/systemd/system/pvenetcommit.service; enabled; vendor preset: enabled)
  183.    Active: active (exited) since Sun 2020-11-08 18:20:50 MSK; 2h 44min ago
  184.  Main PID: 939 (code=exited, status=0/SUCCESS)
  185.     Tasks: 0 (limit: 4915)
  186.    Memory: 0B
  187.       CPU: 0
  188.    CGroup: /system.slice/pvenetcommit.service
  189.  
  190. Nov 08 18:20:50 node-0 systemd[1]: Starting Commit Proxmox VE network changes...
  191. Nov 08 18:20:50 node-0 mv[870]: /bin/mv: cannot stat '/etc/network/interfaces.new': No such file or directory
  192. Nov 08 18:20:50 node-0 systemd[1]: Started Commit Proxmox VE network changes.
  193.  
  194. ● pve-firewall.service - Proxmox VE firewall
  195.    Loaded: loaded (/lib/systemd/system/pve-firewall.service; enabled; vendor preset: enabled)
  196.    Active: failed (Result: exit-code) since Sun 2020-11-08 18:20:55 MSK; 2h 44min ago
  197.       CPU: 378ms
  198.  
  199. Nov 08 18:20:55 node-0 pve-firewall[1698]: ipcc_send_rec[1] failed: Connection refused
  200. Nov 08 18:20:55 node-0 pve-firewall[1698]: ipcc_send_rec[2] failed: Connection refused
  201. Nov 08 18:20:55 node-0 pve-firewall[1698]: ipcc_send_rec[2] failed: Connection refused
  202. Nov 08 18:20:55 node-0 pve-firewall[1698]: ipcc_send_rec[3] failed: Connection refused
  203. Nov 08 18:20:55 node-0 pve-firewall[1698]: ipcc_send_rec[3] failed: Connection refused
  204. Nov 08 18:20:55 node-0 pve-firewall[1698]: Unable to load access control list: Connection refused
  205. Nov 08 18:20:55 node-0 systemd[1]: pve-firewall.service: Control process exited, code=exited status=111
  206. Nov 08 18:20:55 node-0 systemd[1]: Failed to start Proxmox VE firewall.
  207. Nov 08 18:20:55 node-0 systemd[1]: pve-firewall.service: Unit entered failed state.
  208. Nov 08 18:20:55 node-0 systemd[1]: pve-firewall.service: Failed with result 'exit-code'.
  209.  
  210. ● pvesr.timer - Proxmox VE replication runner
  211.    Loaded: loaded (/lib/systemd/system/pvesr.timer; enabled; vendor preset: enabled)
  212.    Active: active (waiting) since Sun 2020-11-08 18:20:53 MSK; 2h 44min ago
  213.  
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!