I noticed my log was around 71% full so I had a look at my log and it is full of the following:

 

Quote

 

Oct 10 19:39:24 Tower smbd[22739]: [2022/10/10 19:39:24.277133, 0] ../../libcli/smb/smb2_signing.c:722(smb2_signing_check_pdu)

Oct 10 19:39:24 Tower smbd[22739]: Bad SMB2 (sign_algo_id=1) signature for message

Oct 10 19:39:24 Tower smbd[22739]: [2022/10/10 19:39:24.277162, 0] ../../lib/util/util.c:571(dump_data) Oct 10 19:39:24 Tower smbd[22739]: [0000] C9 01 01 33 D9 58 2D 58 9F 63 3C 18 A9 5A 40 1E ...3.X-X .c<..Z@.

Oct 10 19:39:24 Tower smbd[22739]: [2022/10/10 19:39:24.277188, 0] ../../lib/util/util.c:571(dump_data) Oct 10 19:39:24 Tower smbd[22739]: [0000] F0 8D F8 FF 0E 34 BF 31 7E 4B 9E 59 1B A7 D4 F0 .....4.1 ~K.Y....

 

 

I'm attaching my diagnostics file.

 

I understand it has something to do with SAMBA.

 

I have stopped the array and started it and it's no longer happening.

 

What can I do about it?

 

Thanks

tower-diagnostics-20221010-2009.zip

Problem started a couple of days after the server was first booted, if it starts again try to see if it coincides with some device accessing the server.