Syslog socket fails

Both syslog and rsyslog are running, but both of them are triggered by
syslog.socket which is not running, and fails to start either on boot
or manually.

It complains

syslog.socket: Socket service rsyslog.service already active, refusing.

I've searched for a couple of hours now and can't find anything on
this.

How can I get the socket running?

Mark
Fedora 37 (Server Edition)

[Garry T. Williams]

On Saturday, February 4, 2023 11:40:41 AM EST Mark @ GMail wrote:
>  Both syslog and rsyslog are running, but both of them are triggered
> by
>  syslog.socket which is not running, and fails to start either on boot
>  or manually.
>
>  It complains
>
>  syslog.socket: Socket service rsyslog.service already active, refusing. 
I don't run any syslog daemon -- I just use the system journal.  But I
suspect that if rsyslog is active (running), then there is no way to
obtain the socket that it is using.  I do not know why you want to do
such a thing, if the daemon is already running.

-- 
Garry T. Williams

On Sat, 2023-02-04 at 21:59 -0500, Garry T. Williams wrote:
>  I don't run any syslog daemon -- I just use the system journal. 
> But
>  I
>  suspect that if rsyslog is active (running), then there is no way to
>  obtain the socket that it is using.  I do not know why you want to do
>  such a thing, if the daemon is already running.
>  
>  -- 
>  Garry T. Williams 
Hmm, of course, you're right.  Once I stopped syslog (rsyslog stopped
as a result, I think I read somewhere it's just a link) then I could
start the socket, brilliant!

Of course, now the question is how to start the socket before the
syslog itself during boot?

Why do I want it to run at all?  I want to receive the log from my home
router.

Mark