Posts by sbocquet

sbocquet · Jan 14th 2022

Hi,

I'm trying to add a panel to the dashboard, but I cannot add a new item to the "Add" button.
By searching the code, I have found the file Dashboard.js, which get the registered dashboard...

Code

/**
* @class OMV.module.admin.system.general.AdminPasswd
* @derived OMV.workspace.dashboard.Dashboard
*/
Ext.define("OMV.module.admin.dashboard.Dashboard", {
extend: "OMV.workspace.dashboard.Dashboard",


getPartAliases: function() {
// Get the registered dashboard widgets aliases.
var aliases = Ext.ClassManager.getAliasesByExpression(
"part.module.admin.dashboard.part.*");
return aliases;
}
});


OMV.WorkspaceManager.registerPanel({
id: "dashboard",
path: "/diagnostic",
text: _("Dashboard"),
position: 1,
iconCls: "mdi mdi-view-dashboard",
className: "OMV.module.admin.dashboard.Dashboard"
});

Display More

So the question is... Where do I register the dashboard widget ?

Thx

sbocquet · Jan 14th 2022

Quote from ryecoaaron

That is what the change was but I'm not backporting to OMV 5.x.

Thanks.
I'm going to try to backport those changes localy on my NAS, as I don't really know how to submit an update.

sbocquet · Jan 13th 2022

Hi !

I have added a plugin to collectd configuration, in order to get iptables statistics.

According to the collectd docs, the configuration file should be something like this :

Code

root@home-server:/# cat /etc/collectd/collectd.conf.d/iptables.conf
LoadPlugin iptables
<Plugin "iptables">
  Chain "filter" "INPUT"
  Chain "filter" "OUTPUT"
</Plugin>

Here are some infos from my iptables :

Code

root@home-server:/# iptables -L -n -v --line-numbers
# Warning: iptables-legacy tables present, use iptables-legacy to see them
Chain INPUT (policy ACCEPT 559 packets, 392K bytes)
num   pkts bytes target     prot opt in     out     source               destination
1     194M  182G ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0            ctstate ESTABLISHED
2     150K   27M ACCEPT     all  --  lo     *       0.0.0.0/0            0.0.0.0/0
3        0     0 ACCEPT     icmp --  *      *       192.168.1.0/24       0.0.0.0/0
...
29    316K   56M DROP       all  --  *      *       0.0.0.0/0            0.0.0.0/0


Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
num   pkts bytes target     prot opt in     out     source               destination


Chain OUTPUT (policy ACCEPT 560K packets, 37M bytes)
num   pkts bytes target     prot opt in     out     source               destination
1     315M  694G ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0            ctstate ESTABLISHED
2     150K   27M ACCEPT     all  --  *      lo      0.0.0.0/0            0.0.0.0/0

Display More

Restarting the collectd demon is fine :

Code

[2022-01-11 23:42:06] Exiting normally.
[2022-01-11 23:42:06] collectd: Stopping 5 read threads.
[2022-01-11 23:42:06] collectd: Stopping 5 write threads.
[2022-01-11 23:42:06] plugin_load: plugin "cpu" successfully loaded.
[2022-01-11 23:42:06] plugin_load: plugin "df" successfully loaded.
[2022-01-11 23:42:06] plugin_load: plugin "disk" successfully loaded.
[2022-01-11 23:42:06] plugin_load: plugin "interface" successfully loaded.
[2022-01-11 23:42:06] plugin_load: plugin "ipmi" successfully loaded.
[2022-01-11 23:42:06] ipmi plugin: Legacy configuration found! Please update your config file.
[2022-01-11 23:42:06] plugin_load: plugin "iptables" successfully loaded.
[2022-01-11 23:42:06] plugin_load: plugin "load" successfully loaded.
[2022-01-11 23:42:06] plugin_load: plugin "memory" successfully loaded.
[2022-01-11 23:42:06] plugin_load: plugin "rrdcached" successfully loaded.
[2022-01-11 23:42:06] plugin_load: plugin "smart" successfully loaded.
[2022-01-11 23:42:06] plugin_load: plugin "syslog" successfully loaded.
[2022-01-11 23:42:06] plugin_load: plugin "unixsock" successfully loaded.
[2022-01-11 23:42:06] plugin_load: plugin "uptime" successfully loaded.
[2022-01-11 23:42:06] Systemd detected, trying to signal readiness.
[2022-01-11 23:42:06] Initialization complete, entering read-loop.
[2022-01-11 23:42:08] ipmi plugin: sensor_list_add: Ignore sensor ` unspecified (0.0)` of `main`, because it isn't readable! Its type: (0xc, memory).

