Connection Problems to Web Interface

Man, where do I begin…I can barely connect to my Volumio2 pi…it starts to load, then times out. Sometimes it never connects at all.

Is the 1.5 download still available? I will just go back to that.

How about you share some more details so maybe we can help you?

same problem here after the latest update …
rpi b+ - ethernet
can ssh but no webinterface …
any help?

i don’t really get what is going on there at all -
i can ping it - but it freezes on ssh and no webinterface …
aargh

well - i just went back to version 0.928 - now works again…
seems there are problems with rpi b+ and the update …

Same problem here (Raspberry PI B+)
Web interface does not load and SSH disconnects.
Tried top command on putty session but connection drops within few minutes.
Ping does work and keep responding.

I had similar problems with 976 on a RPi 1 B+. Web interface never finished coming up, couldn’t ssh in over ethernet, etc. Volumio hotspot was broadcast. Same 976 image worked perfectly on my Rpi 3. I have an IQAudio Pi-DAC+ on both Pi’s.

When you can coonect could you paste via past bin the output of
Sudo journalctl
?

Same problem here, Pi B with a Hifiberry Dac+

It seems like Volumio is in an endless loop, i keep hearing the Volumio startup sound regularly.

ping = ok
putty = “crashing”, can login though and execute commands, sometimes
webpage= not loading.

Hope this helps

Some output of the journalctl command(too much text).

Jul 28 10:38:53 volumio kernel: vc_vchi_sm_init: failed to open VCHI service (-1)
Jul 28 10:38:53 volumio kernel: [vc_sm_connected_init]: failed to initialize shared memory service

Jul 28 10:38:55 volumio systemd-udevd[175]: specified group ‘spi’ unknown

Jul 28 10:39:24 volumio dbus[592]: [system] Activating via systemd: service name=‘org.freedesktop.UDisks’ unit=‘udisks.service’
Jul 28 10:39:24 volumio dhcpd[573]: Internet Systems Consortium DHCP Server 4.3.1
Jul 28 10:39:24 volumio dhcpd[573]: Copyright 2004-2014 Internet Systems Consortium.
Jul 28 10:39:24 volumio dhcpd[573]: All rights reserved.
Jul 28 10:39:24 volumio dhcpd[573]: For info, please visit isc.org/software/dhcp/
Jul 28 10:39:24 volumio dhcpd[573]: Wrote 0 leases to leases file.
Jul 28 10:39:25 volumio dhcpd[573]:
Jul 28 10:39:25 volumio dhcpd[573]: No subnet declaration for eth0 (192.168.0.105).
Jul 28 10:39:25 volumio dhcpd[573]: ** Ignoring requests on eth0. If this is not what
Jul 28 10:39:25 volumio dhcpd[573]: you want, please write a subnet declaration
Jul 28 10:39:25 volumio dhcpd[573]: in your dhcpd.conf file for the network segment
Jul 28 10:39:25 volumio dhcpd[573]: to which interface eth0 is attached. **
Jul 28 10:39:25 volumio dhcpd[573]:
Jul 28 10:39:25 volumio dhcpd[573]:
Jul 28 10:39:25 volumio dhcpd[573]: Not configured to listen on any interfaces!
Jul 28 10:39:25 volumio dhcpd[573]:
Jul 28 10:39:25 volumio dhcpd[573]: If you think you have received this message due to a bug rather
Jul 28 10:39:25 volumio dhcpd[573]: than a configuration issue please read the section on submitting
Jul 28 10:39:25 volumio dhcpd[573]: bugs on either our web page at www.isc.org or in the README file
Jul 28 10:39:25 volumio dhcpd[573]: before submitting a bug. These pages explain the proper
Jul 28 10:39:25 volumio dhcpd[573]: process and the information we find helpful for debugging…
Jul 28 10:39:25 volumio dhcpd[573]:
Jul 28 10:39:25 volumio dhcpd[573]: exiting.
Jul 28 10:39:25 volumio avahi-daemon[585]: Service “volumio” (/services/udisks.service) successfully established.
Jul 28 10:39:25 volumio dnsmasq[603]: started, version 2.72 cachesize 150
Jul 28 10:39:25 volumio dnsmasq[603]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect
Jul 28 10:39:25 volumio dnsmasq[603]: reading /etc/resolv.conf
Jul 28 10:39:25 volumio dnsmasq[603]: using nameserver 192.168.0.1#53
Jul 28 10:39:25 volumio dnsmasq[603]: read /etc/hosts - 4 addresses
Jul 28 10:39:25 volumio systemd[1]: dhcpd.service: control process exited, code=exited status=1
Jul 28 10:39:25 volumio systemd[1]: Failed to start dhcpd.service.
Jul 28 10:39:25 volumio systemd[1]: Unit dhcpd.service entered failed state.

