since 6.12 hard freezes cought a call trace

20 minutes ago, nuhll said:

I dont really understand how that can be a portainer problem when it was working for,

 

I am not assigning blame, I'm just saying I know nothing about that app. As a general rule, your best bet to finding someone who does know about a specific app is to ask in that app's thread. That is all I'm saying.

 

8 minutes ago, nuhll said:

Anyway, the router is one of the most used routers in germany, i dont think thats the problem, also  i dont care, it has now a fixed ip again. I just wanted to report it incase unraid want to fix it.

 

I'm not saying the router is faulty, just that there is a configuration issue with the router. Unraid has no control over what IP it is assigned by DHCP, the router is in control. The router's DHCP configuration needs to use the same MAC address that Unraid is using.

Your earlier diagnostics showed that eth0 was assigned a static IP using the Unraid webgui (not a DHCP address). That's why I suggested editing network.cfg earlier, to preserve your static IP assignment on eth0. Since you deleted that file instead, the static assignment was lost and Unraid switched to DHCP, where the router gave it a different IP because is not configured with the correct MAC address.

 

22 minutes ago, nuhll said:

Im currently not facing any problems after removing the nic config and updating to 6.12.2. I guess well see in some days.

 

When do you want the diag, before crash, or after?

 

Great! It can wait until there is an issue you want to discuss

 

Are you by any chance using a fritzbox? I have similar problems ever since 6.12 came along. Apparently AVM is not so good with the whole vlan thing

yes, but im not using vlan...

 

also unraid is the only device i ever saw in my life which doesnt work with dhcp...

Edited June 30, 2023 by nuhll

9 minutes ago, nuhll said:

also unraid is the only device i ever saw in my life which doesnt work with dhcp...

 

Unraid works fine with DHCP

 

You simply have to make sure the router is setup to use the correct MAC address for the DHCP lease

10 minutes ago, nuhll said:

yes, but im not using vlan...

 

also unraid is the only device i ever saw in my life which doesnt work with dhcp...

Are you using docker? then I am quite certain you are using either ipvlan or macvlan

3 minutes ago, ljm42 said:

 

Unraid works fine with DHCP

 

You simply have to make sure the router is setup to use the correct MAC address for the DHCP lease

Its a consumer router,  i posted already what we can see. There is nothing to do wrong..

 

2 minutes ago, Zeze21 said:

Are you using docker? then I am quite certain you are using either ipvlan or macvlan

 

I also posted a picture that im u sing ipvlan (since thats what all suggest)

 

 

Edited June 30, 2023 by nuhll

Ok just wanted to make sure... you seem to have the same problem as I have basically. At least I am not alone in this @sonic6 seems to have the same problem.

I have posted diagnostics and description of my inital problem in the german section of the forum:

 

Thanks. The router is giving Unraid a different IP though, 192.168.0.21, right? Please look in your router's interface for that IP address and post a screenshot

That doesnt make sense, i had macvlan since years, even with fritzbox, i just switched to ipvlan AFTER those crashes.... 

3 minutes ago, ljm42 said:

Thanks. The router is giving Unraid a different IP though, 192.168.0.21, right? Please look in your router's interface for that IP address and post a screenshot

After i removed the file and restartet it didnt took the dhcp (or the fritz didnt gave the correct one - your theory), which i doubt since all other stuff worked 110% - im using these routers since 20 years.

 

Im looking thru the syslog for dhcp now...

 

Jun 26 20:14:24 Unraid-Server dnsmasq[11178]: started, version 2.89 cachesize 150
Jun 26 20:14:24 Unraid-Server dnsmasq[11178]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset no-nftset auth cryptohash DNSSEC loop-detect inotify dumpfile
Jun 26 20:14:24 Unraid-Server dnsmasq-dhcp[11178]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h

 

Jun 28 03:10:44 Unraid-Server dnsmasq[17708]: started, version 2.89 cachesize 150
Jun 28 03:10:44 Unraid-Server dnsmasq[17708]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset no-nftset auth cryptohash DNSSEC loop-detect inotify dumpfile
Jun 28 03:10:44 Unraid-Server dnsmasq-dhcp[17708]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
Jun 28 03:10:44 Unraid-Server dnsmasq-dhcp[17708]: DHCP, sockets bound exclusively to interface virbr0

 

 

