Posts by trayntab

    hi guys,


    i have a strange problem with my hdd.


    there is one 3TB external HDD with 2 patitions (1x 1TB und 1x 2TB)


    the 1 tb patition is filled with ~880G.


    root@nas:/srv/dev-disk-by-label-sync# du -h -d 1 ./
    16K ./lost+found
    880G ./sync
    880G ./


    but the patitions size is 916G so there should be some gb of free space.


    root@nas:/srv/dev-disk-by-label-sync# df -h
    Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
    /dev/sdd1 916G 880G 0 100% /srv/dev-disk-by-label-sync


    i can delete files but there is still 0 free space available.


    the omv-webinterface have the same values.


    but the notification mail is right;


    Resource limit matched Service filesystem_srv_dev-disk-by-label-sync Date: Wed, 30 May 2018 18:04:00 Action: alert Host: nas Description: space usage 96.0% matches resource limit [space usage>85.0%]Your faithful employee,Monit



    i can't find a reason - why?



    Do you have an idea?


    best regards

    hi guys,


    i have a short question, does OMV3 support SMB3?


    I use OMV with a libreelec client (with SMB-Share). After the last libreelec update they switched to SMB3.

    The fall “Creators Update” for Windows 10 removes SMB1 client/server support and NAS devices now ship with configuration that only supports SMB2/3 – causing problems because all versions of Kodi before 17.4 can only make SMB1 connections. This release includes changes that allow the Kodi SMB client and our embedded Samba server to work with SMB2/3 connections; improving SMB security and performance.

    there is a workaround to use SMB1, thats the only way to get this configuration OMV - Libreelec working. - So i have no Problem until now.


    But can i also enable SMB3 on my NAS?


    I have no windows systems at home, but what about Win10 systems? Have they problems too?


    Best regards
    trayntab

    Hi guys,


    i have a problem with the php5-fpm deamon.


    i installed nextcloud via the nginx addon with this How-To.


    After an omv-update and an reboot, i have a problem with the omv gui and the nextcloud-site.


    i get an nginx error : 502 Bad Gateway


    i found some errors in the logfile:


    root@nas-pi:~# systemctl status -l php5-fpm
    ● php5-fpm.service - The PHP FastCGI Process Manager
    Loaded: loaded (/lib/systemd/system/php5-fpm.service; enabled)
    Active: failed (Result: exit-code) since Sat 2016-09-17 14:06:43 CEST; 22min ago
    Process: 2287 ExecStart=/usr/sbin/php5-fpm --nodaemonize --fpm-config /etc/php5/fpm/php-fpm.conf (code=exited, status=78)
    Process: 2280 ExecStartPre=/usr/lib/php5/php5-fpm-checkconf (code=exited, status=0/SUCCESS)
    Main PID: 2287 (code=exited, status=78)



    Sep 17 14:06:43 nas-pi php5-fpm[2287]: [17-Sep-2016 14:06:43] ERROR: [/etc/php5/fpm/pool.d/1d745a75-7efd-467f-b4b2-c9f3d52a0fc2.conf:26] value is NULL for a ZEND_INI_PARSER_ENTRY
    Sep 17 14:06:43 nas-pi php5-fpm[2287]: [17-Sep-2016 14:06:43] ERROR: Unable to include /etc/php5/fpm/pool.d/1d745a75-7efd-467f-b4b2-c9f3d52a0fc2.conf from /etc/php5/fpm/php-fpm.conf at line 26
    Sep 17 14:06:43 nas-pi php5-fpm[2287]: [17-Sep-2016 14:06:43] ERROR: failed to load configuration file '/etc/php5/fpm/php-fpm.conf'
    Sep 17 14:06:43 nas-pi php5-fpm[2287]: [17-Sep-2016 14:06:43] ERROR: FPM initialization failed
    Sep 17 14:06:43 nas-pi systemd[1]: php5-fpm.service: main process exited, code=exited, status=78/n/a
    Sep 17 14:06:43 nas-pi systemd[1]: Failed to start The PHP FastCGI Process Manager.
    Sep 17 14:06:43 nas-pi systemd[1]: Unit php5-fpm.service entered failed state.





    root@nas-pi:~# cat /etc/php5/fpm/pool.d/1d745a75-7efd-467f-b4b2-c9f3d52a0fc2.conf
    [1d745a75-7efd-467f-b4b2-c9f3d52a0fc2]
    listen = /var/run/fpm-1d745a75-7efd-467f-b4b2-c9f3d52a0fc2.sock
    listen.owner = www-data
    listen.group = www-data
    listen.mode = 0600



    user = www-data
    group = www-data



    ; Process manager
    pm = dynamic
    pm.max_children = 5
    pm.start_servers = 2
    pm.min_spare_servers = 1
    pm.max_spare_servers = 3
    pm.max_requests = 0



    ; php.ini
    php_flag[display_errors] = Off
    php_flag[html_errors] = On
    php_value[max_execution_time] = 30
    php_value[memory_limit] = 128M
    php_value[post_max_size] = 8M
    php_value[upload_max_filesize] = 2M
    ; extra options
    client_max_body_size 10G; # set max upload size
    fastcgi_buffers 64 4K;



    rewrite ^/caldav(.*)$ /remote.php/caldav$1 redirect;
    rewrite ^/carddav(.*)$ /remote.php/carddav$1 redirect;
    rewrite ^/webdav(.*)$ /remote.php/webdav$1 redirect;



    index index.php;
    error_page 403 /core/templates/403.php;
    error_page 404 /core/templates/404.php;



    location = /robots.txt {
    allow all;
    log_not_found off;
    access_log off;
    }



    location ~ ^/(data|config|\.ht|db_structure\.xml|README) {
    deny all;
    }



    location / {
    # The following 2 rules are only needed with webfinger
    rewrite ^/.well-known/host-meta /public.php?service=host-meta last;
    rewrite ^/.well-known/host-meta.json /public.php?service=host-meta-json last;



    rewrite ^/.well-known/carddav /remote.php/carddav/ redirect;
    rewrite ^/.well-known/caldav /remote.php/caldav/ redirect;



    rewrite ^(/core/doc/[^\/]+/)$ $1/index.html;



    try_files $uri $uri/ index.php;
    }



    location ~ ^(.+?\.php)(/.*)?$ {
    try_files $1 = 404;



    include fastcgi_params;
    fastcgi_param SCRIPT_FILENAME $document_root$1;
    fastcgi_param PATH_INFO $2;
    fastcgi_param HTTPS on;
    fastcgi_pass $socket;
    }



    # Optional: set long EXPIRES header on static assets
    location ~* ^.+\.(jpg|jpeg|gif|bmp|ico|png|css|js|swf)$ {
    expires 30d;
    # Optional: Don't log access to assets
    access_log off;
    }





    Do you have some ideas?


    Best Regards!

    <notification>
    <notifications>
    <!--
    <xxx>0|1</xxx>
    -->
    <notification>
    <uuid>da9465e0-d519-481a-b05d-02045f63a3db</uuid>
    <id>monitprocevents</id>
    <enable>1</enable>
    </notification>
    <notification>
    <uuid>91da046b-2db4-42ca-a1d2-c60372de4be0</uuid>
    <id>monitloadavg</id>
    <enable>1</enable>
    </notification>
    <notification>
    <uuid>f38346dc-7d96-4739-8c51-fda3a4af83dc</uuid>
    <id>monitmemoryusage</id>
    <enable>1</enable>
    </notification>
    <notification>
    <uuid>02fa2733-7d7d-4947-863c-61abc6eb87a8</uuid>
    <id>monitcpuusage</id>
    <enable>1</enable>
    </notification>
    <notification>
    <uuid>4f6a676d-14e3-40ba-bfc9-15f43cac6dec</uuid>
    <id>monitfilesystems</id>
    <enable>1</enable>
    </notification>
    <notification>
    <uuid>1beaefb0-1b36-451a-ab17-e78c448a9bd8</uuid>
    <id>mdadm</id>
    <enable>1</enable>
    </notification>
    <notification>
    <uuid>6eddc6ec-6fe4-4d9b-820a-5521c4c09786</uuid>
    <id>smartmontools</id>
    <enable>1</enable>
    </notification>

    Hi guys,


    i get an error on my raspberry pi 3 if i want to configure the e-mail notification. (omv 3.0.35)


    The XPath query '//system/notification/notifications/notification[id='cronapt']' does not return the requested number of 1 object(s).
    Fehler #0:exception 'InvalidArgumentException' with message 'The XPath query '//system/notification/notifications/notification[id='cronapt']' does not return the requested number of 1 object(s).' in /usr/share/php/openmediavault/config/database.inc:172Stack trace:#0 /usr/share/openmediavault/engined/rpc/notification.inc(66): OMV\Config\Database->getByFilter('conf.system.not...', Array, 1)#1 [internal function]: OMVRpcServiceNotification->get(Array, Array)#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)#3 /usr/share/php/openmediavault/rpc/rpc.inc(84): OMV\Rpc\ServiceAbstract->callMethod('get', Array, Array)#4 /usr/sbin/omv-engined(516): OMV\Rpc\Rpc::call('Notification', 'get', Array, Array, 1)#5 {main}


    Thank you :)


    best regards
    trayntab

    hm okay, i tried omv-update and rpi-update but it's the same problem :(


    ah, the systeminformation:


    processor: ARMv7 Processor rev 4 (v7l)


    thats not right, the Pi3 have an A 1.2GHz 64-bit quad-core ARMv8 CPU

    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
    valid_lft forever preferred_lft forever
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b8:27:eb:be:48:c7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.215.37/24 brd 192.168.215.255 scope global eth0
    valid_lft forever preferred_lft forever
    3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether b8:27:eb:eb:1d:92 brd ff:ff:ff:ff:ff:ff