Jul 28 10:39:30 volumio dbus[592]: [system] Activating via systemd: service name=‘org.freedesktop.PolicyKit1’ unit=‘polkitd.service’
Jul 28 10:39:30 volumio systemd[1]: Starting Authenticate and Authorize Users to Run Privileged Tasks…
Jul 28 10:39:31 volumio dhcpd[629]:
Jul 28 10:39:31 volumio dhcpd[629]: No subnet declaration for eth0 (192.168.0.105).
Jul 28 10:39:31 volumio dhcpd[629]: ** Ignoring requests on eth0. If this is not what
Jul 28 10:39:31 volumio dhcpd[629]: you want, please write a subnet declaration
Jul 28 10:39:31 volumio dhcpd[629]: in your dhcpd.conf file for the network segment
Jul 28 10:39:31 volumio dhcpd[629]: to which interface eth0 is attached. **
Jul 28 10:39:31 volumio dhcpd[629]:
Jul 28 10:39:31 volumio dhcpd[629]:
Jul 28 10:39:31 volumio dhcpd[629]: Not configured to listen on any interfaces!
Jul 28 10:39:31 volumio dhcpd[629]:
Jul 28 10:39:31 volumio dhcpd[629]: If you think you have received this message due to a bug rather
Jul 28 10:39:31 volumio dhcpd[629]: than a configuration issue please read the section on submitting
Jul 28 10:39:31 volumio dhcpd[629]: bugs on either our web page at www.isc.org or in the README file
Jul 28 10:39:31 volumio dhcpd[629]: before submitting a bug. These pages explain the proper
Jul 28 10:39:31 volumio dhcpd[629]: process and the information we find helpful for debugging…

Same problem with update - extremely frustrating. I cannot offer any troubleshooting information other than I cannot ssh or there is no web interface. I assume i will have to re-flash to get back to the previous working version?

Thankfully I made an image of the SD card, so I’m back to version 1.55

I have the same issues, B+, Edimax WiFi dongle, HiFiBerry.

I connected to a local display, and the system boots, but after some time you get the node binary crashing and dying and the entire system is out of memory, the crash message repeats on screen over and over and over.

I will try to take a picture with my phone since the amount of time before the system becomes unresponsive is not that much.

Ok, to add some information, it is definitely the node app (or the volumio service, however you prefer) that is causing things to go insane.

If you don’t stop the volumio service right away you will lose all memory and the entire device will hard lock.

I tried to run the node server from the command line “NODE_ENV=production node index.js”, but I get no output, and a process that wants to consume 100% of the CPU and will also lock up the box.

I guess as a clarification to the title, this completely breaks V2 running on a RPi B+. This is build 976. I will try to find older builds to flash that are still relatively recent.

I’m switching to the discussion here: github.com/volumio/Volumio2/issues/599

Pi2 with hifiberry, latest release.
Works fine until I change the IP to static, (this is mostly to keep all my AV stuff in one area for control but also to not have to re-do the Volumio icons on other devices). As soon as you make a static change all connection is lost and its back to the imager.

I got over this by assigning a static lease on my Asus (ddwrt) router, which forced an IP on startup.

I must add, I appreciate everything done on this project and so donate €10 for every unit i flash. Tony

See here
github.com/volumio/Volumio2/issues/599

This issue affects devices with 512MB of RAM. We ll work on a solution, if someone can take a look at the build script and suggest an effective way to reduce the rootfs size that would be very helpful. In the link above there are a couple of suggestions that may help fix temporarily the issue…

Not working on Asus Vivo PC

Please open a separate thread with some more info about your problem. “not working” is a bit unfair to developers, we’re not so good at guessing what might be wrong :wink:
And mark it with x86, so the right people can look at it.

I’m having the same issue on RPi 2. No Web UI, no SSH, but I can ping the RPi. Solid power light and flashing activity light. Very confusing and frustrating. Tried 976 and 928 on different SD cards. Would it help to try 923 or 861? Or, should I stick with 1.55 until somebody figures out the problem?

See here for a fix; 976-rpi-rpi-system-not-booting-responsive-fix-t4426.html