spectralforce

unraid 3 13 19

Mar 13th, 2019
149
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.15 KB | None | 0 0
  1. ErrorWarningSystemArrayLogin
  2.  
  3.  
  4. Mar 12 21:50:00 tower root: Fix Common Problems: Error: Unable to communicate with GitHub.com
  5. Mar 12 21:50:00 tower root: Fix Common Problems: Other Warning: Could not check for blacklisted plugins
  6. Mar 12 21:50:00 tower root: Fix Common Problems: Other Warning: Could not perform unknown plugins installed checks
  7. Mar 12 21:50:00 tower ntpd[1829]: Listen normally on 8 br0 [fe80::38b3:97ff:feec:ef2c%10]:123
  8. Mar 12 21:50:00 tower ntpd[1829]: new interface(s) found: waking up resolver
  9. Mar 12 21:50:01 tower root: Fix Common Problems: Other Warning: Could not perform docker application port tests
  10. Mar 12 21:50:05 tower dhcpcd[1773]: br0: probing for an IPv4LL address
  11. Mar 12 21:50:08 tower kernel: r8169 0000:25:00.0 eth0: link down
  12. Mar 12 21:50:08 tower kernel: bond0: link status definitely down for interface eth0, disabling it
  13. Mar 12 21:50:08 tower kernel: device eth0 left promiscuous mode
  14. Mar 12 21:50:08 tower kernel: bond0: now running without any active interface!
  15. Mar 12 21:50:08 tower kernel: br0: port 1(bond0) entered disabled state
  16. Mar 12 21:50:09 tower dhcpcd[1773]: br0: carrier lost
  17. Mar 12 21:50:10 tower ntpd[1829]: Deleting interface #8 br0, fe80::38b3:97ff:feec:ef2c%10#123, interface stats: received=0, sent=0, dropped=0, active_time=10 secs
  18. Mar 12 21:50:11 tower kernel: r8169 0000:25:00.0 eth0: link up
  19. Mar 12 21:50:11 tower kernel: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex
  20. Mar 12 21:50:11 tower kernel: bond0: making interface eth0 the new active one
  21. Mar 12 21:50:11 tower kernel: device eth0 entered promiscuous mode
  22. Mar 12 21:50:11 tower dhcpcd[1773]: br0: carrier acquired
  23. Mar 12 21:50:11 tower kernel: bond0: first active interface up!
  24. Mar 12 21:50:11 tower kernel: br0: port 1(bond0) entered blocking state
  25. Mar 12 21:50:11 tower kernel: br0: port 1(bond0) entered forwarding state
  26. Mar 12 21:50:11 tower dhcpcd[1773]: br0: soliciting a DHCP lease
  27. Mar 12 21:50:12 tower dhcpcd[1773]: br0: offered 192.168.1.211 from 192.168.1.1
  28. Mar 12 21:50:12 tower dhcpcd[1773]: br0: probing address 192.168.1.211/24
  29. Mar 12 21:50:12 tower ntpd[1829]: Listen normally on 9 br0 [fe80::38b3:97ff:feec:ef2c%10]:123
  30. Mar 12 21:50:12 tower ntpd[1829]: new interface(s) found: waking up resolver
  31. Mar 12 21:50:17 tower dhcpcd[1773]: br0: leased 192.168.1.211 for 600 seconds
  32. Mar 12 21:50:17 tower avahi-daemon[9271]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.211.
  33. Mar 12 21:50:17 tower avahi-daemon[9271]: New relevant interface br0.IPv4 for mDNS.
  34. Mar 12 21:50:17 tower dhcpcd[1773]: br0: adding route to 192.168.1.0/24
  35. Mar 12 21:50:17 tower dhcpcd[1773]: br0: adding default route via 192.168.1.1
  36. Mar 12 21:50:17 tower avahi-daemon[9271]: Registering new address record for 192.168.1.211 on br0.IPv4.
  37. Mar 12 21:50:17 tower dnsmasq[11534]: reading /etc/resolv.conf
  38. Mar 12 21:50:17 tower dnsmasq[11534]: using nameserver 192.168.1.1#53
  39. Mar 12 21:50:18 tower ntpd[1829]: Listen normally on 10 br0 192.168.1.211:123
  40. Mar 12 21:50:18 tower ntpd[1829]: new interface(s) found: waking up resolver
  41. Mar 12 21:58:10 tower root: Fix Common Problems Version 2019.03.10
  42. Mar 12 21:59:43 tower emhttpd: req (5): timeZone=America%2FNew_York&USE_NTP=no&newDateTime=2019-03-12+21%3A59%3A31&setDateTime=Apply&csrf_token=****************
  43. Mar 12 21:59:43 tower emhttpd: shcmd (127): ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime-copied-from
  44. Mar 12 21:59:43 tower emhttpd: shcmd (128): cp /etc/localtime-copied-from /etc/localtime
  45. Mar 12 21:59:43 tower emhttpd: shcmd (129): /usr/local/emhttp/webGui/scripts/update_access
  46. Mar 12 21:59:43 tower sshd[9050]: Received signal 15; terminating.
  47. Mar 12 21:59:44 tower sshd[11549]: Server listening on 0.0.0.0 port 22.
  48. Mar 12 21:59:44 tower sshd[11549]: Server listening on :: port 22.
  49. Mar 12 21:59:45 tower emhttpd: shcmd (130): /etc/rc.d/rc.ntpd stop
  50. Mar 12 21:59:45 tower ntpd[1829]: ntpd exiting on signal 1 (Hangup)
  51. Mar 12 21:59:45 tower ntpd[1829]: 127.127.1.0 local addr 127.0.0.1 -> <null>
  52. Mar 12 21:59:45 tower ntpd[1829]: 216.239.35.0 local addr 192.168.1.211 -> <null>
  53. Mar 12 21:59:45 tower ntpd[1829]: 216.239.35.4 local addr 192.168.1.211 -> <null>
  54. Mar 12 21:59:45 tower ntpd[1829]: 216.239.35.8 local addr 192.168.1.211 -> <null>
  55. Mar 12 21:59:45 tower ntpd[1829]: 216.239.35.12 local addr 192.168.1.211 -> <null>
  56. Mar 12 21:59:45 tower root: Stopping NTP daemon...
  57. Mar 12 21:59:45 tower emhttpd: shcmd (131): date -s '2019-03-12 21:59:31'
  58. Mar 12 21:59:31 tower root: Tue Mar 12 21:59:31 EDT 2019
  59. Mar 12 21:59:31 tower emhttpd: shcmd (132): hwclock --utc --systohc --noadjfile
  60. Mar 12 21:59:31 tower nginx: 2019/03/12 21:59:31 [error] 9370#9370: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen.
  61. Mar 12 21:59:32 tower nginx: 2019/03/12 21:59:32 [error] 9370#9370: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen.
  62. Mar 12 21:59:42 tower emhttpd: req (6): timeZone=America%2FNew_York&USE_NTP=yes&NTP_SERVER1=time1.google.com&NTP_SERVER2=time2.google.com&NTP_SERVER3=time3.google.com&NTP_SERVER4=time4.google.com&setDateTime=Apply&csrf_token=****************
  63. Mar 12 21:59:42 tower emhttpd: shcmd (133): ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime-copied-from
  64. Mar 12 21:59:42 tower emhttpd: shcmd (134): cp /etc/localtime-copied-from /etc/localtime
  65. Mar 12 21:59:42 tower emhttpd: shcmd (135): /usr/local/emhttp/webGui/scripts/update_access
  66. Mar 12 21:59:42 tower sshd[11549]: Received signal 15; terminating.
  67. Mar 12 21:59:43 tower sshd[11971]: Server listening on 0.0.0.0 port 22.
  68. Mar 12 21:59:43 tower sshd[11971]: Server listening on :: port 22.
  69. Mar 12 21:59:44 tower emhttpd: shcmd (136): /etc/rc.d/rc.ntpd restart
  70. Mar 12 21:59:44 tower root: Stopping NTP daemon...
  71. Mar 12 21:59:45 tower ntpd[12050]: ntpd [email protected] Thu Aug 16 17:20:22 UTC 2018 (1): Starting
  72. Mar 12 21:59:45 tower ntpd[12050]: Command line: /usr/sbin/ntpd -g -u ntp:ntp
  73. Mar 12 21:59:45 tower root: Starting NTP daemon: /usr/sbin/ntpd -g -u ntp:ntp
  74. Mar 12 21:59:45 tower ntpd[12052]: proto: precision = 0.050 usec (-24)
  75. Mar 12 21:59:45 tower ntpd[12052]: Listen normally on 0 lo 127.0.0.1:123
  76. Mar 12 21:59:45 tower ntpd[12052]: Listen normally on 1 br0 192.168.1.211:123
  77. Mar 12 21:59:45 tower ntpd[12052]: Listen normally on 2 lo [::1]:123
  78. Mar 12 21:59:45 tower ntpd[12052]: Listen normally on 3 br0 [fe80::38b3:97ff:feec:ef2c%10]:123
  79. Mar 12 21:59:45 tower ntpd[12052]: Listening on routing socket on fd #20 for interface updates
  80. Mar 12 21:59:45 tower ntpd[12052]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
  81. Mar 12 21:59:45 tower ntpd[12052]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
  82. Mar 12 22:00:09 tower ntpd[12052]: receive: Unexpected origin timestamp 0xe032e29a.c700f128 does not match aorg 0000000000.00000000 from [email protected] xmt 0xe032e2a9.2b8121d9
  83. Mar 12 22:00:09 tower ntpd[12052]: receive: Unexpected origin timestamp 0xe032e29a.c701b7fd does not match aorg 0000000000.00000000 from [email protected] xmt 0xe032e2a9.2b8253e2
  84. Mar 12 22:05:50 tower ntpd[12052]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
Advertisement
Add Comment
Please, Sign In to add comment