Volumio on Pi 2 B - Web UI Service Not Started?

Hi,

I downloaded the latest Volumio image (version 2.001 dated 15-10-2016), flashed it on a SD card, stuck it in the Pi, plugged in ethernet cable, and fired it up.

I could ping to it, could SSH to it, but could not reach the web UI.

From the SSH interface, I could see that port 80 is not even open.

I tried rebooting, as well as restarting MPD service, but none worked.

Any advice, please?

How long did you wait? I did this yesterday and it was several minutes before I could access the UI.

erm… 45 minutes (i just checked ‘uptime’). shouldn’t be taking that long right?

Tomorrow I will investigate if there are residual problems on the PI 1… But we’ve extensively tested on it and everything was working…
Thanks for your patience

Thanks!

BTW, in my OP i said “PI 2 B”, sorry got that wrong, it should be a PI 1 model B (2 USB ports).

Let me know what you need from me. (dmesg output? any logs?)

Thanks.

Aaaah… wait… how much RAM does it have? If it has 256 MB of RAM, then its not going to work… sorry… If that’s the case, an upgrade to PI3 is strongly suggested…

hmm should be 512 MB:

volumio@volumio:~$ free total used free shared buffers cached Mem: 493844 414160 79684 16860 69372 230660 -/+ buffers/cache: 114128 379716 Swap: 353864 0 353864

I got the same problem with pi1 B

I am having the same problem as well. I wrote the unzipped .img from volumio-2.001-2016-10-15-pi.img.zip to a freshly formatted microSD card.
My system is a Raspberry Pi 2 B+ Model with 1GB memory. It displayed a lot of Linux messages and then showed command line for entering
the UserID and Password. I entered volumio for both. It sat there with no Web UI displayed.

Hi, please follow the instructions:
volumio.github.io/docs/User_Man … Guide.html

You are meant to see the UI via an external browser, from your phone, pc or tablet. Just type the Volumio ip address (or connect to Volumio network, pw volumio2) and you’ll see the magic…

Thanks a lot. I have been feeling poorly the last couple days, so I totally forgot it was accessed that way.

Sorry

No problem, enjoy!

I think my problem is different from GoodGuy98’s.

I did try an external browser, and also verified (via SSH) that port 80 wasn’t opened.

Is there any logs that I can check to see if it attempted to start the web server and what problems it ran into? I see from mpd.conf that logging was commented out. dmesg doesn’t seem to contain anything relevant to this.

Thanks!

Hi, I am experiencing the same problem as described with the lack of web connectivity. This is a Pi3 with a clean install of the latest version of volumio 2.

root@volumio:/volumio# lsof -i | grep volumio
volumio-r 585 volumio 10u IPv4 12275 0t0 TCP *:3006 (LISTEN)
ntpd 640 ntp 22u IPv4 19161 0t0 UDP volumio.local:ntp
nmbd 695 root 28u IPv4 25372 0t0 UDP volumio.local:netbios-ns
nmbd 695 root 30u IPv4 25374 0t0 UDP volumio.local:netbios-dgm
sshd 1636 volumio 3u IPv4 18128 0t0 TCP 192.168.1.2:ssh->192.168.1.3:55346 (ESTABLISHED)
node 20990 volumio 10u IPv6 134546 0t0 TCP *:3000 (LISTEN)

Any ideas?

I did a bit more digging, here’s what happens when trying to start the volumio service by hand. Seems like it can’t read the config file for some reason

volumio@volumio:~$ /usr/local/bin/node /volumio/index.js
info: -------------------------------------------
info: ----- Volumio2 ----
info: -------------------------------------------
info: ----- System startup ----
info: -------------------------------------------
Error reading configuration. Defaulting to empty configuration
info: Found new core plugin music_service/airplay_emulation. Adding it
info: Found new core plugin music_service/mpd. Adding it
info: Found new core plugin music_service/webradio. Adding it
info: Found new core plugin music_service/example_plugin. Adding it
info: Found new core plugin music_service/last_100. Adding it
info: Found new core plugin audio_interface/upnp. Adding it
info: Found new core plugin audio_interface/alsa_controller. Adding it
info: Found new core plugin miscellanea/alarm-clock. Adding it
info: Found new core plugin miscellanea/albumart. Adding it
info: Found new core plugin miscellanea/appearance. Adding it
info: Found new core plugin user_interface/websocket. Adding it
info: Found new core plugin user_interface/mpdemulation. Adding it
info: Found new core plugin system_controller/updater_comm. Adding it
info: Found new core plugin system_controller/network. Adding it
info: Found new core plugin system_controller/networkfs. Adding it
info: Found new core plugin system_controller/services. Adding it
info: Found new core plugin system_controller/system. Adding it
info: Found new core plugin system_controller/i2s_dacs. Adding it
info: Found new core plugin system_controller/volumiodiscovery. Adding it
info: Found new core plugin system_controller/volumio_command_line_client. Adding it
info: Plugin folders cleanup
info: Scanning into folder /volumio/app/plugins/
info: Scanning category audio_interface
info: Scanning category miscellanea
info: Scanning category music_service
info: Scanning category plugins.json
info: Scanning category system_controller
info: Scanning category user_interface
info: Scanning into folder /data/plugins/
info: Plugin folders cleanup completed
info: Loading plugins from folder /volumio/app/plugins/
info: Loading plugins from folder /data/plugins/
info: Loading plugin “system”…
Error reading configuration. Defaulting to empty configuration
No id defined. Creating one
info: Loading plugin “appearance”…
Error reading configuration. Defaulting to empty configuration
info: Loading plugin “network”…
Error reading configuration. Defaulting to empty configuration
info: Loading plugin “services”…
info: Loading plugin “alsa_controller”…
Error reading configuration. Defaulting to empty configuration
info: CoreCommandRouter::volumioUpdateVolumeSettings
info: CoreCommandRouter::executeOnPlugin: i2s_dacs , getI2sStatus
info: Found match in Cards Database: setting mixer PCM for card Audio Jack
info: CoreCommandRouter::volumioUpdateVolumeSettings
info: CoreCommandRouter::volumioUpdateVolumeSettings
info: CoreCommandRouter::volumioUpdateVolumeSettings
info: Loading plugin “volumio_command_line_client”…
info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam
info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam
info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam
info: Loading plugin “upnp”…
info: [1476786320844] Starting Upmpd Daemon
/volumio/app/plugins/audio_interface/upnp/index.js:138
var name = nameraw.charAt(0).toUpperCase() + nameraw.slice(1);
^

