Anyone trying Node yet? Helpful tips/ideas?

[garyo]

I have an older Raspberry Pi I could use for this, and a little powered speaker. I'd like to have a little bedroom system driven from my Madsonic. But before I jump in it'd be nice to hear from some folks who've done it successfully. Any reports from the field?

[c.jordan84]

It took a little work to make mine usable (see the other post on "Trouble Setting Up and Using New Node"), but it does work. Still very beta.

[thechez]

I attempted getting things set up but no luck so far. There isn't much documentation on it or support at the moment. It sounds like a really cool idea and I'd like to use it to run nodes of Pis on my soundbars around the house. I'm the type though that has to wait for someone to do a write up of exactly how to do Linux things before I can even figure out what's going on.

[thechez]

I am wondering, can we just replace the main files in our server folder for node? Or is this supposed to be installed in a different folder completely so that it can run from port 8181? I have had zero luck getting this going on my Pi so far and the documentation is sparse. I'd be happy to do a write up if I can get things working. I'm running the QNAP package on my NAS and the server runs great, I've just had no luck with the node service.
Cheers.

[Madevil]

@all

The next Madsonic Node version comes with a new installer for Linux and Windows and should fix some problems with the current version.

[thechez]

@all

The next Madsonic Node version comes with a new installer for Linux and Windows and should fix some problems with the current version.

Well, I managed to get it placed in /var/madsonic-node on my RasPi running Raspbian. I started the process as well but no luck. It doesn't show in processes and when I try to enter the pi's local address at port 8181 it doesn't open. I tried the NAS server address as well but not working there either. Is Node something installed on the server end as well?

[Madevil]

Did you try the latest version?

Info: http://beta.madsonic.org/pages/changelog.jsp#node-6.2.9240

best regards

[thechez]

Yes, it's the most current version. I am going to make certain the port is open on my VPN and on my router. I swear I opened those two pipes though. But they're just not communicating with each other.

[Madevil]

default Madsonic Node installation 6.2.9260 on debian 8.7.1

troubleshooting logfile:

example: /var/madsonic-node/madsonic-node.log

Code: Select all

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]]]]

[thechez]

When I look in the log all I see is this:
Error: Unable to access jarfile madsonic-node-booter.jar

I have it directed to that directory that node is in but it doesn't seem to initiate. Are all of the node files supposed to be in their own folder or in with the regular Madsonic server files? I installed it in its own folder completely.