dstroot

Members
  • Posts

    79
  • Joined

  • Last visited

Posts posted by dstroot

  1. Not to mention keeps power use to a minimum with integrated graphics.

     

    True ... and many of us who build mini-ITX servers are very focused on keeping our power consumption as low as possible.    For example, my Q25B system idles under 20w  :)

     

    @garycase - hey Gary if you read this I am building a small system in the next couple weeks.  No more than four drives and some headroom for a few docker containers.  Just looking for MB/CPU and maybe Power Supply advice.  What would be the best low(ish) power bang for the buck MB and CPU these days?  Since I know you are an ECC memory fan let's assume ECC RAM as well.  Thanks!

  2. I get an email every day with the following:

     

    error: skipping "/var/log/docker.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
    error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
    error: skipping "/var/log/vsftpd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
    error: skipping "/var/log/wtmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
    error: skipping "/var/log/btmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
    

     

    Also reported many times elsewhere:

     

    http://lime-technology.com/forum/index.php?topic=36527.msg339961#msg339961

    http://lime-technology.com/forum/index.php?topic=36527.msg339963#msg339963

    http://lime-technology.com/forum/index.php?topic=36527.msg339973#msg339973

    http://lime-technology.com/forum/index.php?topic=36527.msg339985#msg339985

    http://lime-technology.com/forum/index.php?topic=36527.msg341657#msg341657

    http://lime-technology.com/forum/index.php?topic=37201.msg343880#msg343880

     

    Help? Advice?

     

    [update]

    How to fix:

    https://linuxslut.net/logrotate-parent-directory-has-insecure-permissions/

    https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1278193

    https://www.novell.com/support/kb/doc.php?id=7005219

     

    I added “su root root” to the bottom of of each file in /etc/logrotate.d.  Example in attached image.

     

    I think it is also possible to address this via “/etc/logrotate.conf” and possibly that is the only file that needs editing.  I just didn’t want to break everything. 

     

    Of course the changes are lost if you reboot. 

    log.png.47bd033b244cd7e518274e15dacf67b9.png

  3. I keep getting emails with this:

     

    error: skipping "/var/log/docker.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
    error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
    error: skipping "/var/log/vsftpd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
    error: skipping "/var/log/wtmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
    error: skipping "/var/log/btmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
    

     

    It was mentioned by others earlier in the thread.  Is there a fix?  Thanks.

  4. This is posted here in case it helps anyone but also so I can store the info somewhere.  ;)  If you have a fresh Unraid 6.x beta:

     

    1) change your default boot option to use Xen/Unraid (Xen is off by default)

    2) Turn on the network bridge br0 so we can share our connection to our new VM

     

    The steps are documented here: http://lime-technology.com/forum/index.php?topic=32733.0

     

    I did not use this but there looks to be a good script to install Ubuntu 14.04 here: http://lime-technology.com/forum/index.php?topic=33132.0

     

    Once you get Ubuntu 14.04 LTS up and running things get pretty easy.  Ubuntu 14.04 LTS has Docker natively packaged.  So to install Docker we just have to:

     

    $ apt-get install docker.io

     

    Now create a container.  This is like inception - we are going to run an Ubuntu container, on Ubuntu, on Slackware.  So pull Ubuntu down:

     

    $ sudo docker.io pull ubuntu

     

    Fire it up:

     

    $ sudo docker.io run -i -t ubuntu /bin/bash

     

    And with that command, Ubuntu is now officially in Docker, on your server. You are now inside of shell in your very own Linux container. Note: just like any shell type `exit` to exit the docker container...

     

    NOTE: Ubuntu uses docker.io as the executable name instead of just docker. This is because of a Debian/Ubuntu policy; there is already a program called “docker”. This can be changed.  Here is a full install script:

     

    # Docker on Ubuntu 14.04 LTS
    sudo apt-get install docker.io
    
    #
    # if you prefer the command docker over docker.io 
    # on Ubuntu 14.04 LTS
    #
    
    # Create /usr/bin/docker the Debian/Ubuntu way
    # (avoid conflicting with docker – System tray)
    sudo update-alternatives –install /usr/bin/docker docker /usr/bin/docker.io 50
    
    # Allow bash completion for docker
    sudo cp -a /etc/bash_completion.d/docker{.io,}
    sudo sed -i 's/\(docker\)\.io/\1/g' /etc/bash_completion.d/docker
    
    # Allow zsh completion for docker
    sudo cp -a /usr/share/zsh/vendor-completions/_docker{.io,}
    sudo sed -i 's/\(docker\)\.io/\1/g' /usr/share/zsh/vendor-completions/_docker
    
    # the man page for docker
    sudo ln -s /usr/share/man/man1/docker{.io,}.1.gz
    
    # not really needed because docker.io is still there
    sudo sed -i 's/\(docker\)\.io/\1/g' /usr/share/docker.io/contrib/*.sh
    
    # Test Docker
    sudo docker pull ubuntu
    sudo docker run -i -t ubuntu /bin/bash
    exit
    

  5. One more question - I have searched all over and feel really dumb but I cannot figure out how to boot into "Dom 0" mode so Xen is working.  I run headless and don't even have a monitor anymore where I could see the boot options - is that what I am missing?  Anyway to set to boot with Xen support via .cfg or go files?  I really have looked all over but most Xen posts seem to assume you have already booted properly to Xen mode.

     

    OK - after more digging I found you can edit syslinux.cfg from the Unraid GUI.  Default settings below:

     

    default /syslinux/menu.c32

    menu title Lime Technology

    prompt 0

    timeout 50

    label unRAID OS

      menu default

      kernel /bzimage

      append initrd=/bzroot

    label unRAID OS Safe Mode (no plugins)

      kernel /bzimage

      append initrd=/bzroot unraidsafemode

    label Memtest86+

      kernel /memtest

    label Xen/unRAID OS

      kernel /syslinux/mboot.c32

      append /xen --- /bzimage --- /bzroot

    label Xen/unRAID OS Safe Mode (no plugins)

      kernel /syslinux/mboot.c32

      append /xen --- /bzimage --- /bzroot unraidsafemode

     

    What do I edit to use Xen?

  6. Just so folks know...

     

    UnRaid has had a race condition problem with the plugin feature.  I do not personally think its fixed yet and that is what I believe some of us are running into and why we have run the installer manually.  If the network has not yet finished initialization by the time the install runs the installs fail.  That's why it works when you run it manually (i.e. by then everything is up).

     

    I have a Supermicro board and I use DHCP to hand out addresses (even "static" ones) - it's just easier that way, and I think this slows my network initialization enough that the plugin installer always fails on boot. 

     

    Hope this helps someone.

  7. Download the "SimpleFeatures Plugins" zip from our Google Code page. Choose the plugins you wish to install. The Base package is required for all other packages to run.

     

    2. Create folder called "plugins" at the base of the flash drive - "/boot/plugins"

     

    3. Copy in the plugins (must have .plg extension) you wish to have installed on Boot.

     

    4. Reboot. If it looks funny, please clear your browser cache!

     

    Uhhh... I just flew for 7 hours but where do you put the core .tgz file? 

     

    Nevermind - I see the core is now a plugin in the plugins directory since I downloaded the whole zip archive.