You are not logged in.

#1 2022-01-09 11:16:24

Beesh
Member
Registered: 2022-01-09
Posts: 4

[Solved] Samba error at service start

I have this lines printed to journal as error level at each service start, how can I solve?

[2022/01/09 09:50:11.166671,  0] ../../source3/smbd/server.c:1739(main)
  smbd version 4.15.3 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2021

Last edited by Beesh (2022-01-09 16:38:56)

Offline

#2 2022-01-09 16:15:44

hortimech
Member
Registered: 2020-10-09
Posts: 9

Re: [Solved] Samba error at service start

That isn't an error, it is just smbd announcing that it has started.

Offline

#3 2022-01-09 16:21:03

Beesh
Member
Registered: 2022-01-09
Posts: 4

Re: [Solved] Samba error at service start

that's what I tought but I don't want it do be classified as error level in the journal, but as info, as every package do normally. I thinks that's some bug from the latest version and probably it will be addressed in the next update; but if that's not the case how can I disable this announce without disabling all the error level logs from samba's systemd service?

Last edited by Beesh (2022-01-09 16:24:28)

Offline

#4 2022-01-09 16:35:03

seth
Member
Registered: 2012-09-03
Posts: 26,570

Re: [Solved] Samba error at service start

Don't log into the systemd journal - the startup message logs at level 0 for > 12 years, I don't expect that to change anywhen soon.

Offline

#5 2022-01-09 16:38:36

Beesh
Member
Registered: 2022-01-09
Posts: 4

Re: [Solved] Samba error at service start

seth wrote:

Don't log into the systemd journal - the startup message logs at level 0 for > 12 years, I don't expect that to change anywhen soon.

thank you for this insight, it seems that I was lacking crucial informations. At this point I think that's something that popped up with the big systemd 250 update. Will check out that way, thank you again for helping me!

Offline

#6 2022-01-14 15:22:11

Beesh
Member
Registered: 2022-01-09
Posts: 4

Re: [Solved] Samba error at service start

follow up: I wasn't be able to fix that log, and only that log, to not show up in the journal as error so I recompiled the samba source code after modifying the code

/source3/smbd/server.c at line 1739 and 1740 from
        DEBUG(0,("smbd version %s started.\n", samba_version_string()));
        DEBUGADD(0,("%s\n", COPYRIGHT_STARTUP_MESSAGE));

to

        DEBUG(1,("smbd version %s started.\n", samba_version_string()));
        DEBUGADD(1,("%s\n", COPYRIGHT_STARTUP_MESSAGE));

this obviously fixed I wonder why that horror code is still in place for so long

Last edited by Beesh (2022-01-14 15:25:04)

Offline

Board footer

Powered by FluxBB