samba - Sep 2019 - Issue after upgrade to samba-client-4.9.1-6.el7.x86_64 - Unable to initialize messaging context

Hi All,

First time poster. Not a unix pro.

We had samba client installed (v. 3.6)  and working to run a single file print
command.

smbclient --debuglevel=1 --log-basename=/mnt/autofs/logs/print/  -U
bbldtl\\adminuser //$3/$2  'obscured-password'  --command "print
$1" | tee -a /mnt/autofs/logs/print/print.log

It would output

[2019/07/04 04:27:36,  0] libsmb/clidfs.c:232(do_connect)
  Domain=[BBLDTL] OS=[Windows Server 2012 R2 Standard 9600] Server=[Windows
Server 2012 R2 Standard 6.3]
[2019/07/04 04:27:36,  1] client/client.c:1883(do_put)
  putting file /mnt/autofs/output/bin/Default/j8989s2bdefault.ps as
j8989s2bdefault.ps-11430 (546.7 kb/s) (average 546.7 kb/s)


Now after upgrade of our Linux environment
"redhatVersion": "Red Hat Enterprise Linux Server release 7.7
(Maipo)",
            "tomcatVersion": "7.0.93",
and Samba to 4.9.1
it now only logs

            Unable to initialize messaging context



Any pointers on where / how to investigate this?

Thanks



Stephen Black   I  Collaboration Squad  I  Technology and Business Enablement
Bendigo and Adelaide Bank<http://www.bendigoadelaidebank.com.au/> I P: 03
5485 6855  I  E: stephen.black at bendigoadelaide.com.au<mailto:stephen.black
at bendigoadelaide.com.au>





********************************************************************************

This communication is intended only for use of the addressee and may contain
legally privileged and confidential information.
If you are not the addressee or intended recipient, you are notified that any
dissemination, copying or use of any of the information is unauthorised.

The legal privilege and confidentiality attached to this e-mail is not waived,
lost or destroyed by reason of a mistaken delivery to you.
If you have received this message in error, we would appreciate an immediate
notification via e-mail to ContactUs at bendigoadelaide.com.au or by phoning
1300 BENDIGO (1300 236 344), and ask that the e-mail be permanently deleted from
your system.

Bendigo and Adelaide Bank Limited ABN 11 068 049 178

********************************************************************************

On 17/09/2019 00:37, Stephen Black via samba wrote:
> Hi All,
>
> First time poster. Not a unix pro.
>
> We had samba client installed (v. 3.6)  and working to run a single file
print command.
>
> smbclient --debuglevel=1 --log-basename=/mnt/autofs/logs/print/  -U
bbldtl\\adminuser //$3/$2  'obscured-password'  --command "print
$1" | tee -a /mnt/autofs/logs/print/print.log
>
> It would output
>
> [2019/07/04 04:27:36,  0] libsmb/clidfs.c:232(do_connect)
>    Domain=[BBLDTL] OS=[Windows Server 2012 R2 Standard 9600]
Server=[Windows Server 2012 R2 Standard 6.3]
> [2019/07/04 04:27:36,  1] client/client.c:1883(do_put)
>    putting file /mnt/autofs/output/bin/Default/j8989s2bdefault.ps as
j8989s2bdefault.ps-11430 (546.7 kb/s) (average 546.7 kb/s)
>
>
> Now after upgrade of our Linux environment
> "redhatVersion": "Red Hat Enterprise Linux Server release
7.7 (Maipo)",
>              "tomcatVersion": "7.0.93",
> and Samba to 4.9.1
> it now only logs
>
>              Unable to initialize messaging context
>
>
>
> Any pointers on where / how to investigate this?
Can you post your smb.conf

Rowland

On 17/09/2019 23:35, Stephen Black wrote:
> Done.
And for those that didn't get the smb.conf

[global]
 ??? workgroup = SAMBA
 ??? security = user

 ??? passdb backend = tdbsam

 ??? printing = cups
 ??? printcap name = cups
 ??? load printers = yes
 ??? cups options = raw

[homes]
 ??? comment = Home Directories
 ??? valid users = %S, %D%w%S
 ??? browseable = No
 ??? read only = No
 ??? inherit acls = Yes

[printers]
 ??? comment = All Printers
 ??? path = /var/tmp
 ??? printable = Yes
 ??? create mask = 0600
 ??? browseable = No

[print$]
 ??? comment = Printer Drivers
 ??? path = /var/lib/samba/drivers
 ??? write list = @printadmin root
 ??? force group = @printadmin
 ??? create mask = 0664
 ??? directory mask = 0775

You are running Samba as a standalone server.

I think your problem is that on 3.6, it was 'ntlm auth = yes', this 
changed to 'ntlm auth = no' at 4.7.0 and then again to 'ntlm auth = 
ntlmv2-only' at 4.7.0

To test this, add 'ntlm auth = yes' to your smb.conf, if this works, I 
would find out how to turn off SMBv1 on your Windows server.

Rowland