Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Openmediavault Install - Error about Monit and Socket 2812 when hitting apply #435

Closed
vepicurean opened this issue Sep 5, 2019 · 10 comments

Comments

@vepicurean
Copy link

commented Sep 5, 2019

Hi:

I installed Openmediavault 4 about a month ago. For the most part it worked OK (some small issues on a notification that came across every week, but it was a minor annoyance rather than a functional issue). I know when I installed and tested the server and Openmediavault, things were working as they should.

Openmediavault and all the plug-ins are fully up-to-date. All I've done is added a couple AFP and SMB shares and run the updates. Nothing else. Basic stuff.

Suddenly, this week, most times (not overtime, most times) when I hit apply I get this strange error about Monit and socket 2812 comes up (the apply fails miserably). No where do I see any information on this issue that makes sense to me.

I basically can't do anything with Openmediavault right now. Every time I try to change and apply something, the apply fails and I have to revert.

How is this happening on a new install?

@vepicurean vepicurean changed the title Brandnew Openmediavault Install - Error about Monit and Socket 2812 when hitting apply New Openmediavault Install - Error about Monit and Socket 2812 when hitting apply Sep 5, 2019

@votdev votdev added the 4.x label Sep 6, 2019

@votdev

This comment has been minimized.

Copy link
Collaborator

commented Sep 6, 2019

Which plugins do you have installed?

@vepicurean

This comment has been minimized.

Copy link
Author

commented Sep 9, 2019

AFP and SMB file sharing protocol plugins. OMV Extras. I'm also using the Promax kernel. I've enabled ZFS and that's the RAID volume my shares run on.
That's about it that I added/configured after the initial OMV install.

All worked fine (except for a strange email notification about an error each week about the SMARTdisk monitoring) til about two weeks ago. The install is basically brand new.

All updates have been implemented.

@votdev

This comment has been minimized.

Copy link
Collaborator

commented Sep 9, 2019

Please check the syslog for more information. There are so many reasons why Monit can fail, so with this less information we can not do anything here.

@vepicurean

This comment has been minimized.

Copy link
Author

commented Sep 10, 2019

What additional info do you need? This is not good. Is Openmediavault always this unstable just from doing a few updates? It was fine a couple weeks ago. The reason I went with Openmediavault over BSD is I know and trust the Linux kernel and the Debian distribution. I run Debian Linux all over my systems and there's almost never an issue. I was expecting the same with OpenMediaVault, but it's obvious some of these plugins are not that stable.

@votdev

This comment has been minimized.

Copy link
Collaborator

commented Sep 10, 2019

Maybe starting Monit via systemd manually from CLI and watch the syslog may be a good starting point.

@vepicurean

This comment has been minimized.

Copy link
Author

commented Sep 11, 2019

Normally I wouldn't mind taking more time to research the issue and help come up with a fix and share my findings.

But I'm concerned this type of thing is going to be an on going issue with Openmediavault. For that reason I've avoided putting data on this new server for fear of losing it. I spent nearly a whole weekend researching this already, and though people have reported issues similar before, they are not describing exactly what I'm seeing.

I think it's a major issue when the "Apply" function basically doesn't work and I've not done anything that could be considered non standard, core functionality in terms of configuration.

It's a time issue. Before I invest the time (which is money expense to myself and others dependent on my time), usually in the Linux community others have seen the same issue before. Instead of me re-doing what others have already done, I was hoping someone in the Openmediavault community would have seen this before and have the fix.

@ryecoaaron

This comment has been minimized.

Copy link
Contributor

commented Sep 11, 2019

But I'm concerned this type of thing is going to be an on going issue with Openmediavault.

Why? I've never seen this issue on hundreds of installs. It could be a hardware or storage or ? issue that has nothing to do with OMV and can't be fixed with a code change. When you use some thing free and have a problem that isn't common, you should expect to do the leg work. If you find a problem that is caused by bad code, I'm sure it will be fixed if reproducible.

And remember, the web interface not working won't cause data loss. In case of emergency, you could disable the omv services and manually configure samba/afp/zfs just like any other Linux system.

@vepicurean

This comment has been minimized.

Copy link
Author

commented Sep 19, 2019

I hear you, but all you mention defeats the purpose of using OMV in the first place. If it's going to be this difficult to determine a fix to something like this, then might as well delete and rebuild the system using FreeNAS.....

Note: Nothing in this world is free (there's is always an exchange in the simplest interaction). All software/technology has a cost (time is money) whether the purchase price is 0 or not is often irrelevant. That's been proven many times over.

I'm even noticing this Monit port inaccessible error when doing the updates within OpenMediaVault.

Here's someone/people talking about a similar issue (s) right here: https://forum.openmediavault.org/index.php/Thread/12214-OMV-on-RPI2-Monit-error/

I reviewed all these and determined if this is going to keep happening and it's been around this long without a built in fix (maybe not exactly the same as what I'm seeing, but it's been seen before and seems prone to breaking even after a one time fix) then I'll ask the forum if there's a way to fix permanently before going a different route. That's all I'm doing.

@ryecoaaron

This comment has been minimized.

Copy link
Contributor

commented Sep 19, 2019

It is only difficult because we aren't able to see everything about the system and you said you preferred not to do leg work. This is probably a failing OS drive that would cause ALL OSes including Windows and FreeNAS to have issues.

The monit port is only inaccessible while monit is being updated or restarted. How would you avoid that??

The RPi2 post you mention is from 4 years when I first created the RPi images. They were beta with a few issues and I am quite sure an old SD card was used. So, this was a case of failing storage as well. In case you think this is OMV-specific, VMware ESXi has this issue as well.

If OMV was broken this bad, hundreds if not thousands of users would be complaining and no one would use OMV. I have been using OMV since the beginning on many systems and don't have these issues. In order for OMV to be flexible like it is, sometimes a little Linux work is necessary. If that isn't something you are willing to do, then a commercial NAS (FreeNAS is commercial as well) is probably what you need.

@votdev

This comment has been minimized.

Copy link
Collaborator

commented Sep 19, 2019

I think this is a Monit issue we can not do anything, it's how Monit works. There is a commit 970abaa that explains this behaviour.

Reduce monit delay from 30 to 5 seconds after the daemon is (re-)started. This is a delay until monit starts monitoring the configured services. During this time to CLI tool was not useable and results in an socket not available error.

@votdev votdev closed this Sep 19, 2019

@votdev votdev added the known issue label Sep 19, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.