That's right, it's always just over two minutes. Thanks for your help. What's the process going forward? Is the request being looked at further from this point? We need it operational for tomorrow. Shall we revert to 4.16 for now? On Mon, Jan 2, 2023 at 1:03 PM Rowland Penny via samba < samba at lists.samba.org> wrote:> > > On 02/01/2023 11:02, Max Serafini via samba wrote: > > Apologies if I annoyed you, in business it is common practice to reply to > > everyone in the thread. > > No, it didn't annoy me, it just breaks the thread, instead of appearing > in my 'samba mailing list' folder, your replies end up in my inbox and I > have to manually move them to the samba mailing list folder. It is > further compounded by having to enter the mailing list address when I > reply to list. > > > Here are the files. > > > > > https://drive.google.com/drive/folders/1GIE0npEovJhuMKGdRFY14u3nJ_TszFOO?usp=share_link > > > > > > You appear to be losing two minutes, as shown in log.smbd: > > [2023/01/02 04:49:23.236086, 5] > ../../source3/rpc_server/srv_pipe_hnd.c:138(np_write_send) > np_write_send: len: 2170 > [2023/01/02 04:49:23.658523, 0] > ../../source3/smbd/smb2_server.c:671(smb2_validate_sequence_number) > smb2_validate_sequence_number: smb2_validate_sequence_number: bad > message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) > [2023/01/02 04:50:25.348121, 0] > ../../source3/smbd/smb2_server.c:671(smb2_validate_sequence_number) > smb2_validate_sequence_number: smb2_validate_sequence_number: bad > message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) > [2023/01/02 04:51:27.624487, 5] > ../../source3/rpc_server/srv_pipe_hnd.c:138(np_write_send) > np_write_send: len: 2170 > > The time starts at 04:49:23 and ends at 04:51:27 > Tracing this back in code, appears to point to protocol negotiation, > though I could be wrong. > > Why this is happening, wiser heads than myself will have to comment. > > Rowland > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
Hi Max,> Op 2 jan. 2023 om 13:38 heeft Max Serafini via samba <samba at lists.samba.org> het volgende geschreven: > > ?That's right, it's always just over two minutes.Is any 2-minute timeout configured?> Thanks for your help. What's the process going forward? Is the request > being looked at further from this point?This is not a request, this is a mailing list thread.> We need it operational for tomorrow.If you need SLAs, get commercial support.> Shall we revert to 4.16 for now? > >> On Mon, Jan 2, 2023 at 1:03 PM Rowland Penny via samba < >> samba at lists.samba.org> wrote: >> >> >> >>> On 02/01/2023 11:02, Max Serafini via samba wrote: >>> Apologies if I annoyed you, in business it is common practice to reply to >>> everyone in the thread. >> >> No, it didn't annoy me, it just breaks the thread, instead of appearing >> in my 'samba mailing list' folder, your replies end up in my inbox and I >> have to manually move them to the samba mailing list folder. It is >> further compounded by having to enter the mailing list address when I >> reply to list. >> >>> Here are the files. >>> >>> >> https://drive.google.com/drive/folders/1GIE0npEovJhuMKGdRFY14u3nJ_TszFOO?usp=share_link >>> >>> >> >> You appear to be losing two minutes, as shown in log.smbd: >> >> [2023/01/02 04:49:23.236086, 5] >> ../../source3/rpc_server/srv_pipe_hnd.c:138(np_write_send) >> np_write_send: len: 2170 >> [2023/01/02 04:49:23.658523, 0] >> ../../source3/smbd/smb2_server.c:671(smb2_validate_sequence_number) >> smb2_validate_sequence_number: smb2_validate_sequence_number: bad >> message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) >> [2023/01/02 04:50:25.348121, 0] >> ../../source3/smbd/smb2_server.c:671(smb2_validate_sequence_number) >> smb2_validate_sequence_number: smb2_validate_sequence_number: bad >> message_id 2 (sequence id 2) (granted = 1, low = 1, range = 1) >> [2023/01/02 04:51:27.624487, 5] >> ../../source3/rpc_server/srv_pipe_hnd.c:138(np_write_send) >> np_write_send: len: 2170 >> >> The time starts at 04:49:23 and ends at 04:51:27 >> Tracing this back in code, appears to point to protocol negotiation, >> though I could be wrong. >> >> Why this is happening, wiser heads than myself will have to comment. >> >> Rowland >> >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba >> > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
On 02/01/2023 12:35, Max Serafini via samba wrote:> That's right, it's always just over two minutes. > Thanks for your help. What's the process going forward? Is the request > being looked at further from this point? > We need it operational for tomorrow. Shall we revert to 4.16 for now? > >If you require this tomorrow, then I suggest you revert to 4.16.x If you want this to be looked at further than this mailing list, then you will need to file a bug report. Rowland