monit too early...

Pasted by karlp on Thu May 5 10:10:25 2022 UTC as Text only
Thu May  5 15:12:51 2022 cron.err crond[1615]: crond (busybox 1.33.1) started, log level 5
Thu May  5 15:12:54 2022 daemon.notice procd: /etc/rc.d/S50uhttpd: 4+0 records in
Thu May  5 15:12:54 2022 daemon.notice procd: /etc/rc.d/S50uhttpd: 4+0 records out
Thu May  5 15:12:57 2022 daemon.info monit[1788]: Starting Monit 5.26.0 daemon with http interface at [127.0.0.1]:2812
Thu May  5 15:12:57 2022 daemon.info monit[1788]: 'eg-xxxx' Monit 5.26.0 started
Thu May  5 15:12:57 2022 daemon.err monit[1788]: HTTP server -- Cannot bind: Address not available
Thu May  5 15:12:57 2022 daemon.err monit[1788]: HTTP server -- Cannot translate IPv6 socket [127.0.0.1]:2812 -- Name does not resolve
Thu May  5 15:12:58 2022 daemon.err monit[1844]: Cannot create socket to [127.0.0.1]:2812 -- Network unreachable
Thu May  5 15:12:58 2022 daemon.warn netifd: You have delegated IPv6-prefixes but haven't assigned them to any interface. Did you forget to set option ip6assign on your lan-interfaces?
Thu May  5 15:12:58 2022 daemon.notice netifd: Interface 'lan' is enabled
Thu May  5 15:12:58 2022 daemon.notice netifd: Interface 'loopback' is enabled
Thu May  5 15:12:58 2022 daemon.notice netifd: Interface 'loopback' is setting up now
Thu May  5 15:12:58 2022 daemon.notice netifd: Interface 'loopback' is now up
Thu May  5 15:12:58 2022 daemon.notice netifd: Network device 'lo' link is up
Thu May  5 15:12:58 2022 daemon.notice netifd: Interface 'loopback' has link connectivity