You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 14, 2021. It is now read-only.
I started seeing this after switching from Ubuntu 14.04 to 16.04 as my base image. In this situation monit starts too early in the boot process and never gets bound to it's TCP port. If you simply restart monit after bootup completes it binds normally to it's port.
An easy fix is to add "After=network-online.target" to the systemd monit.service file created by poise-service.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I started seeing this after switching from Ubuntu 14.04 to 16.04 as my base image. In this situation monit starts too early in the boot process and never gets bound to it's TCP port. If you simply restart monit after bootup completes it binds normally to it's port.
An easy fix is to add "After=network-online.target" to the systemd monit.service file created by poise-service.
The text was updated successfully, but these errors were encountered: