Alright I will experiment with this. Thank you!
Posts by David B
-
-
votdev After clearing all of my fail2ban entries and trying again, the command runs instantly and the timeout no longer happens when using the web UI.
ryecoaaron I can certainly move it, but I thought that the way those scanners typically worked meant that it would still get hammered. I would actually like to close it off, but unfortunately, I need SSH access to be open.
-
I have attached a copy of the output from time omv-sysinfo. I think I have a guess as to what is causing the problem: the fail2ban output is very lengthy, and it seems to take some time for that information to print out when running the command in the terminal.
-
The time omv-sysinfo command has been running for about 10 minutes and it's not done yet. I will post an update when it's finished, but for now, OMV lists my CPU as Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz. The machine has 8GB of RAM.
As for the plugins I use, here it the list of what I have installed:
- openmediavault-cputemp 6.1.1
- openmediavault-fail2ban 6.0.2
- openmediavault-flashmemory 6.1
- openmediavault-omvextrasorg 6.0.8
- openmediavault-remotemount 6.0
- openmediavault-sharerootfs 6.0-4
- openmediavault-symlinks 6.0.4
- openmediavault-wol 6.0.1
I also use several Docker containers, but I would that that they would be irrelevant.
-
Alright I just tried again, but I still don't see anything.
-
Hmm alright. I will try again and post back here again.
In the meantime, I do have these entries in /var/log/nginx/openmediavault-webgui_error.log, but that doesn't really help much with solving the problem, I would think.
Code2022/05/03 09:24:13 [error] 2483#2483: *32247 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.4, server: openmediavault-webgui, request: "POST /rpc.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.4-fpm-openmediavault-webgui.sock", host: "192.168.1.2", referrer: "http://192.168.1.2/" 2022/05/03 11:24:35 [error] 2483#2483: *32547 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.4, server: openmediavault-webgui, request: "POST /rpc.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.4-fpm-openmediavault-webgui.sock", host: "192.168.1.2", referrer: "http://192.168.1.2/" 2022/05/03 11:26:14 [error] 2483#2483: *32547 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.4, server: openmediavault-webgui, request: "POST /rpc.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.4-fpm-openmediavault-webgui.sock", host: "192.168.1.2", referrer: "http://192.168.1.2/" 2022/05/03 11:31:35 [error] 2483#2483: *32705 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.4, server: openmediavault-webgui, request: "POST /rpc.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.4-fpm-openmediavault-webgui.sock", host: "192.168.1.2", referrer: "http://192.168.1.2/" 2022/05/03 14:17:34 [error] 2483#2483: *33100 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.4, server: openmediavault-webgui, request: "POST /rpc.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.4-fpm-openmediavault-webgui.sock", host: "192.168.1.2", referrer: "http://192.168.1.2/" 2022/05/03 14:21:30 [error] 2483#2483: *33089 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.4, server: openmediavault-webgui, request: "POST /rpc.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.4-fpm-openmediavault-webgui.sock", host: "192.168.1.2", referrer: "http://192.168.1.2/" 2022/05/03 14:24:16 [error] 2483#2483: *33100 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.4, server: openmediavault-webgui, request: "POST /rpc.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.4-fpm-openmediavault-webgui.sock", host: "192.168.1.2", referrer: "http://192.168.1.2/"
-
I didn't see any errors in /var/log/syslog, so I tried doing what you described, and I still don't see any errors. I have attached the output from omv-engined -d -f. Perhaps you will be able to find something that I can't? It looks pretty unhelpful though.
-
votdev Is there any information I could provide for getting this addressed?
-
Hello OMV Community,
I am having a recurring issue with the "Diagnostics → Report" page on my OMV installation. Every time I try to load it, it tries to load for several minutes before ultimately following with this error: "Http failure response for http://192.168.1.2/rpc.php: 504 Gateway Time-out"
Has anyone else seen this and does anyone know if there is a way to fix it?
My OMV version is 6.0.25-1 (Shaitan).
-
I managed to resolve this on my system. Here is what worked for me:
- SSH as root to your OMV server.
- apt install usrmerge
- omv-salt stage run prepare
- omv-salt deploy run samba
- Samba should be working again. If it isn't for whatever reason, try disabling it and re-enabling it via the web UI.
-
I am seeing the same issue as well after updating to 6.0.6. votdev
-
ryecoaaron Just got the update to support the WOL plugin on OMV 6. Thank you!
-
Definitely not. It caused too many problems because people read the instructions as mandatory even though labeled as optional.
Ah, that's understandable.
I just glanced at the code. I could probably port in 15-30 mins. If you really want to do it, I can leave it. Otherwise, it isn't really the time killer some of the others are.
If you would do it, that would be greatly appreciated!
It's not that I don't want to do it, but moreso that I don't really have the time to invest in learning how to do it well right now.
-
Correct. There is no page with instructions on it. There is a status indicator in the services status tab now though.
Ah, I had not noticed the status indicator. Thanks for pointing that out! Are there any plans to restore the page with instructions? I don't need it, but I am curious.
It is a pretty easy port. The mergerfs and kvm plugins have been taking most of my time. If you want to give it a shot, I won't tell you no
Otherwise, I can probably take a productive break from mergerfs.
Time permitting, I would not mind trying to take a crack at it over the weekend. Although if I am being honest, I have struggled with the most basic of plugin tasks in the past, so I am sure it would not be easy for me. 😆
-
openmediavault-flashmemory - done
Does the new flashmemory plugin not have a UI component to it at this time? I am running version 6.0.1 of the plugin on my server, but I don't see any menu entry for it.
openmediavault-wol - not started
How much work will the WOL plugin require to port? Is it just a UI port? I am asking because I use it on my server, and if you don't have plans to get to it any time soon, I might try taking a stab at porting it if time permits.
-
Awesome! Thank you votdev both for your detailed explanation as well as fixing the issue!
-
So, after a bit more research, it sounds like all of this depends on the MDTM command, which is not supported by ProFTPD, but can be added via a third party module? - http://www.proftpd.org/docs/contrib/mod_site_misc.html
Perhaps votdev would know?
-
Sorry, I have never used ftp and really don't know much about proftpd.
That's alright! Thanks anyway! I just assumed that you would know because it feels to me like you know all that their is to know about Linux. 🙂
Try to add it to the extra options field in the ftp service in the GUI of OMV
If you are talking about this box, then I have already tried it (see initial post), and sadly, it did not work.
-
I hate to be that annoying guy who tags people, but I have a feeling that ryecoaaron can probably help.
-
Hello all,
I have noticed that ProFTPD shows modification timestamps for files in UTC instead of my local timezone. Does anyone know how to adjust this? I found in the documentation that setting TimesGMT off as a custom configuration entry should change this behavior, but it hasn't.
I also found a supposed solution here that recommends setting the following:
I have tried to use this in the custom configuration with and without the <Global> tags, but nothing seems to work. The FTP client that I am using is FileZilla, if that makes any difference.