Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Thread Closed 
Moode eventually unrechable until i reboot...
#1
So, since a few weeks, i'm making my firts steps in the wonderfull world of RPI+Moode. It's just magic.
But :

Here is my config

RPi 3B+ and Amplified DAC
Connected via ethernet (wifi is also active), on fixed IP
around 25 000 songs in a NAS via SAMBA
Last version of moode


Everything is working just fine, but, eventually, around 12 to 24 h after running, moode is unreacheable, nor with ethernet nor Wifi. Eventually, moode is loading, but blank and unclickable. Then i reboot, everything is fine again.

It seems that i can exclude the ethernet, because it's the same with wifi, and my other devices are running withour problems.

Ideas ?
#2
Damned. Did it again

I've rebooted, and just arrived to the end of an Album. Not even (i was on the last track)

Edit : i've tried to disable wifi, upnp, etc.. and it's still the same. Almost un-usable, sadly.
#3
Possibly a bad/corrupt SD card or an insufficient power supply?
When you say "unreachable", what is unreachable? Is it just the web interface or does the Pi not respond on the network when pinging or attempting an ssh connection?
Also when you say "reboot" what do you mean? Are you logging in and running 'sudo reboot' or yanking the power cable?
#4
thanks a lot for the reply. It's very frustrating.

1/ Unreachable : i can access the SD card on the IP adress under windows. But moode page on chrome doesn't respond nor load (like it would not exist)
2/ Reboot: hard reboot. I just switch off the power and plug it again. So yes, yanking the power cable

I'm begining to think that it could be due to bluez, as i using it a lot to send the MPD to a bluetooth speaker, and/or to receveive ound from a projector.


Would the logs help ? How can i get them ?
#5
(01-21-2020, 06:59 AM)Maitresinh Wrote: thanks a lot for the reply. It's very frustrating.

1/ Unreachable : i can access the SD card on the IP adress under windows. But moode page on chrome doesn't respond nor load (like it would not exist)
2/ Reboot: hard reboot. I just switch off the power and plug it again. So yes, yanking the power cable

I'm begining to think that it could be due to bluez, as i using it a lot to send the MPD to a bluetooth speaker, and/or to receveive ound from a projector.


Would the logs help ? How can i get them ?

...bluez... bluetooh speaker... projector... ?!  Why don't you FIRST remove any 'additions' (software/hardware) and play JUST music for 1-2 days connected DIRECTLY to speakers ?... and if the result is positive introduce changes one at a time.
#6
i did sir.
It worked fine. So i wanted to have a more extented use of my moode. And again, it works. The *only* problem is that it seems to crash.

For now, i'm just trying to send moode sound over bluetooth, nothing more.

So:

1/ Does it usually work better/does it has more chance to work better/safer with an external bluetooth devices on the USB port ?
2/ same question if i downgrade moode version, and with wich one
#7
(01-21-2020, 12:08 PM)Maitresinh Wrote: i did sir.
It worked fine. So i wanted to have a more extented use of my moode. And again, it works. The *only* problem is that it seems to crash.

For now, i'm just trying to send moode sound over bluetooth, nothing more.

So:

1/ Does it usually work better/does it has more chance to work better/safer with an external bluetooth devices on the USB port ?
2/ same question if i downgrade moode version, and with wich one


1/ No. It works fine with either internal or external bluetooth adapters. 

2/ No. Downgrading solves nothing.

When a "crash" occurs can you still access the command line---either through the built-in, Web SSH terminal (must be enabled in m>System) or through an ssh-session from another computer?

If so, look for telltale info at the tails of the logs: /var/log/moode.log and /var/log/syslog.

Regards,
Kent
#8
(01-21-2020, 04:37 PM)TheOldPresbyope Wrote:
(01-21-2020, 12:08 PM)Maitresinh Wrote: i did sir.
It worked fine. So i wanted to have a more extented use of my moode. And again, it works. The *only* problem is that it seems to crash.

