I have had this problem for a while, where airsonic does not create a UPnP player thats visible in the network.
I am running AirSonic in a freeNas jail. I tried running the latest version, aswell as the 10.6.0-dlna-fix version.
The logs show a successfull start, however the UPnP player is not visible in the networt.
2020-04-22 18:12:47.876 INFO --- o.a.p.s.search.IndexManager : Index was found (index version 18).
2020-04-22 18:12:47.901 INFO --- o.a.p.s.MediaScannerService : Automatic media library scanning scheduled to run every 1 day(s), starting at 2020-04-23T03:00:00.891
2020-04-22 18:12:48.962 INFO --- o.a.p.service.PodcastService : Automatic Podcast update scheduled to run every 24 hour(s), starting at Wed Apr 22 18:17:48 CEST 2020
2020-04-22 18:12:49.260 INFO --- o.a.player.service.UPnPService : Starting UPnP service...
2020-04-22 18:12:49.369 INFO --- o.a.player.service.UPnPService : Successfully started UPnP service on port 4041!
2020-04-22 18:12:49.504 INFO --- o.a.player.service.UPnPService : Enabling UPnP/DLNA media server
2020-04-22 18:12:52.464 INFO --- org.airsonic.player.Application : Detected Tomcat web server
2020-04-22 18:12:54.628 INFO --- org.airsonic.player.Application : Started Application in 29.335 seconds (JVM running for 39.977)
2020-04-22 18:13:04.278 INFO --- org.airsonic.player.Application : Starting Application v10.6.0-RELEASE on AirSonic with PID 45172 (/usr/local/apache-tomcat-8.0/webapps/airsonic/WEB-INF/classes started by root in /)
2020-04-22 18:13:04.284 INFO --- org.airsonic.player.Application : The following profiles are active: legacy
2020-04-22 18:13:08.307 ERROR --- o.a.p.spring.SpringLiquibase : ===============================================
Also AirSonic does not seem to listen.
root@AirSonic:/ # sockstat -l4
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
www jsvc 45172 48 tcp46 *:8080 *:*
www jsvc 45172 53 tcp46 *:8009 *:*
Nmap scan report for AirSonic.fritz.box (192.168.178.36)
Host is up (0.0041s latency).
Not shown: 998 closed ports
PORT STATE SERVICE VERSION
8009/tcp open ajp13 Apache Jserv (Protocol v1.3)
|_ajp-methods: Failed to get a valid response for the OPTION request
8080/tcp open http Apache Tomcat/Coyote JSP engine 1.1
FreeBSD AirSonic 11.3-RELEASE-p7 FreeBSD 11.3-RELEASE-p7
root@AirSonic:/ # java -version
openjdk version "1.8.0_192"
OpenJDK Runtime Environment (build 1.8.0_192-b26)
OpenJDK 64-Bit Server VM (build 25.192-b26, mixed mode)
Proxy server: None
Language: english
I would be very happy for any help, I am not sure where to progress from here.
https://github.com/airsonic/airsonic/issues/1634 will likely fix it, can you test Airsonic 10.6.1?
@fxthomas at my end, it worked like a charm. Thank you very much and @randomnicode for porting it to airsonic-advanced.
1634 will likely fix it, can you test Airsonic 10.6.1?
First of all, thanks for the fast reply. Sorry I should have specified, I tried the 10.6.1 version first and then checked out the 10.6.0-dlna-fix.
I think my problem is unrelated as airsonic was never really working for me.
Do you have another cause what could be causing this?
Thanks
Ah, you're right. That might be a different issue then, maybe your jail settings are preventing Airsonic from listening on the needed ports? As far as I know it needs at least 4041/tcp and 1900/udp for that to work.
Jails do not limit the applications ability to listen on a port (I think). I have been running other services on this or other jails without problems. Also Airsonic is listening on port 8080 without a problem. I am not very good in tomcat, is there a way that it might be the limiting factor here? Any advice in what direction I should put my research efforts in?
In your "sockstat" command earlier, Airsonic does not seem to be listening at all. So I would have a look at the system configuration? Other than that I don't know much about running Tomcat like this unfortunately...
So I finally got it working, however I did some things and its hard for me which one fixed the issue.
OpenJDK 11Tomcat 9Airsonic Advanced implementationThanks for the help and good luck to other people having this problem :)
Upgrading to OpenJDK 11 did it for me, @xerg0n. Thanks!