Upgraded from 5.14 to 5.19.0 and found a regression with our monit configuration. Specifically, "monit start all" and "monit stop all" now fail without starting or stopping any services. For example:
$ monit start all There is no service named "FS=" $ monit stop all There is no service named "FS="
Note that we have several service checks of type filesystem defined as follows:
check filesystem FS=/foo/bar with path /foo/bar
It seems that 5.14 monit would correctly handle <service name> of this form but in 5.19 this name causes a regression.
We would really really like to not change the service names to adopt or trip over this issue in some other manner.
Thanks for your consideration. -sandy