if squid-deb-proxy is OOM-killed, it's not started back up

Bug #1900474 reported by Junien F
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu Repository Cache Charm
Triaged
Medium
Unassigned

Bug Description

Hi,

Seen this last weekend : squid-deb-proxy got OOM killed, and systemd didn't bring it back up.
As a matter of fact, I had to "systemctl stop" / "systemctl start" to start it back up.

I think the charm should configure squid-deb-proxy to be restarted upon kill.

Thanks

Related branches

Tom Haddon (mthaddon)
Changed in ubuntu-repository-cache:
status: New → Confirmed
importance: Undecided → Medium
Haw Loeung (hloeung)
Changed in ubuntu-repository-cache:
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.