FAQ  •  Register  •  Login

Remote access to serviio console v1.9.1 - upgrade issue

<<

atkins8

Serviio newbie

Posts: 2

Joined: Tue Apr 03, 2018 8:07 pm

Post Tue Apr 03, 2018 8:26 pm

Remote access to serviio console v1.9.1 - upgrade issue

Serviio worked great in ubuntu 14.04 and v1.2.1 but i decided to upgrade to 16.04. This upgrade went without issue. I also upgrade serviio to 1.9.1. and decided to rebuild ffmpeg also. I run Ubuntu on a headless machine.

serviio starts, I have debugging turned on, but I do not see any scanning of the directories now. If I add a new file, its doesnt appear in VLC on my ipad or samsung tv (both worked before the upgrade).
As the server is headless I cannot work out how to run the console now remotely

I have download serviio on a windows pc with console and used this viewtopic.php?t=10290 to configure it to the address of the media server - however I do not see the directories on the media server in console.

So the two problems I have are I cannot remote access serviio now and the db of media seems to be corrupt.

any help appreciated.
derby output file is:

Mon Apr 02 21:07:53 BST 2018:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.12.1.1 - (1704137): instance a816c00e-0162-87f9-20cc-00005d5ab10e
on database directory /home/atkins8/serviio/serviio-1.9.1/library/db with class loader sun.misc.Launcher$AppClassLoader@355da254
Loaded from file:/home/atkins8/serviio/serviio-1.9.1/lib/derby.jar
java.vendor=Oracle Corporation
java.runtime.version=1.8.0_151-8u151-b12-0ubuntu0.16.04.2-b12
user.dir=/home/atkins8/serviio/serviio-1.9.1/bin
os.name=Linux
os.arch=amd64
os.version=4.4.0-116-generic
derby.system.home=/home/atkins8/serviio/serviio-1.9.1/library
derby.stream.error.file=../log/derby.log
Database Class Loader started - derby.database.classpath=''

serviio.log is just repeating.......

