Hello,
unfortunately my start in your forum starts with a cry for help
I switched from runeaudio to moodeaudio but setting access to wifi seems to be stucked in the middle of setup..
I have a Raspi 4 (2GB) with a Mamboberry DAC. Moode version is the latest 6.5.2.
Initial setup via the local website over ethernet works. So, at this point I can access the webui and hear music. Then I set up my wifi, do a clean shutdown via the menu.
After removing the lan-cable and powering up again, the web interface is not accessible anymore - even if I connect the ethernet again and try over it.
The log (moodeutl -l) seems to be fine before setting the wifi up. Afterwards, it doesn't show anything past the filesystem:
20200521 041850 worker: -- Start
20200521 041850 worker: Successfully daemonized
20200521 041850 worker: Integrity check (passed)
20200521 041850 worker: Session loaded
20200521 041850 worker: Debug logging (off)
20200521 041850 worker: Device raw: (0:ALSA|1:empty|i2s:none)
20200521 041850 worker: Device cfg: (On-board audio device|0|0|PCM|0)
20200521 041851 worker: ALSA volume set to (0%)
20200521 041851 worker: -- System
20200521 041852 worker: Host (moode)
20200521 041852 worker: moOde (6.5.2 2020-05-03)
20200521 041852 worker: Raspbian (10.3)
20200521 041852 worker: Kernel (4.19.115-v7l+ #1305)
20200521 041852 worker: Platform (Pi-4B 2GB v1.1)
20200521 041852 worker: ARM arch (armv7l, 32-bit kernel)
20200521 041852 worker: MPD ver (0.21.22)
20200521 041852 worker: CPU gov (ondemand)
20200521 041852 worker: USB boot not available
20200521 041852 worker: File system expanded
..and here it ends.. (before setting wlan up here network, audio, mpd.. showed up)
Curiously, the ssh access via wifi (as well as via ethernet when plugging in again) still is working.
So far I tried
- static ip as well as dhcp
- manually setting up wifi via wpa_supplicant.conf
- expanding the filesystem manually (shouldn't do any harm but also no good at this point, I think.. as it worked before.. just doing so because it was the last log, next would be hdmi port - doesn't shows up but I don't see which problems this could do to the webinterface..)
- letting ethernet active but only unplugging it, manually deactivating ethernet via ssh, deactivating it same time when setting up wifi (via web-ui)
- powering via usb instead of via i2s (mamboberry)
- not setting the Mamboberry but setting wifi up first
- removing the audio device, repeating every step (without the Mamboberry hat, so without any audio device)
- restarting servers via moodeutl -r (message 'watchdog.sh: no process found' pops up before restarting - tbh, I have absolutely no clue if this helps at all and what it does, I just saw it and tried because I don't know what's going up there down the rabbithole..)
- tried a different sd card (yep I know, doesn't make any sense..)
Everytime it ends up the same -as soon as wifi is on, I only can access via ssh but webui is not working anymore.
Anyone has an idea for what possible errors I can look next?
Any help would be awesome! Here in Germany today's a day off and I was so hard looking forward to fiddle around with my new baby
unfortunately my start in your forum starts with a cry for help
I switched from runeaudio to moodeaudio but setting access to wifi seems to be stucked in the middle of setup..
I have a Raspi 4 (2GB) with a Mamboberry DAC. Moode version is the latest 6.5.2.
Initial setup via the local website over ethernet works. So, at this point I can access the webui and hear music. Then I set up my wifi, do a clean shutdown via the menu.
After removing the lan-cable and powering up again, the web interface is not accessible anymore - even if I connect the ethernet again and try over it.
The log (moodeutl -l) seems to be fine before setting the wifi up. Afterwards, it doesn't show anything past the filesystem:
20200521 041850 worker: -- Start
20200521 041850 worker: Successfully daemonized
20200521 041850 worker: Integrity check (passed)
20200521 041850 worker: Session loaded
20200521 041850 worker: Debug logging (off)
20200521 041850 worker: Device raw: (0:ALSA|1:empty|i2s:none)
20200521 041850 worker: Device cfg: (On-board audio device|0|0|PCM|0)
20200521 041851 worker: ALSA volume set to (0%)
20200521 041851 worker: -- System
20200521 041852 worker: Host (moode)
20200521 041852 worker: moOde (6.5.2 2020-05-03)
20200521 041852 worker: Raspbian (10.3)
20200521 041852 worker: Kernel (4.19.115-v7l+ #1305)
20200521 041852 worker: Platform (Pi-4B 2GB v1.1)
20200521 041852 worker: ARM arch (armv7l, 32-bit kernel)
20200521 041852 worker: MPD ver (0.21.22)
20200521 041852 worker: CPU gov (ondemand)
20200521 041852 worker: USB boot not available
20200521 041852 worker: File system expanded
..and here it ends.. (before setting wlan up here network, audio, mpd.. showed up)
Curiously, the ssh access via wifi (as well as via ethernet when plugging in again) still is working.
So far I tried
- static ip as well as dhcp
- manually setting up wifi via wpa_supplicant.conf
- expanding the filesystem manually (shouldn't do any harm but also no good at this point, I think.. as it worked before.. just doing so because it was the last log, next would be hdmi port - doesn't shows up but I don't see which problems this could do to the webinterface..)
- letting ethernet active but only unplugging it, manually deactivating ethernet via ssh, deactivating it same time when setting up wifi (via web-ui)
- powering via usb instead of via i2s (mamboberry)
- not setting the Mamboberry but setting wifi up first
- removing the audio device, repeating every step (without the Mamboberry hat, so without any audio device)
- restarting servers via moodeutl -r (message 'watchdog.sh: no process found' pops up before restarting - tbh, I have absolutely no clue if this helps at all and what it does, I just saw it and tried because I don't know what's going up there down the rabbithole..)
- tried a different sd card (yep I know, doesn't make any sense..)
Everytime it ends up the same -as soon as wifi is on, I only can access via ssh but webui is not working anymore.
Anyone has an idea for what possible errors I can look next?
Any help would be awesome! Here in Germany today's a day off and I was so hard looking forward to fiddle around with my new baby
