RN102: Empty Resource Call error starting Plex app

[minnow24]

Hi-

I noticed my Plex Media Server had turned off when I was trying to update it. I had recently also updated the firmware to 6.5.1. When I tried to turn it back on, I am getting an error: Empty Resource Call:l Bad NML Code: 22002010000. I do not have any Linux experience but I was a reading a thread that I think could resolve my issue. Can someone tell me how I can remove a .pid file? Here is the original thread posted:

https://community.netgear.com/t5/Current-NETGEAR-and-Partners/PLEX-is-failing-to-initialize-with-err...

Thanks

[Tommy_Langzik]

I ran into this problem yesterday and reported my findings to the best of my ability on PLEX's forums:

https://forums.plex.tv/discussion/196307/plex-is-failing-to-initialize-with-error-22002010000-on-lat...

______________________________________________________
I think your best bet would be to contact technical support unless you're familiar with SSH. The file in question won't be visible to you because the Operating System's User Interface is designed to be more minimalist in nature to cater to users that value simplicity (and don't want to accidentally kill their machines); SSH [a unix programming language commonly used in conjunction with a program called Putty] skirts the artificial [visual] limitations of the product and will allow you to both navigate and edit deep within the core of your NAS, but at the cost of providing you an outlet for acutely dammaging your NAS's software (if you don't know what you're doing).

When I contacted Netgear for ReadyNAS's tech support in the past, they were able to access my NAS directly with very little involvement on my end, so I'd approach them with your issue directly [if you're still under any sort of warranty]; they'll try to solve your problem overall, and they might address that file for you if they regard it as necessary.

______________________________________________________

If you're not under any warranty at all and are stuck doing things the SSH way, you'll need to enable it first:
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:
http://www.mybloggingthing.com/ssh-putty-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

______________________________________________________
NOTE: Not sure if you got your issue solved already, Minnow, but just FYI for anyone that comes across a similar issue.