Lebowski Posted August 2, 2019 Share Posted August 2, 2019 Been running my second unRaid machine for months without any hiccups, found that it had locked up with the following error on the screen Any suggestions to what this could be? I was not able to ping it or anything like that. Its reset and working okay again. Quote Link to comment
Xaero Posted August 2, 2019 Share Posted August 2, 2019 (edited) 39 minutes ago, Lebowski said: Been running my second unRaid machine for months without any hiccups, found that it had locked up with the following error on the screen Any suggestions to what this could be? I was not able to ping it or anything like that. Its reset and working okay again. See this thread: If you have any dockers with manually assigned IP addresses, try disabling those dockers and see if the issue persists. The line starting with R I P : is your hint. nf_nat_setup_info belongs to netfilter, so the party responsible for causing this crash is also netfilter. I think this is used by docker to assign the ip addresses internally - which would explain this behavior both in the linked post, and in your case. It's not up to limetech to fix this - but they should be aware of this issue. Also see this defect report: Edited August 2, 2019 by Xaero 1 Quote Link to comment
Lebowski Posted August 4, 2019 Author Share Posted August 4, 2019 (edited) Cheers, thank you I am running Pi-Hole docker, that may be the culprit. Edited August 4, 2019 by Lebowski Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.