• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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