[PROBLEM] Plexamp - super slow web interface

[bikerman]

Hi
Since updating to 9.08 I have had problems running Plexamp. 

When I start the renderer and attempt to open the web interface http://192.x.x.x:32500 I get the background render but nothing else. Refreshing the browser doesn't help

When I restart the Plexamp renderer, I would immediately get a connection refused from the web browser (indicating the service was running)

Restarting the RP doesn't help

Eventually, seemingly randomly, the interface will finally populate and I am able to play music. If I close the tab and re-open a new instance of the web interface it will take up to 7 mins to fully populate the web interface again.

Once the web interface is fully populated, selecting albums, playing music and or navigating the UI is smooth as butter.

The only odd thing I noticed, was after the update to 9.0.8. when the problem started, when the UI eventually came up it asked me to login to Plex (as if a new install).

My plex server install is in another country, however I can access music library using the full fat Plex client app on ubuntu no problems or pointing browser directly to plex server, so seems to me this an issue on my Moodeaudio install


Any ideas?

[Tim Curtis]

Are there any errors in the startup log?

The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from any of the Config screens. The startup log will be at the end of System info output.

[bikerman]

Are there any errors in the startup log?

The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from  any of the Config screens. The startup log will be at the end of System info output.

No obvious errors, I can send the full log if you want but it looked pretty ok to me with the line below suggesting it started ok

20240903 085624 worker: Plexamp:         started, ALSA maxvol: 100%


Is there log file can I run 'tail -f' to capture in realtime when recreating the problem?

Thanks

[Tim Curtis]

I don't have a Plex account anymore so I'm not able to do any testing but maybe you have to go through the "claim code" process again?

You could also verify that node.js (which plexamp uses) is running. If the command below doesn't return anything it means that node is not running and this indicates some sort of breakage.

Code:

pgrep -a node | grep plexamp

[bikerman]

I don't have a Plex account anymore so I'm not able to do any testing but maybe you have to go through the "claim code" process again?

You could also verify that node.js (which plexamp uses) is running. If the command below doesn't return anything it means that node is not running and this indicates some sort of breakage.

Code:

pgrep -a node | grep plexamp

It seems to be running 

PHP Code:

damien@MoodePi3B:~ $ pgrep -a node | grep plexamp
1641 /usr/bin/node /home/damien/plexamp/js/index.js 


How do I instigate the claim code process? I did a quick search and it appears I have the kill the process ID? I am assuming by running will do it?

Code:

node plexamp/js/index.js

 Thanks

[Tim Curtis]

Theres a link to a Setup Guide in the Plexamp section of Audio Config that explains the whole process of getting Plexamp installed and getting the claim code.