-- adjusted the title to better reflect the issue

 

Edit: Below issue seem to be with the Photoprism app / container.

 

Hi folks,

 

since couple of hours my system log is full of these entries.

 

Nov 29 21:18:08 Ryzen kernel: eth0: renamed from veth49cafcb
Nov 29 21:18:10 Ryzen kernel: veth49cafcb: renamed from eth0
Nov 29 21:19:11 Ryzen kernel: eth0: renamed from veth0124e07
Nov 29 21:19:13 Ryzen kernel: veth0124e07: renamed from eth0
Nov 29 21:20:15 Ryzen kernel: eth0: renamed from vethb387d3f
Nov 29 21:20:17 Ryzen kernel: vethb387d3f: renamed from eth0
Nov 29 21:21:18 Ryzen kernel: eth0: renamed from vethb1a6ac2
Nov 29 21:21:20 Ryzen kernel: vethb1a6ac2: renamed from eth0
Nov 29 21:22:22 Ryzen kernel: eth0: renamed from vetha2266bd
Nov 29 21:22:24 Ryzen kernel: vetha2266bd: renamed from eth0
Nov 29 21:23:25 Ryzen kernel: eth0: renamed from veth9335967
Nov 29 21:23:28 Ryzen kernel: veth9335967: renamed from eth0
Nov 29 21:24:05 Ryzen kernel: vethd93d4cd: renamed from eth0

 

How can I troubleshoot this? How can I get the full system log from last 24hrs on UnRaid?

 

Not sure if this is related, but I have a Pihole instance which I had to stop today since it seem to be broken, however this renaming keept going for hours and hours.

I stopped the heimdall container and it seems like the renaming stopped now. Can the renaming have an effect on Pihole?

 

Any advise how to pin this down?

 

Thanks!

Edited November 30, 20205 yr by doesntaffect
Adjusted the title to better reflect the issue

Those messages are normal if a container restarts

well, then it looks like several container are constantly restarting. Is this a default?

I troubleshooted this further and it seems like the Photoprism container which I am running is causing the trouble.

 

The container log says:

fatal msg="can't create /photoprism/storage/sidecar: please check configuration and permissions"

 

The container does start, however I cannot access the webinterface or start a terminal - How do I troubleshoot the permissions on UnRaid? Afaik I didnt touch anything regarding the container.

Other container like NextCloud are running fine.

 

Trying to start a terminal adds following to the system log:

 

Nov 30 12:10:08 Ryzen nginx: 2020/11/30 12:10:08 [error] 4096#4096: *662414 connect() to unix:/var/tmp/PhotoPrism.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.178.32, server: , request: "GET /dockerterminal/PhotoPrism/token HTTP/1.1", upstream: "http://unix:/var/tmp/PhotoPrism.sock:/token", host: "ryzen", referrer: "http://ryzen/dockerterminal/PhotoPrism/"

 

 

Edited November 30, 20205 yr by doesntaffect