apt - mail spam
Closed, MigratedEdits Locked
Actions

Assigned To

Authored By

	zack
	Jan 3 2019, 10:38 AM

Description

the cron in question is spam-my for at least a couple of reasons:

apt.cache.LockFailedException: Failed to lock /var/lib/apt/lists/lock
apt.cache.FetchFailedException: E:The repository 'https://enterprise.proxmox.com/debian/pve stretch Release' does not have a

Release file.

neither seems to warrant a dedicated email

Related Objects

Mentioned Here: rSPSITE0a6dd89020a7: Let the apt prometheus script go through even if the cache update failed

Event Timeline

zack triaged this task as High priority.Jan 3 2019, 10:38 AM

zack created this task.

The first one was already fixed in puppet, it was just not applied on prado.

I've applied rSPSITE0a6dd890 to always be silent, and only report a prometheus metric that indicates whether the cache update failed. This should cut down the mails to actual error conditions.

This task has been migrated to GitLab.

Cron <root@prado> chronic /var/lib/prometheus/node-exporter-scripts/apt - mail spamClosed, MigratedEdits LockedActions

Description

Related Objects

Event Timeline

Cron <root@prado> chronic /var/lib/prometheus/node-exporter-scripts/apt - mail spam
Closed, MigratedEdits Locked
Actions