Re: Syslog/Rsyslog/Systemctl issue

[debian@sioban.net]

Le 31/01/2023 à 19:29, Greg Wooledge a écrit :

> > Requires=syslog.socket
> >       
> This is the only part of it that looks like a "dependency".  Maybe
> this is the thing that's breaking?  You can try
> "systemctl status syslog.socket" and see if it gives anything useful.
>     
    Here is the result:
    
    ❯ systemctl status syslog.socket
    ● syslog.socket - Syslog Socket
         Loaded: loaded (/lib/systemd/system/syslog.socket; static)
         Active: failed (Result: resources)
       Triggers: ● rsyslog.service
           Docs: man:systemd.special(7)
                
    https://www.freedesktop.org/wiki/Software/systemd/syslog
         Listen: /run/systemd/journal/syslog (Datagram)
    
    And same for cat:
    
    ❯ systemctl cat syslog.socket
    # /lib/systemd/system/syslog.socket
    #  SPDX-License-Identifier: LGPL-2.1-or-later
    #
    #  This file is part of systemd.
    #
    #  systemd is free software; you can redistribute it and/or modify
    it
    #  under the terms of the GNU Lesser General Public License as
    published by
    #  the Free Software Foundation; either version 2.1 of the License,
    or
    #  (at your option) any later version.
    
    [Unit]
    Description=Syslog Socket
    Documentation=man:systemd.special(7)
Documentation=https://www.freedesktop.org/wiki/Software/systemd/syslog
    DefaultDependencies=no
    Before=sockets.target
    
    # Don't allow logging until the very end
    Conflicts=shutdown.target
    Before=shutdown.target
    
    # Don't try to activate syslog.service if sysinit.target has failed.
    Conflicts=emergency.service
    Before=emergency.service
    
    [Socket]
    ListenDatagram=/run/systemd/journal/syslog
    SocketMode=0666
    PassCredentials=yes
    PassSecurity=yes
    ReceiveBuffer=8M
    
    # The default syslog implementation should make syslog.service a
    # symlink to itself, so that this socket activates the right actual
    # syslog service.
    #
    # Examples:
    #
    # /etc/systemd/system/syslog.service ->
    /lib/systemd/system/rsyslog.service
    # /etc/systemd/system/syslog.service ->
    /lib/systemd/system/syslog-ng.service
    #
    # Best way to achieve that is by adding this to your unit file
    # (i.e. to rsyslog.service or syslog-ng.service):
    #
    # [Install]
    # Alias=syslog.service
    #
    # See https://www.freedesktop.org/wiki/Software/systemd/syslog for
    details.
    
    
    And trying to start it:
    ❯ systemctl start syslog.socket
    Job failed. See "journalctl -xe" for details.
    
    Nothing in journalctl, and nothings in any logs related to this
    issue at this specific time
    
> > I'm pretty sure the issue is not with Rsyslog, but with another service that
> > cannot start preventing rsyslog to start through systemctl (a dependency).
> > Starting Rsyslog by hand is just fine.
> >       
> How did you do that?  "By hand" can mean a lot of different things.
>
>     
    
    As root: "/usr/sbin/rsyslogd -i /run/rsyslogd.pid"
    
    I know it's not the best but I was hoping to see things in the logs
    related to the issues :/