Posts by Cubytus

    For regular updates and if you're used to it, it doesn't take more time then 1-2 minutes.It's like: Stop server, download and extract new version, run upgrade script, start server

    That's all fine and dandy on a locally-hosted OC installation, but completely impossible on a shared hosting people may use for availability reason.


    The first or second command line for an upgrade, according to OC's manual, is:


    sudo -u www-data php occ maintenance:mode --on


    There's no such thing as sudo on a shared hosting, or the provider has more serious problems than supporting an outdated version of OC.

    Hi there,


    Since a few days, I am attempting to reinstall OMV 2.2.x on a Raspberry Pi B. The intent is to first install an up-to-date version on the SD card, set up the RTC correctly (was a long process, but finally did it), then clone it to a USB SSD and switch the /boot/cmdline.txt to point toward the SSD partition.


    However, OMV now refuses to apply one change (I don't remember which one) and gives off error #4000:



    Setup is unremarkable: updated rasps-config to the latest version, corrected memory split to only leave 16MiB to the GPU, in addition of the modifications required for RTC functionality. Plugins Netatalk, CUPS and WebDAV installed, but not activated (yet).


    Tested: cloned the mmcblk0p2 partition to the /dev/sda1 on the SSD with command line:
    rsync -avxS / /media/one_SSD_UUID.
    Pointed /boot/cmdline.txt to it.
    Result: nginx doesn't run.
    Pointed back to original mmcblk0p2:
    Result: nginx runs, but can't apply the modification.


    How would I solve this annoying and seemingly random issue? If possible avoiding the tedious RTC config, update, upgrade, install process.

    I disagree with your disagree.Seafile is much faster, (full WAN/LAN instead of 1.8kbit/s with OwnCloud) full encrypted and such stuff. For using it as a Cloud, what it is, it is much better than NC/OC. For CalDav and such stuff you can use different things.

    Does it include easier updates than OC? OC isn't exactly automated in this regard and requires more manual work than other comparable PHP-based framework.


    Fully encrypted?


    Considering the world we live in, I think anything non-encrypted on OMV should be quietly abandoned.

    Not exactly a plugin, more an installation method:


    Name-branded NASes using a single disk sometimes have a "fake RAID" setup for their system files. This way, if something goes wrong, the user only has to reset the NAS to bring it back to a working state, no manual /lenghty flashing of a disk image is required.


    Or add GRUB in the standard installation so one could boot on a "debug" partition, much like Ubuntu does. (DK if this is already implemented as I run OMV headless most of the time.)

    Sorry to say but I think you need to give up your dream of a smooth running OMV install on this thing. I have a Qnap ts-451 that runs regular 64 bit (amd64) OMV 3.x and it is wonderful.

    I'm jealous. Being cash-strapped at the present time I have to choose between a completely silent setup (i.e. SSD) OR a recent Pi, but not both.


    Would a Banana Pi be powerful enough for OMV 3.0?


    Still wondering if it would be possible to upgrade the internals of a regular Qnap firmware and keep their low-requirements GUI.

    Hello there,


    I used the omv-upgrade command in OMV 2.2.13 to upgrade to the latest version, since there was no version 3.0 made for RPi B, as I understood. I put a hold on php5-pam as required on the Raspberry Pi B model.


    However, Nginx doesn't seem to start:


    I get

    Code
    service nginx status
    ● nginx.service - LSB: starts the nginx web server
    Loaded: loaded (/etc/init.d/nginx)
    Active: active (exited) since Fri 2016-11-11 20:43:54 CST; 1s ago
    Process: 1214 ExecStop=/etc/init.d/nginx stop (code=exited, status=0/SUCCESS)
    Process: 1177 ExecReload=/etc/init.d/nginx reload (code=exited, status=0/SUCCESS)
    Process: 1278 ExecStart=/etc/init.d/nginx start (code=exited, status=0/SUCCESS)

    I am not sure what this means, but I tried to stop / start the service, to no avail. There's no port 80 open on doing a port scan, and no web GUI displayed.
    On plugging in the TV, it still reports OMV 2.2.13 version.
    Configuration: RPi B running off USB HDD, RTC installed. Software configuration, except for running off the HDD, is stock 2.2.13 OMV.


    If that is any helpful, I don't see the omv-* utilities anymore, only omv-mkgraph is available.


    How would I solve this issue?

    Would there be a way to work around this issue so floating points operations are avoided as much as possible?


    I know it's kind of strange since non-floating point CPUs have almost disappeared.


    Does that means Debian has been compiled for armel, but not php5-fpm?

    Hmmm, the top command yields


    top - 13:17:25 up 2:16, 1 user, load average: 0,88, 0,31, 0,20
    Tasks: 86 total, 6 running, 80 sleeping, 0 stopped, 0 zombie
    %Cpu(s): 95,3 us, 4,1 sy, 0,0 ni, 0,0 id, 0,0 wa, 0,0 hi, 0,6 si, 0,0 st


    while the interface is displayed.


    wa seems nil


    There's no iostat here.


    iotop yields:
    Total DISK READ : 0.00 B/s | Total DISK WRITE : 0.00 B/s
    Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 0.00 B/s
    TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND
    1 be/4 root 0.00 B/s 0.00 B/s 0.00 % 0.00 % init
    2 be/4 root 0.00 B/s 0.00 B/s 0.00 % 0.00 % [kthreadd]
    3 be/4 root 0.00 B/s 0.00 B/s 0.00 % 0.00 % [ksoftirqd/0]
    5 be/0 root 0.00 B/s 0.00 B/s 0.00 % 0.00 % [kworker/0:0H]


    Not sure if indeed CPU is too weak (I have OMV 2.0 on a RPi 1 rev B that has issues, but nowhere as bad as this board). What is your hypothesis on this?

    I finally got the OMV-Extras.org plugin installed, and managed to activate the flashmemory plugin, between error boxes. As SSH access was available and working, I also edited fstab like flashmemory-plugin instructed, saved, rebooted, and did omv-aptclean. This was rather long, about 10 minutes to complete execution.


    But it's not really faster overall, and, accross reboots, ports for SSH and the Web GUI may or may not open, and the serial console would or wouldn't let me log in (stays frozen at the "login: prompt").


    Using htop, I see the CPU stays at 100% with very high load numbers (5 and above), all caused by the webgui itself (multiple instances of php-fpm: pool openmediavault-webgui).


    I don't know if this can be helpful, but the OMV engine itself rarely takes more than 10%.


    Perhaps the issue on this low-power system comes from php-fpm configuration? Starting too manu child processes?

    Indeed it doesn't seem to do much, except putting a high load on the CPU while OMV interface is loaded (above 6).


    How would I turn off monitoring and install this plugin from the command line, even the serial interface, if possible? OMV's web interface is currently unusable due to these issues. I am also curious to know what would the flashmemory plugin would change, since the OS and OMV are running off a regular HDD

    It has 256MB RAM, but not swapping yet, only 60MB used.


    The low resources was indeed my concern installing Debian Jessie on this system. Maybe it's fast enough for a non - GUI system, but not for a detailed interface like OMV. also, I assume OMV 3 is heavier on resources than OMV 2.


    The lower resources may be the reason why Qnap didn't upgrade this system in two years.


    Would there be a lighter and up-to-date GUI to run on it? I thought nginx would be low enough on resources...

    I can quickly click some other tabs, but still receive the same "Error" box as in the first post. In the console, still the same messages:

    omv-engined[4882]: Child process forked (pid=4882)
    omv-engined[4884]: Child process forked (pid=4884)
    omv-engined[3517]: SIGCHLD received ...
    omv-engined[3517]: Child (pid=4850) terminated with exit code 0
    omv-engined[4882]: Executing RPC (service=CertificateMgmt, method=getSshList, params={"start":0,"limit":25,"sortfield":"comment","sortdir":"
    ASC"}, context={"username":"admin","role":1}) ...
    omv-engined[4882]: RPC response (service=CertificateMgmt, method=getSshList): {"response":{"total":0,"data":[]},"error":null}
    omv-engined[4884]: Executing RPC (service=CertificateMgmt, method=getList, params={"start":0,"limit":25,"sortfield":"name","sortdir":"ASC"},
    context={"username":"admin","role":1}) ...
    omv-engined[4884]: RPC response (service=CertificateMgmt, method=getList): {"response":{"total":0,"data":[]},"error":null}
    omv-engined[3517]: SIGCHLD received ...
    omv-engined[3517]: Child (pid=4882) terminated with exit code 0
    omv-engined[3517]: SIGCHLD received ...
    omv-engined[3517]: Child (pid=4884) terminated with exit code 0
    omv-engined[4848]: RPC response (service=Services, method=getStatus): {"response":{"total":7,"data":[{"name":"ftp","title":"FTP","enabled":f
    alse,"running":true},{"name":"nfs","title":"NFS","enabled":false,"running":true},{"name":"rsyncd","title":"RSync server","enabled":false,"ru
    nning":false},{"name":"samba","title":"SMB\/CIFS","enabled":false,"running":true},{"name":"snmp","title":"SNMP","enabled":false,"running":tr
    ue},{"name":"ssh","title":"SSH","enabled":true,"running":true},{"name":"tftp","title":"TFTP","enabled":false,"running":false}]},"error":null
    }
    omv-engined[3517]: SIGCHLD received ...
    omv-engined[3517]: Child (pid=4848) terminated with exit code 0



    If the dashboard is that intensive on the CPU, wouldn't it be a better idea to default to another page, when the system is already busy loading the interface itself?

    See above.


    I see scrolling messages very similar to this extract (couldn't get them all);



    v-engined[3517]: SIGCHLD received ...
    omv-engined[3517]: Child (pid=3962) terminated with exit code 0
    omv-engined[3965]: RPC response (service=System, method=getInformation): {"response":[{"name":"Hostname","value":"NASAD13D6.example.org","ty
    pe":"string","index":0},{"name":"Version","value":"3.0.35 (Erasmus)","type":"string","index":1},{"name":"Processor","value":"Feroceon rev 0
    (v5l)","type":"string","index":2},{"name":"Kernel","value":"Linux 3.16.0-4-orion5x","type":"string","index":3},{"name":"System time","value"
    :"ven 16 sep 2016 13:47:53 EDT","type":"string","index":4},{"name":"Uptime","value":"0 days 1 hour 28 minutes 7 seconds","type":"string","in
    dex":5},{"name":"Load average","value":"7.73, 3.81, 1.61","type":"string","index":6},{"name":"CPU usage","value":{"text":"100%","value":100}
    ,"type":"progress","index":7},{"name":"Memory usage","value":{"text":"32% of 249.48 MiB","value":32},"type":"progress","index":8}],"error":n
    ull}
    omv-engined[3517]: SIGCHLD received ...
    omv-engined[3517]: Child (pid=3965) terminated with exit code 0
    omv-engined[3960]: RPC response (service=Services, method=getStatus): {"response":{"total":7,"data":[{"name":"ftp","title":"FTP","enabled":f
    alse,"running":true},{"name":"nfs","title":"NFS","enabled":false,"running":true},{"name":"rsyncd","title":"RSync server","enabled":false,"ru
    nning":false},{"name":"samba","title":"SMB\/CIFS","enabled":false,"running":true},{"name":"snmp","title":"SNMP","enabled":false,"running":tr
    ue},{"name":"ssh","title":"SSH","enabled":true,"running":true},{"name":"tftp","title":"TFTP","enabled":false,"running":false}]},"error":null
    }





    They look very similar

    Here it is:
    http://pastebin.com/0GHNdF6V


    I can log in in the web interface, but still receive this ugly message box. On the serial console, I receive:


    omv-engined[3626]: Child process forked (pid=3626)
    omv-engined[3626]: Executing RPC (service=UserMgmt, method=authUser, params={"username":"admin","password":"openmediavault"}, context={"user
    name":"admin","role":1,"_SERVER":{"SERVER_PROTOCOL":"HTTP\/1.1","GATEWAY_INTERFACE":"CGI\/1.1","SERVER_SOFTWARE":"nginx\/1.6.2","REMOTE_ADDR
    ":"::ffff:192.168.1.20","REMOTE_PORT":"63484","SERVER_ADDR":"::ffff:192.168.1.9","SERVER_PORT":"1080","SERVER_NAME":"openmediavault-webgui",
    "REDIRECT_STATUS":"200","HTTP_HOST":"192.168.1.9:1080","HTTP_USER_AGENT":"Mozilla\/5.0 (Macintosh; Intel Mac OS X 10.6; rv:48.0) Gecko\/2010
    0101 Firefox\/48.0","HTTP_CONTENT_TYPE":"application\/json","HTTP_REFERER":"http:\/\/192.168.1.9:1080\/"}}) ...
    omv-engined[3626]: RPC response (service=UserMgmt, method=authUser): {"response":{"authenticated":true,"username":"admin"},"error":null}
    omv-engined[3517]: SIGCHLD received ...
    omv-engined[3517]: Child (pid=3626) terminated with exit code 0


    I try again, and get a blank page from OMV, and this from the serial console;


    omv-engined[3653]: Child process forked (pid=3653)
    omv-engined[3653]: Executing RPC (service=UserMgmt, method=authUser, params={"username":"admin","password":"openmediavault"}, context={"user
    name":"admin","role":1,"_SERVER":{"SERVER_PROTOCOL":"HTTP\/1.1","GATEWAY_INTERFACE":"CGI\/1.1","SERVER_SOFTWARE":"nginx\/1.6.2","REMOTE_ADDR
    ":"::ffff:192.168.1.20","REMOTE_PORT":"63508","SERVER_ADDR":"::ffff:192.168.1.9","SERVER_PORT":"1080","SERVER_NAME":"openmediavault-webgui",
    "REDIRECT_STATUS":"200","HTTP_HOST":"192.168.1.9:1080","HTTP_USER_AGENT":"Mozilla\/5.0 (Macintosh; Intel Mac OS X 10.6; rv:48.0) Gecko\/2010
    0101 Firefox\/48.0","HTTP_CONTENT_TYPE":"application\/json","HTTP_REFERER":"http:\/\/192.168.1.9:1080\/"}}) ...
    omv-engined[3653]: RPC response (service=UserMgmt, method=authUser): {"response":{"authenticated":true,"username":"admin"},"error":null}
    omv-engined[3517]: SIGCHLD received ...
    omv-engined[3517]: Child (pid=3653) terminated with exit code 0


    Reload again, I finally see most of OMV's interface, with the same "Error" box. Serial console doesn't output anything new.

    I got the serial cable finally working in Ubuntu! Making sure the TX pin from the CP2102 dongle was connected to the RX pin of the TS-109, and vice-versa.
    From boot time, here is what I see:



    End of log:
    [ OK ] Started LSB: manage the statistics collection daemon.
    openmediavault 3.0.35 (Erasmus) NASAD13D6 ttyS0
    Copyright (C) 2009-2016 by Volker Theile. All rights reserved.
    To manage the system visit the openmediavault web control panel:


    eth0: 192.168.1.9


    By default the web control panel administrator account has the
    username 'admin' and password 'openmediavault'.
    It is recommended that you change the password for this account
    within the web control panel or using the 'omv-firstaid' CLI
    command.


    For more information regarding this appliance, please visit the
    web site: http://www.openmediavault.org


    NASAD13D6 login:


    Full log:
    http://pastebin.com/kQg8wswF


    Using the serial console, it accepts the admin /openmediavault login pair, but then says "this account is not available", and kicks me back to the login prompt.
    I can log in successfully with user / password pair I created when installing Debian, then do a su afterward.


    Scanning the ports, I see 80 is open, but the OMV page isn't shown.


    Where does the issue comes from?

    So I replaced the line
    deb http://packages.openmediavault.org/public kralizec main


    with
    deb http://packages.openmediavault.org/public erasmus main


    updated, installed OMV.
    On the first dialog about RAID setup, even though this unit doesn't have RAID, I left "all", since sometimes single drives have an software RAID setup.


    But near the end, I got this error:
    flash-kernel: installing version 3.16.0-4-orion5x


    The initial ramdisk is too large. This is often due to the unnecessary inclusion
    of all kernel modules in the image. To fix this set MODULES=dep in one or both
    /etc/initramfs-tools/conf.d/driver-policy (if it exists) and
    /etc/initramfs-tools/initramfs.conf and then run 'update-initramfs -u -k 3.16.0-4-orion5x'


    Not enough space for initrd in MTD 'RootFS1' (need 5784993 but is actually 4194304).
    run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1


    So I compressed initram according to these instructions: https://www.cyrius.com/debian/…p/ts-109/troubleshooting/


    and tried to install openmediavault package again. Turns out it was installed, so I rebooted just to make sure compressing the initramfs wouldn't brick it. It works, but now the SSH server has been disabled, which is a pain.


    The Web interface of OMV is available, and I can log in, but I am constantly nagged by this unhelpful message box:


    If I repeatedly try to reload, sometimes I can see the complete page, but I couldn't get syslog to display.


    What could be happening?