Jump to content

The_Mountain

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About The_Mountain

  • Rank
    Member

Converted

  • Gender
    Undisclosed
  1. Love me some unRAID bling! Happy 14th birthday.
  2. i disabled my ipv6 on my controller and then restarted avahi-daemon and restarted docker service, and i have not seen the error since.
  3. Looking back at my syslog, and it first appeared right after loading avahi-daemon. Jul 4 06:22:17 Tower kernel: docker0: port 6(veth7d57666) entered forwarding state Jul 4 06:22:18 Tower avahi-daemon[22640]: Joining mDNS multicast group on interface veth7d57666.IPv6 with address fe80::682c:f0ff:fe8f:7f06. Jul 4 06:22:18 Tower avahi-daemon[22640]: New relevant interface veth7d57666.IPv6 for mDNS. Jul 4 06:22:18 Tower avahi-daemon[22640]: Registering new address record for fe80::682c:f0ff:fe8f:7f06 on veth7d57666.*. Jul 4 11:47:45 Tower root: error: /gcsp/2.0: missing csrf_token Jul 4 11:47:45 Tower root: error: /gcsp/2.0: missing csrf_token Jul 4 11:47:45 Tower root: error: /gcsp/2.0: missing csrf_token
  4. Being that this did not start until July 4th for me, makes me believe this is probably related to one of my docker containers, rather than the OS it self. Server has been up since the end of June but this did not start until 4-5 days later.
  5. tower-diagnostics-20190712-0658.zip Here is my diagnostics.
  6. Looking back at my logs, i am seeing it started on July 4th just before 2AM for me.
  7. Is there any reason i would not see an update available for the container when i am several versions back
  8. I am loving the new black theme.