[2.3] Packaging doesn't remove /dev/shm/squid-cf__metadata.shm

Bug #1734980 reported by Andres Rodriguez on 2017-11-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
Andres Rodriguez

Bug Description

Not removing /dev/shm/squid-cf__metadata.shm means that if we install the snap right after removing the debian package, the snap will fail to launch squid.

Changed in maas:
milestone: none → 2.4.x
Andres Rodriguez (andreserl) wrote :

14:05 < tyhicks> roaksoax: I can verify that at least the `apt autoremove --purge maas` command in your paste doesn't remove the /dev/shm/squid-cf__metadata.shm
                 file
14:06 < tyhicks> mode 600, owner proxy:proxy
14:12 < tyhicks> roaksoax: `chmod a+rw /dev/shm/squid*.shm` "fixes" the errors and allows the squid proxy to start
14:13 < tyhicks> roaksoax: the squid proxy from the snap is running as the 'nobody' user, which is why it can't open the shared memory files left behind by the
                 deb (mode 600, owner proxy:proxy)
14:13 < tyhicks> roaksoax: imo, the bug is in the deb not removing those files upon purge
14:14 < tyhicks> jdstrand: ^ thanks for throwing out that idea

Changed in maas:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Andres Rodriguez (andreserl)
Andres Rodriguez (andreserl) wrote :

I'm unable to reproduce this issue. It may have been related to the OS itself.

Changed in maas:
status: Triaged → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers