• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Question Watchdog problem

Dork

Regular Pleskian
Server operating system version
CentOS 7.9
Plesk version and microupdate number
18.0.57 Update #5,
maillog contains the following entry every hour:

Dec 30 13:24:44 h2675909 dovecot: pop3-login: Disconnected: Aborted login by logging out (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, TLS, session=<ovPXO7kNwrF/AAAB>
Dec 30 13:24:44 h2675909 dovecot: pop3-login: Disconnected: Aborted login by logging out (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, TLS, session=<ovPXO7kNwrF/AAAB>
Dec 30 13:24:44 h2675909 dovecot: pop3-login: Disconnected: Aborted login by logging out (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<k1PYO7kNaMV/AAAB>
Dec 30 13:24:44 h2675909 dovecot: pop3-login: Disconnected: Aborted login by logging out (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<k1PYO7kNaMV/AAAB>
Dec 30 13:24:44 h2675909 dovecot: imap-login: Disconnected: Aborted login by logging out (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, TLS, session=<OJfYO7kNHsR/AAAB>
Dec 30 13:24:44 h2675909 dovecot: imap-login: Disconnected: Aborted login by logging out (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, TLS, session=<OJfYO7kNHsR/AAAB>
Dec 30 13:24:44 h2675909 dovecot: imap-login: Disconnected: Aborted login by logging out (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<d9PYO7kN2pN/AAAB>
Dec 30 13:24:44 h2675909 dovecot: imap-login: Disconnected: Aborted login by logging out (no auth attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, session=<d9PYO7kN2pN/AAAB>

I`m very sure that it is watchdog which produced it.
Any idea how to prevent that?
 
Yes, those are produced by Watchdog. But those are also expected log entries (and not caused by error or anything). If these log entries bother you, you could disable Dovecot monitoring in Watchdog.
 
Yes, those are produced by Watchdog. But those are also expected log entries (and not caused by error or anything). If these log entries bother you, you could disable Dovecot monitoring in Watchdog.
Sounds like a soution but not a real solution.
Watchdog should be able to login.
 
Logging in would produce even more log entries, so I'm not sure that would improve things.
 
Back
Top