For now, i'm just trying to send moode sound over bluetooth, nothing more.

So:

1/ Does it usually work better/does it has more chance to work better/safer with an external bluetooth devices on the USB port ?
2/ same question if i downgrade moode version, and with wich one


1/ No. It works fine with either internal or external bluetooth adapters. 

2/ No. Downgrading solves nothing.

When a "crash" occurs can you still access the command line---either through the built-in, Web SSH terminal (must be enabled in m>System) or through an ssh-session from another computer?

If so, look for telltale info at the tails of the logs: /var/log/moode.log and /var/log/syslog.

Regards,
Kent

And the obvious question:  Did you expand the disk space?  Is there any left?

#9
Thank you for your help.

So

1/ You're right : i've connected and usb adaptater, and it crash the same way. So that's not the problem
2/ Yes i've expanded the system. I've got a 32 Go SD card, so there is plenty of space
3/ Moode just crashed, and via putty i could open a ssh session !

But i don't know how to get the logs, sorry (yes, i'm that kind of user....)
#10
(01-22-2020, 09:25 PM)Maitresinh Wrote: Thank you for your help.

So

1/ You're right : i've connected and usb adaptater, and it crash the same way. So that's not the problem
2/ Yes i've expanded the system. I've got a 32 Go SD card, so there is plenty of space
3/ Moode just crashed, and via putty i could open a ssh session !

But i don't know how to get the logs, sorry (yes, i'm that kind of user....)

Ok, so when you've opened an ssh session with your moOde player, let's start with Tim's moodeutl command. (I don't use putty so I don't know how best to capture the output; you may need to cut and paste.)

The output from "moodeutl -i" will tell us the basics about your player. Here's an example, taken from my player with hostname moodecd:

Code:
pi@moodecd:~ $ moodeutl -i
Generating info...

S Y S T E M   P A R A M E T E R S

moOde release        = 6.4.0 2019-11-24
Raspbian OS        = 10.2
Linux kernel        = 4.19.83-v7l+ #1277
Platform        = Pi-4B 4GB
Architecture        = armv7l (32-bit)
System uptime        = up 1 day, 21 hours, 8 minutes
Timezone        = America/New_York
Current time        = 2020-01-23 09:49:51

Host name        = moodecd
Ethernet address    = unassigned
Ethernet MAC        = dc:a6:32:0e:e6:25
WLAN address        = 192.168.1.201
WLAN MAC        = dc:a6:32:0e:e6:26
WLAN country        = US

SoC identifier        = bcm2711
Core count        = 4
Kernel timer freq    = 100 Hz
SDCard freq        = 50 MHz
USB boot        = not available
Warranty        = OK

Root size        = 3.4G
Root used        = 79%
Root available        = 697M
Root expand        = not expanded
Memory free        = 3345 MB
Memory used        = 128 MB
SoC temperature        = 37.5°C

CPU governor        = ondemand
Onboard WiFi        = On
Onboard BT        = On
HDMI output        = On
Eth addr wait        = On
Max USB current        = Off
USB (UAC2) fix        = Off
Pi-3B+ eth fix        = Off
SSH term server        = Off

PHP-FPM version        = 7.3.11
NGINX version        = 1.14.2
SQLite3 version        = 3.27.2
Hostapd version        = 2.8-devel
WiringPi version    = 2.50
RPi.GPIO version    = 0.7.0

A U D I O   P A R A M E T E R S

Audio device        = USB audio device
Interface        = USB
Mixer name        = PCM
Hardware volume        = None
Max ALSA volume        = 100
Audio source        = Local
Output device        = Local
Resume MPD        = No
Volume knob        = 40
Volume mute        = Unmuted
Saved MPD vol        = 0
Preamp volume        = 0
ALSA version        = 1.1.8-1+rpt1
SoX version        = 0.1.2-3

