Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I have email notifications configured for cron jobs and unattended-upgrades on my server. Everything was working as expected for years.
However, for some reason today I started receiving hourly emails titled Cron <root@myserver> cd / && run-parts --report /etc/cron.hourly with the contents like this:
/etc/cron.hourly/droplet-agent:
Waiting 608 seconds
Checking architecture support...OK
Preparing to check for update
Package Host: [https://repos-droplet.digitalocean.com](https://repos-droplet.digitalocean.com/)
Package Path: apt/droplet-agent/pool/main/main/d/droplet-agent/droplet-agent_
Keyring Path: apt/droplet-agent/pool/main/main/d/droplet-agent-keyring/droplet-agent-keyring_
Local Keyring:2.0.0
Local Version:1.2.12
Checking Latest Version...
Latest keyring package:2.0.0
Latest agent package:1.2.12
No need to update
Before today, I only received email notifications when the droplet-agent job failed:
run-parts: /etc/cron.hourly/droplet-agent exited with return code 100
The latest unattended upgrade was performed yesterday, however the only updated package seems to be distro-info-data, so it’s not clear to me how could this update cause a change in behavior for crontab and email notifications.
Any ideas what could have caused this change?
hashembarret@gmail.com
Witomir Łękowski
doug.landau
5350d4b31109448dbeb34a6ffc857a
max johnson
rem3n
bo
d.mckinstry
Jim Cason
Charles kubai
Charles kubai
a8873f4302264068ba1fb130bccff6