I have nearly the same messages, but no problems up to now.
There is no possibility to adjust the CPU voltage in the UEFI. Only the RAM voltage and that's already set to minimum. It allows only 1.5V and 1.35V
I have nearly the same messages, but no problems up to now.
There is no possibility to adjust the CPU voltage in the UEFI. Only the RAM voltage and that's already set to minimum. It allows only 1.5V and 1.35V
Thanks for the hint. From poking around in https://wiki.openmediavault.or…Environment_Variables/all I expect that OMV_NGINX_SITE_WEBGUI_INCLUDE_DIR and OMV_NGINX_SITE_WEBGUI_SSL_CIPHERS are the ones that are relevant for me and I have to set them in /etc/default/openmediavault, correct?
But will they be appended to the defaults or will they overwrite the defaults?
myscha: Do you use your setup headless? 21W vor 2 drives with this board is moderat, but could be lower. Did you deactive the soundchip within UEFI? Do you use DDR3L SO-Dimms? Whats your power supply? Does UEFI offer a voltage adjustment?
No it's not headless. I also installed XFCE, but about 99.5% of the time there won't be anyone using it.
Sound is active.
DIMMs are low-power ones (2pcs.).
The power-supplies came with my Chenbro ES34069: a FSP180-ABA for AC=>19V and an internal PCB for 19V => 12V/5V/3.3V.
I'll check the UEFI settings later.
Alles anzeigenI am Sorry, I cant measure the power consumption, guess I should buy something for that.
I use the PicoPSU90 together with an "Leicke NT33402 Netzteil 90W" from amazon, and until now there where no Problems with the Power (even with 4 Harddrives)
The MB itself is not perfect, still give me strange errors, but until everything works like i should i will try to ignore it
2018-01-20T07:40:28+0100 server kernel: mce: [Hardware Error]: Machine check events logged
2018-01-20T07:40:28+0100 server kernel: mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: a600000000020408
2018-01-20T07:40:28+0100 server kernel: mce: [Hardware Error]: TSC 0 ADDR fef13b80
2018-01-20T07:40:28+0100 server kernel: mce: [Hardware Error]: PROCESSOR 0:506c9 TIME 1516430428 SOCKET 0 APIC 0 microcode 2c
2018-01-20T07:40:28+0100 server kernel: Enabling non-boot CPUs ...
How or where did you get that error message? Never noticed it anywhere.
Yes, it works: see Nginx Plugin Vhost Website auf Port 80 in einem Unterordner installieren. There part-db is mentioned, but it also works with Baikal.
EDIT:
This is my version for baikal. It slightly differs from the one for part-db, but either should work.
$ cat /srv/dev-disk-by-label-vol1/www/sites-enabled/baikal
# taken from /etc/nginx/openmediavault-webgui.d/openmediavault-mysql-management-site.conf
location /baikal {
root /srv/dev-disk-by-label-vol1/www;
index index.php;
try_files $uri $uri/ index.php;
# taken from https://www.mikrocontroller.net/topic/438916#5261351
location ~ \.php(?:$|/) {
include fastcgi.conf;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $request_filename;
fastcgi_pass unix:/var/run/php-fpm-openmediavault-mysql.sock;
}
}
Alles anzeigen
@Felix1220
Did you measure the power consumption of the setup?
I'm using the J4205 version of that board with only 2x WD Reds and it consumes about 21W idle. So I would be interested in your values.
I have configured OMV 4 to force SSL usage and I'm running Baikal for syncing calendars to some Android 4.2/4.4 smartphones. Those old Android versions don't work with the default ssl_ciphers, so I have to add additional ones to /etc/nginx/openmediavault-webgui.d/security.conf.
In addition to this I'm running some PHP services and I have setup the paths and usage as described there. To make this working another include directive has to be added to /usr/share/openmediavault/mkconf/nginx.d/10webgui.
With every update, my manual additions are being deleted, so I'd like to know if there is any way to customize Nginx to allow such customization?
By watching the variable 'sockets-enqueued' in /proc/fs/nfsd/pool_stats (according to knfsd-stats.txt) I found out that 8 threads are not enough and result in ten-thousands of enqueued sockets. When I increased the number of threads to 64, the number of enqueued sockets remained constant.
Then I've made more benchmarks, but I still don't know why NFS is so much slower.
protocol | rate [MB/s] | export options |
SMB/CIFS | 108.97 | |
NFS | 84,51 | rw,async,no_subtree_check,all_squash,anonuid=1028,anongid=100 |
NFS | 82.06 | rw,subtree_check,secure,async |
NFS | 72.16 | rw,subtree_check,secure |
The test file was about 3.5GB large and each test was run 3 times and the results were averaged. The file was copied using rsync as dd is not able to work over SMB/CIFS. You can find the test script below.
The NFS client options were always the same:
rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.178.35,local_lock=none,addr=192.168.178.2
where most values are defaults on my machine (Arch Linux).
#!/bin/sh
function perform_copy {
echo "$(mount | grep /mnt/test)"
echo "copying data"
loop=3
while [ $loop -ne 0 ];
do
rm /mnt/test/Deadpool.ts
# dd if=/home/me/Deadpool.ts of=/mnt/test/Deadpool.ts bs=1M
rsync -av Deadpool.ts /mnt/test/
loop=$[$loop-1]
sleep 1
done
sudo umount /mnt/test
sleep $1
}
echo "--------------------------------------------------"
#sudo umount /mnt/test
echo "cifs share"
#sudo mount -t cifs -o rw //omv.local./test0 /mnt/test/
perform_copy 3
echo "--------------------------------------------------"
echo "export options: rw,async,no_subtree_check,all_squash,anonuid=1028,anongid=100"
sudo mount -t nfs -o rw,bg,intr,soft,proto=tcp omv.local.:/test1 /mnt/test/
perform_copy 3
echo "--------------------------------------------------"
echo "export options: rw,subtree_check,secure,async"
sudo mount -t nfs -o rw,bg,intr,soft,proto=tcp omv.local.:/test2 /mnt/test/
perform_copy 3
echo "--------------------------------------------------"
echo "export options: rw,subtree_check,secure"
sudo mount -t nfs -o rw,bg,intr,soft,proto=tcp omv.local.:/test3 /mnt/test/
perform_copy 0
Alles anzeigen
In the meantime the problem has gone. But I have no idea why.
Hello guys,
I've built up my own NAS system based on:
- ASRock J4205-ITX
- 8GB DDR3 RAM
- 64GB Samsung 470 as system disk
- 2TB WD Red
- 3TB WD Red
- Debian Stretch 9.3
- OMW Arrakis 4.0.16-1
Now I'd like to share some folders with some Linux machines (Arch, ubuntu mate & xubuntu). As I have no Windows machines and therefore no real need for SMB shares I'd favour to share it via NFS. But unfortunately the NFS performance seems quite poor according to some benchmarks I've made:
Protocol | Speed [MB/s] |
SMB/CIFS | 115.27 |
NFS3 | 71.38 |
NFS4, sync | 72.08 |
NFS4, async | 66.63 |
NFS4, several options, see code below | 67.99 |
While performing the test neither the server nor the client did something challenging.
The client was a Lenovo T61 with Arch on a 256GB Samsung 750 disk, which may be nearly on the edge as the T61 only offers SATA1 interfaces.
All software on server and client was up-to-date.
NFS ran with 8 threads and the export options were: rw,subtree_check,secure
SMB/CIFS was shared with OMV default options
Are there options thatcould speed up NFS transmission or is SMB really faster?
michael@t61:~$ sudo mount -t cifs -o rw,uid=1026,username=michael //server.home./share /mnt/test/
Password for michael@//server.home./share:
michael@t61:~$ rsync -av --progress Projekte/aqemu/ubuntu_mate_HDA.img /mnt/test
sending incremental file list
ubuntu_mate_HDA.img
8,296,333,312 100% 115.27MB/s 0:01:08 (xfr#1, to-chk=0/1)
sent 8,298,358,898 bytes received 35 bytes 112,902,842.63 bytes/sec
total size is 8,296,333,312 speedup is 1.00
michael@t61:~$ rm /mnt/test/ubuntu_mate_HDA.img
michael@t61:~$ sudo umount /mnt/test
michael@t61:~$ sudo mount -t nfs -o rw server.home.:/export/share /mnt/test/
michael@t61:~$ rsync -av --progress Projekte/aqemu/ubuntu_mate_HDA.img /mnt/test
sending incremental file list
ubuntu_mate_HDA.img
8,296,333,312 100% 71.38MB/s 0:01:50 (xfr#1, to-chk=0/1)
sent 8,298,358,898 bytes received 35 bytes 72,474,750.51 bytes/sec
total size is 8,296,333,312 speedup is 1.00
michael@t61:~$ rm /mnt/test/ubuntu_mate_HDA.img
michael@t61:~$ sudo umount /mnt/test
michael@t61:~$ sudo mount -t nfs -o rw server.home.:/share /mnt/test/
michael@t61:~$ rsync -av --progress Projekte/aqemu/ubuntu_mate_HDA.img /mnt/test
sending incremental file list
ubuntu_mate_HDA.img
8,296,333,312 100% 72.08MB/s 0:01:49 (xfr#1, to-chk=0/1)
sent 8,298,358,898 bytes received 35 bytes 70,624,331.34 bytes/sec
total size is 8,296,333,312 speedup is 1.00
michael@t61:~$ rm /mnt/test/ubuntu_mate_HDA.img
michael@t61:~$ sudo umount /mnt/test
michael@t61:~$ sudo mount -t nfs -o rw,async server.home.:/share /mnt/test/
michael@t61:~$ rsync -av --progress Projekte/aqemu/ubuntu_mate_HDA.img /mnt/test
sending incremental file list
ubuntu_mate_HDA.img
8,296,333,312 100% 66.63MB/s 0:01:58 (xfr#1, to-chk=0/1)
sent 8,298,358,898 bytes received 35 bytes 67,193,189.74 bytes/sec
total size is 8,296,333,312 speedup is 1.00
michael@t61:~$ rm /mnt/test/ubuntu_mate_HDA.img
michael@t61:~$ sudo umount /mnt/test
michael@t61:~$ sudo mount -t nfs -o rw,bg,intr,soft,users,noauto,_netdev,proto=tcp,retry=3,timeo=10 server.home.:/share /mnt/test/
michael@t61:~$ rsync -av --progress Projekte/aqemu/ubuntu_mate_HDA.img /mnt/test
sending incremental file list
ubuntu_mate_HDA.img
8,296,333,312 100% 173.73MB/s 0:00:45 (xfr#1, to-chk=0/1)
rsync: write failed on "/mnt/test/ubuntu_mate_HDA.img": Input/output error (5)
rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2]
michael@t61:~$ sudo umount /mnt/test
michael@t61:~$ sudo mount -t nfs -o rw,bg,intr,soft,users,noauto,_netdev,proto=tcp server.home.:/share /mnt/test/
michael@t61:~$ rsync -av --progress Projekte/aqemu/ubuntu_mate_HDA.img /mnt/test
sending incremental file list
ubuntu_mate_HDA.img
8,296,333,312 100% 67.99MB/s 0:01:56 (xfr#1, to-chk=0/1)
sent 8,298,358,898 bytes received 35 bytes 68,866,049.24 bytes/sec
total size is 8,296,333,312 speedup is 1.00
michael@t61:~$ rm /mnt/test/ubuntu_mate_HDA.img
michael@t61:~$ sudo umount /mnt/test
Alles anzeigen
Here's another update as it works now:
Assuming that your custom PHP services shall go to /srv/dev-disk-by-label-vol1/www.
Make two additional folders according to the Nginx style: /srv/dev-disk-by-label-vol1/www/sites-available and /srv/dev-disk-by-label-vol1/www/sites-enabled.
Create configs in /srv/dev-disk-by-label-vol1/www/sites-available.
Make a symlink to /srv/dev-disk-by-label-vol1/www/sites-enabled to enable a service.
That's like the common Nginx mechanism, but in custom folders.
A single config in /srv/dev-disk-by-label-vol1/www/sites-available may look like this
location /part-db {
root /srv/dev-disk-by-label-vol1/www;
index index.php;
try_files $uri $uri/ index.php;
location ~ \.php(?:$|/) {
include fastcgi.conf;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $request_filename;
fastcgi_pass unix:/var/run/php-fpm-openmediavault-mysql.sock;
}
}
Alles anzeigen
But another sock should be taken, I think.
To load the additional configurations /srv/dev-disk-by-label-vol1/www/sites-enabled must be included in the OMV Nginx server configuration (/etc/nginx/sites-enabled/openmediavault-webgui) like this:
This is also the main drawback of this method: this last line has to be manually added after each update of the OMV Nginx plugin. If you don't use the plugin this shouldn't be a problem.
Now you can open the OMV webinterface with omv.local in the browser and the service with omv.local/part-db. No more need to add DNS entries or work with different ports.
EDIT:
To make the include persistent you have to edit /usr/share/openmediavault/mkconf/nginx.d/10webgui at about line 127:
-b \
-o " include ${OMV_NGINX_SITE_WEBGUI_INCLUDE_DIR}/*.conf;" -n \
-o " include /srv/dev-disk-by-label-vol1/www/sites-enabled/*;" -n \
-o "}" \
Add line 127 here.
I have a version which works at least for the php files:
location /part-db {
alias /srv/dev-disk-by-label-vol1/www/part-db;
index index.php;
try_files $uri $uri/ index.php;
location ~ \.php(?:$|/) {
include fastcgi.conf;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $request_filename;
fastcgi_pass unix:/var/run/php-fpm-openmediavault-mysql.sock;
}
}
Alles anzeigen
It's based on /etc/nginx/openmediavault-webgui.d/openmediavault-mysql-management-site.conf, but unfortunately it doesn't work with css and js files that are located in the according subfolders. It still searches those in /var/www/openmediavault/js instead of /srv/dev-disk-by-label-vol1/www/part-db/js.
How could I fix this?
Thanks for the link.
So for every service I'd add in that way I'd also have to add a DNS entry, is that correct?
Would it also be possible to get something like
location /part-db/ {
alias /srv/dev-disk-by-label-vol1/www/part-db/;
fastcgi_index index.php;
}
to work? This way no DNS entries would have to be added.
With the above I see
018/01/02 09:52:13 [error] 6571#6571: *1 open() "/srv/dev-disk-by-label-vol1/www/part-db/css/omv.css" failed (2: No such file or directory), client: 192.168.144.235, server: openmediavault-webgui, request: "GET /part-db/css/omv.css HTTP/1.1", host: "nas.home.", referrer: "http://nas.home./part-db/"
in the errorlog (/var/log/nginx/openmediavault-webgui_error.log). This makes sense, as there is no file omv.css anywhere on my system. But what goes wrong here?
It works with the following server config
server {
listen 8080;
listen [::]:8080;
server_name nas.home.;
set $root_path "/srv/dev-disk-by-label-vol1/www";
root $root_path;
index index.html index.php;
set $socket "unix:/var/run/fpm-f5e655f9-218f-4d18-b9fe-0be6e86a63bd.sock";
location ~ \.php(?:$|/) {
include snippets/fastcgi-php.conf;
fastcgi_pass $socket;
}
access_log /var/log/nginx/b62e7238-8b64-4c25-a486-5712af496cdf-access.log;
error_log /var/log/nginx/b62e7238-8b64-4c25-a486-5712af496cdf-error.log;
large_client_header_buffers 4 8k;
}
Alles anzeigen
when I open http://nas.home.:8080/part-db
I startet the server about 3 hours ago.
● monit.service - LSB: service and resource monitoring daemon
Loaded: loaded (/etc/init.d/monit; generated; vendor preset: enabled)
Active: active (running) since Sun 2017-12-31 09:39:20 CET; 3h 11min ago
Docs: man:systemd-sysv-generator(8)
Tasks: 4 (limit: 4915)
CGroup: /system.slice/monit.service
└─1001 /usr/bin/monit -c /etc/monit/monitrc
Dez 31 09:39:19 nas systemd[1]: Starting LSB: service and resource monitoring daemon...
Dez 31 09:39:20 nas monit[962]: Starting daemon monitor: monit.
Dez 31 09:39:20 nas systemd[1]: Started LSB: service and resource monitoring daemon.
Dez 31 09:39:50 nas monit[1001]: 'nas' Monit 5.20.0 started
Alles anzeigen
Unfortunately that doesn't help. I performed about 6 reboots since then, but the behaviour stays the same.
Recently I installed above mentioned OMV version on a fresh installation of Debian Stretch 9.3 (firmware-9.3.0-amd64-netinst.iso).
When I applied the configuration after creating a new NFS share, I got the following message for the first time.
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; monit monitor collectd 2>&1' with exit code '1': Cannot create socket to [localhost]:2812 -- Connection timed out
Fehler #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; monit monitor collectd 2>&1' with exit code '1': Cannot create socket to [localhost]:2812 -- Connection timed out in /usr/share/php/openmediavault/system/process.inc:175
Stack trace:
#0 /usr/share/php/openmediavault/system/monit.inc(115): OMV\System\Process->execute()
#1 /usr/share/php/openmediavault/system/monit.inc(82): OMV\System\Monit->action('monitor', false)
#2 /usr/share/openmediavault/engined/module/collectd.inc(81): OMV\System\Monit->monitor()
#3 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleCollectd->startService()
#4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(150): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(528): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatus0l...', '/tmp/bgoutput7x...')
#8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(151): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#9 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#10 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
#11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#12 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#13 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#14 {main}
Alles anzeigen
I got nearly the same message after creating and applying a shared folder. Since then OMV shows a changed configuration all the time, but when I click on the 'Apply' button I only see a message box after some time that tells me that there was an error. But there are no error details any more. When I close the box by clicking 'OK' the 'configuration changed' banner appears again.
Does anyone know the problem or can tell me how I can find the cause for this?
Could you please be more specific or provide a link to one of those threads? The threads I found seem to be about other problems.
Hallo,
ich stehe vor dem selben Problem und finde keine Lösung. Hast du das inzwischen hinbekommen?
In Verbindung mit einem anderen Port habe ich es hinbekommen, aber leider nicht mit den Standardports. Also https://<meine-domain>:8080/nextcloud geht, mein Wunsch wäre aber auf den Port verzichten zu können.
Viele Grüße.