Variety of questions about Syslog

[Smitty2k1]

Hey all, unRaid has been running fairly smooth but I've got a few things in the Syslog I'm unsure about:

 

Apr 26 18:05:53 Tower avahi-daemon[9261]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!

 

and also this one:

 

May  9 18:09:53 Tower root: Fix Common Problems: Error: Docker Application binhex-delugevpn, Container Port 58946 not found or changed on installed application
May  9 18:09:53 Tower root: Fix Common Problems: Error: Docker Application binhex-delugevpn, Container Port 58946 not found or changed on installed application

 

and also this one:

 

May  9 18:11:16 Tower kernel: docker0: port 1(veth7ed9424) entered disabled state
May  9 18:11:16 Tower kernel: veth3d0a169: renamed from eth0
May  9 18:11:16 Tower kernel: docker0: port 1(veth7ed9424) entered disabled state
May  9 18:11:16 Tower kernel: device veth7ed9424 left promiscuous mode
May  9 18:11:16 Tower kernel: docker0: port 1(veth7ed9424) entered disabled state
May  9 18:11:18 Tower kernel: docker0: port 1(veth6f8025c) entered blocking state
May  9 18:11:18 Tower kernel: docker0: port 1(veth6f8025c) entered disabled state
May  9 18:11:18 Tower kernel: device veth6f8025c entered promiscuous mode
May  9 18:11:18 Tower kernel: eth0: renamed from veth5f0ca19
May  9 18:11:18 Tower kernel: docker0: port 1(veth6f8025c) entered blocking state
May  9 18:11:18 Tower kernel: docker0: port 1(veth6f8025c) entered forwarding state

 

 

any thoughts on the above would be great

 

Edited May 16, 2017 by Smitty2k1

[Squid]

3 minutes ago, Smitty2k1 said:

Apr 26 18:05:53 Tower avahi-daemon[9261]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!

Standard in unRaid...  Don't worry about it.

3 minutes ago, Smitty2k1 said:

May  9 18:11:16 Tower kernel: docker0: port 1(veth7ed9424) entered disabled state
May  9 18:11:16 Tower kernel: veth3d0a169: renamed from eth0
May  9 18:11:16 Tower kernel: docker0: port 1(veth7ed9424) entered disabled state
May  9 18:11:16 Tower kernel: device veth7ed9424 left promiscuous mode
May  9 18:11:16 Tower kernel: docker0: port 1(veth7ed9424) entered disabled state
May  9 18:11:18 Tower kernel: docker0: port 1(veth6f8025c) entered blocking state
May  9 18:11:18 Tower kernel: docker0: port 1(veth6f8025c) entered disabled state
May  9 18:11:18 Tower kernel: device veth6f8025c entered promiscuous mode
May  9 18:11:18 Tower kernel: eth0: renamed from veth5f0ca19
May  9 18:11:18 Tower kernel: docker0: port 1(veth6f8025c) entered blocking state
May  9 18:11:18 Tower kernel: docker0: port 1(veth6f8025c) entered forwarding state

The docker application is starting up.  Completely normal...

4 minutes ago, Smitty2k1 said:

May  9 18:09:53 Tower root: Fix Common Problems: Error: Docker Application binhex-delugevpn, Container Port 58946 not found or changed on installed application

The template currently available from Binhex for delugevpn specifies that port 58946 should be defined.  You would have either installed it before he made that change or deleted the port for some reason.  Ask in his support thread.

[Smitty2k1]

Great thanks Squid!