[SAC] [OSGeo] #2964: grasswiki and grass logrotates still broken

[OSGeo]

#2964: grasswiki and grass logrotates still broken
---------------------------+---------------------------------------
 Reporter:  robe           |       Owner:  sac@…
     Type:  defect         |      Status:  new
 Priority:  normal         |   Milestone:  Sysadmin Contract 2023-I
Component:  Systems Admin  |  Resolution:
 Keywords:                 |
---------------------------+---------------------------------------
Comment (by robe):

 Yah has to do with the security.

 I relaxed the security with


 {{{
 lxc config set grass security.nesting=true
 }}}

 and after that was able to start up the logrotate service
 and was able to set that back to false and still restart logrotate.

 But even though in restarting it starts fine, it still has


 {{{
 ls -la /run/systemd/unit-root/proc
 ls: cannot access '/run/systemd/unit-root/proc': No such file or directory
 }}}

 if I check or perhaps that's only needed when it's in process of a
 logrotate.

 I'll keep this ticket open to see if it shuts down again.

 Regarding these issues, I had simialr when upgrading the host to 22.04
 something to do with
 cgroup2 hierarchy not properly set with moving from 20.04 to 22.04, thou
 as dicussed here https://discuss.linuxcontainers.org/t/2nd-system-
 upgraded-from-ubuntu-20-04-w-working-lxd-to-ubuntu-22-04-lxd-again-not-
 working/14009/29 but those were more serious with the containers not even
 restarting and not being able to create older containers like centos 7.

 but this might be some dangling left over from that.

 Speaking of which -- you want to upgrade to bookworm :).  Peertube I
 upgraded last week to bookworm seems to be doing fine logrotate working
-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2964#comment:5>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.