• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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