Stokkes

Members
  • Posts

    361
  • Joined

  • Last visited

Everything posted by Stokkes

  1. If you do not put the "at now + 1 minute" and you have your Application Support directory or cache directory on a disk that's part of your array, there is a risk that Plex won't start properly or won't be able to find your Library due in part to emhttp not having brought up the array in time. The extra "garbage" is simply used as a failsafe.
  2. The only thing I can think of is that it's trying to create one (or more) of the folders and can't for whatever reason. After you've clicked "Save Configuration", can you go see if the folders you set (specifically Application Support and Temporary folders) were created? I will add some logging in the next version I'll release this weekend.
  3. Hey Tom, Any chances of adopting speeding ant's "Simple Features" GUI as the main unRAID interface for 5.0 final? If you haven't considered it yet, I would like to put my vote towards strongly considering it. It's very much indicative of what UI's in today's most cutting edge web apps look like and I think would give a much better impression to unRAID as a whole (marketing wise anyway). Cheers,
  4. Funny you mention this. I was contemplating adding an extra configuration field for "Run As".. I'll release an update sometime over the weekend with this included.
  5. I'll have more to share soon enough on this Let's just say I wouldn't be worried.
  6. I am running all three (PMS, Sickbeard, SAB) and even a few more things in the background without any issues. What is probably happening is that the PMS process is writing temp files to your root directory (/tmp) which is only as big as your USB flash. It may be running out of room, causing it to crap out. If you run this plugin and configure your tmp somewhere on your array (or even better, your cache drive in like /mnt/cache/.tmp), it's one way to alleviate this issue (not saying it'll fix it, but won't hurt).
  7. Did you download v0.2 and install that one? It includes a special file so you can "see" Plex in the Utils page.
  8. Correct. Whatever the version, put it in your flash/extra folder (or /boot/extra if you're a linux command line guy) and it will re-install properly on every boot. Your configuration files will NOT be overwritten.
  9. Nope.. Make sure you've met these conditions: You have unRAID v5-beta10 You have downloaded the full version (v0.2) You have put the downloaded file in your flash/extra directory (not flash/custom) You have rebooted your server once you've put the tgz file in your flash/extra folder If you follow all these steps and have v5b10, there really is no reason why it will not work. You will have to go to your unRAID gui, click on "Utils" and you will see a Plex Media Server icon. Click on it and configure it as necessary.
  10. A few things 1) Try adding this line instead in your /boot/config/go (this SHOULD work.. let me know). /boot/custom/plex.sh &> /dev/null |& at now + 1 minute 2) Add the .tgz to /boot/extra so that it gets installed. The alternative is to use the "Light" version and manually install plex on your cache drive or your array. It's up to you. There should be no reason to do an "installpkg" in your go. There shouldn't be too many repercussions running Plex in memory as nothing really gets written to the install dir (it all goes into the Application Support dir). Let me know!
  11. Version 0.2 Posted in OP. Only fix: Made sure to include the proper parent page for unRAID so that Plex appears in the Utils menu. It should now show up for everyone. (The URL http://server_ip/Utils/Plex still worked though).
  12. Yes it will, but your library, etc will be protected. You can definitely store the generated files on your cache drive if you so wish (that's currently what I'm doing but thinking of moving it to the array). Cheers
  13. To auto-start Plex on boot-up (v0.3+) Insert the following lines in your /boot/config/go file, it will auto start Plex in the background, using the configured "run as" user after 1 minute : # Auto-start PMS on boot echo "/boot/custom/plex/init.sh" | at now +1 minute Note that when you shut down your server, your array will be unable to unmount due to files being in use by Plex. You will have to stop Plex manually when you shutdown.
  14. Last Update: August 7, 2011 v0.3. Please note of the changes that affect the way Plex is started. This is especially important if you have Plex in your /boot/config/go to auto-start on startup. Hello Everyone, For the past few weeks I have been working on developing a Plex plugin for unRAID that will greatly simplify the process of getting Plex Media Server up and running on your unRAID (v5.0 and greater) boxes. I am happy to announce that the day has come to share it with my fellow unRAID-ers out there. There is still some work to do, but hopefully this will help people get up and running pretty quickly with an oh-so-nice gui to control PMS from your unRAID web interface Let's get to it! Features Simple to install unRAID package, just drop and go! GUI interface to configure Plex Media Server on your unRAID box Start / Stop / Manage your Plex Media Server directly from the default unRAID gui Two versions of the plugin. A "Full" version that includes Plex v0.9.3.5-c3e763f and a "Light" version that does not. Current Limitations You must manually start/stop Plex Media Server upon booting/shutting down your unRAID box. Requirements unRAID v5.0-beta10 (untested on previous 5.0 betas). Will not work on v4. Plex v0.9.3.5-c3e763f (if using the Light version). Optional: Simple features plugin by speeding_ant (makes your unRAID 5.0 gui look uber-sexy). Available at http://lime-technology.com/forum/index.php?topic=12698.0 Installation Download either the Full or Light version (link below) Put the downloaded file on your USB drive in the extra folder (create if necessary). If you want to do this directly from your Windows/Mac PC, you would copy it to the "flash" share in the "extra" directory. Reboot your unRAID server OR open a telnet session, type "cd /boot/extra" and then "installpkg plex-<version>-i386-unRAID.tgz" or "installpkg plexlight-<version>-i386-unRAID.tgz" depending on the version you have downloaded. For Light Version Download Plex from the official website and extract the .bz2 file somewhere on your array. Remember where you have installed it as you will need it for the configuration steps below. You will still need to put plexlight-<version>-i386-unRAID.tgz in your flash/extra folder. Configuration Once the plugin has been installed, follow the next steps in order to configure Plex Media Server on your system. Go to your unRAID gui, click on "Utils" and you will see an icon for "Plex Media Server". Alternatively, you can go to http://unraid_ip/Utils/Plex. If you see errors indicating folders do not exist/etc, don't worry, this is normal on first launch Configure your settings: Installed Directory: Enter the path where you have extracted the official Plex release. This is not necessary if you are running the full version! Application Support Directory: Enter the path where you would like to save your Plex Media Server user-generated files (library, logs, etc.). Recommended that you put this somewhere on your protected array. Do not use your flash drive for the library. For those who are already running Plex and already have a library, choose the parent folder where your Library is currently located. This would be something along the lines of /Path/to/Library/Application Support/. Temporary Directory: Enter the path where you would like to save any temporary files (ie: transcodes for iOS devices, etc.) Do not select /tmp or /boot or anywhere on your USB flash drive. Click on Save Configuration to save your settings. If any errors were detected in the path locations that you specified, the plugin will tell you. If all went well, click on Start to start Plex Media Server. By default, Plex is installed in /usr/local/plex and all user generated data (library, plug-ins, temporary files) are stored in /mnt/disk1/plex/. Thanks I'd like to thank Elan from the Plex team for answering a bunch of questions I had during the development of this plugin as well as bubbaQ for his lighttpd plugin that I used as a template in developing the Plex plugin. Download Full Version (55mb): http://dl.dropbox.com/u/26943/Plex%20Plugin/plex-0.3-i386-unRAID.tgz Light Version (13kb): http://dl.dropbox.com/u/26943/Plex%20Plugin/plexlight-0.3-i386-unRAID.tgz Changes v0.1 - August 3, 2011 First public release v0.2 - August 4, 2011 FIX: Plugin wouldn't show up under "Utils" in unRAID (direct URL still worked). v0.3 - August 7, 2011 NEW: Add the ability to run Plex as a different user other than "root". Please re-configure your plugin once you've installed this version. Default will still be "root". NEW: New initialization script /boot/custom/plex/init.sh that is auto-generated and starts Plex in the background under the user configured to run the process. Please use this initialization script from now on to start plex in your /boot/config/go. Do not use plex.sh NEW: Preliminary logging to /var/log/plexunraid.log
  15. There seems to be a problem with AVAHI in beta10 (at least from what I can tell). Upon starting Plex Media Server, it doesn't broadcast via avahi on the default daemon that is started with beta10. If I do an avahi-daemon -r (to reload services), it spits out an error. If I force kill the built-in avahi process that starts with emhttp and restart it using avahi-daemon -D, then things start working properly (and Plex starts broadcasting). Also, trying to do an avahi-daemon -c (to check to see if its running) doesn't return anything. Something is definitely wonky..
  16. I think we need to get the addon procedures ironed out before 5.0 should go final, unless Tom has changed his mind. It would be nice to have all the tools required to develop addons (with auto start/stop, etc.). I've set something up based on some posts here, but it's by far official and definitely a hack job.
  17. Agree - should be up to the individual user Disagree - think a lot (not all) people are babies. Why else would we have so many warnings on packages that should be common sense? Do not touch Iron, you could get burned. Do not put plastic bag over head, you could suffocate. Warning: Never iron clothes on the body. (iron) Warning: Contents may be hot. (coffee) Never use a lit match or open flame to check fuel level Need I say more? And yet McDonald's has always had "Caution: Hot" and someone in the USA still managed to successfully sue after having burned themselves. Do not underestimate the will of the stupid.
  18. I agree with one of two methods already proposed 1) Closed beta, invite only 2) Semi-closed, ability to sign yourself up after a clear disclaimer, maybe a password protected site or something. I see WAY too many posts from people who install a beta and get upset because things don't work, wiped their data, messed up their array or just generally behaved unexpectedly. Quite a few of these posts are also inflammatory. The comment earlier about people being babies is true. Anyone who's worked in any type of support environment can attest to this. Sorry, but this is the cold hard truth. I think there are quite a few unRAIDers that would be more than willing to be guinea pigs for the greater cause (myself included), but I think it's currently way too easy to install a beta.. Why? 1) Posts announcing the new betas are available in the same forum as stable releases 2) Download links for the betas appear on the same page as the stable releases 3) Forums are easily accessible. I think all 3 of these need to be looked at going forward. My $0.02.
  19. Are you still having this issue on beta6? Did you: 1) Make note of where your drives are assigned 2) delete config/super.dat 3) copy bzroot/bzimage to your flash 4) shutdown and reboot your server 5) When it comes back up, re-assign your drives 6) Run the parity sync 7) stop array/reboot after the parity sync is complete.. If you follow these steps, do the drives still show up as missing after #7?
  20. Here's my syslog for the disk issue above. To note that it's disk20 in the log. syslog-20110301-1.txt.zip
  21. Another weird issue: Adding a 500GB disk for Time Machine, assigning it to slot 20 (I actually only have 7 disks, but chose 20 for the TM drive). 1) Pre-clear the disk using Joe's pre_clear.sh script (v1.7 latest) with the parameter -A (for sector 64) 2) Disk preclears fine, no errors 3) Assign to slot 20 4) Start the array, asks to format disk 5) Format disk 6) Turns green, able to copy data on it 7) Stop array Once array is stopped, disk20 turns blue 9) I have to select 'I am sure I want to do this" to restart the array 10) It proceeds to go through a FULL preclear and wipes the drive of any data. 11) Once it's done, rinse and repeat from step #4 I rebooted my server a bit too quickly so I will redo the steps above and post the full syslog. But it's a curious problem and I wouldn't want this to happen to anyone else. Thankfully my drive was empty.
  22. Confirming that modifying security settings / export now works.
  23. Got to work this morning and put beta-5a on a VM (clean, right from zip) and was unable to modify the disk export status for either AFP or SMB.
  24. Interesting new issue that cropped up. Tom/others, if you can confirm? I've wiped my config directory and tried from a fresh configuration, still the same issue: 1) From the main unRAID screen, click on any of the disks to view the disk settings 2) Try turning on or off AFP or SMB export 3) Click Apply 4) It should revert back to whatever it was set to before. I can't turn off or on any AFP/SMB disk export, it simply doesn't "apply" the changes. I believe 5.0-beta4, this was fine.