Search come to Wheel of death most of the time

[Tangs]

Most of the time I use Search I end up with a wheel of death.

Sometimes it works, for a few searches I have the results in a second, then, the Search is crashing.

I can have this issue with every of my devices, database optimised, with a strong Internet connection 4G or WiFi, it doesn’t matter.
Specially if I am looking for a search with more than 2 words, but even with 1 word it can happen.

It is so frustrating. Most of the time to stop it I have to force close or/and delete the cache.

This issue is there since a long time. If I try to do the same searches on Qobuz, Tidal, Spotify, Appel Music, I have instant results. With Plexamp, it doesn’t work, Search is weak in my experience.

I recorded a video here, this is just one exemple, I can reproduce this issue in a minute using this fonction.

Video :

24 mars 2024

And logs:
196390554588310.zip (192.9 KB)

[elan]

This is not a Plexamp bug, your searches are timing out (28 is timeout). Either a connectivity issue or a server issue.

Mar 24, 2024 03:02:19.434 [0xaf647cc0] DEBUG - Networking: Completed request 63: (GET https://79-87-64-20.1b4318a1d4044f70ba272bbf129084a6.plex.direct:32400/hubs/search?query=The%20beatl&excludeFields=summary&limit=4&includeCollections=1&includeFields=thumbBlurHash&X-Plex-Device-Name=Android) with code -28 (have 0 bytes) in 30037 ms.
Mar 24, 2024 03:02:19.879 [0xaf647cc0] DEBUG - Networking: Completed request 65: (GET https://79-87-64-20.1b4318a1d4044f70ba272bbf129084a6.plex.direct:32400/hubs/search?query=The%20beatle&excludeFields=summary&limit=4&includeCollections=1&includeFields=thumbBlurHash&X-Plex-Device-Name=Android) with code -28 (have 0 bytes) in 30210 ms.
Mar 24, 2024 03:02:20.087 [0xaf647cc0] DEBUG - Networking: Completed request 67: (GET https://79-87-64-20.1b4318a1d4044f70ba272bbf129084a6.plex.direct:32400/hubs/search?query=The%20beatles&excludeFields=summary&limit=4&includeCollections=1&includeFields=thumbBlurHash&X-Plex-Device-Name=Android) with code -28 (have 0 bytes) in 30165 ms.
Mar 24, 2024 03:02:32.499 [0xaf647cc0] DEBUG - Networking: Completed request 131: (GET https://79-87-64-20.1b4318a1d4044f70ba272bbf129084a6.plex.direct:32400/hubs/search?query=Agnostic%20fdont&excludeFields=summary&limit=4&includeCollections=1&includeFields=thumbBlurHash&X-Plex-Device-Name=Android) with code -7 (have 0 bytes) in 37 ms.
Mar 24, 2024 03:02:57.729 [0xaf647cc0] DEBUG - Networking: Completed request 105: (GET https://79-87-64-20.1b4318a1d4044f70ba272bbf129084a6.plex.direct:32400/hubs/search?query=A&excludeFields=summary&limit=4&includeCollections=1&includeFields=thumbBlurHash&X-Plex-Device-Name=Android) with code -28 (have 0 bytes) in 30266 ms.
Mar 24, 2024 03:02:58.126 [0xaf647cc0] DEBUG - Networking: Completed request 107: (GET https://79-87-64-20.1b4318a1d4044f70ba272bbf129084a6.plex.direct:32400/hubs/search?query=Ag&excludeFields=summary&limit=4&includeCollections=1&includeFields=thumbBlurHash&X-Plex-Device-Name=Android) with code -28 (have 0 bytes) in 30255 ms.
Mar 24, 2024 03:02:58.742 [0xaf647cc0] DEBUG - Networking: Completed request 109: (GET https://79-87-64-20.1b4318a1d4044f70ba272bbf129084a6.plex.direct:32400/hubs/search?query=Agn&excludeFields=summary&limit=4&includeCollections=1&includeFields=thumbBlurHash&X-Plex-Device-Name=Android) with code -28 (have 0 bytes) in 30426 ms.
Mar 24, 2024 03:02:59.141 [0xaf647cc0] DEBUG - Networking: Completed request 111: (GET https://79-87-64-20.1b4318a1d4044f70ba272bbf129084a6.plex.direct:32400/hubs/search?query=Agno&excludeFields=summary&limit=4&includeCollections=1&includeFields=thumbBlurHash&X-Plex-Device-Name=Android) with code -28 (have 0 bytes) in 30288 ms.
Mar 24, 2024 03:02:59.628 [0xaf647cc0] DEBUG - Networking: Completed request 113: (GET https://79-87-64-20.1b4318a1d4044f70ba272bbf129084a6.plex.direct:32400/hubs/search?query=Agnos&excludeFields=summary&limit=4&includeCollections=1&includeFields=thumbBlurHash&X-Plex-Device-Name=Android) with code -28 (have 0 bytes) in 30298 ms.

[elan]

@elan

code -7

And you’re getting one code 7 which is a failure for the connection to even work at the lowest level. Something network is bad.

[Tangs]

Thank you Elan, then i’ll investigate on the server side, I am getting crazy with this

[Tangs]

Hi Elan,
I ran somes tests using Search on Plex app localy, Plexamp app localy and Plexamp on my phone.
I tested my connection before the test :

My PC :

My phone :

to be sure i have a good connection.

I made a search for 2 bands :“The Beatles”, “Beatles”, “The Who”, “Who”, and 2 songs :“i’ve got the feeling”, “A little cold” that i have in my librairie.

Plex app localy found everything.

Plexamp localy found the bands, but make mistake for "i’vegot the feeling:

it’s stay there and nothing came after
as for “a litlle cold” it didn’t find it and made a wheel of death after i changed the search for “little cold”:

Plexamp on the phone had similar results from plexamp on pc for the bands but i couldn’t try the songs because of a wheel of death

Here are the warning i got from using Plexamp:

Mar 27, 2024 13:31:51.815 [8512] WARN - [Req#4c05] SLOW QUERY: It took 1156.250000 ms to retrieve 4 items.

I also noticed that seraching for “Beatles” was a lot faster than searching for “The Beatles”, same goes with “Who” and “The Who”
Also removing the “a” before “a little cold” gives also a much faster results

I attached the logs from the server and from Plexamp
The tests started at 13h25

Here are the Plex server logs from this test :
Plex Media Server Logs_2024-03-27_13-41-13.zip (3.7 MB)

Plexamp logs :
13393440564993.zip (113.6 KB)

[zotje]

I’ve had the same issue with Plexamp. I don’t bother doing searches in Plexamp anymore. Anything with special characters or spaces seems to grind on my server.

[elan]

Shouldn’t be the case with an optimized database, unless you have a massive library on very slow hardware.