votdev Is there any information I could provide for getting this addressed?
Posts by David B
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.
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.
I added it a year ago - https://github.com/OpenMediaVa…cdb5127a58cccc19974af6b7e
All you have to do click install Docker again. This will update the drive list and docker-compose.
Oh cool! Sorry about missing that. I did start to poke around the plugin source code to see if I could find it, but I haven't really had enough free time to hunt it down. I regularly reinstall Portainer (since trying to do a container upgrade through the UI does not seem to work), but I don't think I've touched Docker since when I first installed it.
That's probably the reason we've seen less and less of this problem. Honestly wasn't aware you'd made an effort to resolve that.
It seems as though good development work always goes on without notice. It's only when there's a problem that everyone starts to pay attention!
Oh I have no doubt what he said worked... that wasn't the question. Even he mentioned though there's a limitation as it's not going to auto update if drives are removed/added... the delay script doesn't have that limitation.
Ah! Alright. Got it. I do not often add or remove drives, so I'll leave it as it is for now and wait for ryecoaaron to chime in. It would be nice if this change would get added to the omv-extras plugin. Even though the timeout script is the most stable for now, it would be nice to use the drive approach since I would think that it's technically the way you'd want to go about it.
I'd never seen that solution, I always just suggested the delay script you posted a couple years ago (and have always heard back that it worked perfectly). I'm assuming this would work fine, but I think the delay script might be a more permanent solution given it doesn't self update... Especially since we are talking Pi's and other SBC's which may have drives getting moved around, etc.
Choices... 1 isn't enough, 2 is to many...
I made this change and it worked! I don't quite understand what the implications are to deleting the files that ryecoaaron mentions in his post though. I assume that the change was never integrated into OMV-extras though.
Do you have omv-extras installed?
RE: Is your docker also corrupt after a reboot? (OMV5, Pi4) This might fix it!
I do indeed! Thanks! I will give this a shot later today.
I am using server external USB hard drives on my OMV server, and have several Docker containers that mount various directories stored on the drives. The problem is that when I boot the server, the containers often start before the drives are mounted. Is there any way that I can force the Docker service to wait for the mounting to complete before starting?
I added compress=zlib to the options in /etc/openmediavault/config.xml in the mntent section. Then omv-mkconf fstab will write the changes.
For anyone that comes along in the future that wants to use the instructions, omv-mkconf fstab is no longer an option and omv-salt stage run all should be used instead.
Embrace it.. we all had to at some point. Once you get the hang of docker, you will wonder why you ever did anything else
Oh I've already migrated everything else to Docker and I agree it's great! I'm just being kind of lazy with OpenVPN. 😆 Does anyone have any recommendations for which a Docker image to use for it?