jace5869
-
Posts
14 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by jace5869
-
-
I kept ipvlan but turned off host access...fixed me
-
Seems strange we are having the same issue and it be LAN.
-
Closely following I will try some of this.
Got two 10g marvel nics coming to try
-
26 minutes ago, Astatine said:
I went through the logs and I don't know why but the following logs seem out of place to me. Maybe it's just that I don't understand what they are for.
Mar 12 18:22:08 astatine avahi-daemon[3663]: Joining mDNS multicast group on interface veth44611d6.IPv6 with address fe80::c026:5fff:feaf:d7c6. Mar 12 18:22:08 astatine avahi-daemon[3663]: New relevant interface veth44611d6.IPv6 for mDNS. Mar 12 18:22:08 astatine avahi-daemon[3663]: Registering new address record for fe80::c026:5fff:feaf:d7c6 on veth44611d6.*. Mar 12 18:22:08 astatine kernel: docker0: port 7(vethb2fb7ee) entered blocking state Mar 12 18:22:08 astatine kernel: docker0: port 7(vethb2fb7ee) entered disabled state Mar 12 18:22:08 astatine kernel: device vethb2fb7ee entered promiscuous mode Mar 12 18:22:08 astatine kernel: docker0: port 7(vethb2fb7ee) entered blocking state Mar 12 18:22:08 astatine kernel: docker0: port 7(vethb2fb7ee) entered forwarding state Mar 12 18:22:08 astatine kernel: eth0: renamed from veth19a3a37 Mar 12 18:22:08 astatine kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb2fb7ee: link becomes ready Mar 12 18:22:08 astatine rc.docker: linkding: started succesfully! Mar 12 18:22:09 astatine avahi-daemon[3663]: Joining mDNS multicast group on interface vethbadb898.IPv6 with address fe80::4cd6:26ff:fe36:9eeb. Mar 12 18:22:09 astatine avahi-daemon[3663]: New relevant interface vethbadb898.IPv6 for mDNS. Mar 12 18:22:09 astatine avahi-daemon[3663]: Registering new address record for fe80::4cd6:26ff:fe36:9eeb on vethbadb898.*. Mar 12 18:22:09 astatine avahi-daemon[3663]: Joining mDNS multicast group on interface vethb2fb7ee.IPv6 with address fe80::8835:e6ff:fe26:d1ac. Mar 12 18:22:09 astatine avahi-daemon[3663]: New relevant interface vethb2fb7ee.IPv6 for mDNS. Mar 12 18:22:09 astatine avahi-daemon[3663]: Registering new address record for fe80::8835:e6ff:fe26:d1ac on vethb2fb7ee.*. Mar 12 18:22:10 astatine avahi-daemon[3663]: Joining mDNS multicast group on interface veth02790f8.IPv6 with address fe80::28b2:6ff:fe74:20c5. Mar 12 18:22:10 astatine avahi-daemon[3663]: New relevant interface veth02790f8.IPv6 for mDNS. Mar 12 18:22:10 astatine avahi-daemon[3663]: Registering new address record for fe80::28b2:6ff:fe74:20c5 on veth02790f8.*.I see pretty much the same logs. I think it's the docker/network cleanup after power and off containers...not sure though.
-
I'm having almost the exact same issue. I keep thinking it's my realtek nics.
This totally disrupts dockers and downloaders.
I'm not sure how it could be routing when I'm using a simple fritzbox
-
the unraid-api log does show an error and I think this is caused by whatever is happening.
Perhaps the docker network is interfering? Should I change to macvlan and assign custom network and nic?
Logging in user: jace5869 <-----UNRAID-API-REPORT-----> SERVER_NAME: Bee-Tower ENVIRONMENT: production UNRAID_VERSION: 6.11.5 UNRAID_API_VERSION: 2.57.0 UNRAID_API_STATUS: running API_KEY: valid MY_SERVERS: authenticated MY_SERVERS_USERNAME: jace5869 CLOUD: STATUS: [error] ERROR [Unable to connect to https://mothership.unraid.net] MINI-GRAPH: STATUS: [ERROR] ERROR: [API Disconnected] TIMEOUT: [0.244s] </----UNRAID-API-REPORT-----> -
I've noticed that My Servers plugin doesn't connect to mothership, or however it says. Something is definitely going on.
I don't think it is a docker because they're always up.
Perhaps when my new nic gets here I will separate out the docker network and unraid one?
cancelled the intel 225v one and getting the 10gb asus one running on marvell chipset.
I will setup the syslog and hopefully capture something tonight.
-
Ordered a Intel i225-v nic that will come tomorrow. I will try that.
Pretty much lose all remote access with Plex and SAB quits downloading. This has been the most unstable build and things just worked on qnap quite frustrating.
-
Well it happened again... Apps wouldn't load after I noticed the docker *rarr apps complaining about no route to host and indexers unavailable.
Seems like if I go to Apps when this happens and let it time out it will start working after this.
-
I will do this tomorrow. I recreated the docker image as directory on nvme drive
-
-
Attaching the syslog
Seems I will sometimes lose network connectivity and it's noticeable because plex will stop working and the Apps plugin won't load anything. I've set the DNS servers manually to cloudflare, google and opendns.
I'm tempted to install another realtek 2.5gb pci e nic and a usb one to see if connections maintain or not, but this is getting a bit ridiculous with how unstable it is. IT will drop at least a couple times a day.
Model: Custom M/B: Gigabyte Technology Co., Ltd. Z790 UD AC Version x.x - s/n: Default string BIOS: American Megatrends International, LLC. Version F2. Dated: 10/11/2022 CPU: 13th Gen Intel® Core™ i5-13500 @ 2475 MHz HVM: Enabled IOMMU: Disabled Cache: 288 KiB, 192 KiB, 7680 KiB, 24 MB, 256 KiB, 512 KiB, 4 MB, 24 MB Memory: 32 GiB DDR5 (max. installable capacity 128 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 Kernel: Linux 5.19.17-Unraid x86_64 OpenSSL: 1.1.1s Uptime: -
I get the below error when trying to open Terminal and Logs. Any idea on how to fix this?
No network connectivity externally except WAN IP
in General Support
Posted
So I am having a huge problem and I've spent hours re-flashing the USB drive and deleting the /boot/config/network.cfg file and trying to get a working system.
I don't know what to do anymore. I got it working a few hours ago, but somehow it booted up with the wrong IP (I guess I left it DHCP) so when I changed the IP no container could get out and my unraid could ping out either, but oddly enough it will ping the WAN IP.
All this happened because one day I mucked around with the network settings and lost my custom docker network and all my containers wouldn't run unless put on bridge or host.
I'm literally at wits end. I've tried setting default routes and making sure everything would go out of br0.
bee-tower-diagnostics-20230415-1454.zip