From: robin_listas@es.invalid   
      
   On 2025-12-30 20:14, Lawrence D’Oliveiro wrote:   
   > On Mon, 29 Dec 2025 03:49:05 -0000 (UTC), I wrote:   
   >   
   >> On Mon, 29 Dec 2025 03:16:27 +0100, Carlos E.R. wrote:   
   >>   
   >>> Dec 14 22:02:17 Telcontar systemd[1]: smb.service: Failed with result   
   'exit-code'.   
   >>   
   >> OK, I tried introducing a config error into my own Samba setup, and   
   >> got similar results to you: I was expecting smb{,d}.service to log   
   >> errors parsing the configuration, but it does not.   
   >>   
   >> And I can’t see any obvious setting in smb.conf to tell it to do so.   
   >>   
   >> Just to be clear, this is a Samba shortcoming.   
   >   
   > I figured it out: Samba does log these errors, and you’ll find them in   
   > /var/log/samba/log.smbd.   
      
   Didn't remember about that file, but nope, no dice:   
      
      
   [2024/02/08 19:39:06.207301,  1] ../../source3/smbd/process.c:56   
   (receive_smb_talloc)   
      receive_smb_raw_talloc failed for client ptr=0x55b4d13380e0,i   
   =1,addr=ipv4:192.168.1.2:2009 read error = NT_STATUS_CONNECTION_RESET.   
   [2025/12/19 13:33:23.158495,  0] ../../source3/smbd/server.c:1748(main)   
      smbd version 4.19.9-git.435.78ced6cf30d150600.3.21.1SUSE-oS15.0-x86_64   
   started.   
      Copyright Andrew Tridgell and the Samba Team 1992-2023   
      
   You see, the file stopped logging 10 months ago, so no data. It started   
   working again when ChatGPT helped me to refine and update the configuration   
   file.   
      
      
   --   
   Cheers, Carlos.   
   ES🇪🇸, EU🇪🇺;   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)