WonkoTheSane

Hi all, I apologize if this has been answered before. I've recently added some cleanup code to some of my scripts allowing me to roll back stuff in case a script gets interrupted, say when closing the script window when the script is running in the foreground. What I've discovered is that since implementing this, those scripts no longer appear to be working when executed in the background/scheduled. Is this a known issue? Is there a way to fix this or is trapping signals just not supported in this scenario? Best Matthias

@ChatNoir: Thanks, it works now.

The forum seems to be experiencing some problems. The upload of my diagnostics archive keeps failing. I'll try again later.

Hi all, my server has been stable for about a year. After a BIOS update, I'm seeing frequent crashes, meaning the server is completely inaccessible, can't even be pinged anymore. In order to isolate the issue, I've fiddled with a couple of BIOS settings and stopped using my VMs, but the problem remains. I'm attaching my diagnostics to this message, hopefully someone will be able to help. Thanks & best regards Matthias nasferatu-diagnostics-20220130-0834.zip

Hi again, what I don't understand is this. When I go to the unraid main tab, I see the "Please wait, retrieving information ..." message from unassigned devices. This takes forever, in the syslog I see this: These are obviously all timing out, so something is definetly up. When I connect to the unraid server running unassigned devices via ssh and manually mount one of those NFS shares, it works without a problem in these situations. I can list the contents of the share and copy stuff to/from it. So the server is not offline but somehow the mounts done by unassigned devices become inaccessible after a while. I'm not sure where to go from here. Adding to this: When I do a lazy unmount of the unassigned devices mounts I'm afterwards able to remount them again with the mount buttons on the unraid main page.

Alright, here's the diagnostics. Thanks for looking into it. diagnostics.zip

Update: I downgraded both my servers back to v. 6.5.3 and the problem persists. Let me know if you need specific information/logs.

Done. Thank you!

Hi all, since the unraid 6.6.0 update I've been having issues with NFS shares mounted by the unassigned devices plugin. I've got 2 unraid servers. Server B mounts a couple of NFS shares on server A and runs a number of rsync scripts on a schedule to push new/modified files to server A. It looks like these NFS mounts become "stale" pretty quickly. Right after a server reboot manually triggering my sync scripts works just fine. A day later, rsync hangs at "sending incremental file list" and I'm unable to "cd" to the NFS mount points. Any clues on how to fix this problem are appreciated. I'm currently on unraid 6.6.1 on both of my servers. Unassigned devices plugin version is 2018.09.23. Also, I'm still able to manually mount the NFS shares from the command line. Cheers!

Hi all, I had to rollback from latest to 2.3.3-1-01 since sabnzbd was unable to resolve the names of my usenet servers. Did I miss anything about some configuration changes required on my part or is this a known issue?

Hi all, I just updated my sabnzbd container and it does not seem to be working any more. Here is the log, any help is appreciated. 2017-05-24 21:06:20,185 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,185::INFO::[SABnzbd:1275] SSL supported protocols ['TLS v1.2', 'TLS v1.1', 'TLS v1']2017-05-24 21:06:20,189 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,188::INFO::[SABnzbd:1386] Starting web-interface on 0.0.0.0:80902017-05-24 21:06:20,189 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,189::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Bus STARTING2017-05-24 21:06:20,193 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,192::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Started monitor thread '_TimeoutMonitor'.2017-05-24 21:06:20,357 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,357::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Serving on http://0.0.0.0:80802017-05-24 21:06:20,359 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,358::ERROR::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Error in 'start' listener <bound method Server.start of <cherrypy._cpserver.Server object at 0x2b1999457950>>Traceback (most recent call last):File "/opt/sabnzbd/cherrypy/process/wspbus.py", line 207, in publishoutput.append(listener(*args, **kwargs))File "/opt/sabnzbd/cherrypy/_cpserver.py", line 167, in startself.httpserver, self.bind_addr = self.httpserver_from_self()File "/opt/sabnzbd/cherrypy/_cpserver.py", line 158, in httpserver_from_selfhttpserver = _cpwsgi_server.CPWSGIServer(self)File "/opt/sabnzbd/cherrypy/_cpwsgi_server.py", line 64, in __init__self.server_adapter.ssl_certificate_chain)File "/opt/sabnzbd/cherrypy/wsgiserver/ssl_builtin.py", line 56, in __init__self.context.load_cert_chain(certificate, private_key)SSLError: [SSL: CA_MD_TOO_WEAK] ca md too weak (_ssl.c:2699)2017-05-24 21:06:20,359 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,359::ERROR::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Shutting down due to error in start listener:Traceback (most recent call last):File "/opt/sabnzbd/cherrypy/process/wspbus.py", line 245, in startself.publish('start')File "/opt/sabnzbd/cherrypy/process/wspbus.py", line 225, in publishraise excChannelFailures: SSLError(336245134, u'[SSL: CA_MD_TOO_WEAK] ca md too weak (_ssl.c:2699)')2017-05-24 21:06:20,359 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,359::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Bus STOPPING2017-05-24 21:06:20,361 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,361::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 8080)) shut down2017-05-24 21:06:20,361 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,361::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE HTTP Server None already shut down2017-05-24 21:06:20,361 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,361::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Stopped thread '_TimeoutMonitor'.2017-05-24 21:06:20,361 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,361::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Bus STOPPED2017-05-24 21:06:20,362 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,361::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Bus EXITING2017-05-24 21:06:20,362 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,362::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Bus EXITED2017-05-24 21:06:20,364 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47147513872536 for <Subprocess at 47147433790064 with name sabnzbd in state STARTING> (stdout)>2017-05-24 21:06:20,364 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47147513480472 for <Subprocess at 47147433790064 with name sabnzbd in state STARTING> (stderr)>2017-05-24 21:06:20,364 INFO exited: sabnzbd (exit status 70; not expected)2017-05-24 21:06:20,364 DEBG received SIGCLD indicating a child quit2017-05-24 21:06:21,365 INFO gave up: sabnzbd entered FATAL state, too many start retries too quickly