TypeError: Cannot read property ‘charAt’ of undefined
at UpnpInterface.startUpmpdcli (/volumio/app/plugins/audio_interface/upnp/index.js:138:20)
at UpnpInterface.onVolumioStart (/volumio/app/plugins/audio_interface/upnp/index.js:27:7)
at PluginManager.loadPlugin (/volumio/app/pluginmanager.js:122:19)
at PluginManager.loadPlugins (/volumio/app/pluginmanager.js:192:10)
at new CoreCommandRouter (/volumio/app/index.js:43:21)
at Object. (/volumio/index.js:34:21)
at Module._compile (module.js:541:32)
at Object.Module._extensions…js (module.js:550:10)
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)

Do:

rm -rf /data/configuration/*

then

killall node

let me know

mi

My Volumio didn’t even have a /data/configuration to start with. Perhaps that’s why it didn’t work?

[code]root@volumio:/# netstat -anop | grep :80

root@volumio:/# ps auxwwf | grep node | grep -v grep
volumio 7558 104 4.2 83408 20856 ? Rsl 15:04 0:02 /usr/local/bin/node /volumio/index.js

root@volumio:/# ls -al /data/configuration/*
ls: cannot access /data/configuration/*: No such file or directory

root@volumio:/# rm -rf /data/configuration/*

root@volumio:/# killall node

root@volumio:/# netstat -anop | grep :80

root@volumio:/# ps auxwwf | grep node | grep -v grep
volumio 7691 0.0 2.3 78560 11572 ? Rsl 15:05 0:00 /usr/local/bin/node /volumio/index.js[/code]

Thanks.

I see, yes that’s why it can’t start…

Try to reflash, and don’t turn the PI off for the first 6 minutes before it starts. I’m trying now with an old pi as we speak

i reflashed, stuck it in the PI, turned on the power, and left it running for at least 20 min before even trying to SSH in…

and it appears to be working!

I could HTTP to it with my browser, and also

[code]root@volumio:/home/volumio# ps auxwwf | grep node | grep -v grep
volumio 792 13.3 7.8 170916 38716 ? Ssl 15:37 2:55 /usr/local/bin/node /volumio/index.js
volumio 1051 0.0 0.0 1816 232 ? S 15:38 0:00 _ /bin/sh -c /usr/local/bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart
volumio 1052 0.1 1.3 83408 6580 ? Sl 15:38 0:02 _ /usr/local/bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart
volumio 1068 0.5 1.9 88704 9516 ? Sl 15:39 0:07 _ /bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart

root@volumio:/home/volumio# ls -al /data/configuration/
total 28
drwxr-xr-x 6 volumio volumio 4096 Oct 18 15:38 .
drwxr-xr-x 1 volumio volumio 4096 Oct 18 15:39 …
drwxr-xr-x 3 volumio volumio 4096 Oct 18 15:38 audio_interface
drwxr-xr-x 5 volumio volumio 4096 Oct 18 15:39 miscellanea
drwxr-xr-x 4 volumio volumio 4096 Oct 18 15:38 music_service
-rwxr-xr-x 1 volumio volumio 3807 Oct 18 15:39 plugins.json
drwxr-xr-x 8 volumio volumio 4096 Oct 18 15:38 system_controller[/code]

but I don’t understand… I still don’t see port 80 open…

root@volumio:/home/volumio# netstat -anop | grep :80

how in the world??

Thanks!

Because we don’t listen on port 80, but rather NAT it from 3000 :wink:

I tried as well and everything works fine on PI1… Good that you made it!