Display More

Unfortunatly, no data are collected/writen in the data directory (should have some iptables_filter_* directories from what I know )

Code

root@home-server:/var/lib/rrdcached/db/localhost# ls
total 160
drwxr-xr-x 40 root root 4096 Dec 14 18:58 .
drwxr-xr-x  3 root root 4096 Jul 30  2020 ..
drwxr-xr-x  2 root root 4096 Jan  2 21:45 cpu-0
drwxr-xr-x  2 root root 4096 Jan  2 21:45 cpu-1
drwxr-xr-x  2 root root 4096 Jan  2 21:45 cpu-10
drwxr-xr-x  2 root root 4096 Jan  2 21:45 cpu-11
drwxr-xr-x  2 root root 4096 Jan  2 21:45 cpu-2
drwxr-xr-x  2 root root 4096 Jan  2 21:45 cpu-3
drwxr-xr-x  2 root root 4096 Jan  2 21:45 cpu-4
drwxr-xr-x  2 root root 4096 Jan  2 21:45 cpu-5
drwxr-xr-x  2 root root 4096 Jan  2 21:45 cpu-6
drwxr-xr-x  2 root root 4096 Jan  2 21:45 cpu-7
drwxr-xr-x  2 root root 4096 Jan  2 21:45 cpu-8
drwxr-xr-x  2 root root 4096 Jan  2 21:45 cpu-9
drwxr-xr-x  2 root root 4096 Jan  2 21:45 df-root
drwxr-xr-x  2 root root 4096 Jan  2 21:45 df-srv-dev-disk-by-label-Backups
drwxr-xr-x  2 root root 4096 Jan  2 21:45 df-srv-dev-disk-by-label-Datas
drwxr-xr-x  2 root root 4096 Jan  2 21:45 disk-md0
drwxr-xr-x  2 root root 4096 Jan  2 21:45 disk-nvme0n1
drwxr-xr-x  2 root root 4096 Jan  2 21:45 disk-sda
drwxr-xr-x  2 root root 4096 Jan  2 21:45 disk-sdb
drwxr-xr-x  2 root root 4096 Jan  2 21:45 disk-sdc
drwxr-xr-x  2 root root 4096 Jan  2 21:45 disk-sdd
drwxr-xr-x  2 root root 4096 Jan  2 21:45 disk-sde
drwxr-xr-x  2 root root 4096 Jan  2 21:45 interface-enp1s0f0
drwxr-xr-x  2 root root 4096 Jan  2 21:45 interface-enp1s0f1
drwxr-xr-x  2 root root 4096 Jan  2 21:45 interface-enp35s0
drwxr-xr-x  2 root root 4096 Jan  2 21:45 interface-enp36s0
drwxr-xr-x  2 root root 4096 Jan  2 21:45 interface-lo
drwxr-xr-x  2 root root 4096 Jan  2 21:45 ipmi
drwxr-xr-x  2 root root 4096 Jan  2 21:45 load
drwxr-xr-x  2 root root 4096 Jan  2 21:45 memory
drwxr-xr-x  2 root root 4096 Jan  2 21:45 rrdcached
drwxr-xr-x  2 root root 4096 Jan  2 21:45 smart-nvme0n1
drwxr-xr-x  2 root root 4096 Jan  2 21:45 smart-sda
drwxr-xr-x  2 root root 4096 Jan  2 21:45 smart-sdb
drwxr-xr-x  2 root root 4096 Jan  2 21:45 smart-sdc
drwxr-xr-x  2 root root 4096 Jan  2 21:45 smart-sdd
drwxr-xr-x  2 root root 4096 Jan  2 21:45 smart-sde
drwxr-xr-x  2 root root 4096 Jan  2 21:45 uptime

Display More

Does anyone already done this and any idea of what the problem is ?

Thanks

sbocquet · Jan 13th 2022

