Web server crash loop after scan finishes

Post Reply
peekpoke
Posts: 2
Joined: Thu Nov 03, 2022 1:10 pm

Web server crash loop after scan finishes

Post by peekpoke »

Shortly after starting up, the My Media web page keeps crashing with "There was an error trying to access your My Media Server".
The message appears for maybe half a second, then the server restarts, then the error appears again, over and over.
If I stop then start the MyMedia service, then access the webpage before the Initialization is complete, I can see settings and no crash.
Once the initialization is complete, and it shows my Watch folder as available it starts the crash loop.

I see it going through all the M3U files again looking at the messages log.
Even better it would be great if it wouldn't rescan a file unless it's datetime/size has changed.

Anyway, while it's in it's crash loop all I see in MyMediaForAlexa.log is a PushClient.cs:_tmrMain_Elapsed:104 Ping message about once a minute.
There is nothing about the web server crashing and restarting.

I have turned on <VerboseLogging> and <SuppressAutoScan>, and restarted MyMedia service.
Unfortunately it still does a scan of the watched Music folder (or is loading the index into memory).

Webserver responds okay until that quick scan is complete, then still crashes over and over.

The only error I see in the VerboseLogging is:
WebServer.cs:DoRequest:621 WebServer::DoRequest - file does not exist - lib.fonts.glyphicons-halflings-regular.woff2

It appears the fonts are embedded into the EXE, so I don't see a way to add the missing font.

Then a loop of CheckSubscription, I assume from each time the web server crashes and reruns
03/11/2022 10:08:04.626 7108:0 20 ServiceAgent.cs:CheckSubscription:424 Active subscription - expires 11/3/2023, isTrial=0
03/11/2022 10:08:05.438 7108:0 16 ServiceAgent.cs:CheckSubscription:409 Checking with My Media server for a subscription...
03/11/2022 10:08:05.532 7108:0 10 ServiceAgent.cs:CheckSubscription:424 Active subscription - expires 11/3/2023, isTrial=0
03/11/2022 10:08:07.454 7108:0 21 ServiceAgent.cs:CheckSubscription:409 Checking with My Media server for a subscription...
03/11/2022 10:08:07.532 7108:0 13 ServiceAgent.cs:CheckSubscription:424 Active subscription - expires 11/3/2023, isTrial=0
03/11/2022 10:08:09.470 7108:0 20 ServiceAgent.cs:CheckSubscription:409 Checking with My Media server for a subscription...
03/11/2022 10:08:09.548 7108:0 21 ServiceAgent.cs:CheckSubscription:424 Active subscription - expires 11/3/2023, isTrial=0
03/11/2022 10:08:13.454 7108:0 13 ServiceAgent.cs:CheckSubscription:409 Checking with My Media server for a subscription...
03/11/2022 10:08:13.532 7108:0 21 ServiceAgent.cs:CheckSubscription:424 Active subscription - expires 11/3/2023, isTrial=0

Are there any other logging or debugging options I can see to see if it's really just a missing font, or something more complex?

...........

Followup a day later: I found that even though the number of tracks/artists did not increase it was still scanning.
Nothing in the logs about the scan, so I found this out using SysInternals ProcessMonitor where I could see it scanning through the Music folder.
Once that was complete the web server crash stopped. So something about the scan is crashing the web server.
I'm sorry I don't have more info. Is there any kind of hidden debug option where I can see which source file/line it's crashing at to tell you?
Post Reply