Monitoring Warning Service proftpd

Burgerbob · 8. Februar 2023

Hello,

since the lastest update and the change to plugin i get 2 "System Monitoring Alert Emails" every start of my System.

Ftp Server works fine, but the messages get annoying, any idea how to fix this?

1st mail: Monitoring restart -- Does not exist proftpd:

The system monitoring needs your attention.

Host: bla

Date: Wed, 08 Feb 2023 21:06:54

Service: proftpd

Event: Does not exist

Description: process is not running

This triggered the monitoring system to: restart

2nd mail 30 seconds later: Monitoring alert -- Exists proftpd

The system monitoring needs your attention.

Host: bla

Date: Wed, 08 Feb 2023 21:07:28

Service: proftpd

Event: Exists

Description: process is running with pid 1748

This triggered the monitoring system to: alert

any ideas?

thanks in advance

ryecoaaron · 9. Februar 2023

ftp was moved to a separate plugin. Just install it from the Plugins tab if you were using ftp.

votdev · 9. Februar 2023

Check https://www.openmediavault.org/?p=3401

Burgerbob · 9. Februar 2023

i installed the plugin, ftp works fine for me, all settings migrated, but i still get the warning emails on every Server start.

here my log:

Code

2023-02-09T18:31:38+0100 tvs-omv6 monit[767]: 'tvs-omv6' Monit 5.27.2 started
2023-02-09T18:31:38+0100 tvs-omv6 monit[767]: 'proftpd' process is not running
2023-02-09T18:31:39+0100 tvs-omv6 postfix/smtpd[1725]: connect from localhost.localdomain[127.0.0.1]
2023-02-09T18:31:39+0100 tvs-omv6 postfix/smtpd[1725]: 13EB0100F1F: client=localhost.localdomain[127.0.0.1]
2023-02-09T18:31:39+0100 tvs-omv6 postfix/cleanup[1728]: 13EB0100F1F: message-id=<1675963899.5f4b7c3c6c98135b@tvs-omv6>
2023-02-09T18:31:39+0100 tvs-omv6 postfix/qmgr[1077]: 13EB0100F1F: from=<bla@bla.de>, size=983, nrcpt=2 (queue active)
2023-02-09T18:31:39+0100 tvs-omv6 postfix/smtpd[1725]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
2023-02-09T18:31:39+0100 tvs-omv6 monit[767]: 'proftpd' trying to restart
2023-02-09T18:31:39+0100 tvs-omv6 monit[767]: 'proftpd' start: '/etc/init.d/proftpd restart'
2023-02-09T18:31:39+0100 tvs-omv6 postfix/pipe[1730]: 13EB0100F1F: to=<openmediavault-notification@localhost.localdomain>, relay=omvnotificationfilter, delay=0.14, delays=0.1/0.01/0/0.03, dsn=2.0.0, status=sent (delivered via omvnotificationfilter service)
2023-02-09T18:31:39+0100 tvs-omv6 systemd[1]: Starting ProFTPD FTP Server...
2023-02-09T18:31:39+0100 tvs-omv6 proftpd[1752]: Checking syntax of configuration file
2023-02-09T18:31:39+0100 tvs-omv6 postfix/smtp[1731]: 13EB0100F1F: replace: header Subject: Monitoring restart -- Does not exist proftpd: Subject: [TVS-OMV6.local] Monitoring restart -- Does not exist proftpd
2023-02-09T18:31:39+0100 tvs-omv6 postfix/smtp[1731]: 13EB0100F1F: to=<bla@bla.de>, relay=xx.xx.xx]:587, delay=0.75, delays=0.1/0.19/0.33/0.13, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as ACBE010A1EA7)
2023-02-09T18:31:39+0100 tvs-omv6 postfix/qmgr[1077]: 13EB0100F1F: removed
2023-02-09T18:31:40+0100 tvs-omv6 systemd[1]: Finished Generate the prelogin message.
2023-02-09T18:31:40+0100 tvs-omv6 systemd[1]: Reached target Login Prompts.
2023-02-09T18:31:40+0100 tvs-omv6 systemd[1]: Reached target Multi-User System.
2023-02-09T18:31:40+0100 tvs-omv6 systemd[1]: Reached target Graphical Interface.
2023-02-09T18:31:40+0100 tvs-omv6 systemd[1]: Starting Beep after system start...
2023-02-09T18:31:40+0100 tvs-omv6 systemd[1]: Starting Update UTMP about System Runlevel Changes...
2023-02-09T18:31:40+0100 tvs-omv6 systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
2023-02-09T18:31:40+0100 tvs-omv6 systemd[1]: Finished Update UTMP about System Runlevel Changes.
2023-02-09T18:31:40+0100 tvs-omv6 proftpd[1764]: 127.0.1.1 - ProFTPD 1.3.7a (maint) (built Sat Sep 18 2021 21:42:19 UTC) standalone mode STARTUP
2023-02-09T18:31:40+0100 tvs-omv6 systemd[1]: Started ProFTPD FTP Server.
2023-02-09T18:31:41+0100 tvs-omv6 systemd[1]: openmediavault-beep-up.service: Succeeded.
2023-02-09T18:31:41+0100 tvs-omv6 systemd[1]: Finished Beep after system start.
2023-02-09T18:31:41+0100 tvs-omv6 systemd[1]: Startup finished in 6.420s (kernel) + 41.140s (userspace) = 47.560s.
2023-02-09T18:32:11+0100 tvs-omv6 monit[767]: 'proftpd' process is running with pid 1764
2023-02-09T18:32:11+0100 tvs-omv6 postfix/smtpd[1725]: connect from localhost.localdomain[127.0.0.1]
2023-02-09T18:32:11+0100 tvs-omv6 postfix/smtpd[1725]: 4FCC7100F1F: client=localhost.localdomain[127.0.0.1]
2023-02-09T18:32:11+0100 tvs-omv6 postfix/cleanup[1728]: 4FCC7100F1F: message-id=<1675963931.63bf20e345d86295@tvs-omv6>
2023-02-09T18:32:11+0100 tvs-omv6 postfix/qmgr[1077]: 4FCC7100F1F: from=<bla@bla.de>, size=973, nrcpt=2 (queue active)
2023-02-09T18:32:11+0100 tvs-omv6 postfix/smtpd[1725]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
2023-02-09T18:32:11+0100 tvs-omv6 postfix/pipe[1730]: 4FCC7100F1F: to=<openmediavault-notification@localhost.localdomain>, relay=omvnotificationfilter, delay=0.14, delays=0.11/0/0/0.03, dsn=2.0.0, status=sent (delivered via omvnotificationfilter service)
2023-02-09T18:32:11+0100 tvs-omv6 postfix/smtp[1731]: 4FCC7100F1F: replace: header Subject: Monitoring alert -- Exists proftpd: Subject: [TVS-OMV6.local] Monitoring alert -- Exists proftpd
2023-02-09T18:32:11+0100 tvs-omv6 postfix/smtp[1731]: 4FCC7100F1F: to=<bla@bla.de>, relay=xx.xx.xx]:587, delay=0.51, delays=0.11/0/0.27/0.13, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as B285510A1E96)
2023-02-09T18:32:11+0100 tvs-omv6 postfix/qmgr[1077]: 4FCC7100F1F: removed
2023-02-09T18:35:01+0100 tvs-omv6 CRON[1858]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
2023-02-09T18:35:01+0100 tvs-omv6 CRON[1859]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
2023-02-09T18:35:01+0100 tvs-omv6 CRON[1858]: pam_unix(cron:session): session closed for user root

