I'm doing some housecleaning on my Moode Player tr3 so the log files don't gather quite so much dross.
1) Every few minutes, /var/log/syslog would get a new entry of the form
With a bit of Google enlightenment, I edited /etc/rsyslog.conf to comment out the final stanza:
After restarting the service, the offending message no longer appears in the log. You may have different needs for the xconsole so YMMV.
2) Every 5 or so minutes, /var/log/syslog gets another 9 lines related to DHCPDISCOVER activity on my (unconnected) eth0 interface. Haven't looking into stopping that yet. Tim?
3) Roughly every 13 minutes, /var/log/samba/log.smbd was getting entries of the form
Tim already alluded to the answer. After a bit of Googling, I edited /etc/samba/smb.conf to add three lines to the global section:
I don't know if all three lines are necessary, but since restarting smbd no more of these entries have appeared in the log.
4) ah, well, I haven't yet gotten to the "lock up" behavior and the concomitant messages which show up in the logs
Regards,
Kent
1) Every few minutes, /var/log/syslog would get a new entry of the form
Code:
May 4 14:07:12 moode rsyslogd-2007: action 'action 17' suspended, next retry is Wed May 4 14:07:42 2016 [try [url=http://www.rsyslog.com/e/2007]diyAudio server HTTPS page[/url] ]With a bit of Google enlightenment, I edited /etc/rsyslog.conf to comment out the final stanza:
Code:
# daemon.*;mail.*;\
# news.err;\
# *.=debug;*.=info;\
# *.=notice;*.=warn |/dev/xconsoleAfter restarting the service, the offending message no longer appears in the log. You may have different needs for the xconsole so YMMV.
2) Every 5 or so minutes, /var/log/syslog gets another 9 lines related to DHCPDISCOVER activity on my (unconnected) eth0 interface. Haven't looking into stopping that yet. Tim?
3) Roughly every 13 minutes, /var/log/samba/log.smbd was getting entries of the form
Code:
[2016/05/13 09:08:52.697072, 0] ../source3/printing/print_cups.c:151(cups_connect)
Unable to connect to CUPS server localhost:631 - Bad file descriptor
[2016/05/13 09:08:52.697816, 0] ../source3/printing/print_cups.c:528(cups_async_callback)
failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL
]Tim already alluded to the answer. After a bit of Googling, I edited /etc/samba/smb.conf to add three lines to the global section:
Code:
[global]
...
printing = bsd
printcap name = /dev/null
disable spoolss = yes
...I don't know if all three lines are necessary, but since restarting smbd no more of these entries have appeared in the log.
4) ah, well, I haven't yet gotten to the "lock up" behavior and the concomitant messages which show up in the logs
Regards,
Kent
Good idea, Phil. I found the stream easily enough. Will submit with a logo icon if no one has already.
Regards,
Kent
Hi,
Not planning to do this in near future because of (a) low demand and (b) it creates an additional support vector.
When Raspbian Stretch is released it will include ALSA .29 which is one of the parts required for native DSD, so maybe in that timeframe I can do something, or possibly the lintweeker DSD patch will be part of stock MPD by then and nothing extra will need to be done
Regards,
Tim
I'm doing some housecleaning on my Moode Player tr3 so the log files don't gather quite so much dross.
1) Every few minutes, /var/log/syslog would get a new entry of the form
Code:May 4 14:07:12 moode rsyslogd-2007: action 'action 17' suspended, next retry is Wed May 4 14:07:42 2016 [try [url=http://www.rsyslog.com/e/2007]diyAudio server HTTPS page[/url] ]
With a bit of Google enlightenment, I edited /etc/rsyslog.conf to comment out the final stanza:
Code:# daemon.*;mail.*;\ # news.err;\ # *.=debug;*.=info;\ # *.=notice;*.=warn |/dev/xconsole
After restarting the service, the offending message no longer appears in the log. You may have different needs for the xconsole so YMMV.
2) Every 5 or so minutes, /var/log/syslog gets another 9 lines related to DHCPDISCOVER activity on my (unconnected) eth0 interface. Haven't looking into stopping that yet. Tim?
3) Roughly every 13 minutes, /var/log/samba/log.smbd was getting entries of the form
Code:[2016/05/13 09:08:52.697072, 0] ../source3/printing/print_cups.c:151(cups_connect) Unable to connect to CUPS server localhost:631 - Bad file descriptor [2016/05/13 09:08:52.697816, 0] ../source3/printing/print_cups.c:528(cups_async_callback) failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL ]
Tim already alluded to the answer. After a bit of Googling, I edited /etc/samba/smb.conf to add three lines to the global section:
Code:[global] ... printing = bsd printcap name = /dev/null disable spoolss = yes ...
I don't know if all three lines are necessary, but since restarting smbd no more of these entries have appeared in the log.
4) ah, well, I haven't yet gotten to the "lock up" behavior and the concomitant messages which show up in the logs
Regards,
Kent
Hi Kent,
#3 already taken care of and I'll check out #1, thanks.
-Tim
After 3 days of using p.max_requests set at 200 i have not yet experienced any symptoms of CPU hog.
I will keep reporting on this
Hi,
Yes it would be NAS.
On Moode NAS config screen, Remote directory should be set to volume1/folder_containing_music. NOTE no forward slash on "volume1".
-Tim
After 3 days of using p.max_requests set at 200 i have not yet experienced any symptoms of CPU hog.
I will keep reporting on this
Thanks for the update, taiebot65. It's encouraging.
nginx and fastcgi are unexplored territory for me. From a quick read of the variable description, this change seems credible. I made it yesterday so don't have much time on the meter yet. I hope this is the answer.
Regards,
Kent
Hi,
Moode 2.6 Test Release 4 (TR4) is available for download at moodeaudio.org under the TEST CODE button.
This TR fixes bugs reported in TR3, adds 320K BBC radio stations, new audio device descriptions and bumps to shairport-sync 2.8.3
Like the previous test releases, TR4 includes support for the new Raspberry Pi 3 and is built on moodeOS 1.0 the new J-Lite based operating system for Moode Audio Player. Features included in TR4 are listed below. Refer to the release notes for the complete list.
- NEW: Support for Raspberry Pi 3
- NEW: moodeOS 1.0 J-Lite factored for Moode Audio Player
- NEW: WiFi automatic Access Point (AP) mode
- NEW: True random play for a continuous stream of music
- NEW: Airplay metadata and cover art
- NEW: Audio scrobbler service for Last.FM
- NEW: USB storage devices auto-mounted by disk label
- NEW: Network configuration system
- NEW: Auto-configuration system
- UPD: Bump to Linux kernel 4.4.8
- UPD: MPD custom compiled version 0.19.15
- UPD: WiringPi compiled version 2.32
- UPD: Bump to shairport-sync 2.8.3
Fixes to bugs reported in previous TR's
- FIX: NFS mount fails because rpcbind not enabled at boot
- FIX: Ext4 file system fails to auto-mount
- FIX: Hfsplus file system fails to auto-mount
- FIX: ALSA vol not set to 0dB when switch MPD volume control to Software or Disabled
- FIX: Channel swap can occur when Pi 3 + I2S + 16 bit audio
Be sure to read the updated SETUP GUIDE to learn how to make use of new capabilities. The (i) help text in Moode itself provides additionl explanation of features.
Enjoy!
Regards,
Tim
Moode 2.6 Test Release 4 (TR4) is available for download at moodeaudio.org under the TEST CODE button.
This TR fixes bugs reported in TR3, adds 320K BBC radio stations, new audio device descriptions and bumps to shairport-sync 2.8.3
Like the previous test releases, TR4 includes support for the new Raspberry Pi 3 and is built on moodeOS 1.0 the new J-Lite based operating system for Moode Audio Player. Features included in TR4 are listed below. Refer to the release notes for the complete list.
- NEW: Support for Raspberry Pi 3
- NEW: moodeOS 1.0 J-Lite factored for Moode Audio Player
- NEW: WiFi automatic Access Point (AP) mode
- NEW: True random play for a continuous stream of music
- NEW: Airplay metadata and cover art
- NEW: Audio scrobbler service for Last.FM
- NEW: USB storage devices auto-mounted by disk label
- NEW: Network configuration system
- NEW: Auto-configuration system
- UPD: Bump to Linux kernel 4.4.8
- UPD: MPD custom compiled version 0.19.15
- UPD: WiringPi compiled version 2.32
- UPD: Bump to shairport-sync 2.8.3
Fixes to bugs reported in previous TR's
- FIX: NFS mount fails because rpcbind not enabled at boot
- FIX: Ext4 file system fails to auto-mount
- FIX: Hfsplus file system fails to auto-mount
- FIX: ALSA vol not set to 0dB when switch MPD volume control to Software or Disabled
- FIX: Channel swap can occur when Pi 3 + I2S + 16 bit audio
Be sure to read the updated SETUP GUIDE to learn how to make use of new capabilities. The (i) help text in Moode itself provides additionl explanation of features.
Enjoy!
Regards,
Tim
Attachments
Found an interesting quirk which you all may already know.
Following on philrandal's suggestion, I located and downloaded a .pls file for BBC World Service Online, captured a reasonable icon (from a third-party site, as it happens), and installed the pair on my tr3-based system.
It turns out the .pls file contains two entries; one is the main bbc stream and the second is the backup stream. With this two-entry .pls in /var/www/mpdmusic/RADIO, and a new row in cfg_radio pointing to it, I see one "BBC World Service Online" station displayed in the Browse/RADIO list. When I add it to the Playback list, I see two "BBC World Service Online" stations displayed in the list. Selecting the first, I get the main stream plus my icon; selecting the second, I get the backup stream and the default Moode icon.
It looks like there are three choices:
1) live with the anomoly;
2) stick my thumb in the eye of the anomoly by reducing the .pls file to one entry for the main bbc stream; or
3) bypass the anomoly by creating two .pls files, one for each stream, and modifying cfg_radio accordingly, so both main and backup streams get a proper icon.
My instinct is to choose door #1 but perhaps someone else has a better idea.
Regards,
Kent
Following on philrandal's suggestion, I located and downloaded a .pls file for BBC World Service Online, captured a reasonable icon (from a third-party site, as it happens), and installed the pair on my tr3-based system.
It turns out the .pls file contains two entries; one is the main bbc stream and the second is the backup stream. With this two-entry .pls in /var/www/mpdmusic/RADIO, and a new row in cfg_radio pointing to it, I see one "BBC World Service Online" station displayed in the Browse/RADIO list. When I add it to the Playback list, I see two "BBC World Service Online" stations displayed in the list. Selecting the first, I get the main stream plus my icon; selecting the second, I get the backup stream and the default Moode icon.
It looks like there are three choices:
1) live with the anomoly;
2) stick my thumb in the eye of the anomoly by reducing the .pls file to one entry for the main bbc stream; or
3) bypass the anomoly by creating two .pls files, one for each stream, and modifying cfg_radio accordingly, so both main and backup streams get a proper icon.
My instinct is to choose door #1 but perhaps someone else has a better idea.
Regards,
Kent
Hi Kent,
If u want to support multiple links in a pls and still get the logo to display just add the additional urls to cfg_radio and specify the logo as images/radio-logos/name_of_logo.png. similar to how the BBC 320K stations use the logo for the regular BBC stations.
-Tim
Last edited:
My USB DAC stopped working under TR4
Hi, thanks for the great work on MoodeAudio.
I've just upgraded from TR3 to TR4. TR4 did not work with my previous USB DAC set-up. I have a Creative Sound Blaster X-Fi Surround 5.1 Pro which was working fine in TR3.
It seems to be repeated connecting and disconnecting the USB DAC, here's an extract from syslog:
Hi, thanks for the great work on MoodeAudio.
I've just upgraded from TR3 to TR4. TR4 did not work with my previous USB DAC set-up. I have a Creative Sound Blaster X-Fi Surround 5.1 Pro which was working fine in TR3.
It seems to be repeated connecting and disconnecting the USB DAC, here's an extract from syslog:
Last edited:
Hi,
On my TR4 systems with configured NAS source(s) the log shows ok startup.
20160514 220731 worker: NAS sources (mountall initiated)
20160514 220731 worker: MPD consume reset to off
20160514 220731 worker: End startup
20160514 220731 worker: Ready
The log u posted shows nothing after trying to mount NAS source(s).
Very odd.
-Tim