if squid-deb-proxy is OOM-killed, it's not started back up
Bug #1900474 reported by
Junien F
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
lp:~tcuthbert/ubuntu-repository-cache/squid-mem-max
Rejected
for merging
into
lp:ubuntu-repository-cache
- Haw Loeung: Disapprove
- Canonical IS Reviewers: Pending requested
-
Diff: 167 lines (+106/-0)4 files modifiedconfig.yaml (+18/-0)
lib/ubuntu_repository_cache/squid.py (+51/-0)
lib/ubuntu_repository_cache/util.py (+29/-0)
templates/squid-deb-proxy.service.d/squid-deb-proxy.conf (+8/-0)
lp:~tcuthbert/ubuntu-repository-cache/squid-mem-qos
Rejected
for merging
into
lp:ubuntu-repository-cache
- Ubuntu Repository Cache Charmers, Canonical: Pending requested
-
Diff: 227 lines (+148/-1)5 files modifiedconfig.yaml (+18/-0)
lib/ubuntu_repository_cache/service.py (+1/-0)
lib/ubuntu_repository_cache/squid.py (+69/-1)
lib/ubuntu_repository_cache/util.py (+52/-0)
templates/squid-deb-proxy.service.d/squid-deb-proxy.conf (+8/-0)
~tcuthbert/ubuntu-repository-cache:squid-systemd.resource-control
Rejected
for merging
into
ubuntu-repository-cache:master
- James Simpson: Needs Fixing
- Canonical IS Reviewers: Pending requested
-
Diff: 224 lines (+141/-2)4 files modifiedconfig.yaml (+18/-0)
reactive/ubuntu_repository_cache.py (+42/-1)
templates/systemd/squid-deb-proxy.service.d/memory-override.conf (+9/-0)
tests/unit/test_ubuntu_repository_cache.py (+72/-1)
Changed in ubuntu-repository-cache: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in ubuntu-repository-cache: | |
status: | Confirmed → Triaged |
To post a comment you must log in.