dawiki

Members
  • Posts

    17
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

dawiki's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Here is what I did: I downloaded the Tretflix appliance to my Mac "extracted" the ova image - tar xvf Tretfilx.ova converted the vmdk disk image to raw-format using VBoxManage - VBoxManage clonehd Tretflix....-disk1.vmdk Tretflix...-disk1.raw -format RAW compressed the raw file and transferred it to the unRAID box extracted the compressed raw file and created a very simple cfg file: name = "Tretflix" bootloader = "pygrub" memory = 4000 vcpus = 8 disk = [ 'phy:/mnt/cache/Xen/Tretflix/Tretflix-v1.3_x64-NAS-disk1.raw,xvda,w', ] vif = [ 'mac=00:16:3e:01:01:02,bridge=br0' ] bootloader = "pygrub" when starting the vm i could not attach to the console session - xl console Tretflix did not work correctly but I checked what the ip of the vm was and was able to connect to the ssh session then the wizard kicked in and i configured my system with several apps (couchpotato, sabnzbd, sickbeard, plex, transmission) this worked like a charm and I added my unRAID share as a cifs storage and now I have all downloads going to my unraid share with all the relevant applications running in the Tretflix appliance -> awesome
  2. I set up tretflix and it is very straight forward after having figured out a working solution for converting to a raw disk I updated the bundled transmission version to the latest. I am using sabnzbd, couchpotato, sickbeard and transmission. Don't want to go back - previously used ironicbadger's archVM which was also working great but requiring more admin stuff
  3. I know it seems to be unfair to post this here (feels like jumping the ship of boiler) but I converted influencers plugins to be x86_64 compatible: http://lime-technology.com/forum/index.php?topic=21260.msg287064#msg287064
  4. Justed wanted you to know that I got the monitoring to work with version 9 of sysstat by only changing this command-line call. in include/HardwareStats.php:116 if ($days<=$graph) exec("sadf -d -U $interval $log $sadf|awk -F';' '$valid {print $3,$data}'",$input); to if ($days<=$graph) exec("sadf -D $interval $log $sadf|awk -F';' '$valid {print $3,$data}'", $input); it worked fine for me and I could use all features - realtime, interval, history I don't want to start a big discussion over this - just saying that I didn't find anything special that didn't work when using sysstat 9.x But that could be just me and my specific hardware
  5. Hi! Thank you for porting dynamix to 6.0 so quickly. I tried to integrate the stats plugin myself and discovered that it should be easily possible to reuse the standard package of sysstat: http://slackware.cs.utah.edu/pub/slackware/slackware64-14.1/slackware64/ap/sysstat-9.0.6.1-x86_64-1.txz I am just wondering why you didn't use this package as a standard dependency but integrated the binaries within the dynamix.system.stats-0.0.0-x86_64-1.txz I thought about making a -noarch- package containing only the emhttp pages and php scripts and using the architecture dependent libs from the system repository. I know that you have to change some php code due to changes from php 4.x to 5.x (talking about the call-time pass-by-reference things for exec calls and some more) but these dependencies are not platform specific but version specific. Nevertheless I installed the web gui and system.stats plugin and i am running it without issues Again thanks for that
  6. Hi! I just wanted to let you know that I ported SabNZBd, CouchPotato, Sickbeard and Transmission to unRAID 6.0. The process was somewhat simple: For each plugin (e.g. sabnzbd_unplugged.plg) I analysed the binary dependencies and manually searched for a slackware64/14.1 alternative So these dependencies: <FILE Name="/boot/packages/python-2.6.6-i486-1.txz" Run="upgradepkg --install-new"> <URL>http://slackware.cs.utah.edu/pub/slackware/slackware-13.37/slackware/d/python-2.6.6-i486-1.txz</URL> <MD5>b8de0c9f8b89aa7b3c89823d20076867</MD5> </FILE> <FILE Name="/boot/packages/sqlite-3.7.5-i486-1.txz" Run="upgradepkg --install-new"> <URL>http://slackware.cs.utah.edu/pub/slackware/slackware-13.37/slackware/ap/sqlite-3.7.5-i486-1.txz</URL> <MD5>6786d3764cb294ecb71cdd24e6d171d1</MD5> </FILE> translate well into simple slackware64-14.1 libs. I remove the packages from the plugin file and just manually download them to /boot/extra. But there are a few exceptions (e.g. python-yenc and python-cheetah) and I compiled these packages myself, removed them from the plg and manually put them in /boot/extra I think the solution to separate the binary (or platform dependent) libs from "scripts" and support files is generally a good approach I did try trolley and created some packages there and I must say it was really easy and works quite well. However I find the solution with separate /boot/config/plugins and /boot/extra work better for me because of the integration in the loading mechanism of unRAID Just my 2 cents PS: If you are interested in the procedure or just want to try it out yourself, I created a install script and uploaded all compiled packages for sabnzbd. https://github.com/dawiki/unRAID_6.0
  7. I added direct linking of unofficial packages in dependencies and sent you a pull request (https://github.com/nicinabox/boiler/pull/2) I converted the transmission_unplugged plugin and this is also registered and works as expected I would like to refactor sabnzbd and get rid of the other packages I created, but I guess you will have to manually remove the boiler packages since there is no unregister command Anyway I will post here when I finished work for sabnzbd and no longer need the other boiler packages to make it work best regards
  8. I managed to get sabNZBd to work with only boiler packages. Thank you for providing these really easy-to-use tools I have a few remarks though but I don't want to sound ungrateful I created a repository for each dependency that is not available in the official slackware repos - I ended up creating these repos: sabnzbd_unplugged unrar python-cheetah python-yenc pyopenssl par2cmdline It works pretty well and is usable however I expected to only need to install sabnzbd_unplugged but then it presented me the following messages: ... => Installing No package named 'par2cmdline' No package named 'pyopenssl' No package named 'python-cheetah' No package named 'python-yenc' No package named 'unbar' => Installed! It would be nice if the boiler dependencies were resolved automatically and installed before the "leaf" package (sabnzbd in my case) Another minor thing is that at first I created a single github repo with just the tgz-packages and linked to the single files from boiler register - well that didn't work and I noticed that the packages are created on the client immediately after executing boiler install I guess the boiler client is also using git for communication and there is no server part that does pre-packaging and so on Nevertheless I am quite satisfied with what I accomplished and I thank you again for providing the tools I think I will continue with the other plugins that I have installed including couchpotato, sickbeard, transmission, openssh and btsync good night from the center of europe
  9. thanks for the reply I started converting the external dependencies to boiler packages and noticed that it is pretty straight forward all i had to do was mkdir packageName - unpack (with tar ...) - boiler init packageName - boiler pack packageName there are only a few things that have to be done manually in this process: define the version (should be possible to parse??) define author(s) - remains manually although could be set to a configured name (dawiki in my case:)) define license define home page I guess this is far down the road but it could be automated - at least for version bumps since it should be possible to take license and home page information from the previous version boiler.json BTW do I have to register a package or is it possible to use a dry run mechanism and check if everything is working without publishing it to a git repo?
  10. ok - thanks for clarifying that I have another question: I want to create a boiler package out of a plugin. I start by converting the plugin to the boiler structure with boiler convert plugin . That works good so far. BTW I'm "testing" it with the SABNZBd plugin from influencer. I noticed that the convert command doesn't recognise all dependencies and also doing things wrong. I noticed this: ... "dependencies": [ "http://slackware.cs.utah.edu/pub/slackware/slackware-13.37/slackware/d/python-2.6.6-i486-1.txz", "http://slackware.cs.utah.edu/pub/slackware/slackware-13.37/slackware/ap/sqlite-3.7.5-i486-1.txz", "http://slackware.cs.utah.edu/pub/slackware/slackware-13.37/slackware/a/infozip-6.0-i486-1.txz", "http://slackware.cs.utah.edu/pub/slackware/slackware-13.37/slackware/n/openssl-0.9.8r-i486-3.txz" ], ... There are two things that are interesting. According to the documentation dependencies should be "A hash of dependencies ("openssl": ">=1.0.1c")..." but in this case the outcome is an array of strings. Does this work? Secondly there are missing dependencies - as far as I see only packages in the slackware.cs.utah.edu package management are converted - all others are ignored. Unfortunately SABNZBd for example has a few dependencies that originate in a different repository - just some examples: http://connie.slackware.com/~alien/slackbuilds/python-cheetah/pkg/13.37/python-cheetah-2.4.4-i486-1alien.tgz http://www.slackware.com/~alien/slackbuilds/unrar/pkg/13.37/unrar-4.2.4-i486-1alien.tgz http://unraid-greenleaf-repository.googlecode.com/files/par2cmdline_tbb-0.4-i486-1kh.tgz How would I use boiler configuration to install those? With a post install step? Also I'm playing with the idea of providing boiler packages for all dependencies like unrar to improve the package version handling
  11. I changed the reference to boiler.json in version.rb to be absolute: module Boiler config = JSON.parse File.read "/var/log/boiler/boiler/boiler.json" VERSION = config['version'] end then it works regardless of the file being present in the working dir
  12. i copied /var/log/boiler/boiler/boiler.json to /usr/local/boiler/lib/boiler .. then it works actually the boiler.json file has to be in the working directory .. hmm btw a lot of boilers in this path
  13. ok .. now I get a different error /usr/local/boiler/lib/boiler/version.rb:2:in `read': No such file or directory - boiler.json (Errno::ENOENT) from /usr/local/boiler/lib/boiler/version.rb:2:in `<module:Boiler>' from /usr/local/boiler/lib/boiler/version.rb:1:in `<top (required)>' from /usr/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/local/boiler/lib/boiler/cli.rb:5:in `<top (required)>' from /usr/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/local/bin/boiler:12:in `<main>' also - bundle list is returning a warning and no meaningful information: /boot/custom/gems/ruby/1.9.1/gems/bundler-1.3.5/lib/bundler/vendor/thor/shell/basic.rb:336: warning: Insecure world writable dir /boot/custom/gems/ruby/1.9.1/bin in PATH, mode 040777 Could not locate Gemfile
  14. I would like to install it but can't get it to work root@Tower:/boot/extra# boiler /usr/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- bundler (LoadError) from /usr/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/local/boiler/lib/boiler/cli.rb:1:in `<top (required)>' from /usr/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/local/bin/boiler:12:in `<main>' as far as I understood the install script installs gems in /boot/custom/gems but when executing boiler it tries to load gems from /usr/lib/ruby/gems. Here is an excerpt of gem environment - GEM PATHS: - /usr/lib/ruby/gems/1.9.1 - /root/.gem/ruby/1.9.1
  15. I also found out the what the php error caused when clicking the stats page in unRAIDStats.page you have defined the Title with unescaped quotes (") inside the string replacing the inner double-quotes with single quotes will get you one step further: Title="<a href='#' id='diskStatsButton'>Disk Stats</a><span id='buttonDivider' style='display:none'> | </span><a href='#' id='unraidStatsButton' style='display:none'>System Stats</a>"