API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Mar 14th, 2020
298
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.85 KB | None | 0 0
raw download clone embed print report
  1. Mar 14 21:24:49 maude NetworkManager[904]: <warn> [1584221089.7742] device (vethbfeb2b0): failed to find device 6 'vethbfeb2b0' with udev
  2. Mar 14 21:24:49 maude NetworkManager[904]: <info> [1584221089.7753] manager: (vethbfeb2b0): new Veth device (/org/freedesktop/NetworkManager/Devices/5)
  3. Mar 14 21:24:49 maude NetworkManager[904]: <warn> [1584221089.7756] device (veth438f61e): failed to find device 7 'veth438f61e' with udev
  4. Mar 14 21:24:49 maude NetworkManager[904]: <info> [1584221089.7763] manager: (veth438f61e): new Veth device (/org/freedesktop/NetworkManager/Devices/6)
  5. Mar 14 21:24:49 maude kernel: [ 117.107234] docker0: port 1(veth438f61e) entered blocking state
  6. Mar 14 21:24:49 maude kernel: [ 117.107236] docker0: port 1(veth438f61e) entered disabled state
  7. Mar 14 21:24:49 maude kernel: [ 117.107276] device veth438f61e entered promiscuous mode
  8. Mar 14 21:24:49 maude kernel: [ 117.107412] IPv6: ADDRCONF(NETDEV_UP): veth438f61e: link is not ready
  9. Mar 14 21:24:49 maude NetworkManager[904]: <info> [1584221089.7832] devices added (path: /sys/devices/virtual/net/vethbfeb2b0, iface: vethbfeb2b0)
  10. Mar 14 21:24:49 maude NetworkManager[904]: <info> [1584221089.7832] device added (path: /sys/devices/virtual/net/vethbfeb2b0, iface: vethbfeb2b0): no ifupdown configuration found.
  11. Mar 14 21:24:49 maude NetworkManager[904]: <info> [1584221089.7853] devices added (path: /sys/devices/virtual/net/veth438f61e, iface: veth438f61e)
  12. Mar 14 21:24:49 maude NetworkManager[904]: <info> [1584221089.7853] device added (path: /sys/devices/virtual/net/veth438f61e, iface: veth438f61e): no ifupdown configuration found.
  13. Mar 14 21:24:50 maude kernel: [ 117.398868] eth0: renamed from vethbfeb2b0
  14. Mar 14 21:24:50 maude NetworkManager[904]: <info> [1584221090.0900] devices removed (path: /sys/devices/virtual/net/vethbfeb2b0, iface: vethbfeb2b0)
  15. Mar 14 21:24:50 maude NetworkManager[904]: <info> [1584221090.0910] device (vethbfeb2b0): driver 'veth' does not support carrier detection.
  16. Mar 14 21:24:50 maude NetworkManager[904]: <info> [1584221090.0915] device (veth438f61e): link connected
  17. Mar 14 21:24:50 maude NetworkManager[904]: <info> [1584221090.0926] device (docker0): link connected
  18. Mar 14 21:24:50 maude kernel: [ 117.422900] IPv6: ADDRCONF(NETDEV_CHANGE): veth438f61e: link becomes ready
  19. Mar 14 21:24:50 maude kernel: [ 117.422994] docker0: port 1(veth438f61e) entered blocking state
  20. Mar 14 21:24:50 maude kernel: [ 117.422999] docker0: port 1(veth438f61e) entered forwarding state
  21. Mar 14 21:24:50 maude kernel: [ 117.423114] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
  22. Mar 14 21:28:07 maude kernel: [ 314.760132] docker0: port 1(veth438f61e) entered disabled state
  23. Mar 14 21:28:07 maude kernel: [ 314.760189] vethbfeb2b0: renamed from eth0
  24. Mar 14 21:28:07 maude NetworkManager[904]: <info> [1584221287.5102] device (veth438f61e): link disconnected
  25. Mar 14 21:28:07 maude NetworkManager[904]: <info> [1584221287.5103] device (docker0): link disconnected (deferring action for 4 seconds)
  26. Mar 14 21:28:07 maude NetworkManager[904]: <warn> [1584221287.5104] device (vethbfeb2b0): failed to find device 6 'vethbfeb2b0' with udev
  27. Mar 14 21:28:07 maude NetworkManager[904]: <info> [1584221287.5120] manager: (vethbfeb2b0): new Veth device (/org/freedesktop/NetworkManager/Devices/7)
  28. Mar 14 21:28:07 maude NetworkManager[904]: <info> [1584221287.5197] devices added (path: /sys/devices/virtual/net/vethbfeb2b0, iface: vethbfeb2b0)
  29. Mar 14 21:28:07 maude NetworkManager[904]: <info> [1584221287.5197] device added (path: /sys/devices/virtual/net/vethbfeb2b0, iface: vethbfeb2b0): no ifupdown configuration found.
  30. Mar 14 21:28:07 maude kernel: [ 314.846805] docker0: port 1(veth438f61e) entered disabled state
  31. Mar 14 21:28:07 maude kernel: [ 314.848481] device veth438f61e left promiscuous mode
  32. Mar 14 21:28:07 maude kernel: [ 314.848484] docker0: port 1(veth438f61e) entered disabled state
  33. Mar 14 21:28:07 maude NetworkManager[904]: <info> [1584221287.5666] devices removed (path: /sys/devices/virtual/net/vethbfeb2b0, iface: vethbfeb2b0)
  34. Mar 14 21:28:07 maude NetworkManager[904]: <info> [1584221287.5676] device (vethbfeb2b0): driver 'veth' does not support carrier detection.
  35. Mar 14 21:28:07 maude NetworkManager[904]: <info> [1584221287.5680] device (veth438f61e): driver 'veth' does not support carrier detection.
  36. Mar 14 21:28:07 maude NetworkManager[904]: <info> [1584221287.5700] devices removed (path: /sys/devices/virtual/net/veth438f61e, iface: veth438f61e)
  37. Mar 14 21:28:11 maude NetworkManager[904]: <info> [1584221291.9812] device (docker0): link disconnected (calling deferred action)
  38. Mar 14 21:28:16 maude NetworkManager[904]: <warn> [1584221296.9784] device (veth93b081f): failed to find device 8 'veth93b081f' with udev
  39. Mar 14 21:28:16 maude NetworkManager[904]: <info> [1584221296.9793] manager: (veth93b081f): new Veth device (/org/freedesktop/NetworkManager/Devices/8)
  40. Mar 14 21:28:16 maude NetworkManager[904]: <warn> [1584221296.9796] device (veth2393ecf): failed to find device 9 'veth2393ecf' with udev
  41. Mar 14 21:28:16 maude NetworkManager[904]: <info> [1584221296.9805] manager: (veth2393ecf): new Veth device (/org/freedesktop/NetworkManager/Devices/9)
  42. Mar 14 21:28:16 maude kernel: [ 324.298884] br-6dc93588b52a: port 1(veth2393ecf) entered blocking state
  43. Mar 14 21:28:16 maude kernel: [ 324.298886] br-6dc93588b52a: port 1(veth2393ecf) entered disabled state
  44. Mar 14 21:28:16 maude kernel: [ 324.298945] device veth2393ecf entered promiscuous mode
  45. Mar 14 21:28:16 maude kernel: [ 324.299639] IPv6: ADDRCONF(NETDEV_UP): veth2393ecf: link is not ready
  46. Mar 14 21:28:16 maude NetworkManager[904]: <info> [1584221296.9873] devices added (path: /sys/devices/virtual/net/veth93b081f, iface: veth93b081f)
  47. Mar 14 21:28:16 maude NetworkManager[904]: <info> [1584221296.9874] device added (path: /sys/devices/virtual/net/veth93b081f, iface: veth93b081f): no ifupdown configuration found.
  48. Mar 14 21:28:16 maude NetworkManager[904]: <info> [1584221296.9887] devices added (path: /sys/devices/virtual/net/veth2393ecf, iface: veth2393ecf)
  49. Mar 14 21:28:16 maude NetworkManager[904]: <info> [1584221296.9887] device added (path: /sys/devices/virtual/net/veth2393ecf, iface: veth2393ecf): no ifupdown configuration found.
  50. Mar 14 21:28:17 maude kernel: [ 324.930474] eth0: renamed from veth93b081f
  51. Mar 14 21:28:17 maude NetworkManager[904]: <info> [1584221297.6339] devices removed (path: /sys/devices/virtual/net/veth93b081f, iface: veth93b081f)
  52. Mar 14 21:28:17 maude NetworkManager[904]: <info> [1584221297.6350] device (veth93b081f): driver 'veth' does not support carrier detection.
  53. Mar 14 21:28:17 maude NetworkManager[904]: <info> [1584221297.6355] device (veth2393ecf): link connected
  54. Mar 14 21:28:17 maude NetworkManager[904]: <info> [1584221297.6370] device (br-6dc93588b52a): link connected
  55. Mar 14 21:28:17 maude kernel: [ 324.954422] IPv6: ADDRCONF(NETDEV_CHANGE): veth2393ecf: link becomes ready
  56. Mar 14 21:28:17 maude kernel: [ 324.954533] br-6dc93588b52a: port 1(veth2393ecf) entered blocking state
  57. Mar 14 21:28:17 maude kernel: [ 324.954538] br-6dc93588b52a: port 1(veth2393ecf) entered forwarding state
  58. Mar 14 21:28:17 maude kernel: [ 324.954658] IPv6: ADDRCONF(NETDEV_CHANGE): br-6dc93588b52a: link becomes ready
  59. Mar 14 21:28:18 maude NetworkManager[904]: <warn> [1584221298.1450] device (vethbcf80f1): failed to find device 10 'vethbcf80f1' with udev
  60. Mar 14 21:28:18 maude kernel: [ 325.465187] br-6dc93588b52a: port 2(veth0a25095) entered blocking state
  61. Mar 14 21:28:18 maude kernel: [ 325.465189] br-6dc93588b52a: port 2(veth0a25095) entered disabled state
  62. Mar 14 21:28:18 maude kernel: [ 325.465265] device veth0a25095 entered promiscuous mode
  63. Mar 14 21:28:18 maude kernel: [ 325.465383] IPv6: ADDRCONF(NETDEV_UP): veth0a25095: link is not ready
  64. Mar 14 21:28:18 maude kernel: [ 325.465386] br-6dc93588b52a: port 2(veth0a25095) entered blocking state
  65. Mar 14 21:28:18 maude kernel: [ 325.465387] br-6dc93588b52a: port 2(veth0a25095) entered forwarding state
  66. Mar 14 21:28:18 maude kernel: [ 325.465743] br-6dc93588b52a: port 2(veth0a25095) entered disabled state
  67. Mar 14 21:28:18 maude NetworkManager[904]: <info> [1584221298.1462] manager: (vethbcf80f1): new Veth device (/org/freedesktop/NetworkManager/Devices/10)
  68. Mar 14 21:28:18 maude NetworkManager[904]: <warn> [1584221298.1465] device (veth0a25095): failed to find device 11 'veth0a25095' with udev
  69. Mar 14 21:28:18 maude NetworkManager[904]: <info> [1584221298.1473] manager: (veth0a25095): new Veth device (/org/freedesktop/NetworkManager/Devices/11)
  70. Mar 14 21:28:18 maude NetworkManager[904]: <info> [1584221298.1537] devices added (path: /sys/devices/virtual/net/veth0a25095, iface: veth0a25095)
  71. Mar 14 21:28:18 maude NetworkManager[904]: <info> [1584221298.1537] device added (path: /sys/devices/virtual/net/veth0a25095, iface: veth0a25095): no ifupdown configuration found.
  72. Mar 14 21:28:18 maude NetworkManager[904]: <info> [1584221298.1561] devices added (path: /sys/devices/virtual/net/vethbcf80f1, iface: vethbcf80f1)
  73. Mar 14 21:28:18 maude NetworkManager[904]: <info> [1584221298.1561] device added (path: /sys/devices/virtual/net/vethbcf80f1, iface: vethbcf80f1): no ifupdown configuration found.
  74. Mar 14 21:28:18 maude kernel: [ 326.242105] eth0: renamed from vethbcf80f1
  75. Mar 14 21:28:18 maude NetworkManager[904]: <info> [1584221298.9536] devices removed (path: /sys/devices/virtual/net/vethbcf80f1, iface: vethbcf80f1)
  76. Mar 14 21:28:18 maude NetworkManager[904]: <info> [1584221298.9538] device (vethbcf80f1): driver 'veth' does not support carrier detection.
  77. Mar 14 21:28:18 maude NetworkManager[904]: <info> [1584221298.9540] device (veth0a25095): link connected
  78. Mar 14 21:28:18 maude kernel: [ 326.274041] IPv6: ADDRCONF(NETDEV_CHANGE): veth0a25095: link becomes ready
  79. Mar 14 21:28:18 maude kernel: [ 326.274089] br-6dc93588b52a: port 2(veth0a25095) entered blocking state
  80. Mar 14 21:28:18 maude kernel: [ 326.274091] br-6dc93588b52a: port 2(veth0a25095) entered forwarding state
  81. Mar 14 21:28:19 maude kernel: [ 326.866060] kvm: disabled by bios
  82. Mar 14 21:28:19 maude kernel: [ 326.932840] kvm: disabled by bios
  83. Mar 14 21:28:19 maude kernel: [ 327.015437] kvm: disabled by bios
  84. Mar 14 21:28:19 maude kernel: [ 327.115463] kvm: disabled by bios
  85. Mar 14 21:28:19 maude kernel: [ 327.183303] kvm: disabled by bios
  86. Mar 14 21:28:19 maude kernel: [ 327.235301] kvm: disabled by bios
  87. Mar 14 21:28:19 maude kernel: [ 327.283799] kvm: disabled by bios
  88. Mar 14 21:28:20 maude kernel: [ 327.335466] kvm: disabled by bios
  89. Mar 14 21:29:05 maude gnome-session-binary[9308]: Entering running state
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
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!