Bluetooth controller    = Off
Pairing agent        = Off
Airplay receiver    = Off
Spotify receiver    = Off
Squeezelite        = Off
UPnP client        = Off
DLNA server        = Off
GPIO button handler    = Off
UPnP browser        = Off

Auto-shuffle        = Off
Autoplay        = Off
Rotary encoder        = Off
Encoder params        = 100 2 3 23 24
Polarity inversion    = Off
Crossfeed        = Off
Crossfade        = Off
Parametric EQ        = Off
Graphic EQ        = Off
MPD httpd        = Off

A P P E A R A N C E   S E T T I N G S

Theme            = Default
Accent color        = Emerald
Alpha blend        = 1.0
Adaptive background    = No
Background image    = No
Cover backdrop        = No
Cover blur        = 20px
Cover scale        = 1.25
CoverView auto-display    = Never
CoverView style        = Animated
Auto-shuffle filter    = None
Extra metadata        = Yes
Playback history    = No

L I B R A R Y   S E T T I N G S

Instant play action    = Clear/Play
Show genres column    = Yes
Album grouping        = by Artist
Compilation identifier    = Various Artists
Recently added        = 1 Month
Ignore articles        = a,an,the
UTF8 character filter    = No
Hi-res thumbs        = Auto
Cover search pri    = Embedded cover
Pixel ratio        = 2

M P D   S E T T I N G S

Version            = 0.21.16
Volume control        = software
ALSA device        = hw:1
SoX resampling        = disabled
SoX quality        = very high
SoX multithreading    = off
DSD over PCM (DoP)    = no
Replaygain        = off
Replaygain preamp    = 0
Volume normalization    = No
Audio buffer        = 4096 (kb)
Output buffer size    = 131072 (kb)

B L U E T O O T H   S E T T I N G S

Bluetooth ver        = 5.50
Bluealsa ver        = 2.0.0
Speaker sharing        = No
Resume MPD        = No
PCM buffer time        = 500000 (μs)

A I R P L A Y   S E T T I N G S

Version            = 3.3.5
Friendly name        = MoodeCD Airplay
ALSA device        = hw:1
Interpolation        = soxr
Output bit depth    = S16
Output sample rate    = 44100
Session interruption    = no
Session timeout        = 120 (ms)
Latency offset        = 0.0 (secs)
Audio buffer        = 0.2 (secs)
Resume MPD        = No

S P O T I F Y   S E T T I N G S

Friendly name        = MoodeCD Spotify
ALSA device        = plughw:1
Bit rate        = 160
Initial volume        = 0
Volume curve        = Logarithmic
Volume normalization    = No
Normalization pregain    = 0
Resume MPD        = No

S Q U E E Z E L I T E   S E T T I N G S

Version            = 1.8.7-1052 "DSD/SRC enabled"
Friendly name        = MoodeCD
ALSA device        = hw:0
ALSA params        = 80:4::1
Output buffers        = 40000:100000
Task priority        = 45
Codec list        = flac,pcm,mp3,ogg,aac,alac,dsd
Other options        = -W -D 500 -R E -S /var/local
Resume MPD        = No

L O C A L   D I S P L A Y   S E T T I N G S

Local UI display    = Off
Mouse cursor        = On
Screen blank        = 600 Secs
Wake display on play    = Off
Brightness        = 255
Pixel aspect ratio    = Default
Rotate screen        = 0 Deg

M O O D E   S T A R T U P   L O G

20200121 124131 worker: -- Start
20200121 124131 worker: Successfully daemonized
20200121 124131 worker: Integrity check (passed)
...

Please note that I truncated this output at the beginning of the startup log. If your player runs for hours, this log may be quite long. We wouldn't necessarily need to see it all, but if there are errors and/or warnings at or near the end of the log we would need to see them.

Regards,
Kent

PS - No doubt some sharp-eyed reader will notice the file system has not been expanded on this player. I skipped this step on purpose for some code testing, but in general it should always be done.


Forum Jump: