Madevil wrote:@all
The next Madsonic Node version comes with a new installer for Linux and Windows and should fix some problems with the current version.
Feb 17, 2017 4:05:17 PM org.springframework.context.support.ClassPathXmlApplicationContext prepareRefresh
INFO: Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@17a7cec2: startup date [Fri Feb 17 16:05:17 CET 2017]; root of context hierarchy
Feb 17, 2017 4:05:17 PM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions
INFO: Loading XML bean definitions from class path resource [applicationContext-deployer.xml]
Feb 17, 2017 4:05:17 PM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@2096442d: defining beans [service,org.springframework.remoting.rmi.RmiServiceExporter#0]; root of factory hierarchy
used forced Install_Dir = /var/madsonic-node
Using WAR file: /usr/share/madsonic-node/madsonic-node.war
Extracting webapp to /var/madsonic-node/jetty/6.2.9260
Using WAR file: /usr/share/madsonic-node/madsonic-node.war
2017-02-17 16:05:17.437:INFO:oejs.Server:jetty-8.y.z-SNAPSHOT
2017-02-17 16:05:17.452:INFO:oejw.WebInfConfiguration:Extract jar:file:/usr/share/madsonic-node/madsonic-node.war!/ to /var/madsonic-node/jetty/6.2.9260/webapp
Feb 17, 2017 4:05:17 PM com.sun.jersey.api.core.PackagesResourceConfig init
INFO: Scanning for root resource and provider classes in the packages:
org.madsonic
Feb 17, 2017 4:05:17 PM com.sun.jersey.api.core.ScanningResourceConfig logClasses
INFO: Root resource classes found:
class org.madsonic.controller.NodeController
class org.madsonic.controller.IndexController
Feb 17, 2017 4:05:17 PM com.sun.jersey.api.core.ScanningResourceConfig init
INFO: No provider classes found.
Feb 17, 2017 4:05:17 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate
INFO: Initiating Jersey application, version 'Jersey: 1.19.3 10/24/2016 03:43 PM'
[2017-02-17 16:05:18] [DEBUG] [main] VersionService - Resolved local Madsonic Node version to: 6.2.9260
[2017-02-17 16:05:18] [INFO ] [main] SettingsService - Java: 1.8.0_121, OS: Linux
[2017-02-17 16:05:18] [INFO ] [main] SystemService - auto register Node ...
[2017-02-17 16:05:18] [INFO ] [main] SystemService - init LocalAudioDeviceList ...
[2017-02-17 16:05:18] [DEBUG] [Thread-3] BroadcastRegister - Request packet data: REGISTER_MADSONIC_NODE_REQUEST_31302e302e302e3133333a38313831
[2017-02-17 16:05:18] [DEBUG] [Thread-3] BroadcastRegister - Request packet sent to: 10.0.0.255; Interface: eth0
[2017-02-17 16:05:18] [DEBUG] [Thread-3] BroadcastRegister - Done looping over all network interfaces. Now waiting for a reply!
[2017-02-17 16:05:18] [DEBUG] [Thread-3] BroadcastRegister - Broadcast response from server: 10.0.0.11
[2017-02-17 16:05:18] [DEBUG] [Thread-3] BroadcastRegister - Register NODE Done. /10.0.0.11
[2017-02-17 16:05:18] [INFO ] [main] SystemService - Available local audio mixers:
[2017-02-17 16:05:18] [INFO ] [main] SystemService - AudioPCI [default]
[2017-02-17 16:05:18] [INFO ] [main] SystemService - AudioPCI [plughw:0,0]
[2017-02-17 16:05:18] [INFO ] [main] SystemService - AudioPCI [plughw:0,1]
[2017-02-17 16:05:18] [INFO ] [main] SystemService - Port AudioPCI [hw:0]
2017-02-17 16:05:18.307:INFO:oejs.AbstractConnector:Started @0.0.0.0:8181
Madsonic running on: http://localhost:8181/
Feb 17, 2017 4:05:18 PM org.springframework.remoting.rmi.RmiServiceExporter getRegistry
INFO: Looking for RMI registry at port '9414'
Feb 17, 2017 4:05:18 PM org.springframework.remoting.rmi.RmiServiceExporter getRegistry
INFO: Could not detect RMI registry - creating new one
Feb 17, 2017 4:05:18 PM org.springframework.remoting.rmi.RmiServiceExporter prepare
INFO: Binding service 'MadsonicDeployerService' to RMI registry: RegistryImpl[UnicastServerRef [liveRef: [endpoint:[10.0.0.133:9414](local),objID:[0:0:0, 0]]]]
Users browsing this forum: No registered users and 1 guest