Ciao a tutti, ho appena aggiornato un serverino a bookwarm e il logon è lentissimo, se lancio un reboot non funziona... in syslog trovo qualcosa
tipo:

2023-07-17T09:48:41.313220+02:00 addressbook systemd[1]: Failed to start systemd-logind.service - User Login Management.

ed in effetti:

# systemctl status systemd-logind.service
× systemd-logind.service - User Login Management
     Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
     Active: failed (Result: exit-code) since Mon 2023-07-17 09:48:41 CEST; 3min 55s ago
       Docs: man:sd-login(3)
             man:systemd-logind.service(8)
             man:logind.conf(5)
             man:org.freedesktop.login1(5)
    Process: 422 ExecStart=/lib/systemd/systemd-logind (code=exited, status=226/NAMESPACE)
   Main PID: 422 (code=exited, status=226/NAMESPACE)
        CPU: 13ms

Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service:
Scheduled restart job, restart counter is at 5.
Jul 17 09:48:41 addressbook systemd[1]: Stopped systemd-logind.service -
User Login Management.
Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service: Start
request repeated too quickly.
Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service: Failed
with result 'exit-code'.
Jul 17 09:48:41 addressbook systemd[1]: Failed to start
systemd-logind.service - User Login Management.

Qualcuno ha qualche idea?

Piviul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

mi sono anche accorto anche che dbus non funziona:

# systemctl status dbus.service
● dbus.service - D-Bus System Message Bus
     Loaded: loaded (/lib/systemd/system/dbus.service; static)
     Active: active (running) since Mon 2023-07-17 09:44:06 CEST; 19min ago
TriggeredBy: ● dbus.socket
       Docs: man:dbus-daemon(1)
   Main PID: 92 (dbus-daemon)
      Tasks: 1 (limit: 619029)
     Memory: 2.3M
        CPU: 26ms
     CGroup: /system.slice/dbus.service
             └─92 /usr/bin/dbus-daemon --system --address=systemd:
--nofork --nopidfile --systemd-activation --syslog-only

Jul 17 09:44:06 addressbook systemd[1]: Starting dbus.service - D-Bus
System Message Bus...
Jul 17 09:44:06 addressbook systemd[1]: Started dbus.service - D-Bus
System Message Bus.
Jul 17 09:45:18 addressbook dbus-daemon[92]: [system] Activating via
systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesk>
Jul 17 09:45:43 addressbook dbus-daemon[92]: [system] Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout>
Jul 17 09:48:41 addressbook dbus-daemon[92]: [system] Activating via
systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesk>
Jul 17 09:49:06 addressbook dbus-daemon[92]: [system] Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout>

e per chiudere il cerchio:

# systemctl status dbus-org.freedesktop.login1.service
× systemd-logind.service - User Login Management
     Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
     Active: failed (Result: exit-code) since Mon 2023-07-17 09:48:41 CEST; 15min ago
       Docs: man:sd-login(3)
             man:systemd-logind.service(8)
             man:logind.conf(5)
             man:org.freedesktop.login1(5)
    Process: 422 ExecStart=/lib/systemd/systemd-logind (code=exited, status=226/NAMESPACE)
   Main PID: 422 (code=exited, status=226/NAMESPACE)
        CPU: 13ms

Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service:
Scheduled restart job, restart counter is at 5.
Jul 17 09:48:41 addressbook systemd[1]: Stopped systemd-logind.service -
User Login Management.
Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service: Start
request repeated too quickly.
Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service: Failed
with result 'exit-code'.
Jul 17 09:48:41 addressbook systemd[1]: Failed to start
systemd-logind.service - User Login Management.

sono informazioni aggiuntive utili? :)

Piviul


On 7/17/23 09:54, Piviul wrote:

Ciao a tutti, ho appena aggiornato un serverino a bookwarm e il logon
è lentissimo, se lancio un reboot non funziona... in syslog trovo
qualcosa tipo:

2023-07-17T09:48:41.313220+02:00 addressbook systemd[1]: Failed to
start systemd-logind.service - User Login Management.

ed in effetti:

