Any idea what might cause this? Corrupt config? I noticed the app wasn’t started and attempting to start it resulted in failing to initialize 22002010000 error code. I upgrade to latest version and still same result. Reboot of the NAS resulted in the same.
Anyone know how to fix this?
Thanks,
Rob
Hey all… I posted this problem over on Netgear’s forums and mdgm was able to fix it. Details are posted here:
To anyone with this problem, the outcome of the above link was cited as:
"At some point Plex crashed and the pid file /apps/plexmediaserver/MediaLibrary/Plex Media Server/plexmediaserver.pid was left behind. Consequently each time you tried to start Plex, Plex thought it was already running and refused to start."
(just in case it ever becomes inaccessible)
I had a string of issues that led up to this while trying to update PLEX (in my case, to v1.0.2.2413) on my ReadyNAS 516.
I’m not entirely sure what ultimately did me in, but here’s how it happened to me…
First, I downloaded the app, but I realized that my computer was disconnecting from the network; I was using the new Internet Explorer on Windows 10, so when I reconnected to the network, it said I could resume the download (which I did).
When it finished downloading, I was unsure about whether or not to turn off the PLEX app while doing the update, so I initially opted to try turning it off so that if any files required replacement or modification, they wouldn’t somehow be in use. At this point I uploaded the update via my NAS’s app installer [Upload button] the first time.
At first, nothing seemed to happen, and I wasn’t even sure if anything was going on because I wasn’t seeing any visual feedback, so I turned the app back on and tried again. Nothing. Completely mystified, I suspected that perhaps the “resume” function didn’t quite perform the task the way one might expect it to, so I re-downloaded the app (without the network error this time).
With the freshly downloaded app on hand, I repeatedly attempted to update, until eventually I was hit with a sudden barrage of messages [all of them the same] saying that the app couldn’t be installed: “Cannot install application plexmediaserver-ros6.binaries_1.0.2.2413-7caf41d_amd64.deb”.
At this point, the app disappeared completely from my list of apps, so [thinking, “uh… this is new…”] I tried installing it again, but the app stayed missing and I was issued the same error mentioned above. Attempting to install an older working version that I had saved a few weeks ago also yielded the same outcome at that point, so I decided I’d go to bed (give it a few hours) and check on it in the morning (in case I was just being impatient).
Nothing changed by the time I got up; PLEX on all devices still deemed the NAS to be missing and it was still not showing up in the apps section. Consequently, I restarted the NAS (via its GUI), and tried to run the install/update again; this yielded the same error as before, and the app remained missing.
Next, I tried installing a different (new) app via the NAS’s app store [to see if the problem was installing apps in general (which could be indicative of a problem with the Operating System itself), or if installing specifically PLEX was the problem]; the app installed without a hitch.
At this point, I switched browsers [from IE to Firefox]; after attempting to upload the app this time, it seemed to install, but despite now seeing a space for PLEX being vacated/allocated in the Installed Apps area, it was blanked out [no image/logo], and I couldn’t switch it on (I kept getting and error, “Empty Resource Call:l Bad NML Code: 22002010000”). In essence, I now had what appeared to be a placeholder.
This went on for 15-30 minutes, until the NAS gave me the ‘green light’ message indicating that PLEX had successfully installed. Upon opening the app, I got an error within the PLEX Web User Interface regarding missing media or home screen issues; it attempted to direct me to the forums, but after refreshing the webpage, and hitting the Home button, everything sorted itself out.
In short, I’d stay away from working on the NAS via IE Explorer (I’d recommend Firefox or Chrome instead), not RESUMING a download (opting rather for a fresh download to avoid a crash while installing), and I’d advise patience for the 22002010000 error (because it may just be an indicator that PLEX is in the process of applying the updates, therefore restarting the NAS during such time could totally screw up the installation).
I just want to highlight that no SSH (the programming language most often used for accessing and navigating hidden items throughout the ReadyNAS) was needed to fix this issue, which I’m bringing up because renaming/deleting the pid file mentioned in the previous post’s solution would [to the best of my knowledge] require some SSH/programming abilities (and I’m pretty sure engaging in such ventures yourself would cripple your warranty if you inadvertently modify something that messes up your Operating System), so [assuming you don’t know what you’re doing] I’d lean towards contacting Netgear’s Tech Support if you suspect the previous solution to be what you need (that way, they can remotely access the file in question, rename it, and if the desired outcome is established, they can then safely delete it).
NOTE: @rfreas Rob, I know your issue was solved already, so I’m not trying to direct this towards you specifically as much as anyone that runs into similar issues in the future. Big thanks for your prior input; fortunately I didn’t have to address the file that was singled out in your link. 
Just wanted to add a quick extra tidbit of information regarding this issue for any unlucky soul who’s not under any warranty and stuck doing things the SSH way on a ReadyNAS system.
First, you’ll need to enable SSH:
http://kb.netgear.com/app/answers/detail/a_id/30068/~/readynas-os-6%3A-ssh-access-support-and-config…
Here’s a quick article covering how to log onto ReadyNAS via Putty:
http://kb.netgear.com/app/answers/detail/a_id/30070/related/1/session/L2F2LzEvdGltZS8xNDY5NTU5NTAxL3…
These are some of the basic SSH commands:
I’m not sure where the .pid files are stored on ReadyNAS, but they’re generally stored in a well-defined location of the filesystem to allow other programs to find out the process identification number (pid) of a running script. In most Linux-based systems, they’re said to be housed under “/var/run”, and most unices will clean this directory on boot (which is why a full reboot usually helps).
Main ReadyNAS Plex Files storage location (according to the PLEX team):
/apps/plexmediaserver/MediaLibrary/Plex Media Server/
Also, I just came across this: “The easiest way to get to it is to startup RAIDar. It should find your NAS, then click on Browse. This will open up the NAS directory. Click on data, then .apps, and then plexmediaserver. I believe that’s where the file is at and you can just delete it. It fixed my issue.”, so… that’s a possible option (?), although the source page had conflicting results in terms of users actually finding the offending file.
Here’s the link to ReadyNAS-related downloads (including RAIDar):
http://kb.netgear.com/app/answers/detail/a_id/20684
I ran into this error AGAIN on a new/2nd server [brought about by a 1-second power-outage] without realizing I had already dealt with it before; luckily, Googling the issue brought me to my old response from 2 years ago! (lol)
This time, I can confidently confirm that renaming “plexmediaserver.pid” (ex. to “plexmediaserver.pid_OLD”, if you want to play it safe) or deleting it right away (if you’re braver) will allow the app to start-up properly without the error, and [based on my experience] will allow for it to generate a new .pid file in place of the old one.
The location of the .pid file [on Netgear ReadyNAS systems] is in the following directory:
\“YOUR_NAS_NAME”\data.apps\plexmediaserver\MediaLibrary\Plex Media Server
I hope this helps someone like it helped me… again… 
thanks, you did help me, and saved my time