Alles anzeigen

votdev · 10. Februar 2023

I also get this emails from beginning of OMV. proftpd requires more time than the delay of the first check of monit is. You can increase the default delay of 30 seconds via the OMV_MONIT_CHECK_START_DELAY environment variable.

Burgerbob · 10. Februar 2023

Changed the delay to 60 or 90 seconds or even back to 5 seconds, still get the message.. used the methode via CLI explained here in the forum.

but it doenst matter what i put into that variable my log always says:

Code

2023-02-10T12:56:21+0100 tvs-omv6 monit[724]: Starting Monit 5.27.2 daemon with http interface at /run/monit.sock
2023-02-10T12:56:18+0100 tvs-omv6 systemd[1]: Starting Preprocess NFS configuration...
2023-02-10T12:56:21+0100 tvs-omv6 monit[756]: Monit will delay for 30s on first start after reboot ...

and like 30 seconds later i can see in my log:

Code

2023-02-10T12:56:51+0100 tvs-omv6 monit[756]: 'proftpd' process is not running
2023-02-10T12:56:52+0100 tvs-omv6 monit[756]: 'proftpd' trying to restart
2023-02-10T12:56:52+0100 tvs-omv6 monit[756]: 'proftpd' start: '/etc/init.d/proftpd restart'
2023-02-10T12:56:52+0100 tvs-omv6 systemd[1]: Starting ProFTPD FTP Server...

now wondering, if my proftpd just starts after monit restarts it?

any ideas?

Burgerbob · 10. Februar 2023

just tried your advice from another topic:

Zitat

Try to rebuild and restart the service via omv-salt deploy run proftpd

This seems to work for me.. did a couple of reboots, proftpd starts fine, no more emails from monit.

Monitoring Warning Service proftpd

votdev 10. Februar 2023

Jetzt mitmachen!