SHARE
TWEET

Untitled

a guest Sep 16th, 2019 83 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. ...
  2. Sep 16 14:39:01 pve systemd[1]: Started Proxmox VE replication runner.
  3. Sep 16 14:40:00 pve systemd[1]: Starting Proxmox VE replication runner...
  4. Sep 16 14:40:01 pve systemd[1]: pvesr.service: Succeeded.
  5. Sep 16 14:40:01 pve systemd[1]: Started Proxmox VE replication runner.
  6. Sep 16 14:41:00 pve systemd[1]: Starting Proxmox VE replication runner...
  7. Sep 16 14:41:01 pve systemd[1]: pvesr.service: Succeeded.
  8. Sep 16 14:41:01 pve systemd[1]: Started Proxmox VE replication runner.
  9. Sep 16 14:42:00 pve systemd[1]: Starting Proxmox VE replication runner...
  10. Sep 16 14:42:00 pve systemd[1]: pvesr.service: Succeeded.
  11. Sep 16 14:42:00 pve systemd[1]: Started Proxmox VE replication runner.
  12. Sep 16 14:42:19 pve kernel: [ 1455.297513] mce: [Hardware Error]: Machine check events logged
  13. Sep 16 14:43:00 pve systemd[1]: Starting Proxmox VE replication runner...
  14. Sep 16 14:43:00 pve systemd[1]: pvesr.service: Succeeded.
  15. Sep 16 14:43:00 pve systemd[1]: Started Proxmox VE replication runner.
  16. Sep 16 14:44:00 pve systemd[1]: Starting Proxmox VE replication runner...
  17. Sep 16 14:44:01 pve systemd[1]: pvesr.service: Succeeded.
  18. Sep 16 14:44:01 pve systemd[1]: Started Proxmox VE replication runner.
  19. Sep 16 14:45:00 pve systemd[1]: Starting Proxmox VE replication runner...
  20. Sep 16 14:45:01 pve systemd[1]: pvesr.service: Succeeded.
  21. Sep 16 14:45:01 pve systemd[1]: Started Proxmox VE replication runner.
  22. Sep 16 14:46:00 pve systemd[1]: Starting Proxmox VE replication runner...
  23. Sep 16 14:46:01 pve systemd[1]: pvesr.service: Succeeded.
  24. Sep 16 14:46:01 pve systemd[1]: Started Proxmox VE replication runner.
  25. ...
  26. Sep 16 08:49:15 pve kernel: [    0.342415] rcu: Hierarchical SRCU implementation.
  27. Sep 16 08:49:15 pve kernel: [    0.342751] random: crng done (trusting CPU's manufacturer)
  28. Sep 16 08:49:15 pve kernel: [    0.343105] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
  29. Sep 16 08:49:15 pve kernel: [    0.343161] smp: Bringing up secondary CPUs ...
  30. Sep 16 08:49:15 pve kernel: [    0.343204] x86: Booting SMP configuration:
  31. Sep 16 08:49:15 pve kernel: [    0.343204] .... node  #0, CPUs:        #1  #2  #3  #4  #5  #6  #7
  32. Sep 16 08:49:15 pve kernel: [    0.343725] mce: [Hardware Error]: Machine check events logged
  33. Sep 16 08:49:15 pve kernel: [    0.343725] mce: [Hardware Error]: CPU 7: Machine Check: 0 Bank 2: b200000000000014
  34. Sep 16 08:49:15 pve kernel: [    0.345144] mce: [Hardware Error]: TSC 0
  35. Sep 16 08:49:15 pve kernel: [    0.345231] mce: [Hardware Error]: PROCESSOR 0:906ec TIME 1568612948 SOCKET 0 APIC e microcode 98
  36. Sep 16 08:49:15 pve kernel: [    0.345334]   #8
  37. Sep 16 08:49:15 pve kernel: [    0.345632] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
  38. Sep 16 08:49:15 pve kernel: [    0.345632]   #9 #10 #11 #12 #13 #14 #15
  39. Sep 16 08:49:15 pve kernel: [    0.345632] smp: Brought up 1 node, 16 CPUs
  40. Sep 16 08:49:15 pve kernel: [    0.345632] smpboot: Max logical packages: 1
  41. Sep 16 08:49:15 pve kernel: [    0.345632] smpboot: Total of 16 processors activated (115200.00 BogoMIPS)
  42. Sep 16 08:49:15 pve kernel: [    0.350101] devtmpfs: initialized
  43. Sep 16 08:49:15 pve kernel: [    0.350101] x86/mm: Memory block size: 128MB
RAW Paste Data
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
 
Top