Quote from ryecoaaron

borgbackup 6.1.0 in the repo now. It will still email you if there is an error. You will not be able to disable that but I don't think errors should be skipped.

I'm using OMV 5 anyway
But I'm still thinking that a little checkbox for emailing in the WebUI in the archive configuration interface could be a nice improvment

sbocquet · Dec 17th 2021

Hi !

I have just added an Intel x550T2 10Gb NIC on my OMV server, and noticed that I have a lot of rx_dropped errors for all NICs (2 Intel i210 on the motherboard, 2 x550 on the card).
The card is on a correct PCIe extension slot (PCIe3.0 x8).

At the moment, they are all linked to a Netgear GS108e switch.

Here are some infos for the i210 NIC :

Code

# ethtool -i enp35s0
driver: igb
version: 5.10.0-0.bpo.9-amd64
firmware-version: 3.16, 0x800004d6
expansion-rom-version:
bus-info: 0000:23:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

Display More

And for the x550 NIC

Code

# ethtool -i enp1s0f0
driver: ixgbe
version: 5.10.0-0.bpo.9-amd64
firmware-version: 0x80000c67, 1.1276.0
expansion-rom-version:
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

# ethtool -S enp1s0f0 | grep rx_dropped
  rx_dropped: 238664

Display More

I have already tried to max the buffer ring but still have the error:

Code

# ethtool -g enp1s0f0
Ring parameters for enp1s0f0:
Pre-set maximums:
RX:             4096
RX Mini:        0
RX Jumbo:       0
TX:             4096
Current hardware settings:
RX:             1024
RX Mini:        0
RX Jumbo:       0
TX:             1024

# ethtool -G enp1s0f0 rx 4096 tx 4096

# ethtool -g enp1s0f0
Ring parameters for enp1s0f0:
Pre-set maximums:
RX:             4096
RX Mini:        0
RX Jumbo:       0
TX:             4096
Current hardware settings:
RX:             4096
RX Mini:        0
RX Jumbo:       0
TX:             4096

Display More

Here are some Iperf tests too :

Code

Connecting to host 192.168.1.100, port 5201
[  4] local 192.168.1.31 port 63926 connected to 192.168.1.100 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec   111 MBytes   934 Mbits/sec
[  4]   1.00-2.00   sec   111 MBytes   928 Mbits/sec
[  4]   2.00-3.00   sec   112 MBytes   942 Mbits/sec
[  4]   3.00-4.00   sec   112 MBytes   940 Mbits/sec
[  4]   4.00-5.00   sec   109 MBytes   911 Mbits/sec
[  4]   5.00-6.00   sec   108 MBytes   904 Mbits/sec
[  4]   6.00-7.00   sec   112 MBytes   942 Mbits/sec
[  4]   7.00-8.00   sec   112 MBytes   940 Mbits/sec
[  4]   8.00-9.00   sec   112 MBytes   942 Mbits/sec
[  4]   9.00-10.00  sec   110 MBytes   919 Mbits/sec
[  4]  10.00-11.00  sec   112 MBytes   941 Mbits/sec
[  4]  11.00-12.00  sec   112 MBytes   942 Mbits/sec
[  4]  12.00-13.00  sec   112 MBytes   942 Mbits/sec
[  4]  13.00-14.00  sec   112 MBytes   936 Mbits/sec
[  4]  14.00-15.00  sec   112 MBytes   939 Mbits/sec
[  4]  15.00-16.00  sec   112 MBytes   942 Mbits/sec
[  4]  16.00-17.00  sec   112 MBytes   937 Mbits/sec
[  4]  17.00-18.00  sec   112 MBytes   941 Mbits/sec
[  4]  18.00-19.00  sec   112 MBytes   942 Mbits/sec
[  4]  19.00-20.00  sec   112 MBytes   942 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-20.00  sec  2.18 GBytes   935 Mbits/sec                  sender
[  4]   0.00-20.00  sec  2.18 GBytes   935 Mbits/sec                  receiver

iperf Done.

