Beiträge von bakman

  • CPU Governor not working at boot

    I have enabled both at boot again. I can see the 'governor' message durng boot appear again.
    I just read this article about vmware passing on static/dynamic frequency data to clients, http://techhead.co/saving-powe…d-frequency-scaling-dvfs/
    This advanced setting value 'Power.CpuPolicy' is not available on ESXi 5.1.


    Even if this data is not passed on to OMV virtual machine, wouldn't the data in

    Code
    # Which governor to use. Must be one of the governors listed in:
#   cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors

    be available in OMV?

  • CPU Governor not working at boot

    Correct


    I'm off now. Will check in tomorrow. I want this boot to be as slick as possible. 8)

  • CPU Governor not working at boot

    I get twice the message:

    Code
    root@demeter:~# update-rc.d cpufrequtils disable
update-rc.d: using dependency based boot sequencing
insserv: warning: current start runlevel(s) (empty) of script `cpufrequtils' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (2 3 4 5) of script `cpufrequtils' overrides LSB defaults (empty).


    The governor warning during boot is gone.
    cpufreq info still the same:

    Code
    root@demeter:~# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  no or unknown cpufreq driver is active on this CPU
  maximum transition latency: 4294.55 ms.
analyzing CPU 1:
  no or unknown cpufreq driver is active on this CPU
  maximum transition latency: 4294.55 ms.

  • CPU Governor not working at boot

    Seems no driver is loaded somehow:

    Code
    root@demeter:~# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  no or unknown cpufreq driver is active on this CPU
  maximum transition latency: 4294.55 ms.
analyzing CPU 1:
  no or unknown cpufreq driver is active on this CPU
  maximum transition latency: 4294.55 ms.

  • Terminal says "No interface available"


    and

  • CPU Governor not working at boot

    I've been staring at my boot log and found another catch:

    Code
    Wed Dec 10 20:19:20 2014: CPUFreq Utilities: Setting conservative CPUFreq governor...disabled, governor not available...done.


    Proof that modules are not being used:

    Code
    root@demeter:~# lsmod | grep cpufreq
cpufreq_userspace      12576  0
cpufreq_stats          12866  0
cpufreq_conservative    13147  0
cpufreq_powersave      12454  0


    Did some searching and found that the location the init.d script is searching for the governor does not exist:

    Code
    # Which governor to use. Must be one of the governors listed in:
#   cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors


    I have found anything related to cpu frequency in the following directory:


    How should the /etc/init.d/cpufrequtils script be changed?

  • Vmware-tools not booting all services - fix

    After install vmware-tools on my OMV 1.5 (<- missing the 1.5 label when posting in this forum...) virtual machine I rebooted and saw something not right.

    Code
    Wed Dec 10 19:58:17 2014:    VM communication interface:^[[71G done
Wed Dec 10 19:58:17 2014:    VM communication interface socket family:^[[71G done
Wed Dec 10 19:58:17 2014: /etc/init.d/vmware-tools: 1153: [: =: unexpected operator
Wed Dec 10 19:58:17 2014:    Guest operating system daemon:^[[71G done


    After some research I found that the init.d script of vmware-tools had a typo. Take a look at line 1153:

    Code
    if [ $vmdb_answer_OPEN_VM_COMPAT = 'yes' ] ; then


    This is not correct. The line should read:

    Code
    if [ "$vmdb_answer_OPEN_VM_COMPAT" = 'yes' ] ; then


    Did you see the double qoutes?


    After this fix and a reboot of the ser(vice)(ver), the boot log is fine:

    Code
    Wed Dec 10 20:09:21 2014: Starting VMware Tools services in the virtual machine:
Wed Dec 10 20:09:21 2014:    Switching to guest configuration:^[[71G done
Wed Dec 10 20:09:22 2014:    VM communication interface:^[[71G done
Wed Dec 10 20:09:22 2014:    VM communication interface socket family:^[[71G done
Wed Dec 10 20:09:22 2014:    Guest operating system daemon:^[[71G done

  • iSCSI with SnapRAID and aufs pooling

    I have installed OMV 1.1 (Linux 3.2.0 kernel) together with SnapRAID and Aufs. Pooled my two content discs together as per guide on this forum. The whole thing seems to work great.
    I exported the poolshare as NFS. My LDAP/application server (both OMV and LDAP/application server are VM's) is mounting the NFS export fine.


    I was good to go and wanted to replace my current system with this new setup until... I found out about the iSCSI-target plugin. I installed it (had some hickups with headers missing but fixed that) and now I want to make a LUN out of the poolshare and feed it to my LDAP/app server. When I add a new LUN the device list is empty. See attached.


    Is it possible to iSCSI a pooled SnapRAID storage?

  • ldap plugin

    Since this is the only thread in Plugin section with the title "ldap plugin" it seems the right place asking questions about... ldap plugin.
    I've setup my OMV with an ClearOS implementation of OpenLDAP backend. ClearOS is based on CentOS. Both machines are my VM host.
    OMV can connect with the ldap server. When I "getent passwd" I get the list of both local OMV plus lpda users. But groups is another thing. When I "getent group" I get the local OMV groups plus a list of lpda groups whicj differs from presentation. See below:

    Code
    root@machine:~# getent group
root:x:0:
daemon:x:1:
...
allusers:*:63000:
guests:*:1000546:


    See the difference? OMV is with the "x" and my ldap group with "*".


    This results in the OMV gui not being able to view any ldap groups. The list is empty. How should I fix/hack this?


    N.B. When I id some ldap user, the group is also shown:

    Code
    root@machine:~# id mactest
UID=1004(mactest) GID=63000(allusers) groepen=63000(allusers)

  • Sickbeard not getting installed

    I misunderstood the way this plugins is installed. Should have known to first choose fork/branch and apply. I can now see the directory created in /opt.
    Am I allowed to change the backup path below? I want to save the backup to the aufs pool mount location.

    Code
    <sickbeard>
      <enable>0</enable>
      <showtab>0</showtab>
      <sb_branch>master</sb_branch>
      <sb_repo>https://github.com/midgetspy/Sick-Beard.git</sb_repo>
      <port>8081</port>
      <mntentref>6ccc8905-1221-4603-b2fa-f7b4cec0bb44</mntentref>
      <path>/media/89003a17-792c-48f2-9f6f-db82ffa7cb3a/SBbackup</path>
      <forks></forks>
    </sickbeard>

  • Sickbeard not getting installed

    I also got some troubles starting SB.
    I installed Sickbeard on my fresh Kralizec OMV Virtual Machine. I used the "official" way; added OMV-extras plugin, enabled "Download Managers" and finally installed "openmediavault-sickbeard 1.0.1" plugin.
    See log:


    When I try to start it, it can't be found. See below:

    Code
    root@machine:~# service sickbeard start
Starting sickbeard
root@machine:~# /usr/bin/python: can't open file '/opt/sickbeard/SickBeard.py': [Errno 2] No such file or directory


    There is nog sign of SB in the /opt directory:

    Code
    root@machine:~# ls -al /opt/
totaal 12
drwxrwxr-x 3 root users 4096 nov 2 23:14 .
drwxr-xr-x 24 root root 4096 okt 29 20:43 ..
drwxrwxr-x 14 sabnzbd users 4096 okt 31 15:16 SABnzbd


    Is this normal behaviour? Why isn't SB installed in the /opt directory?
    What's the best way of fixing this? Trace the correct .py file and edit all scripts to this valid location?