ich777 Posted March 6, 2023 Share Posted March 6, 2023 20 minutes ago, Coco said: Should I just uninstall unmanic? I would recommend that you post that in the Unmanic support forum so that this gets resolved. 1 Quote Link to comment
Coco Posted March 6, 2023 Author Share Posted March 6, 2023 Ok I'll give it a try. Thx I stopped unmanic and monitoring to see if error is really cause by it. 1 Quote Link to comment
Coco Posted March 7, 2023 Author Share Posted March 7, 2023 9 hours ago, ich777 said: No. Try to not auto start it on boot and see if you can spot the python3 messages in your syslog, if you don't see any such messages try to start it and watch out the messages from above. It could also be the case that is another container which uses pyhton3 since you don't have python3 installed on the host. Ok, so my server been running for a few more hours, with unmanic stopped and the error just showed up again python3[14323]: segfault at ffffffffffffffe8 ip 00001546f913a38a sp 0000154703dc1168 error 5 in libstdc++.so.6.0.30[1546f90b0000+119000] Mar 6 19:58:23 Jarvis kernel: Code: ed 10 00 4c 89 e7 48 83 c0 10 48 89 43 18 e8 5d 64 f7 ff 48 89 ef e8 15 a6 f7 ff 0f 1f 44 00 00 f3 0f 1e fa 48 8b 06 48 89 07 <48> 8b 40 e8 48 8b 56 28 48 89 14 07 48 8b 46 30 48 89 47 10 48 8b Mar 6 19:58:32 Jarvis kernel: python3[27662]: segfault at ffffffffffffffe8 ip 000014f1dd13a38a sp 000014f1e5f44168 error 5 in libstdc++.so.6.0.30[14f1dd0b0000+119000] Mar 6 19:58:32 Jarvis kernel: Code: ed 10 00 4c 89 e7 48 83 c0 10 48 89 43 18 e8 5d 64 f7 ff 48 89 ef e8 15 a6 f7 ff 0f 1f 44 00 00 f3 0f 1e fa 48 8b 06 48 89 07 <48> 8b 40 e8 48 8b 56 28 48 89 14 07 48 8b 46 30 48 89 47 10 48 8b Mar 6 19:58:46 Jarvis kernel: python3[30805]: segfault at 0 ip 0000000000000000 sp 00001544b7571fb8 error 14 Mar 6 19:58:46 Jarvis kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6. Mar 6 19:58:53 Jarvis kernel: python3[2886]: segfault at ffffffffffffffe8 ip 000014c1b653a38a sp 000014c1c0a4b168 error 5 in libstdc++.so.6.0.30[14c1b64b0000+119000 Any idea? jarvis-diagnostics-20230306-2018.zip Quote Link to comment
ich777 Posted March 7, 2023 Share Posted March 7, 2023 4 hours ago, Coco said: Any idea? Then it seems to me that this isn‘t caused Unmanic. Can you stop all your containers and enable it one by one so that you can isolate the issue and which container is causing this? 1 Quote Link to comment
Coco Posted March 7, 2023 Author Share Posted March 7, 2023 6 hours ago, ich777 said: Then it seems to me that this isn‘t caused Unmanic. Can you stop all your containers and enable it one by one so that you can isolate the issue and which container is causing this? Yes guess that is the only option. I'll get on that. Strange that it just started to do that out of no where. Wonder if I should reinstall them all, maybe something got corrupted or something. Quote Link to comment
ich777 Posted March 7, 2023 Share Posted March 7, 2023 17 minutes ago, Coco said: Wonder if I should reinstall them all, maybe something got corrupted or something. Please try to start them one by one and see which one is causing this issue. 1 Quote Link to comment
Coco Posted March 7, 2023 Author Share Posted March 7, 2023 3 hours ago, ich777 said: Please try to start them one by one and see which one is causing this issue. Currently trying to restart dockers one at the time, waiting an hour in between each. This is going to take a while. 3 started so far have not seen the error. What worry me with this is that yesterday many hours passed before the error pop up. What if I only see it once they are all started? Well we will see. Thx for your help Quote Link to comment
Coco Posted March 7, 2023 Author Share Posted March 7, 2023 Wow, Still monitoring dockers, started bazaar and the error appeared, tried to duplicate but it doesn't want to appear after stopping/ starting bazaar. Now also getting a new one ????? Mar 7 14:06:41 Jarvis nginx: 2023/03/07 14:06:41 [error] 28931#28931: OCSP responder prematurely closed connection while requesting certificate status, Any idea what this one is? Man, what's going on with my server, I haven't change a thing and all seem to be going FUBAR !!! jarvis-diagnostics-20230307-1410.zip Quote Link to comment
Coco Posted March 7, 2023 Author Share Posted March 7, 2023 2 hours ago, Coco said: Wow, Still monitoring dockers, started bazaar and the error appeared, tried to duplicate but it doesn't want to appear after stopping/ starting bazaar. Now also getting a new one ????? Mar 7 14:06:41 Jarvis nginx: 2023/03/07 14:06:41 [error] 28931#28931: OCSP responder prematurely closed connection while requesting certificate status, Any idea what this one is? Man, what's going on with my server, I haven't change a thing and all seem to be going FUBAR !!! jarvis-diagnostics-20230307-1410.zip 185.7 kB · 0 downloads Fixed the nginx error, had to change DNS server to 8.8.8.8, for some reason it didn't like 1.1.1.1 anymore and reinstalled the my server plugin. Error is now gone Still monitoring for the python3 error, so hard to spot since it occurs not on docker startup but after a while running, I order to be sure to spot it, I would have to start a container, let it run for a day. Then start another one. This is going to take for ever Quote Link to comment
Coco Posted March 8, 2023 Author Share Posted March 8, 2023 16 hours ago, Coco said: Wow, Still monitoring dockers, started bazaar and the error appeared, tried to duplicate but it doesn't want to appear after stopping/ starting bazaar. Now also getting a new one ????? Mar 7 14:06:41 Jarvis nginx: 2023/03/07 14:06:41 [error] 28931#28931: OCSP responder prematurely closed connection while requesting certificate status, Any idea what this one is? Man, what's going on with my server, I haven't change a thing and all seem to be going FUBAR !!! jarvis-diagnostics-20230307-1410.zip 185.7 kB · 0 downloads Fixed the nginx error, had to change DNS server to 8.8.8.8, for some reason it didn't like 1.1.1.1 anymore and reinstalled the my server plugin. Error is now gone Still monitoring for the python3 error, so hard to spot since it occurs not on docker startup but after a while running, I order to be sure to spot it, I would have to start a container, let it run for a day. Then start another one. This is going to take for ever Quote Link to comment
Coco Posted March 8, 2023 Author Share Posted March 8, 2023 23 hours ago, ich777 said: Please try to start them one by one and see which one is causing this issue. Ok, Last night the error showed up had a doubt that bazaar was causing it cause the error poped up earlier when I started but wouldn't come back when I stopped and started. So I stopped bazaar just prior to bed time and the python3 error did not show up at all. Now to start uanic to see if it come back. I'll keep you posted. Thx 1 Quote Link to comment
Coco Posted March 9, 2023 Author Share Posted March 9, 2023 It now has been almost 24 hours that unmanic have been running. No python3 error. Also almost 24 hours since a stop bazaar. No python error. I think it is safe to say that bazaar was causing the error. Not a big thing since I wasn't really using it anyway. 24 hours without any errors on my log. Feels good. Thanks for all you help and advice. Now to figure out how to close this post. Your a savior ich!!! Thx again 1 Quote Link to comment
ich777 Posted March 9, 2023 Share Posted March 9, 2023 12 minutes ago, Coco said: Now to figure out how to close this post. Leave it as it is, you've already marked it as solved. Please let the maintainer from your Bazarr container know that you have those issues caused by Bazarr in your syslog, maybe he can help. Quote Link to comment
Coco Posted March 9, 2023 Author Share Posted March 9, 2023 Yep will do. Thx again. For all your help really appreciated! 1 Quote Link to comment
Coco Posted March 16, 2023 Author Share Posted March 16, 2023 Hello, Just to give an update since last time. So I did go and change the docker network from macvlan to Ipvlan. Worked for a bit untill I started losing Internet connection from my unraid server. Turns out, my unraid server IP was changing, taking whatever last docker IP that started last. So I changed back the docker settings to macvlan. Did ich777 suggested solved to stop the avahi service. And I am now going on 4 days with 0 errors in the log. Just wanted to post this in case someone else come through this. The other issues I had were all related to this. The my server plugin stopping working, server crashing, server GUI unresponsive.... All because my router was giving my unraid server the ip adress of last docker container that had started. So thank @ich777for the solution and all the help. as for the python3 error, did not see it since I uninstalled bazaar. Since I don't really need it right now, not a major problem but might be later anyway, all that to say thank you to @ich777 . Your the best !!! 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.