018-04-03 21:20:32,161 DEBUG [RendererSearchSender] Searching for Renderer devices
2018-04-03 21:20:32,161 DEBUG [RendererSearchSender$RendererSearchWorker] Multicasting SSDP M-SEARCH using interface eth1 (eth1) and address 192.168.0.2, timeout = 0
2018-04-03 21:20:32,161 DEBUG [RendererSearchSender$RendererSearchWorker] Sending 1 'm-search' messages
2018-04-03 21:20:32,161 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.0.2:59299s
2018-04-03 21:20:32,161 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.0.2:59299s
2018-04-03 21:20:32,161 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.0.2
2018-04-03 21:20:32,161 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.0.2
2018-04-03 21:20:32,161 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.0.2:59299s
2018-04-03 21:20:32,162 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.0.2
2018-04-03 21:20:32,590 DEBUG [RendererSearchSender$RendererSearchWorker] Received search response: location: http://192.168.0.11:1400/xml/device_description.xml, st: urn:schemas-upnp-org:device:MediaRenderer:1
2018-04-03 21:20:32,590 DEBUG [RendererSearchSender$RendererSearchWorker] Received a valid M-SEARCH response from Renderer rincon_5caafd279b7001400_mr from address 192.168.0.11
2018-04-03 21:20:32,590 DEBUG [RendererManager] Retrieve device description from http://192.168.0.11:1400/xml/device_description.xml
2018-04-03 21:20:32,742 DEBUG [RendererSearchSender$RendererSearchWorker] Received search response: location: http://192.168.0.11:1400/xml/device_description.xml, st: urn:schemas-upnp-org:device:MediaRenderer:1
2018-04-03 21:20:32,742 DEBUG [RendererSearchSender$RendererSearchWorker] Received a valid M-SEARCH response from Renderer rincon_5caafd279b7001400_mr from address 192.168.0.11
2018-04-03 21:20:32,742 DEBUG [RendererManager] Retrieve device description from http://192.168.0.11:1400/xml/device_description.xml
2018-04-03 21:20:38,167 DEBUG [RendererSearchSender] Finished searching for Renderer devices
2018-04-03 21:20:38,229 DEBUG [RendererSearchSender] Searching for Renderer devices
2018-04-03 21:20:38,230 DEBUG [RendererSearchSender$RendererSearchWorker] Multicasting SSDP M-SEARCH using interface eth1 (eth1) and address 192.168.0.2, timeout = 0
2018-04-03 21:20:38,230 DEBUG [RendererSearchSender$RendererSearchWorker] Sending 1 'm-search' messages
2018-04-03 21:20:38,230 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.0.2:51761s
2018-04-03 21:20:38,230 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.0.2:51761s
2018-04-03 21:20:38,230 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.0.2
2018-04-03 21:20:38,230 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.0.2
2018-04-03 21:20:38,230 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.0.2:51761s
2018-04-03 21:20:38,230 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.0.2
2018-04-03 21:20:38,641 DEBUG [RendererSearchSender$RendererSearchWorker] Received search response: location: http://192.168.0.11:1400/xml/device_description.xml, st: urn:schemas-upnp-org:device:MediaRenderer:1
2018-04-03 21:20:38,641 DEBUG [RendererSearchSender$RendererSearchWorker] Received a valid M-SEARCH response from Renderer rincon_5caafd279b7001400_mr from address 192.168.0.11
2018-04-03 21:20:38,641 DEBUG [RendererManager] Retrieve device description from http://192.168.0.11:1400/xml/device_description.xml
2018-04-03 21:20:38,703 DEBUG [RendererSearchSender$RendererSearchWorker] Received search response: location: http://192.168.0.11:1400/xml/device_description.xml, st: urn:schemas-upnp-org:device:MediaRenderer:1
2018-04-03 21:20:38,703 DEBUG [RendererSearchSender$RendererSearchWorker] Received a valid M-SEARCH response from Renderer rincon_5caafd279b7001400_mr from address 192.168.0.11
2018-04-03 21:20:38,703 DEBUG [RendererManager] Retrieve device description from http://192.168.0.11:1400/xml/device_description.xml
2018-04-03 21:20:44,236 DEBUG [RendererSearchSender] Finished searching for Renderer devices
2018-04-03 21:20:44,820 DEBUG [RendererSearchSender] Searching for Renderer devices
2018-04-03 21:20:44,821 DEBUG [RendererSearchSender$RendererSearchWorker] Multicasting SSDP M-SEARCH using interface eth1 (eth1) and address 192.168.0.2, timeout = 0
2018-04-03 21:20:44,821 DEBUG [RendererSearchSender$RendererSearchWorker] Sending 1 'm-search' messages
2018-04-03 21:20:44,821 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.0.2:54209s
2018-04-03 21:20:44,821 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.0.2:54209s
2018-04-03 21:20:44,821 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.0.2
2018-04-03 21:20:44,821 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.0.2
2018-04-03 21:20:44,821 DEBUG [DiscoverySSDPMessageListener] Received a valid M-SEARCH message for search target urn:schemas-upnp-org:device:MediaRenderer:1 from address /192.168.0.2:54209s
2018-04-03 21:20:44,821 DEBUG [RendererDAOImpl] Reading a Renderer with ip address 192.168.0.2
2018-04-03 21:20:45,104 DEBUG [RendererSearchSender$RendererSearchWorker] Received search response: location: http://192.168.0.11:1400/xml/device_description.xml, st: urn:schemas-upnp-org:device:MediaRenderer:1
2018-04-03 21:20:45,104 DEBUG [RendererSearchSender$RendererSearchWorker] Received a valid M-SEARCH response from Renderer rincon_5caafd279b7001400_mr from address 192.168.0.11
2018-04-03 21:20:45,104 DEBUG [RendererManager] Retrieve device description from http://192.168.0.11:1400/xml/device_description.xml
2018-04-03 21:20:45,154 DEBUG [RendererSearchSender$RendererSearchWorker] Received search response: location: http://192.168.0.11:1400/xml/device_description.xml, st: urn:schemas-upnp-org:device:MediaRenderer:1
2018-04-03 21:20:45,154 DEBUG [RendererSearchSender$RendererSearchWorker] Received a valid M-SEARCH response from Renderer rincon_5caafd279b7001400_mr from address 192.168.0.11
2018-04-03 21:20:45,154 DEBUG [RendererManager] Retrieve device description from http://192.168.0.11:1400/xml/device_description.xml
2018-04-03 21:20:50,827 DEBUG [RendererSearchSender] Finished searching for Renderer devices
<<

atc98092

User avatar

DLNA master

Posts: 2761

Joined: Fri Aug 17, 2012 10:22 pm

Location: Washington (the state)

Post Wed Apr 04, 2018 12:25 pm

Re: Remote access to serviio console v1.9.1 - upgrade issue

You don't need to install Serviio on a different computer for the console. I don't remember exactly which version it changed (somewhere around 1.6), but the console is now web based and can be accessed from any computer on your network. Just use the URL http://ip_address:23423/console with ip_address being the Serviio box.
Dan

Panasonic ST30 Plasma, Samsung JU7100 4K TV, Sony BDP-S3500, Sharp 4K Roku TV, Insignia Roku TV, Roku 4, Ultra and Stick, Yamaha RX-V583 AVR.
Primary server: Intel i5-6400, 8 gig ram, Windows 10 Pro, 18 TB hard drive space | Test server Windows 7 Home Premium, AMD Phenom II X4 965, 8 gig ram

HOWTO: Enable debug logging HOWTO: Identify media file contents
<<

atkins8

Serviio newbie

Posts: 2

Joined: Tue Apr 03, 2018 8:07 pm

Post Wed Apr 04, 2018 8:46 pm

Re: Remote access to serviio console v1.9.1 - upgrade issue

Many thanks for that. I missed that somewhere along the line.

I can now see that serviio is actually working correctly ! the reason why I cannot see any files is because I decided to install it to a different path. Once I used a browser connected to the server I could see that no media paths had been defined.

So many thanks for that, your reply helped me get serviio running again.

Return to Serviio Support & Help

Who is online

Users browsing this forum: No registered users and 2 guests

Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software for PTF.