I have a monitor of type Execute Process. On that process, I do not want to check it if another monitor, which is of type check process, is down. So, in the box labelled "Don't check if monitor is down", I put the check process monitor. After I do that, it forever thinks the execute process monitor is down, even though the other process clearly shows always up (it checks a MySQL replication slave instance). As soon as I remove the dependency in that box, both show up.
So, it seems like perhaps the don't check if down is actually checking don't check if up perhaps?
It confused me for a long time as when I get into the main screen which shows the status of all monitors, they all show up, when I bring up the execute process monitor, it also shows up, yet, the history always showed down. Took me a while to see that the issue was the dependency box.
Comments
Submitted by JamieCameron on Tue, 05/27/2014 - 18:59 Comment #1
The "don't check" option will actually completely disable updating the status of the "execute process" monitor if the "check process" monitor is down. So it will remain in whatever state it was in when the "check process" monitor started failing.
The better solution is to write your command in the "execute process" monitor so that it succeeds if the process isn't running. Something like :
if (ps axuwww | grep -v grep | grep someprocess); then /path/to/command; fiSubmitted by sfatula on Tue, 05/27/2014 - 19:11 Comment #2
The check process is and always is/was up. Always. Nevertheless, the execute process monitor remains down, even though it shows up on the status screen, and, if you edit it, it also says up. The reason is says up is that it is, and executing the command from the command line shows as well. It's not difficult to know that MySQL is running of course.
I do want to use the two as the check process monitor checks if mysql is running, there is no reason for the execute process to check if replication slave threads are running if mysql itself is not running. So, I believe it should work but does not work as you say at all. I believe webmin check has boolean logic reversed.
Submitted by sfatula on Tue, 05/27/2014 - 19:17 Comment #3
This is odd too.... See how it shows that is is up, near top, and, in the history below. This is without check process involved. Now, I back out of the screen to the main webmin system and server status screen ,and it shows down! Always. This is after the update today to the latest webmin version. And, it's configured to show CURRENT status in module config.
Submitted by JamieCameron on Tue, 05/27/2014 - 22:44 Comment #4
Don't forget that by default the main page of the module only shows the status from the last scheduled check, but when you click on a monitor it shows the current live status. You can change this on the Module Config page via the "Status to display in list" setting though.
Submitted by sfatula on Tue, 05/27/2014 - 23:33 Comment #5
Yes, am well aware, and as I had said in the ticket, it is set to "Current Status". In any case, the monitors do not work. See portion #2 in this ticket.
Submitted by JamieCameron on Thu, 05/29/2014 - 00:34 Comment #6
Another possible cause is that when you click on a monitor, its status is shown regardless of the status of whatever monitor is in the "Don't check if monitor is down" field. That only controls what checking is done on schedule (to prevent false alerts), not in the UI.
Submitted by sfatula on Thu, 05/29/2014 - 00:49 Comment #7
Ok, I should not have mentioned the second issue as it is clear I have confused things, I will report that as a separate case. Back to the original. When the monitor has the box checked to not check if monitor is down, then, I am finding that the monitor is never run, whether or not the other monitor is down. That is the issue I am reporting here.
I would like for that to be fixed.
Submitted by JamieCameron on Thu, 05/29/2014 - 14:06 Comment #8
I'm not seeing this on my test system, sorry. However, I just realized when you have the main page set to show the current status vs. the last background collected, it does NOT take dependencies into account.
However, when you change the "Status to display in list" to "From last scheduled check", monitors that had a failed dependencies will have their status shown as a dash.
Submitted by sfatula on Thu, 05/29/2014 - 14:13 Comment #9
Ok, so, it sounds like I may need to grant you access to this Virtualmin so you can see for yourself.
Submitted by JamieCameron on Thu, 05/29/2014 - 14:18 Comment #10
That would be useful. Email me at jcameron@webmin.com
Submitted by sfatula on Thu, 05/29/2014 - 16:10 Comment #11
I sent email, however, I do not see the Virtualmin support module any more to grant access?
Submitted by JamieCameron on Thu, 05/29/2014 - 16:16 Comment #12
You may need to install it with the command
yum install wbm-virtualmin-supportSubmitted by sfatula on Thu, 05/29/2014 - 16:25 Comment #13
Yep, but, it is not a valid module that yum sees. So, I did a yum clean all just in case, and a yum search virtualmin, and get this output. I do not see support as a module!
Loaded plugins: fastestmirror Determining fastest mirrors epel/metalink | 12 kB 00:00
* base: mirror.stanford.edu * epel: mirror.prgmr.com * extras: mirror.web-ster.com * updates: mirror.pac-12.org base | 3.7 kB 00:00
base/primary_db | 4.4 MB 00:00
epel | 4.4 kB 00:00
epel/primary_db | 6.2 MB 00:00
extras | 3.4 kB 00:00
extras/primary_db | 19 kB 00:00
updates | 3.4 kB 00:00
updates/primary_db | 3.2 MB 00:00
virtualmin | 1.2 kB 00:00
virtualmin/primary | 31 kB 00:00
virtualmin-universal | 1.2 kB 00:00
virtualmin-universal/primary | 23 kB 00:00
virtualmin-universal 193/193 epel/pkgtags | 1.0 MB 00:00
=========================== N/S Matched: virtualmin ============================ virtualmin-base.noarch : Wrapper package to trigger installation of the : Virtualmin Stack virtualmin-release.noarch : Virtualmin release file and package configuration wbm-virtualmin-dav.noarch : Webmin module for 'Virtualmin DAV' wbm-virtualmin-git.noarch : Webmin module for 'Virtualmin Git Repositories' wbm-virtualmin-google-analytics.noarch : Webmin module for 'Virtualmin : Analytics' wbm-virtualmin-htpasswd.noarch : Webmin module for 'Virtualmin Protected : Directories' wbm-virtualmin-init.noarch : Webmin module for 'Virtualmin Bootup Actions' wbm-virtualmin-mailman.noarch : Webmin module for 'Virtualmin Mailman Mailing : Lists' wbm-virtualmin-oracle.noarch : Webmin module for 'Virtualmin Oracle Databases' wbm-virtualmin-registrar.noarch : Webmin module for 'Virtualmin Domain : Registration' wbm-virtualmin-signup.noarch : Webmin module for 'Virtualmin Mailbox Signup' wbm-virtualmin-slavedns.noarch : Webmin module for 'Virtualmin Slave DNS Plugin' wbm-virtualmin-sqlite.noarch : Webmin module for 'Virtualmin SQLlite Databases' wbm-virtualmin-svn.noarch : Webmin module for 'Virtualmin Subversion : Repositories' ust-virtual-server-mobile.noarch : Usermin theme 'Virtualmin Mobile Theme' ust-virtual-server-theme.noarch : Usermin theme 'Virtualmin Framed Theme' wbm-security-updates.noarch : Webmin module for 'Virtualmin Package Updates' wbm-virtual-server.noarch : Webmin module for 'Virtualmin Virtual Servers (GPL)' wbm-virtualmin-awstats.noarch : Webmin module for 'AWstats Reporting' wbm-virtualmin-nginx.noarch : Webmin module for 'Nginx Webserver' wbm-virtualmin-nginx-ssl.noarch : Webmin module for 'Nginx SSL Webserver' wbt-virtual-server-mobile.noarch : Webmin theme 'Virtualmin Mobile Theme' wbt-virtual-server-theme.noarch : Webmin theme 'Virtualmin Framed Theme'
Submitted by JamieCameron on Thu, 05/29/2014 - 16:54 Comment #14
I assume you are using the Pro version there?
Submitted by sfatula on Thu, 05/29/2014 - 17:06 Comment #15
True, it turns out this is a GPL machine. So, how to proceed? My email documented what to do, assuming you could get on of course. There is definitely at least one bug, probably two. Perhaps I could just create a temporary webmin user and email to you? How do people usually handle this? Can I grant access to just system and server status perhaps? Or, do you need more?
Submitted by sfatula on Fri, 05/30/2014 - 11:52 Comment #16
I installed your patch for the issue where adding a don't check if monitor down causes it to always say down, and I get the same results. I uploaded the patch, installed from the local directory, it said it was installed, I even restarted webmin just in case.
Submitted by JamieCameron on Sat, 05/31/2014 - 00:49 Comment #17
Ok, I've emailed your the virtualmin-support RPM - you can install it with the command :
rpm -U wbm-virtualmin-support-1.6-1.noarch.rpm