Synology DS416 upgraded to version 1.22.1.4200-6000 and fails to start

Server Version#:1.22.1.4200-6000
Player Version#:n/a
Just upgraded my Synology DS416 to 1.22.1.4200-6000 and it can’t start.

logs from my DS416 :
==> synopkg.log <==
2021/03/17 09:23:03 start Plex Media Server: begin to start version 1.22.1.4200-6000

==> synoservice.log <==
2021-03-17T09:23:03-05:00 Tortula synoscgi_SYNO.Core.Package.Control_1_start[22898]: service_start.c:74 synoservice: [pkgctl-Plex Media Server] starting …

==> synopkg.log <==
2021/03/17 09:23:03 start Plex Media Server 1.22.1.4200-6000 Begin pre-load apparmor
2021/03/17 09:23:03 start Plex Media Server 1.22.1.4200-6000 End pre-load apparmor ret=[0]
2021/03/17 09:23:03 start Plex Media Server 1.22.1.4200-6000 Begin start-stop-status start

==> auth.log <==
2021-03-17T09:23:04-05:00 Tortula su: pam_unix(su:session): session opened for user plex by (uid=0)
2021-03-17T09:23:06-05:00 Tortula su: pam_unix(su:session): session closed for user plex

==> synopkg.log <==
2021/03/17 09:23:29 start Plex Media Server 1.22.1.4200-6000 End start-stop-status start ret=[1]
2021/03/17 09:23:29 (system) trigger Plex Media Server 1.22.1.4200-6000 Begin start-stop-status stop

==> rm.log <==
2021-03-17T09:23:30-05:00 Tortula rm: uid: 0, euid: 0, arguments:["-rf" “/usr/syno/synoman/webman/3rdparty/plex”]

==> synopkg.log <==
2021/03/17 09:23:30 (system) trigger Plex Media Server 1.22.1.4200-6000 End start-stop-status stop ret=[0]
2021/03/17 09:23:30 (system) trigger Plex Media Server 1.22.1.4200-6000 Begin unload apparmor
2021/03/17 09:23:30 (system) trigger Plex Media Server 1.22.1.4200-6000 End unload apparmor ret=[0]

==> synoservice.log <==
2021-03-17T09:23:31-05:00 Tortula synoscgi_SYNO.Core.Package.Control_1_start[22898]: service_start.c:180 synoservice: [pkgctl-Plex Media Server] start failed.[0xD900 manager.cpp:204]

==> synopkg.log <==
2021/03/17 09:23:31 stop Plex Media Server: begin to stop version 1.22.1.4200-6000

==> synoservice.log <==
2021-03-17T09:23:31-05:00 Tortula synoscgi_SYNO.Core.Package.Control_1_start[22898]: service_stop.c:23 synoservice: [pkgctl-Plex Media Server] stopping …
2021-03-17T09:23:31-05:00 Tortula synoscgi_SYNO.Core.Package.Control_1_start[22898]: service_stop.c:38 synoservice: [pkgctl-Plex Media Server] is already stopped.
2021-03-17T09:23:31-05:00 Tortula synoscgi_SYNO.Core.Package.Control_1_start[22898]: service_stop.c:86 synoservice: [pkgctl-Plex Media Server] stopped.

==> synopkg.log <==
2021/03/17 09:23:31 stop Plex Media Server: stop version 1.22.1.4200-6000 successfully, result 0
2021/03/17 09:23:31 start Plex Media Server: start version 1.22.1.4200-6000 failed, result 272

Logs.zip (4.8 MB)

Sorry, I wasn’t clear. I was running 4163. I upgraded to 4200 and now it won’t start. 4163 worked fine. That’s why I sent the logs of the NAS showing the error loading the plex server application and not plex logs. There are no plex logs from 4200 because it never ran.

If I uninstall plex and install 4200 clean will my data be safe?

Ok, I’ll uninstall and re-install after verifying the crc

Uninstalled Plex, downloaded 4200 checking to make sure it was for ARMv7 DS416 variant, verified CRC SHA-1, did a manual install on the NAS, still, “Failed to run the package service”

After uninstalling and rebooting again I installed the previous version and it’s working. For now I’ll just wait for the next version. Thanks for your help.

@tsmolen

Would you mind doing that iteration one last time?

If so, Engineering would like both the logs and the database.
They are trying to reproduce the problem but cannot.
They hope to have a copy of a failed state to examine.

I will send you a PM when you’re ready

@ChuckPa I can try it again. Before I start what exactly do you want me to capture prior to and after trying the upgrade.

Hey guys, jumping in here because I think I have the same issue on my QNAP TS-831X. Installing ”PlexMediaServer-1.22.1.4200-c073686f2-armv7hf_neon.qpkg” gives me no errors, but PMS fails to run. Reverting back to v1.22.0.4163 solves the problem.

Attaching my logs + database to the Plex Gods. So I installed 4200, tried to run it but neither Plex Web or Plex Media Player would find any server. Reinstalled 4163. Made sure it started, and saved the logs.

Happy to help if there is anything else I can do.

Plex Media Server Logs_2021-03-18_22-43-00.zip (600.2 KB)
databaseBackup.db3b354045-f08e-4ec5-9428-fa991121ab3c.zip (2.9 MB)

ARMv7 ? PMS 1.22.1.4200?

Please install the previous (public) build for now.

We’re trying to find out why the HF (+ Neon) builds are impacted.
The build system didn’t change so this has caught us off guard

@Shroomis

Reviewing your logs shows very slow database tine (SLOW QUERY).

When’s the last you optimized the database?

If it’s been a while / not set for automatic, Please do so now and restart PMS

@ChuckPa

Hm, that’s odd. Just optimized and cleaned the database today right before I installed the update and collected the logs - as well as have it automatically clean every week. Maybe just slow because it’s running on a NAS with mechanical hard drives? Or because PMS was just restarted?

Anyway, thanks for the fantastic forum support! You guys actually seem to care about your users, which is basically unheard of in the business. Very appreciated!

EDIT: Just installed v.4204 (from Plex Media Server - Forum Preview: Faster and smaller builds with new toolchain!) and it works just fine :slight_smile:

4204 does not run on DS416.

2021/03/19 07:44:18 start Plex Media Server: start version 1.22.2.4204-6000 failed, result 272

Will revert back to last working version.

@tsmolen

Hope you don’t mind me asking, but you made sure you downloaded the DSM6 version (and not the DSM7)?

I downloaded and installed “PlexMediaServer-1.22.2.4204-0a657c52f-armv7neon_DSM6.spk”

Ok, sorry to hear it didn’t work for you. Hopefully the devs will sort it out soon.

Me too. I can wait. Looking forward to the smaller and faster builds. If there’s anything I can do to help troubleshoot just ask.

It seems there is a problem with 4200 and 4204 on ARMv7.
At last report, Engineering is working on it.

2 Likes

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.