Question Often seeing table hash .../poplock... has changed -- restarting

[tkalfaoglu]

I am seeing this in the mail logs every few minutes:

Sep 18 14:37:58 jedi postfix/smtpd[56365]: table hash:/var/spool/postfix/plesk-pop/poplock(0,lock|fold_fix) has changed -- restarting

Sep 18 14:37:58 jedi postfix/smtpd[56368]: table hash:/var/spool/postfix/plesk-pop/poplock(0,lock|fold_fix) has changed -- restarting

Is that normal?
Thanks, -t

 

[AndreiW]

Same thing
Nov 9 18:58:17 mail postfix/smtpd[1401]: table hash:/var/spool/postfix/plesk-pop/poplock(0,lock|fold_fix) has changed -- restarting
Nov 9 18:58:17 mail postfix/smtpd[1400]: table hash:/var/spool/postfix/plesk-pop/poplock(0,lock|fold_fix) has changed -- restarting
Nov 9 18:58:17 mail postfix/smtpd[1441]: table hash:/var/spool/postfix/plesk-pop/poplock(0,lock|fold_fix) has changed -- restarting
Nov 9 18:58:17 mail postfix/smtpd[1415]: table hash:/var/spool/postfix/plesk-pop/poplock(0,lock|fold_fix) has changed -- restarting

What does this means?!

 

[Monty]

That's normal behaviour: You seem to have enabled "POP3 before SMTP" in the mail server settings of your server. So Plesk stores the IP/username in the pop-lock database file to allow relaying for this user/IP for a certain time (specified by the "timeout" value in the mail server settings).

Postfix automatically detects changes to hash tables (such as poplock.db) and will restart the processes accessing those files to load the new data of the hash table.

So those messages are nothing to worry about, it's expected behaviour.