Connecting to host 192.168.1.200, port 5201
[  4] local 192.168.1.31 port 63921 connected to 192.168.1.200 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec   112 MBytes   942 Mbits/sec
[  4]   1.00-2.00   sec   111 MBytes   933 Mbits/sec
[  4]   2.00-3.00   sec   112 MBytes   940 Mbits/sec
[  4]   3.00-4.00   sec   112 MBytes   940 Mbits/sec
[  4]   4.00-5.00   sec   111 MBytes   933 Mbits/sec
[  4]   5.00-6.00   sec   111 MBytes   930 Mbits/sec
[  4]   6.00-7.00   sec   112 MBytes   942 Mbits/sec
[  4]   7.00-8.00   sec   112 MBytes   942 Mbits/sec
[  4]   8.00-9.00   sec   112 MBytes   937 Mbits/sec
[  4]   9.00-10.00  sec   112 MBytes   941 Mbits/sec
[  4]  10.00-11.00  sec   109 MBytes   914 Mbits/sec
[  4]  11.00-12.00  sec   112 MBytes   940 Mbits/sec
[  4]  12.00-13.00  sec   112 MBytes   938 Mbits/sec
[  4]  13.00-14.00  sec   112 MBytes   942 Mbits/sec
[  4]  14.00-15.00  sec   112 MBytes   936 Mbits/sec
[  4]  15.00-16.00  sec   112 MBytes   942 Mbits/sec
[  4]  16.00-17.00  sec   112 MBytes   938 Mbits/sec
[  4]  17.00-18.00  sec   112 MBytes   942 Mbits/sec
[  4]  18.00-19.00  sec   112 MBytes   942 Mbits/sec
[  4]  19.00-20.00  sec   111 MBytes   934 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-20.00  sec  2.18 GBytes   937 Mbits/sec                  sender
[  4]   0.00-20.00  sec  2.18 GBytes   937 Mbits/sec                  receiver

iperf Done.

Display More

I can see that ALL my NIC have some dropped packets :

Code

