-
Notifications
You must be signed in to change notification settings - Fork 106
Open
Description
We have five or so droplets, all of which started generating an email from a failure of /etc/cron.hourly/droplet-agent. As far as I can tell, this just checks to see if it should be updated. The emails don't contain much interesting - just the output from the job if I run it on the command line:
/etc/cron.hourly/droplet-agent:
Waiting 596 seconds
Checking architecture support...OK
Preparing to check for update
Package Host: 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
The question is - why did this start generating emails from the hourly run? Was the agent changed to produce output?
Our droplets are running debian 12.
bern-spl, jacopo-j, uxmaster and elanghout
Metadata
Metadata
Assignees
Labels
No labels