spall

Hallo, I'm having this issue again, too (as expected seeing the comment here). What's the proper way of reverting to the prior version until a fix is rolled in? I've never had a good handle on that process. Thanks!

EDIT: Saw there was another update push. Problem solved on my end. Thanks! Hallo, I'm having the same issue as cheese_man. Updated 10 minutes ago and cannot connect anymore. Snippet from log below. Any help appreciated! -S 2017-04-15 16:14:36,669 DEBG 'nzbget' stderr output: /usr/bin/nzbget: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory 2017-04-15 16:14:36,669 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47043699021008 for <Subprocess at 47043699021512 with name nzbget in state STARTING> (stdout)> 2017-04-15 16:14:36,669 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47043699225016 for <Subprocess at 47043699021512 with name nzbget in state STARTING> (stderr)> 2017-04-15 16:14:36,669 INFO exited: nzbget (exit status 127; not expected) 2017-04-15 16:14:36,669 DEBG received SIGCLD indicating a child quit 2017-04-15 16:14:39,673 INFO spawned: 'nzbget' with pid 49 2017-04-15 16:14:39,678 DEBG 'nzbget' stdout output: [info] NZBGet configuration file exists 2017-04-15 16:14:39,678 DEBG 'nzbget' stderr output: /usr/bin/nzbget: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory 2017-04-15 16:14:39,678 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47043699021008 for <Subprocess at 47043699021512 with name nzbget in state STARTING> (stdout)> 2017-04-15 16:14:39,679 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47043699224800 for <Subprocess at 47043699021512 with name nzbget in state STARTING> (stderr)> 2017-04-15 16:14:39,679 INFO exited: nzbget (exit status 127; not expected) 2017-04-15 16:14:39,679 DEBG received SIGCLD indicating a child quit 2017-04-15 16:14:39,679 INFO gave up: nzbget entered FATAL state, too many start retries too quickly

First, thanks for this script I found this because I stumbled upon an empty directory in one of my shares and was looking for something to locate those. The good news: I found about 250GB of duplicate files I had no idea existed. So again, thank you. The bad news: I cannot for the life of me get the -f/-F args to produce anything. I created a duplicate folder on the chance that the one I stumbled on was the only one, but it is not being reported by the script. Any help appreciated, Thanks!