When installing Sabnzb for a second time, after uninstalling and installing it in Package Center, the following message blocks the installation after downloading:

Port 8080 configured for this package is either used by another service or reserved for system. Please disable or modify the conflicting service, or contact the developer to modify the package configuration”.

I’ve checked all my DSM settings and I can’t find anything else that’s using 8080. Any chance getting this to run?

Is SABnzbd running? Did you stopped SABnzbd before uninstalling?
You should just wait a bit and try to reinstall.

Well, during the 1st installation, it told me to install the Python first. I then ran into this issue (I could not stop Sabnzb because it never came this far). When I look in the processes, I do not see any reference to Sabnzb proces (or the name must be completely different).

I have this issue for weeks already. Rebooting the Synology has no effect. I updated to DSM 4.1 beta yesterday and that also did not help.

Well, maybe you have another software using the port 8080, maybe DSM: http://www.synology.com/support/faq_show.php?q_id=299
Photo Station, Web Station : 80 (additional port can be added), 443 (HTTPS)

Just go to http://ip.of.your.nas:8080/ and see what's there

Yes, I check and uninstalled every single app, and tried installing Sabnzb without luck.

When I enter http://ipofmysynology:8080 I get:

This XML file does not appear to have any style information associated with it. The document tree is shown below.

[SOAP-ENV:Envelope xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/' xmlns:SOAP-ENC='http://schemas.xmlsoap.org/soap/encoding/' xmlns:xsi='http://www.w3.org/1999/XMLSchema-instance' xmlns:xsd='http://www.w3.org/1999/XMLSchema' xmlns:ifx='urn:dsl_api']
[SOAP-ENV:Body]
[SOAP-ENV:Fault SOAP-ENV:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/']
[faultcode>SOAP-ENV:Server</faultcode]
[faultstring>Timeout</faultstring]
[SOAP-ENV:Detail>accept failed in soap_accept()</SOAP-ENV:Detail]
[/SOAP-ENV:Fault]
[/SOAP-ENV:Body]
[/SOAP-ENV:Envelope]

(changed the < int [ to be displayed here correctly)

Well, you have a web service running on port 8080.
Check if your WebStation hasn't another port configured (8080 in this case).

Obviously there's something on your port 8080, I think @bud77 knows a command to know which program use this port number.

Command :

netstat -an grep 8080

But this will only display if you actually have something running. But seeing something with a browser, there is most definetly something running

Some users have reported to fix the issue by replacing the file named 'PkgMan.cgi' (not sure about the name, but something alike) but, WE DO NOT RECOMMEND THIS AT ALL

netstat -lp grep webcache gives you the process ID back

webcache is equal to 8080

Nice one @Jeroenve , thanks for the tip !!!!

This is the output:

DS111> netstat -lp grep webcache
netstat: showing only processes with your user ID
tcp 1 0 ::%10:webcache ::%3201964404:* LISTEN -
DS111>

So you have something running, but there is no PID, that's weird

Did you try to cold boot the syno ? (not reboot, shutdown, then start with the physical button)

Thanks for replying! Hope we can solve this....

I made the Synology to shutdown via DSM. Then started it by pressing the button on the DS111 itself. After a while I heard the 'ready beep'.

Tried to install Sabnzb, but got the same error. When entering URL http://ipofmysynology/8080 the browser does not return the xml file as yesterday, but keeps waiting and waiting.

Netstat command gave the following:

DS111> netstat -lp grep webcache
netstat: showing only processes with your user ID
tcp 9 0 ::%10:webcache ::%3200805236:* LISTEN -
DS111>

Any idea's?

netstat: showing only processes with your user ID@bud77 is there a way to avoid that behaviour?

Well, few users reported they resolved the issue by either upgrading DSM, or replacing the file PkgMan.cgi

But as stated above, I do not recommend replacing the file at all, since I don't know the side effects, which might be terrible

Ha, think I found it: when logging in with root i.s.o. admin, Netstat came with:

DS111> netstat -lp grep webcache
tcp 9 0 ::%10:webcache ::%3202009540:* LISTEN 3988/tinyproxy
DS111>

Now I need to figure out how to change the port of tinyproxy or how to uninstall

Thanks for your help! Any suggestion on tinyproxy is welcome. :-)

tinyproxy surely doesn't come from SynoCommunity. If this is another 3rd party package I suggest you ask the developer. If you installed it with IPKG then you should be able to disable it somehow.

I'm glad you could find the cause of all this :)

mmm, seems optware is disabled with the upgrade of DSM4.1. Need to install it again.

Thanks for your help! And continue the good work.

I completely removed tinyproxy and all settings and rebooted the Synology. Port 8080 is now indeed not in us anymore! netstat gives no processes or whatsoever.

I did a 'cold reboot' and opened DSM again. The installation of Sabnzbd now continues (!) and asks me for an download directory. I enter the directory and get the window where I have to confirm the settings. I press 'apply' and after a second I get:

'Failed to install the package'

I checked the logfiles in DSM but don't see any entry. Any idea's what could be the cause? (DS111 running DSM 4.1 beta)

Put the full path:

And make sure the directory exists

@Diaoul See why I proposed to add a few lines in the help file ? :p

@voorstad Also the folder names are case sensitive

Yup, that did the trick! I tried several directories, but missed this full path.

a BIG THANKS for all the prompt help!

@bud77: Just don't have the time to merge & make a release etc. Will do, maybe next week.

No hurry, that was just a poke :p

bud77, I finally worked out how to solve this issue for me.
I found even when I did a hard reset that I couldn't install sabnzbd because the synology claimed the port was already in use or reserved for system use.

I therefore went with my gut and thought it might be linked to synology's webdav. What I did was enable webdav but to a different port number - eg 8000 (ie not the default 8080).
I then installed sabnzbd and it installed fine. Later I just disabled webdav.

I am now a happy sabnzbd user again