[SAC] [OSGeo] #2900: scping to upload.osgeo.org seems to be timing out

#2900: scping to upload.osgeo.org seems to be timing out
---------------------------+--------------------------------------
Reporter: robe | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2023-I
Component: Systems Admin | Keywords:
---------------------------+--------------------------------------

--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2900&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#2900: scping to upload.osgeo.org seems to be timing out
---------------------------+---------------------------------------
Reporter: robe | Owner: sac@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2023-I
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+---------------------------------------
Comment (by robe):

Issue seems to be with the systemd-logind.service.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2900#comment:1&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2900: scping to upload.osgeo.org seems to be timing out
---------------------------+---------------------------------------
Reporter: robe | Owner: sac@…
     Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2023-I
Component: Systems Admin | Resolution: fixed
Keywords: |
---------------------------+---------------------------------------
Changes (by robe):

* status: new => closed
* resolution: => fixed

Comment:

I ended up making the same change as I had done to grass.
Namely disabling or masking all these services that couldn't start

{{{
systemctl disable binfmt-support.service
systemctl disable systemd-networkd-wait-online.service
systemctl disable systemd-journald-audit.socket
systemctl mask modprobe@drm.service
systemctl mask systemd-logind.service
systemctl disable systemd-networkd.service
systemctl disable systemd-resolved.service
systemctl mask systemd-journald-audit.socket
systemctl disable systemd-networkd.socket
}}}

The binfmt-support one didn't seem to be running at all. So I think its
maybe something that got upgraded and lxc is just blocking these cause
they aren't needed for containers, but since sshd relied on at least
systemd-logind seemed like it was waiting for it to start before ignoring
it.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2900#comment:2&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

#2900: scping to upload.osgeo.org seems to be timing out
---------------------------+---------------------------------------
Reporter: robe | Owner: sac@…
     Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2023-I
Component: Systems Admin | Resolution: fixed
Keywords: |
---------------------------+---------------------------------------
Comment (by robe):

I'm assuming this is some resent change on bullseye.

hop3.osgeo.org doesn't have the issue, but then I noticed, I must have
missed updating that one to bullseye (still on buster).

osgeo4, osgeo9 all had the issue

running

{{{
sudo systemctl list-units --failed
}}}

on them showed the same stopped services and running the above fixed them.

strangely osgeo8 seems fine. No failed service and it is running
bullseye. But I suspect maybe as part of my bullseye image, I had
disabled all of these because all these services are already disabled on
it and I had this slowness issue before when upgrading busters.

I thought I had build osgeo9 from the same image, but looks like that was
built from my old debian buster hop image and osgeo8 hop is the only one
that freshly started as bullseye.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2900#comment:3&gt;
OSGeo <https://osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.