*I just realized I posted to the wrong thread. Sorry about that. Hi all, I just updated my sabnzbd container and it does not seem to be working any more. Here is the log, any help is appreciated. 2017-05-24 21:06:20,185 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,185::INFO::[SABnzbd:1275] SSL supported protocols ['TLS v1.2', 'TLS v1.1', 'TLS v1']2017-05-24 21:06:20,189 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,188::INFO::[SABnzbd:1386] Starting web-interface on 0.0.0.0:80902017-05-24 21:06:20,189 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,189::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Bus STARTING2017-05-24 21:06:20,193 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,192::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Started monitor thread '_TimeoutMonitor'.2017-05-24 21:06:20,357 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,357::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Serving on http://0.0.0.0:80802017-05-24 21:06:20,359 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,358::ERROR::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Error in 'start' listener <bound method Server.start of <cherrypy._cpserver.Server object at 0x2b1999457950>>Traceback (most recent call last):File "/opt/sabnzbd/cherrypy/process/wspbus.py", line 207, in publishoutput.append(listener(*args, **kwargs))File "/opt/sabnzbd/cherrypy/_cpserver.py", line 167, in startself.httpserver, self.bind_addr = self.httpserver_from_self()File "/opt/sabnzbd/cherrypy/_cpserver.py", line 158, in httpserver_from_selfhttpserver = _cpwsgi_server.CPWSGIServer(self)File "/opt/sabnzbd/cherrypy/_cpwsgi_server.py", line 64, in __init__self.server_adapter.ssl_certificate_chain)File "/opt/sabnzbd/cherrypy/wsgiserver/ssl_builtin.py", line 56, in __init__self.context.load_cert_chain(certificate, private_key)SSLError: [SSL: CA_MD_TOO_WEAK] ca md too weak (_ssl.c:2699)2017-05-24 21:06:20,359 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,359::ERROR::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Shutting down due to error in start listener:Traceback (most recent call last):File "/opt/sabnzbd/cherrypy/process/wspbus.py", line 245, in startself.publish('start')File "/opt/sabnzbd/cherrypy/process/wspbus.py", line 225, in publishraise excChannelFailures: SSLError(336245134, u'[SSL: CA_MD_TOO_WEAK] ca md too weak (_ssl.c:2699)')2017-05-24 21:06:20,359 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,359::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Bus STOPPING2017-05-24 21:06:20,361 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,361::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 8080)) shut down2017-05-24 21:06:20,361 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,361::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE HTTP Server None already shut down2017-05-24 21:06:20,361 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,361::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Stopped thread '_TimeoutMonitor'.2017-05-24 21:06:20,361 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,361::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Bus STOPPED2017-05-24 21:06:20,362 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,361::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Bus EXITING2017-05-24 21:06:20,362 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,362::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Bus EXITED2017-05-24 21:06:20,364 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47147513872536 for <Subprocess at 47147433790064 with name sabnzbd in state STARTING> (stdout)>2017-05-24 21:06:20,364 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47147513480472 for <Subprocess at 47147433790064 with name sabnzbd in state STARTING> (stderr)>2017-05-24 21:06:20,364 INFO exited: sabnzbd (exit status 70; not expected)2017-05-24 21:06:20,364 DEBG received SIGCLD indicating a child quit2017-05-24 21:06:21,365 INFO gave up: sabnzbd entered FATAL state, too many start retries too quickly