# systemctl status systemd-logind.service
× systemd-logind.service - User Login Management
     Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)      Active: failed (Result: exit-code) since Mon 2023-07-17 09:48:41 CEST; 3min 55s ago
       Docs: man:sd-login(3)
             man:systemd-logind.service(8)              man:logind.conf(5)
             man:org.freedesktop.login1(5)
    Process: 422 ExecStart=/lib/systemd/systemd-logind (code=exited, status=226/NAMESPACE)
   Main PID: 422 (code=exited, status=226/NAMESPACE)
        CPU: 13ms

Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service:
Scheduled restart job, restart counter is at 5.
Jul 17 09:48:41 addressbook systemd[1]: Stopped systemd-logind.service
- User Login Management.
Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service: Start
request repeated too quickly.
Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service: Failed
with result 'exit-code'.
Jul 17 09:48:41 addressbook systemd[1]: Failed to start systemd-logind.service - User Login Management.

Qualcuno ha qualche idea?

Piviul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Scusate, ho risolto. Era una macchina virtuale anzi per la precisione un container. Inserendo

features: nesting=1

nel .conf del container e riavviando il problema è andato a posto

grazie e scusate

Piviul


On 7/17/23 10:05, Piviul wrote:

mi sono anche accorto anche che dbus non funziona:

# systemctl status dbus.service
● dbus.service - D-Bus System Message Bus
     Loaded: loaded (/lib/systemd/system/dbus.service; static)
     Active: active (running) since Mon 2023-07-17 09:44:06 CEST;
19min ago
TriggeredBy: ● dbus.socket
       Docs: man:dbus-daemon(1)
   Main PID: 92 (dbus-daemon)
      Tasks: 1 (limit: 619029)
     Memory: 2.3M
        CPU: 26ms
     CGroup: /system.slice/dbus.service
             └─92 /usr/bin/dbus-daemon --system --address=systemd:
--nofork --nopidfile --systemd-activation --syslog-only

Jul 17 09:44:06 addressbook systemd[1]: Starting dbus.service - D-Bus
System Message Bus...
Jul 17 09:44:06 addressbook systemd[1]: Started dbus.service - D-Bus
System Message Bus.
Jul 17 09:45:18 addressbook dbus-daemon[92]: [system] Activating via
systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesk>
Jul 17 09:45:43 addressbook dbus-daemon[92]: [system] Failed to
activate service 'org.freedesktop.login1': timed out
(service_start_timeout>
Jul 17 09:48:41 addressbook dbus-daemon[92]: [system] Activating via
systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesk>
Jul 17 09:49:06 addressbook dbus-daemon[92]: [system] Failed to
activate service 'org.freedesktop.login1': timed out
(service_start_timeout>

e per chiudere il cerchio:

# systemctl status dbus-org.freedesktop.login1.service
× systemd-logind.service - User Login Management
     Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)      Active: failed (Result: exit-code) since Mon 2023-07-17 09:48:41 CEST; 15min ago
       Docs: man:sd-login(3)
             man:systemd-logind.service(8)              man:logind.conf(5)
             man:org.freedesktop.login1(5)
    Process: 422 ExecStart=/lib/systemd/systemd-logind (code=exited, status=226/NAMESPACE)
   Main PID: 422 (code=exited, status=226/NAMESPACE)
        CPU: 13ms

Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service:
Scheduled restart job, restart counter is at 5.
Jul 17 09:48:41 addressbook systemd[1]: Stopped systemd-logind.service
- User Login Management.
Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service: Start
request repeated too quickly.
Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service: Failed
with result 'exit-code'.
Jul 17 09:48:41 addressbook systemd[1]: Failed to start systemd-logind.service - User Login Management.

sono informazioni aggiuntive utili? :)

Piviul

On 7/17/23 09:54, Piviul wrote:

Ciao a tutti, ho appena aggiornato un serverino a bookwarm e il logon
è lentissimo, se lancio un reboot non funziona... in syslog trovo
qualcosa tipo:

2023-07-17T09:48:41.313220+02:00 addressbook systemd[1]: Failed to
start systemd-logind.service - User Login Management.

ed in effetti:

# systemctl status systemd-logind.service
× systemd-logind.service - User Login Management
     Loaded: loaded (/lib/systemd/system/systemd-logind.service; static) >>      Active: failed (Result: exit-code) since Mon 2023-07-17 09:48:41
CEST; 3min 55s ago
       Docs: man:sd-login(3)
             man:systemd-logind.service(8)
             man:logind.conf(5)
             man:org.freedesktop.login1(5)
    Process: 422 ExecStart=/lib/systemd/systemd-logind (code=exited,
status=226/NAMESPACE)
   Main PID: 422 (code=exited, status=226/NAMESPACE)
        CPU: 13ms

Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service:
Scheduled restart job, restart counter is at 5.
Jul 17 09:48:41 addressbook systemd[1]: Stopped
systemd-logind.service - User Login Management.
Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service: Start
request repeated too quickly.
Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service:
Failed with result 'exit-code'.
Jul 17 09:48:41 addressbook systemd[1]: Failed to start
systemd-logind.service - User Login Management.