Jun 29 23:56:06 Unraid-Server dhcpcd[1341]: dhcpcd-9.4.1 starting
Jun 29 23:56:06 Unraid-Server dhcpcd[1344]: DUID 00:04:ba:d0:e4:00:72:ba:11:e3:b1:7d:9c:5c:8e:87:c4:08
Jun 29 23:56:06 Unraid-Server kernel: 8021q: 802.1Q VLAN Support v1.8
Jun 29 23:56:06 Unraid-Server kernel: 8021q: adding VLAN 0 to HW filter on device bond0
Jun 29 23:56:06 Unraid-Server dhcpcd[1344]: br0: soliciting a DHCP lease
Jun 29 23:56:06 Unraid-Server kernel: NET: Registered PF_PACKET protocol family
Jun 29 23:56:06 Unraid-Server dhcpcd[1344]: br0: offered 192.168.0.21 from 192.168.0.1
Jun 29 23:56:06 Unraid-Server dhcpcd[1344]: br0: probing address 192.168.0.21/24
Jun 29 23:56:12 Unraid-Server dhcpcd[1344]: br0: leased 192.168.0.21 for 864000 seconds
Jun 29 23:56:12 Unraid-Server dhcpcd[1344]: br0: adding route to 192.168.0.0/24
Jun 29 23:56:12 Unraid-Server dhcpcd[1344]: br0: adding default route via 192.168.0.1
Jun 29 23:56:12 Unraid-Server rc.inet1: ip link set br0 up

 

maybe its really about vlan shit

 

 

13 minutes ago, nuhll said:

Jun 29 23:56:06 Unraid-Server dhcpcd[1344]: br0: offered 192.168.0.21 from 192.168.0.1

 

OK so that shows it *did* get assigned 192.168.0.21 by the router. Since it isn't the address you expected, that implies there is a MAC address mismatch. That's why I'm asking you to check the router for the for the MAC address of the system it assigned to 192.168.0.21. If that is somehow a different MAC address, *that* is the one you want to assign to 192.168.0.110

i even posted pictures from router and unraid to prove its the same... 

I know. But I'm trying to help you get to the bottom of this as we can see that the router handed out an unexpected IP. 

 

If you don't want to figure it out, you can go back to your previous config, which is Settings -> Network Settings and set a static IP. This is how the system was configured before you deleted network.cfg

yes, im already back to static ip.  thanks for all your help. il report back after next crash. seems to be quite some users with issues since 6.12

I can confirm it doesnt crash anymore, instead if just looses connectifity atleast partly (you always know when 

"Unraid-Server

Unraid API Error

CLOUD: Socket closed" shows up on top right)

Also logs show

Jul 12 19:31:32 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png
Jul 12 19:31:49 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png
Jul 12 19:33:49 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png
Jul 12 19:34:05 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png
Jul 12 19:35:54 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png
Jul 12 19:36:10 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png

 

The best thing is while it cant reach a URL IT WILL LITERALLY FREEZE unraid till it times out... network restart didnt help, i have to restart every time (sometimes once a day, sometimes it works for some days)

 

Still not a answer from devs, sad, they could atleast tell us, they know theres somethign wrong and they work on it, i dont get it.

 

Sometimes some dockers partly still work, like i can reach plex (via internet), but cant play anything. 

Edited July 12, 2023 by nuhll

No trace for me (syslog not enabled), but I do have a Kernel Panic too on 6.12.2, never had any crash before.

 

Here's a picture of the IPMI.

 

Hope you'll have a fix soon... can I rollback to 6.11 ?

 

I did rollback.

 

They label it as mayjor release, not beta, while so much is broken, cant understand. 

 

And not a single answer from dev if they work on it or not, some mods even seems to not noticing how many ppl have problems...

On 7/15/2023 at 12:22 AM, nuhll said:

I did rollback.

 

They label it as mayjor release, not beta, while so much is broken, cant understand. 

 

And not a single answer from dev if they work on it or not, some mods even seems to not noticing how many ppl have problems...

 

@ljm42 has been trying to help you so that last statement of yours is ridiculous.

If you've rolled back, there's not much we can do to help you without diagnostics after the issues occur.

 

Furthermore, when you bounce around on multiple problems in one thread, it is difficult to understand what we are trying to solve. It seems like you are frustrated and we are sorry you are having issues but also please review our Community Guidelines as your general tone and some of your comments are a bit rude. 

 

I am updating this report to retest as there is nothing we can do since you rolled back and we do not have diagnostics to inspect. 

Changed Priority to Other

I don't even have the nerve anymore to talk about this whole ...

 

Youre right lim answered, but literally NOTHING about my problem, we just chatted about the "why unraid has wrong ip" thing. This answer, came how many days after i posted this and direct sent it to you via feedback?

 

As long as unraid is working as expected all is good, but if not, your on your own, even if you provide all details and do what asked. And that is a fact.

 

If you would use as much time on threads or reviewing/answering emails you use to defend yourself (or attack me), then we wouldnt have this problem.

 

AND STILL no one answered if this problem is now fixed or not, its like im talking to a wall.

 

I dont understand it.

 

Maybe you should use a ticket system or something.

 

I see everyday the same problems with unraid since 6.12 popping up in facebook or here in the forums and it doesnt seem like you guys want to fix it (or see the problem)... and if these problems are still there, your still saying 6.12 is a major release, update.

 

-Freezing (even with ipvlan)

-"no internet" (some DNS issue)

Edited July 18, 2023 by nuhll

Hi,

Got the exact same problem, even after switching Docker to ipvlan.

I will try this :

But I won't waste much time on this and will revert to 6.11.5, with this version everything was working well and Docker was using macvlan.
Regards,

Mat