I am using the latest everything like typical, but I have run into a server lockup condition every few days in the last week. I can see from MLWorker what the effect is, but I do not know if this is the cause.
Between weather map look-ups and filing cabinet queries, MLWorker gets into this sort of loop of events. If I kill worker, all is well. If I kill weather and DVDLobby, all is well. See the log attached for a short piece of what was happening for the last 14 hours or so. This eats up so much processor time, that the system fails. Note that this file repeated over and over and over for hours.
And for all the normal questions; I am downloading about 10 maps every hour. I do not have excessive media changes. All paths and the Internet connection are solid. Everything works great for a good period of time after an MLS restart. This is acting almost like the trigger that tells either weather or DVDLobby that the data was retrieved is not happening from I am assuming MLWorker. I do not know the logic.
Discuss topics related to the plugins and uses for MLServer beta
2 posts • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest