Not nzbget-server or wrong nzbget-server version

Get help, report and discuss bugs.
Post Reply
MrCorleone
Posts: 10
Joined: 05 Aug 2017, 17:35

Not nzbget-server or wrong nzbget-server version

Post by MrCorleone » 11 Aug 2017, 13:20

After migrating to new hardware, I am getting the message -

No response or invalid response (timeout, not nzbget-server or wrong nzbget-server version)

- whenever I try to execute commands.

Options that work so far are stuff like; -v, --help
Options that give me the error message are like; -Q, -C, -O, -V, etc...

It seems that whenever I want to issue commands that affect the nzbget daemon like listing the queue or history and even changing the download speeds, etc., fail with that message above.

I have tried these routes;
1. Migrating the installation from old to new hardware located at /opt/nzbget w 775 & 777
2. New installation at /opt/nzbget w 775 & 777
3. New installation with Hyper-V on different hardware w 775 & 777
4. Using systemd service and directly with nzbget -D

I am at a loss... Nothing is in the nzbget logs or sys logs, maybe its somewhere else???

**UPDATE**
Anything that interacts with nzbget while running as daemon, fails...
Anything that interacts with nzbget while running as server, succeeds...

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: Not nzbget-server or wrong nzbget-server version

Post by hugbug » 11 Aug 2017, 13:40

MrCorleone wrote:
11 Aug 2017, 13:20
Anything that interacts with nzbget while running as daemon, fails...
How do you know it's running?

MrCorleone
Posts: 10
Joined: 05 Aug 2017, 17:35

Re: Not nzbget-server or wrong nzbget-server version

Post by MrCorleone » 11 Aug 2017, 14:10

In either instance I can open the GUI and interact like normal...

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: Not nzbget-server or wrong nzbget-server version

Post by hugbug » 11 Aug 2017, 14:13

If webui works then remote commands should work. Type the whole path to nzbget binary to make sure the correct binary is executed. It seems you have multiple installations from different versions.

MrCorleone
Posts: 10
Joined: 05 Aug 2017, 17:35

Re: Not nzbget-server or wrong nzbget-server version

Post by MrCorleone » 11 Aug 2017, 17:29

Started from scratch again... This time I was able to see why.

INFO Fri Aug 11 2017 13:18:53 Script TestScript with command TestValue successful
INFO Fri Aug 11 2017 13:18:53 TestScript: No response or invalid response (timeout, not nzbget-server or wrong nzbget-server version)
INFO Fri Aug 11 2017 13:18:53 TestScript: Request sent
WARNING Fri Aug 11 2017 13:18:53 nzbget request received on port 6789 from 127.0.0.1, but username or password invalid
INFO Fri Aug 11 2017 13:18:53 TestScript: nzbget version: 19.1
INFO Fri Aug 11 2017 13:18:53 TestScript: /opt/nzbget/nzbget
INFO Fri Aug 11 2017 13:18:53 Executing script TestScript with command TestValue
INFO Fri Aug 11 2017 13:18:47 nzbget 19.1 daemon-mode

I have the configuration AuthorizedIP=127.0.0.1 ~ So it should bypass this... Here is the script that I am trying to test.

#!/bin/bash
#################################
### NZBGET POST-PROCESSING SCRIPT

# Testing

#################################
### OPTIONS ###

# Press button
#TestValue@Execute Script

### NZBGET POST-PROCESSING SCRIPT
#################################
SUCCESS=93
ERROR=94

CMD=$NZBOP_APPBIN

echo $NZBOP_APPBIN
$CMD -v
$CMD -V

exit $SUCCESS

Same message when I attempt the commands from the terminal...

:~/Documents$ /opt/nzbget/nzbget -V
Request sent
No response or invalid response (timeout, not nzbget-server or wrong nzbget-server version)

Any ideas what would cause this???

Post Reply

Who is online

Users browsing this forum: No registered users and 53 guests