Hi all.
My setup is a QNAP TS-230 NAS running LMS 8.1.0 with two players, both based on RPi4/PiCorePlayer connected via USB into a standalone DAC, and control points on PCs and various Android phones/tablets all using the Material skin plugin.
Yesterday this all worked fine. During the evening I added some more music files to the NAS and replaced some existing files with higher res versions. I didn't stop the LMS while I was doing that, maybe I should have, and while I was working on it someone else tried unsuccessfully to listen to some music on one of the players.
Anyway, when I had finished the update I performed a scan for new and updated files and when that had finished I tried the system out. Alas, it no longer functioned properly. The control points can see the players and the LMS and can manipulate the playlists on the players as normal. The players, however, cannot play the files in the playlist. When <play> is selected nothing happens; the progress bar does not advance, suggesting that the playback does not even start.
I have restarted the Squeezelite instances and the RPis but this has had no effect. I have also restarted the LMS, of course, and performed a complete rescan, all to no avail.
System details are as follows:
Logitech Media Server Version: 8.1.0 - 1606896523 @ Wed Dec 2 09:24:10 CET 2020
Operating system: QLMS 2.X (QNAP TurboStation) [Debian 9 stretch] - EN - utf8
Platform Architecture: aarch64-linux
Perl Version: 5.28.2 - aarch64-linux-thread-multi
Audio::Scan: 1.02
IO::Socket::SSL: 2.060
Database Version: DBD::SQLite 1.58 (sqlite 3.22.0)
Total Players Recognized: 1
piCorePlayer 2
Player Model: SqueezeLite
Player Type: squeezelite
Firmware: v1.9.6-1206-pCP
Player IP Address: 192.168.1.xx
Player MAC Address: dc:a6:32...
The log shows the following from the morning startup to the time I first tried to play some music:
[20-12-02 06:38:04.7606] main::init (388) Starting Logitech Media Server (v8.1.0, 1606829767, Tue Dec 1 16:19:49 CET 2020) perl 5.028002 - aarch64-linux-thread-multi
[20-12-02 10:18:24.9604] Slim::Web::JSONRPC::requestMethod (455) Request failed with error: Bad params!
[20-12-02 10:18:24.9644] Slim::Web::JSONRPC::requestMethod (455) Request failed with error: Bad params!
[20-12-02 10:18:24.9690] Slim::Web::JSONRPC::requestMethod (455) Request failed with error: Bad params!
[20-12-02 10:18:24.9741] Slim::Web::JSONRPC::requestMethod (455) Request failed with error: Bad params!
[20-12-02 10:18:24.9794] Slim::Web::JSONRPC::requestMethod (455) Request failed with error: Bad params!
Subsequent attempts to play music produce nothing at 'Error' level in the logs so these entries probably don't relate to individual play attempts, more to something in the LMS startup,I guess.
I enabled some more verbose logging and captured the following segment of log which was generated when I attempted to play a song in the playlist:
[20-12-02 16:39:31.0017] Slim::Networking::Slimproto::_stat_handler (784) dc:a6:32:xx:xx:xx: STAT-STMt: fullness=2097151, output_fullness=3513856, elapsed=0.000
[20-12-02 16:39:31.7487] Slim::Player::Squeezebox::stream (1049) strm-q
[20-12-02 16:39:31.8674] Slim::Player::Squeezebox::stream_s (542) stream_s called: format: aac url: file:///share/MMLibraries/MusicLibrary/Compilations/1975%20Chart%20Compilation/02%20Ms%20Grace.m4a
[20-12-02 16:39:31.8690] Slim::Player::Squeezebox::stream_s (937) Using smart transition mode
[20-12-02 16:39:31.8694] Slim::Player::Squeezebox::stream_s (997) Starting decoder with format: a flags: 0x0 autostart: 1 buffer threshold: 255 output threshold: 0 samplesize: 5 samplerate: ? endian: ? channels: ?
[20-12-02 16:39:31.8769] Slim::Networking::Slimproto::_stat_handler (784) dc:a6:32:xx:xx:xx: STAT-STMf: fullness=2097151, output_fullness=3513856, elapsed=0.000
[20-12-02 16:39:31.8775] Slim::Networking::Slimproto::_stat_handler (784) dc:a6:32:xx:xx:xx: STAT-STMf: fullness=0, output_fullness=-1, elapsed=0.000
[20-12-02 16:39:31.8779] Slim::Networking::Slimproto::_stat_handler (784) dc:a6:32:xx:xx:xx: STAT-STMc: fullness=0, output_fullness=-1, elapsed=0.000
[20-12-02 16:39:31.9816] Slim::Networking::Slimproto::_http_response_handle r (553) Squeezebox got HTTP response:
HTTP/1.1 200 OK
Server: Logitech Media Server (8.1.0 - 1606896523)
Connection: close
Content-Type: audio/aac
Set-Cookie: Squeezebox-albumView=; path=/
Set-Cookie: Squeezebox-expandPlayerControl=true; path=/
Set-Cookie: Squeezebox-expanded-MY_MUSIC=1; path=/
Set-Cookie: Squeezebox-expanded-FAVORITES=0; path=/
Set-Cookie: Squeezebox-expanded-PLUGINS=0; path=/
Set-Cookie: Squeezebox-expanded-PLUGIN_MY_APPS_MODULE_NAME=1; path=/
Set-Cookie: Squeezebox-expanded-RADIO=0; path=/
[20-12-02 16:39:31.9821] Slim::Player::Squeezebox2::directHeaders (470) Processing headers for direct streaming:
HTTP/1.1 200 OK
Server: Logitech Media Server (8.1.0 - 1606896523)
Connection: close
Content-Type: audio/aac
Set-Cookie: Squeezebox-albumView=; path=/
Set-Cookie: Squeezebox-expandPlayerControl=true; path=/
Set-Cookie: Squeezebox-expanded-MY_MUSIC=1; path=/
Set-Cookie: Squeezebox-expanded-FAVORITES=0; path=/
Set-Cookie: Squeezebox-expanded-PLUGINS=0; path=/
Set-Cookie: Squeezebox-expanded-PLUGIN_MY_APPS_MODULE_NAME=1; path=/
Set-Cookie: Squeezebox-expanded-RADIO=0; path=/
[20-12-02 16:39:36.0015] Slim::Networking::Slimproto::_stat_handler (784) dc:a6:32:xx:xx:xx: STAT-STMt: fullness=2097151, output_fullness=3513856, elapsed=0.000
[20-12-02 16:39:40.0012] Slim::Networking::Discovery::gotTLVRequest (217) sending response
[20-12-02 16:39:40.0018] Slim::Networking::Discovery::Server::gotTLVRespons e (197) discovery response packet:
[20-12-02 16:39:41.0567] Slim::Networking::Slimproto::_stat_handler (784) dc:a6:32:xx:xx:xx: STAT-STMt: fullness=2097151, output_fullness=3513856, elapsed=0.000
The only thing I notice from this log info is that the player's name is 'piCorePlayer 2' but in the log file it is referenced as 'Squeezebox2'. I don't suppose that's important tho'.
Whoa... I just noticed from the log that yesterday I was running LMS version 8.0.1 and today I'm running 8.1.0, so apparently when I restarted the server after doing the file updates the new version was installed.
I had thought that updating files without stopping the LMS had caused my issue but now I think maybe it is because of the upgrade.
I would be grateful for any help or advice that anyone can offer to get me back up and running pronto.
Thanks in advance,
Jon