lainie

Members
  • Posts

    444
  • Joined

  • Last visited

Everything posted by lainie

  1. this is something that lainie should answer as *s*he is compiling the package. The VirtualBox installer (the VirtualBox<version>.run file that comes from the VirtualBox Download page) extracts binary files to "/opt/VirtualBox" directory, creates an udev rule, compiles and insert the kernel modules and creates a lot of links. If you need further customization (like a specific other location), you will probably need to compile your own; here is a link to the guide on how to compile VirtualBox for unRAID. If you can present a good reason why everyone (using this package/plugin) would want VirtualBox installed elsewhere & provide instructions, I can look into incorporating it into future versions.
  2. There is a wiki page with instructions on how to compile VirtualBox for unRAID. Some people reported having issues with the scripts at the bottom. I don't use the scripts, I use the step-by-step instructions. The kernel file to download differs with each version, but the site to get the latest kernel remains the same. It was requested that I add in some code to the doinst.sh file to add in a fix for USB & the commands appear to differ slight across unRAID versions: unRAID all 5.x versions mkdir -p /boot/custom/vbox -m 0777 groupadd vboxusers usermod -aG vboxusers root usermod -aG vboxusers nobody mkdir /dev/vboxusb -m 0750 chown root:vboxusers /dev/vboxusb unRAID 4.7 mkdir -p /boot/custom/vbox -m 0777 groupadd vboxusers usermod -G vboxusers root usermod -G vboxusers nobody mkdir /dev/vboxusb -m 0750 chown root:vboxusers /dev/vboxusb If you follow back the links in the second post of this thread to the previous thread on VirtualBox, you will see it was never something other people could not do. It was just a process (documented on the wiki) which involved installing additional software & building custom headers. Many people requested someone else to do it for them (some people did not have the hardware, others did not want to install additional software or just had trouble with the steps), I was able to make the vbox package & offered the files. It grew a little from there, but is still something that is documented. I previously tried hosting the files in other locations. Initially SkyDrive, but the links were not direct downloads (which was requested). I thought GitHub would be a good choice, but the files are over 80MB & can not be individually downloaded (had to clone the whole archive to download... which meant either store 1 file per archive or force anyone wanting one file to download them all if I stored them in one archive). So I went with private hosting on one of my domains. This allows direct download, I can post the md5 checksum (also requested) & keep updated instructions. The plugin is pulling from my host (which seems to be working well). If you add having multiple people be able to upload & maintain files, it may require the files to move elsewhere again (it is a very basic hosting plan).
  3. According to the phpvirtualbox wiki, the error " The object functionality is limited" usually occurs when phpvirtualbox is started before virtualbox is available. If you stop (kill) vboxwebsrv & restart it, does the error still occur? Since the plugin is not installing phpvirtualbox, if you have phpvirtualbox starting before the plugin fully loads virtualbox, that could be the issue.
  4. When I visit the wiki page for phpvirtualbox & look up that error, this is the page I find on it: Issue 640: Vbox 4.2.4 error: The object functionality is limited (0x80070005) Are you starting VirtualBox with a script at startup (before unRAID finishes loading up the drive where vbox is located)? If so try waiting until after unRAID has started the array fully & any external drives are mounted.
  5. Looks like a difference in the usermod command on unRAID 4.7. I was asked to include the following lines to allow USB devices to work: groupadd vboxusers usermod -aG vboxusers root usermod -aG vboxusers nobody mkdir /dev/vboxusb -m 0750 chown root:vboxusers /dev/vboxusb Think these 2 lines are giving you the error: usermod -aG vboxusers root usermod -aG vboxusers nobody Here are the options of usermod in unRAID 5: usermod --help Usage: usermod [options] LOGIN Options: -c, --comment COMMENT new value of the GECOS field -d, --home HOME_DIR new home directory for the user account -e, --expiredate EXPIRE_DATE set account expiration date to EXPIRE_DATE -f, --inactive INACTIVE set password inactive after expiration to INACTIVE -g, --gid GROUP force use GROUP as new primary group -G, --groups GROUPS new list of supplementary GROUPS -a, --append append the user to the supplemental GROUPS mentioned by the -G option without removing him/her from other groups -h, --help display this help message and exit -l, --login NEW_LOGIN new value of the login name -L, --lock lock the user account -m, --move-home move contents of the home directory to the new location (use only with -d) -o, --non-unique allow using duplicate (non-unique) UID -p, --password PASSWORD use encrypted password for the new password -s, --shell SHELL new login shell for the user account -u, --uid UID new UID for the user account -U, --unlock unlock the user account AaronJAnderson: I would think that virtualbox would still work & it is showing installed. Not sure about your RAM... could be related to unRAID being a 32bit OS... not sure. Are you unable to run VirtualBox? Or does it work, but you were just reporting the errors? I've never run unRAID 4.x (except for making the vbox package), seems like those with the USB fix may not have either. Will await your response before changing anything further. I can remove the USB fix or try to customize it for unRAID 4.x with better usermod command options... (may take some testing if I try to find the right command options)... whatever is preferred.
  6. [glow=red,2,300]Compiled virtualbox 4.2.6 for unRAID 5RC11 kernel 3.4.26 is now available.[/glow] Our phpVbox leader Lanie can affirm, but you have both described the two different approaches to get the install up and running. Either fix the root unraid user/pw or comment the prompt out altogether. I have updated the installation instructions (specifically the phpvirtualbox instructions). See if this is more to everyone's liking & let me know if it still needs further changing. I think you should try to implement a basic unraid install as a virtualbox guest with vbox host installed inside your esxi unraid install with vbox host. Performance would probably be abysmal, but it would be a definite 'yo dawg, I heard you like virtual machines' moment. When I compile these virtualbox files for unRAID, I use my Windows 7 Pro system running VirtualBox, create a VM for unRAID (whichever version I am compiling for), then install virtualbox inside the unRAID VM & make a package for it. Do I get a 'yo dawg, I heard you like virtual machines' moment? It is VirtualBox inside VirtualBox instead of VirtualBox inside VMware... but I think that should be close enough
  7. I noticed RC11 came out several days ago. I thought I would have time to do it one night earlier this week, but have been busier than I expected. I should have some time this weekend. Apologies for the delay... it will be available soon.
  8. Can't change my vote, but came here to thank burr for PM-ing me & update my above statement. I do have a 64bit CPU & do not care which version (32 or 64) that I run. I have 8GB of RAM that could benefit from the 64bit. Happy to know I should be able to run either. Why I thought I had a 32bit: The link to my CPU info from my hw thread no longer works. I swear there used to be 2 pages on the Xeon 5160, one for SLABS which is 64bit & one for SL9RT (that I have) which is 32bit. I see links to SLABS & SL9RT on the side of this page on the 5160, but don't see it mentioning 32bit instructions anywhere now. My output showing lm flags: root@Lament:~# uname -a Linux Lament 3.4.24-unRAID #1 SMP Mon Jan 7 16:44:53 PST 2013 i686 Intel(R) Xeon(R) CPU 5160 @ 3.00GHz GenuineIntel GNU/Linux root@Lament:~# root@Lament:~# grep flags /proc/cpuinfo |grep lm flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca lahf_lm dtherm tpr_shadow flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca lahf_lm dtherm tpr_shadow flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca lahf_lm dtherm tpr_shadow flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca lahf_lm dtherm tpr_shadow root@Lament:~#
  9. When I purchased my server for unRAID last year it was a 64bit system, but the 1 CPU it came with was a dual core 1.86GHz processor. As unRAID was only capable of 32bit processing & I wanted more speed, when I purchased faster (2 dual core 3GHz CPUs), I did not check if it was 32 or 64 bit... turns out I purchased the 32bit version. I thought it was beefy enough to survive a few major upgrades, but if 32bit goes away... I guess my options are a slower single CPU (which I still have) with an up-to-date OS on it -or- much faster CPUs with an older OS... I blew my computer budget at the time of my upgrades... Some of the RAM in my desktop Windows PC went bad & I have not even been able to replace it (which is painfully obvious that I need it). I voted to keep 32bit support available for a little longer... would vote to maintain both 32 & 64 if it were available as a poll option.
  10. Here is a link to a beginners guide to svn. Subversion or SVN is a software version-ing and revision control system. Developers use SVN to maintain current and historical versions of files such as source code, web pages, and documentation. For Newznab SVN connection details, join the official IRC, /query newznab !svn YOUR-NNID - Please be careful not to say your NNID in the main channel. To make sure you're in the right window try /query newznab !hello test I had googled it after posting although wasn't sure how you install it? The 2nd link in the beginner's guide explains how to checkout files from svn. To install / download / checkout the files, you will need the server information, username & password... which is obtained in IRC as described above.
  11. Here is a link to a beginners guide to svn. Subversion or SVN is a software version-ing and revision control system. Developers use SVN to maintain current and historical versions of files such as source code, web pages, and documentation. For Newznab SVN connection details, join the official IRC, /query newznab !svn YOUR-NNID - Please be careful not to say your NNID in the main channel. To make sure you're in the right window try /query newznab !hello test
  12. My unRAID server is using an APC Back-UPS XS-1500. Signature has a "Link to my server & hardware mods" with pictures (mostly of my server, but the UPS is in the background). I do not have it set to auto-shutdown or have the USB attached at this point. I live in central FL (lightening capital of the US) & we get many 'brown outs' all year, but mostly in the summer months. Have yet to have a 'brown out' or 'black out' out last longer than my UPS, though any hurricane season could change that... but if a storm is coming, I 'hunker down' at home & can turn it off myself.
  13. If you create a directory on the cache drive that begins with a period (for example: ".apps") the mover will not touch it. When I initially installed sick & sab, the instructions I used recommended using a directory named ".custom" on the cache drive to contain the apps. Later I moved to using plugins, but never changed the location. I am on version 5 & could make a cache only share (& might some day), but have not wanted to change all my settings to use a new path. Only problem I have seen was when a specific program on my Windows PC did not list the ".custom" directory when browsing the cache drive. I typed the directory name / path in manually & it worked. Hidden directories - an option to consider.
  14. I need to try this when I get home. Thanks Jang!! Jangjong, I have updated the install instructions now to use vboxwebsrv -b -H 127.0.0.1 --logfile /var/log/vbox.log instead of /dev/null. That way the log will be in the same directory as syslog & other logs. Your post on how to setup multiple web ports for lighttpd helped me & when I see someone wanting to run multiple web apps, I point them to your thread. Lots are using the information found in that thread successfully (including me). Thank you for sharing it. Jtech007, You need to edit the lighttpd.cfg file for your setup. This includes editing the IP addresses for your server, providing the path to phpvirtualbox & making sure there are no rewrite rules applied to phpvirtualbox. The above log file fix is not the issue for you. It would not hurt to change it, but it has nothing to do with changing how your web server displays pages.
  15. If you ran Sickbeard on the flash drive, it was not part of the parity protected array. Yes, you can set Sickbeard & Sabnzbd to run from the cache drive (or a SNAP drive or some other mounted disk outside the array) & then move any of your downloads once they are complete to their final home on your parity protected array. Just create an apps share that uses the cache drive only then set Sickbeard to move & rename the files to their correct parity protected location. If you are afraid of the cache drive dying, occasionally run a backup of it to your parity protected array. If you are keeping your media stored on the array, it is only your app settings that will need to be backed up & those are not likely to change often. tar -pczf name_of_your_archive.tar.gz /path/to/directory should work well. Replace "name_of_archive" with something like "/mnt/user/user_shared_directory/apps_backup_YYYY-mm-dd" (YYYY-mm-dd for the date). The "/path/to/directory" would be something like "/mnt/cache/apps" or whatever you name the share. As a side note, unRAID 5RC10 has been working great for me.
  16. I'm not sure I am getting a full picture of what is going on, so let me get you to clarify your last post. You copied exactly what jangjong listed? (which includes IP address, port numbers & paths for his setup, not yours) His post is a guideline for your to see how multiple rewrite rules can be used on different ports. You will need to put in your IP address, the path to your web directories... might be able to use the port numbers he listed, but can also change them to be something easy for you to remember (just need to make sure nothing else on your system is using the port number you choose). Installed all 3 what? Vbox, vboxwebsrv & the extension pack are the 3 I think you mean. For setproperty, I think you mean you ran these 2: VBoxManage setproperty websrvauthlibrary default VBoxManage setproperty vrdeauthlibrary default If you are able to get a login prompt, but having trouble logging in, then running "VBoxManage setproperty websrvauthlibrary null" without the quotes would fix that. This will depend on how you setup your lighttpd.cfg file & what port & path you set. Did you remove any settings you originally configured for newznab? Or did you specify a path to phpvirtualbox on another port?
  17. Everything looks like it is running that should be. You mentioned Plex... that made me think about other plugins... Are you running Newznab or Spotweb or anything that includes rewrite rules for your web server? I don't run Plex, so not sure if it had you change any settings on the web server; I know both spotweb & newznab require rewrite rules which do not play well with other web applications. If rewrite rules from another program is the issue, let me direct you to this post by jangjong in the spotweb thread. I used his information to have newznab on its own port, spotweb on its own port & phpvirtualbox running on the same port as PHPMyAdmin, all on the same system.
  18. There is a wiki page for phpvirtualbox at http://code.google.com/p/phpvirtualbox/w/list that lists some common errors with phpvirtualbox. If you have a problem with it that is not listed there, click the Issues tab link, click the dropdown box next to Search (which is default set to Open Issues) & change it to "All Issues" then use the next box to type part of your error message & click the Search button.
  19. It is probably the same ones listed in the wiki. I downloaded them a while back & to install just run installpkg *.t?z For unRAID 5.x all kernels: binutils-2.20.51.0.8-i486-1.txz cxxlibs-6.0.13-i486-2.txz gcc-4.4.4-i486-1.txz gcc-g++-4.4.4-i486-1.txz glibc-2.11.1-i486-3.txz make-3.81-i486-1.txz mpfr-2.4.2p03-i486-1.txz ncurses-5.7-i486-1.txz patch-2.5.4-i486-1.txz perl-5.10.1-i486-1.txz For unRAID 4.7 kernel: binutils-2.18.50.0.9-i486-1.tgz cpio-2.5-i486-3.tgz cxxlibs-6.0.9-i486-1.tgz gcc-4.2.4-i486-1.tgz glibc-2.7-i486-17.tgz make-3.81-i486-1.tgz ncurses-5.6-i486-3.tgz patch-2.5.4-i486-1.tgz perl-5.10.0-i486-1.tgz pkgtools-12.1.0-noarch-7.tgz
  20. I remember seeing someone post that the spaces in the links caused it to not work, but removing them worked. I thought it was fixed, but looks like they are still there. for example: add_pkg http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/a/ glibc-solibs-2.11.1-i486-3.txz should be add_pkg http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/a/glibc-solibs-2.11.1-i486-3.txz Glad it helped.
  21. Can be done with one line. Look at the manpage for the "find" command. Here is an example of what you want. find /mnt/user/Backup/Mysql/ -mtime +2 -name newznab* -type f -exec rm -rf {} \; This command will do a search in /mnt/user/Backup/Mysql/ for all files that were last modified 2 or more days ago and executes a recursive forced (-rf) remove (rm). The "{}" (curly braces) is the place holder for exec to use where it will put the name of the file, and the "\;" tells exec that's the end of the statement. Find is very powerful, and I suggest you do some reading BEFORE you do any removing using "find". Also, as a test you can replace the "rm -rf" with "ls -la" to get a list of all the files that would be removed.
  22. Tybio created a newznab_extras plugin that contains screen. It contains other additional programs, not "just" screen. Here is the link to his github: https://github.com/Tybio/mux/blob/master/newznab_extras.plg. Looks like this is the part where he installs screen: install_screen() { add_pkg http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/a/ aaa_terminfo-5.7-noarch-1.txz add_pkg http://slackware.cs.utah.edu/pub/slackware/slackware-13.37/slackware/a/ utempter-1.1.5-i486-1.txz add_pkg http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/ap/ screen-4.0.3-i486-1.txz } I have not used this plugin yet (may in the future, but I already have most of the programs installed separately), so not sure if there are options to choose which programs you want or if you have to take them all. Wanted to share the link since it might help you.
  23. lainie

    Rsync

    Is DeltaCopy the program you want?
  24. With a keyboard & monitor attached to your server, can you get into the computer's BIOS?
  25. Tweaknews says they carry a.b.hdtv.x264, but many have reported not being able to view it... & not very helpful responses about it from TN support. Seems to be a really good place for a block account, but not sure about them as a main provider.