Facebook
TwitterHi there
We have noticed on a few servers this entry in the action log
127.0.0.1 admin [2020-04-15 12:56:03] 'Update IP Address' ('Interface': 'eth0' => 'eth0', 'IP Address': 'xxx.xxx.xxx.xxx' => 'xxx.xxx.xxx.xxx', 'IP Mask': '255.255.255.0' => '255.255.255.0')
the time (in this case ever 56th minute) corresponds to this cron
56 4 * * * /opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/letsencrypt/scripts/keep-secured.php'
Every time it runs it restarts nginx
In this case killing a cron job that the client has running.
While we can work around this it seems very intrusive behaviour to restart nginx once an hour for any reason?
What is going on here? Is there a way around this other than disabling the cron and the functionality it provides.
A quick checks shows other servers with the same problem However, some servers with the same set up do not.
Let's Encrypt
Version
2.9.0-611
We have noticed on a few servers this entry in the action log
127.0.0.1 admin [2020-04-15 12:56:03] 'Update IP Address' ('Interface': 'eth0' => 'eth0', 'IP Address': 'xxx.xxx.xxx.xxx' => 'xxx.xxx.xxx.xxx', 'IP Mask': '255.255.255.0' => '255.255.255.0')
the time (in this case ever 56th minute) corresponds to this cron
56 4 * * * /opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/letsencrypt/scripts/keep-secured.php'
Every time it runs it restarts nginx
In this case killing a cron job that the client has running.
While we can work around this it seems very intrusive behaviour to restart nginx once an hour for any reason?
What is going on here? Is there a way around this other than disabling the cron and the functionality it provides.
A quick checks shows other servers with the same problem However, some servers with the same set up do not.
Let's Encrypt
Version
2.9.0-611
| OS | Ubuntu 16.04.6 LTS |
| Product | Plesk Obsidian Version 18.0.20 Update #3, last updated on April 16, 2020 01:08 AM |