Qualcuno ha qualche idea?

Piviul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Non ho mai avuto problemi con il servizio di login, Macon altri servizi si.
Ho risolto avviando il servizio manualmente e vedendo l'errore che mi dava. Praticamente ho eseguito da terminale il comando ExetcStar

--
Giancarlo Martini
http://www.giancarlomartini.it
http://www.linkedin.com/in/giancarlo-martini

Il lun 17 lug 2023, 10:12 Piviul <piviul@riminilug.it> ha scritto:

Ciao a tutti, ho appena aggiornato un serverino a bookwarm e il logon è lentissimo, se lancio un reboot non funziona... in syslog trovo qualcosa tipo:

2023-07-17T09:48:41.313220+02:00 addressbook systemd[1]: Failed to start systemd-logind.service - User Login Management.

ed in effetti:

# systemctl status systemd-logind.service
× systemd-logind.service - User Login Management
Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)
Active: failed (Result: exit-code) since Mon 2023-07-17 09:48:41
CEST; 3min 55s ago
Docs: man:sd-login(3)
man:systemd-logind.service(8)
man:logind.conf(5)
man:org.freedesktop.login1(5)
Process: 422 ExecStart=/lib/systemd/systemd-logind (code=exited, status=226/NAMESPACE)
Main PID: 422 (code=exited, status=226/NAMESPACE)
CPU: 13ms

Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service:
Scheduled restart job, restart counter is at 5.
Jul 17 09:48:41 addressbook systemd[1]: Stopped systemd-logind.service -
User Login Management.
Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service: Start
request repeated too quickly.
Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service: Failed
with result 'exit-code'.
Jul 17 09:48:41 addressbook systemd[1]: Failed to start systemd-logind.service - User Login Management.

Qualcuno ha qualche idea?

Piviul

<div dir="auto">Non ho mai avuto problemi con il servizio di login, Macon altri servizi si. Ho risolto avviando il servizio manualmente e vedendo l&#39;errore che mi dava. Praticamente ho eseguito da terminale il comando ExetcStar<br><br><div data-
smartmail="gmail_signature">--<br>Giancarlo Martini<br><a href="http://www.giancarlomartini.it">http://www.giancarlomartini.it</a><br><a href="http://www.linkedin.com/in/giancarlo-martini">http://www.linkedin.com/in/giancarlo-martini</a></div></div><br><
div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il lun 17 lug 2023, 10:12 Piviul &lt;<a href="mailto:piviul@riminilug.it">piviul@riminilug.it</a>&gt; ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #
ccc solid;padding-left:1ex">Ciao a tutti, ho appena aggiornato un serverino a bookwarm e il logon è <br>
lentissimo, se lancio un reboot non funziona... in syslog trovo qualcosa <br> tipo:<br>

2023-07-17T09:48:41.313220+02:00 addressbook systemd[1]: Failed to start <br> systemd-logind.service - User Login Management.<br>

ed in effetti:<br>

# systemctl status systemd-logind.service<br>
× systemd-logind.service - User Login Management<br>
      Loaded: loaded (/lib/systemd/system/systemd-logind.service; static)<br>
      Active: failed (Result: exit-code) since Mon 2023-07-17 09:48:41 <br>
CEST; 3min 55s ago<br>
        Docs: man:sd-login(3)<br>
              man:systemd-logind.service(8)<br>               man:logind.conf(5)<br>
              man:org.freedesktop.login1(5)<br>
     Process: 422 ExecStart=/lib/systemd/systemd-logind (code=exited, <br> status=226/NAMESPACE)<br>
    Main PID: 422 (code=exited, status=226/NAMESPACE)<br>
         CPU: 13ms<br>

Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service: <br>
Scheduled restart job, restart counter is at 5.<br>
Jul 17 09:48:41 addressbook systemd[1]: Stopped systemd-logind.service - <br> User Login Management.<br>
Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service: Start <br> request repeated too quickly.<br>
Jul 17 09:48:41 addressbook systemd[1]: systemd-logind.service: Failed <br> with result &#39;exit-code&#39;.<br>
Jul 17 09:48:41 addressbook systemd[1]: Failed to start <br> systemd-logind.service - User Login Management.<br>

Qualcuno ha qualche idea?<br>

Piviul<br>


</blockquote></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)