# ifconfig -a
enp1s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet 192.168.1.100  netmask 255.255.255.0  broadcast 192.168.1.255
ether b4:96:91:8d:8f:c8  txqueuelen 1000  (Ethernet)
RX packets 1155390517  bytes 1252988750330 (1.1 TiB)
RX errors 0  dropped 241402  overruns 0  frame 0
TX packets 1272400729  bytes 1513362541979 (1.3 TiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


enp1s0f1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
ether b4:96:91:8d:8f:c9  txqueuelen 1000  (Ethernet)
RX packets 4520  bytes 875489 (854.9 KiB)
RX errors 0  dropped 1105  overruns 0  frame 0
TX packets 231  bytes 54376 (53.1 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


enp35s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
ether d0:50:99:d8:dd:5f  txqueuelen 1000  (Ethernet)
RX packets 176942580  bytes 109978029619 (102.4 GiB)
RX errors 0  dropped 10104  overruns 0  frame 0
TX packets 416419193  bytes 546134806422 (508.6 GiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device memory 0xf7500000-f757ffff


enp36s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
ether d0:50:99:d8:dd:60  txqueuelen 1000  (Ethernet)
RX packets 1262473  bytes 1255531882 (1.1 GiB)
RX errors 0  dropped 1760  overruns 0  frame 0
TX packets 1457957  bytes 1779356814 (1.6 GiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Display More

So :

It's probably not the cables (all the cables are directly connected to the switch), even the test PC... => Not the cables in the walls !
It's probably not the NICs, as 2 are on the motherboard (ASRock Rack x470D4U) and 2 are on the PCie x550T2 Card,
Switch ?
Server configuration... maybe/maybe not ? Intel drivers ?

Any help or idea is welcome as I'm a little lost at the moment

sbocquet · Dec 8th 2021

Little NAS Updated !

Case: Lian Li PC-V354
Motherboard: ASRock Rack x470D4U
CPU: AMD Ryzen 5 3600
RAM: 1 x 16GB Crucial DDR4 PC2666 ECC
PSU: Seasonic M12 - 500W

NIC Card: Intel x550T2 - 10Gb
CPU Fan: 1 x Be Quiet! Pure Rock Slim PWM
System Fans: 3 x Be Quiet! Silent Wings 3 PWM
System Disk: 1 x NVMe XDATA 8200Pro 256GB
Datas Disks: 5 x Western Digital 10TB (RAID 6)

Backups Disk: 1 x Seagate 2TB

sbocquet · Dec 8th 2021

Scripts done... will see next upgrade

sbocquet · Dec 8th 2021

Quote from votdev

Sorry, the OMV SaltStack infrastructure does not provide that feature at the moment. I'll implement this for OMV6 asap.

No problem, I think that post invoke scripts will do the job just fine.
I just don't know if I can aim a specific package in order to not run those scripts at every other package update.

sbocquet · Dec 8th 2021

Hi,

That's not when rebooting, but after each 'apt upgrade' of openmediavault package...
At the moment, I'm investigating the post-invoke option of APT, but I'm a little lost. I need to learn more on the subject...

sbocquet · Dec 7th 2021

Hi,

After each OMV update, I would like to run some commands automatically... not something very complicated, like re-set my dark web theme and the graph size in OMV stats pages for example.

This could be done with those CLI commands :

Code

# Dark OMV theme
cd /var/www/openmediavault/css; cp defaults.sav defaults.scss
make all; chown openmediavault-webgui:openmediavault-webgui *; chmod 664 *;


# OMV Graphs
sed -i 's/400/1400/' /usr/sbin/omv-mkrrdgraph; sed -i 's/120/200/' /usr/sbin/omv-mkrrdgraph;

So... Should I stay with a script that I have to manually run after each upgrade, or is there a nice way to automatically execute those commands after each update (salt ?).

Any idea is welcome...

sbocquet · Dec 2nd 2021

Quote from votdev

If you have not pressed the Apply button in the UI then nothing should have happened. The latest version 5.6.21 has marked the nginx, host and postfix modules as dirty, thus their configuration is re-deployed on pressing Apply. But there are no changes in the code, except that the IPv6 detection has been improved/fixed, thus it can happen that now only IPv4 configuration is generated if IPv6 is not configured.

Thanks Volker ( votdev), you point me in the right direction once again As you said, no IPv6 was configured in those servers... but the nginx reverse proxy conf file was "misconfigured" !

Modified the configuration from

Code

listen [::]:80;
listen [::]:443 ssl http2;

to

Code

listen 80;
listen 443 ssl http2;

Big thanks both of you for your time.

sbocquet · Dec 2nd 2021

Quote from Zoki

You do not find anything in the error log, because nginx does not consider it an error, but redirects to the main server.
Did you have a chance to compare the nginx -T between working and non working servers?
Can you compare the versions of nginx between working and non working? (nginx -v)

Nginx -T are the same... so same broken reverse proxy.
Nginx is v1.14.2, the latest package from debian repo.

The fact that I'm sure is :
- they have exactly the same nginx/proxy config files.
- this morning, I update from v5.6.20 to v5.6.21 the first server; reverse proxy stopped just after (<1 min).
- this afternoon, I updated the second server, reverse proxy stopped just after (<1 min).

Log file from QB access and error are empty since the update, and the access are logged in OMV access log file....

OMV access log file :

Code

Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.20 Safari/537.36 Edg/97.0.1072.13"
91.212.21.220 - - [02/Dec/2021:15:18:49 +0100] "GET / HTTP/1.1" 200 1279 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.20 Safari/537.36 Edg/97.0.1072.13"
127.0.0.1 - - [02/Dec/2021:15:18:53 +0100] "GET / HTTP/1.1" 200 3436 "-" "Monit/5.26.0"
127.0.0.1 - - [02/Dec/2021:15:18:53 +0100] "GET / HTTP/1.1" 200 3436 "-" "Monit/5.26.0"

OMV error log file

Code

91.212.21.220 - - [02/Dec/2021:15:25:25 +0100] "GET /favicon.ico HTTP/1.1" 200 1406 "https://torrent.myURL.fr/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.20 Safari/537.36 Edg/97.0.1072.13"
127.0.0.1 - - [02/Dec/2021:15:25:54 +0100] "GET / HTTP/1.1" 200 3436 "-" "Monit/5.26.0"
127.0.0.1 - - [02/Dec/2021:15:25:54 +0100] "GET / HTTP/1.1" 200 3436 "-" "Monit/5.26.0"

sbocquet · Dec 2nd 2021

Just updated the other server and reverse proxy is broken too with v5.6.21... so for sure, this is related to the update.

So, started nginx in cli mode, and everything is normal... no error code. I'm lost !

Code

2021/12/02 14:54:15 [debug] 6736#6736: bind() 0.0.0.0:80 #11
2021/12/02 14:54:15 [debug] 6736#6736: bind() 0.0.0.0:443 #12
2021/12/02 14:54:15 [debug] 6736#6736: bind() [::]:80 #13
2021/12/02 14:54:15 [debug] 6736#6736: bind() [::]:443 #14
2021/12/02 14:54:15 [notice] 6736#6736: using the "epoll" event method
2021/12/02 14:54:15 [debug] 6736#6736: counter: 00007F5A35620080, 1
2021/12/02 14:54:15 [notice] 6736#6736: nginx/1.14.2
2021/12/02 14:54:15 [notice] 6736#6736: OS: Linux 5.10.0-0.bpo.9-amd64
2021/12/02 14:54:15 [notice] 6736#6736: getrlimit(RLIMIT_NOFILE): 1024:1048576
2021/12/02 14:54:15 [debug] 6736#6736: write: 15, 00007FFFB0BEBC00, 5, 0
2021/12/02 14:54:15 [debug] 6736#6736: setproctitle: "nginx: master process /usr/sbin/nginx -g daemon off;error_log /dev/stdout debug;"
2021/12/02 14:54:15 [notice] 6736#6736: start worker processes
2021/12/02 14:54:15 [debug] 6736#6736: channel 3:15
2021/12/02 14:54:15 [notice] 6736#6736: start worker process 6737
2021/12/02 14:54:15 [debug] 6736#6736: channel 16:17
2021/12/02 14:54:15 [debug] 6737#6737: add cleanup: 000056125677ABB8
2021/12/02 14:54:15 [debug] 6737#6737: malloc: 0000561256774CF0:8
2021/12/02 14:54:15 [notice] 6736#6736: start worker process 6738
2021/12/02 14:54:15 [debug] 6736#6736: pass channel s:1 pid:6738 fd:16 to s:0 pid:6737 fd:3
2021/12/02 14:54:15 [debug] 6737#6737: notify eventfd: 17
2021/12/02 14:54:15 [debug] 6736#6736: channel 18:19
2021/12/02 14:54:15 [debug] 6737#6737: testing the EPOLLRDHUP flag: success
2021/12/02 14:54:15 [debug] 6737#6737: malloc: 000056125673D8D0:6144
2021/12/02 14:54:15 [debug] 6737#6737: malloc: 00007F5A317E5010:184320
2021/12/02 14:54:15 [debug] 6737#6737: malloc: 0000561256782B60:73728
2021/12/02 14:54:15 [debug] 6738#6738: add cleanup: 000056125677ABB8
2021/12/02 14:54:15 [debug] 6737#6737: malloc: 0000561256794B70:73728
2021/12/02 14:54:15 [debug] 6738#6738: malloc: 0000561256774CF0:8
2021/12/02 14:54:15 [debug] 6737#6737: epoll add event: fd:15 op:1 ev:00002001
2021/12/02 14:54:15 [debug] 6737#6737: setproctitle: "nginx: worker process"
2021/12/02 14:54:15 [debug] 6737#6737: worker cycle
...

Display More

sbocquet · Dec 2nd 2021

Quote from Zoki

As your config did not change, can you please check if your file is really included in the nginx config file.
nginx -c /pat/to/mginx/config -T | more will check the config and dump the result. Hit <Enter> to scroll through the pages.

Thanks for the tip... unfortunately, after verification, the conf file is included.

sbocquet · Dec 2nd 2021

Anyway to rollback and re-install openmediavault v5.6.20 ?

sbocquet · Dec 2nd 2021

OMV Update :

Latest known got access :

tail -f qbittorrent-webgui_access.log

Code

::ffff:91.212.21.220 - - [02/Dec/2021:09:03:54 +0100] "POST /api/v2/rss/items?kwonl09y HTTP/2.0" 200 65605 "https://torrent.myInternetURL.fr/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.20 Safari/537.36 Edg/97.0.1072.13"

sbocquet · Dec 2nd 2021

Hummm... I don't want to use docker for several reasons, and it work fine since more than 1 year !

Any other suggestions ?

sbocquet · Dec 2nd 2021

To be complete, this configuration still works fine on another OMV server not updated yet !

sbocquet · Dec 2nd 2021

Hi,

I'm facing a reverse proxy problem since this morning.
I have a qbittorrent-nox server running on my NAS, listening on port 8080 for the WebUI.
I setup a reverse proxy on nginx in order to access it from the internet with an URL on port 443.

Code

root@home-server:/etc/nginx/sites-enabled# ls -al
total 8
drwxr-xr-x 2 root root 4096 Dec  2 10:38 .
drwxr-xr-x 9 root root 4096 May 29  2021 ..
lrwxrwxrwx 1 root root   40 Jul 30  2020 openmediavault-webgui -> ../sites-available/openmediavault-webgui
lrwxrwxrwx 1 root root   37 Aug  5  2020 qbittorrent-webgui -> ../sites-available/qbittorrent-webgui


root@home-server:/etc/nginx/sites-enabled# cat qbittorrent-webgui
server {
server_name torrent.myinterneturl.fr;
listen [::]:80;
listen [::]:443 ssl http2;
ssl_certificate /etc/ssl/certs/openmediavault-68ade6e6-a294-4dd1-ac65-e60c344c6b65.crt;
ssl_certificate_key /etc/ssl/private/openmediavault-68ade6e6-a294-4dd1-ac65-e60c344c6b65.key;

access_log /var/log/nginx/qbittorrent-webgui_access.log;
error_log /var/log/nginx/qbittorrent-webgui_error.log;

location / {
proxy_pass              http://127.0.0.1:8080;
proxy_hide_header       Referer;
proxy_hide_header       Origin;
proxy_set_header        Referer                 '';
proxy_set_header        Origin                  '';
proxy_set_header        Host                    $host;
proxy_set_header        X-Forwarded-Host        $server_name:$server_port;
proxy_set_header        X-Real-IP               $remote_addr;
proxy_set_header        X-Forwarded-For         $proxy_add_x_forwarded_for;
proxy_set_header        X-Forwarded-Proto       $scheme;
add_header              Front-End-Https         on;
}
}

Display More

It used to work fine but until the last update (v5.6.21) this morning. I have checked the changelog but nothing seems related.

Anyway, when I try to access https://torrent.myInternetURL.fr, I have the OMV WebUI page instead of the qBittorrent page, like no redirection is done.
If I try to access directly the qBittorrent WebUI with http://torrent.myInternetURL.fr:8080, I have the correct page.

I can't figure out what could have changed to brake te redirection...
Any Web server expert here ?

Thanks

sbocquet · Dec 1st 2021

+1 for Netgear GS110MX (8 x 1Gb ports + 2 x 10Gb ports).
Plug your PC and the NAS on the two 10Gb ports with RJ45 Cat6 cable, the other devices and your router on the 1 Gb ports.

I think that it's the simpliest and best solution for your problem. if you have the money to buy one (near 170/180€ here)

Posts by sbocquet

[DEV] How to add a widget to the dashboard menu?

Borgbackup disable email

Get collectd iptables stats

Borgbackup disable email

Intel x550 10Gb and i210 NIC with rx_dropped packet

My NAS

Best way to customize OMV after an update ? Salt/Script/?

Best way to customize OMV after an update ? Salt/Script/?

Best way to customize OMV after an update ? Salt/Script/?

Best way to customize OMV after an update ? Salt/Script/?

Nginx reverse proxy broken after latest OMV 5 update (v5.6.21)

Nginx reverse proxy broken after latest OMV 5 update (v5.6.21)

Nginx reverse proxy broken after latest OMV 5 update (v5.6.21)

Nginx reverse proxy broken after latest OMV 5 update (v5.6.21)

Nginx reverse proxy broken after latest OMV 5 update (v5.6.21)

Nginx reverse proxy broken after latest OMV 5 update (v5.6.21)

Nginx reverse proxy broken after latest OMV 5 update (v5.6.21)

Nginx reverse proxy broken after latest OMV 5 update (v5.6.21)

Nginx reverse proxy broken after latest OMV 5 update (v5.6.21)

Setting up a network for 10GBase-T with DHСP on a 1G router