So what i feel now, looking back, is that stale PMS service was running all along even though on the QTS desktop i see one app for PMS which i started/stopped/removed/etc and that seemed broken and was messing up with the latest app. So then i killed that process and restarted the PMS all over again and that solved the problem.
It stayed at the above logs.īut when i ran netstat, i could still see a process namely “Plex Media Server” running, which is odd, since i just stopped the server. Plus when i stopped PMS from QTS Desktop the logs did not update, no indication of “server shutting down” or anything for that matter. So clearly there was problem starting the server, but the default port (32400) was still accessible via telnet/nc. I ssh’ed into the installation and checked the logs, there it showed me the following error messages,Ġ9:49:31.078 DEBUG - Completed forward migration 20201103130000.Ġ9:49:31.102 DEBUG - HttpServer: Listening on IPv6 as well as IPv4.Ġ9:49:31.102 ERROR - HttpServer: Error binding acceptor: Address already in useĠ9:49:31.102 ERROR - HttpServer: Error opening acceptor on IPv6, falling back to IPv4: Address already in useĠ9:49:31.102 ERROR - Error: Unable to set up server: listen: Address already in use (N5boost10wrapexceptINS_6system12system_errorEEE) Here’s what i did, might prove helpful for anyone else that might face similar problems. Plex Media Server - DSM 6 -> 7 upgrade on Tue Jun 8 22:08. However, post update, Plex no longer starts, citing MFPlat.DLL not installed. Prior to installing the Windows 10 Anniversary update today, my Plex Media Server ran fine on Windows 10 PRO N, having once previously installed the Media Feature Pack for Windows 10. In the notification center, I saw (probably during installation): Unable to update 'Plex Media Server'. PLEX Media Server fails to start after anniversary update - MFPlat.dll not found. DSM 7: Recently, I upgraded to DSM 7 Beta and I see the same issue with Plex beta. If(( Get-RestMethod -Uri " $PlexToken " -OutVariable response -PassThru -ErrorAction Silentl圜ontinue).I did some more troubleshooting and i guess i seem to have figured out the problem. Few months ago, it simply failed to start. Invoke-Command -ComputerName Server1 -Credential Administrator -ScriptBlock Update-PlexMediaServer -EmailNotify -SmtpTo -SmtpFrom -SmtpUser Username -SmtpPassword Password -SmtpServer -SmtpPort Port -EnableSSL Update-PlexMediaServer -PlexLogin -PlexPassword Update-PlexMediaServer -PlexServerToken -Passive EXAMPLE Run Passive and update using Server Online Authentication Token.
0 kommentar(er)
