Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
[resolved] Subsonic started but port not listen
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-23
06:32 AM
2012-10-23
06:32 AM
[resolved] Subsonic started but port not listen
Hi,
I installed a Subsonic server on my ReadyNAS Duo v2, started on port 4040. Until this morning I had it perfectly working in local, but not remotely. After many tries I think I eventually found the error (my mistake, in the config file). But meanwhile, I may have broken something else: Subsonic doesn't work anymore. At all.
Actually, the service well started:
but port is not in the LISTEN state:
and of course, Subsonic is not reachable, even with an SSH port forwarding, since port is not listen:
Why can't I connect to this port?
Why service is well started but not using the port?
If it helps, this morning, when I was still a noob with iptables, I tried few experiments... but reboot is ok and I now have the following configuration back:
Thanks for helping!
I installed a Subsonic server on my ReadyNAS Duo v2, started on port 4040. Until this morning I had it perfectly working in local, but not remotely. After many tries I think I eventually found the error (my mistake, in the config file). But meanwhile, I may have broken something else: Subsonic doesn't work anymore. At all.
Actually, the service well started:
root@Nas:~# ps aux | grep jav
root 11307 0.0 0.3 5276 760 pts/0 R+ 13:06 0:00 grep jav
root 15605 7.5 60.8 402544 150264 ? Sl Oct22 101:54 java -Xmx150m -Dsubsonic.home=/var/subsonic -Dsubsonic.host=0.0.0.0 -Dsubsonic.port=4040 -Dsubsonic.httpsPort=0 -Dsubsonic.contextPath=/ -Dsubsonic.defaultMusicFolder=/var/music -Dsubsonic.defaultPodcastFolder=/var/music/Podcast -Dsubsonic.defaultPlaylistFolder=/var/playlists -Djava.awt.headless=true -verbose:gc -jar subsonic-booter-jar-with-dependencies.jar
but port is not in the LISTEN state:
root@Nas:/var/subsonic# netstat -an | grep 4040
root@Nas:/var/subsonic#
and of course, Subsonic is not reachable, even with an SSH port forwarding, since port is not listen:
root@Nas:/var/subsonic# telnet localhost 4040
telnet: can't connect to remote host (127.0.0.1): Connection refused
Why can't I connect to this port?
Why service is well started but not using the port?
If it helps, this morning, when I was still a noob with iptables, I tried few experiments... but reboot is ok and I now have the following configuration back:
root@Nas:/var/subsonic# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
LeafNetsIN all -- anywhere anywhere
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain LeafNetsIN (1 references)
target prot opt source destination
Thanks for helping!
Message 1 of 2
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-10-23
07:00 AM
2012-10-23
07:00 AM
Re: [resolved] Subsonic started but port not listen
Ok, it seems that Subsonic just need 20 minutes on my ReadyNas Duo v2 to be completely started...
Solved. 😞
Solved. 😞
Message 2 of 2