Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Paul Smedley

Pages: 1 2 [3] 4 5 ... 140
31
Networking / Re: Updated Samba Client
« on: January 26, 2024, 12:23:33 am »

32
Networking / Re: ArcaMapper and Network Protocols
« on: January 26, 2024, 12:20:52 am »
Try using the IP  instead of paladin

The error suggests paladin is unreachable -  you can ping the server?

33
Networking / Re: Updated Samba Client
« on: January 25, 2024, 10:42:09 pm »
Paul,

No help - log attached, OOM toward the end of 6:16. I never noticed that 'A.+,;=[].B' before, but the log is riddled with it - must be a code error somewhere...

EDIT: tried running the 4.11 server with the 4.19 client (where I do not get the OOM) and I see those 'A.+,;=[].B' in the log all over the place there too.

Regards,

I think this is still the old plugin. The first line reports: Samba client 4.19-1 build 202401xx based on 4.19.4
I changed the build date for this one to 20240125

It's still showing:
Code: [Select]
2024/01/25 06:16:45.02: 9 2: NdpQueryPathInfo smbwrp_getattr for <\A.+,;=[].B>
2024/01/25 06:16:45.02: 4 2: getattr 0 16 <\A.+,;=[].B>
2024/01/25 06:16:45.02: 4 2: smbwrp_getattr, calling cli_qpathinfo3
2024/01/25 06:16:45.02: 9 2: NdpQueryPathInfo smbwrp_getattr, rc = 8

Whereas I would expect to see:
Code: [Select]
2024/01/25 17:49:56.99: 9 2: NdpQueryPathInfo in [0x4928e0] <A.+,;=[].B>
2024/01/25 17:49:56.99: 9 2: NdpQueryPathInfo in [0x4928e0] <A.+,;=[].B> - return ERROR_FILE_NOT_FOUND

Let me also double check that I zipped the right file....

bldlevel on ndpsmb.dll should show:
Description:     NDPSMB - SMBFS NetDrive External Plugin Build 20240125

34
Networking / Re: Updated Samba Client
« on: January 25, 2024, 10:36:22 pm »
must be a code error somewhere...

AFAIR, it's the WPS checking for long file name support. If that file operation produces a specific error, a FAT-like file system is assumed. The WPS will then shorten file names and store the originals in EAs.

Yeah it's definitely a WPS thing....

35
Networking / Re: Samba Users and Groups
« on: January 25, 2024, 10:34:48 pm »
Can you try changing the \ to a /
ie F:/Programs/samba/usermod.cmd

36
Networking / Re: ArcaMapper and Network Protocols
« on: January 25, 2024, 09:26:33 am »
Client logs might help us understand more.

Add to smb.conf:
log level = 8

Create a file in the root of the OS drive - ndpsmb.dbg

Reboot or restart ndctl.exe
try to connect

zip/share x:\var\log\log.ndpsmb & x:\var\log\log.smbc

Once logs are captured - you can reset log level  and remove x:\ndpsmb.dbg

37
Networking / Re: Samba Users and Groups
« on: January 25, 2024, 09:24:22 am »
I don't understand how:
Code: [Select]
sh.exe: 1: F:Programssambausermod.cmd: not foundis being called if my smbpasswd  is being used?

You are running smbpasswd.exe directly from a command line, or via the WPS objects from AOS?

38
Networking / Re: Updated Samba Client
« on: January 25, 2024, 09:22:30 am »
Does  https://smedley.id.au/tmp/ndpsmb-20240125.zip help?  If  it doesn't, can I have a new log.ndpsmb please?

39
Networking / Re: Updated Samba Client
« on: January 25, 2024, 09:01:03 am »
Here's a corresponding log from the client:
Code: [Select]
2024/01/23 09:38:27.27: 9 2: NdpQueryPathInfo in [0x342160] <Music\Pearl Jam\A.+,;=[].B>
2024/01/23 09:38:27.27: 9 2: dircache_find_path [Music\Pearl Jam\A.+,;=[].B]
2024/01/23 09:38:27.27: 9 2: dcFindPath: [Music\Pearl Jam][A.+,;=[].B]
2024/01/23 09:38:27.27: 9 2: dircache: FindPath Music\Pearl Jam\A.+,;=[].B not found
2024/01/23 09:38:27.27: 9 2: NdpQueryPathInfo pathparser for <\A.+,;=[].B> rc=0
2024/01/23 09:38:27.27: 9 2: NdpQueryPathInfo smbwrp_getattr for <\A.+,;=[].B>
2024/01/23 09:38:27.27: 4 2: getattr 0 16 <\A.+,;=[].B>
2024/01/23 09:38:27.27: 4 2: smbwrp_getattr, calling cli_qpathinfo3
2024/01/23 09:38:27.28: 9 2: NdpQueryPathInfo smbwrp_getattr, rc = 2
2024/01/23 09:38:27.28: 9 2: NdpQueryPathInfo <Music\Pearl Jam\A.+,;=[].B> (\A.+,;=[].B) 2
2024/01/23 09:38:27.28: 9 3: NdpQueryPathInfo in [0x317ac0] <Music\Pearl Jam\A.+,;=[].B>
2024/01/23 09:38:27.28: 9 3: dircache_find_path [Music\Pearl Jam\A.+,;=[].B]
2024/01/23 09:38:27.28: 9 3: dcFindPath: [Music\Pearl Jam][A.+,;=[].B]
2024/01/23 09:38:27.28: 9 3: dircache: FindPath Music\Pearl Jam\A.+,;=[].B not found
2024/01/23 09:38:27.28: 9 3: NdpQueryPathInfo pathparser for <\A.+,;=[].B> rc=0
2024/01/23 09:38:27.28: 9 3: NdpQueryPathInfo smbwrp_getattr for <\A.+,;=[].B>
2024/01/23 09:38:27.28: 4 3: getattr 0 16 <\A.+,;=[].B>
2024/01/23 09:38:27.28: 4 3: smbwrp_getattr, calling cli_qpathinfo3
2024/01/23 09:38:27.28: 9 3: NdpQueryPathInfo smbwrp_getattr, rc = 8
2024/01/23 09:38:27.28: 9 3: NdpQueryPathInfo <Music\Pearl Jam\A.+,;=[].B> (\A.+,;=[].B) 3

The WPS seems to try and open 'A.+,;=[].B'  in each folder  and somehow this triggers an OOM error in the server. Interesting....

40
Networking / Re: Updated Samba Client
« on: January 24, 2024, 09:56:43 am »
I should have known about the truncation - sorry about that. Did it again with max log set to 500000 - started at 9:35 and got the OOM at 9:38. I can pretty consistently get it in about 3 minutes now. Attached.

Nice. I'd love to know what steps you follow to reproduce it in 3min - might help me reproduce.

Anyway, turns out maybe  your previous log was sufficient - the first out of memory error looks to be:
Code: [Select]
[2024/01/23 09:38:27.270000, 5] ../../source3/smbd/files.c:1985(file_free)
  file_free: freed files structure 0 (1 used)
[2024/01/23 09:38:27.270000, 5] ../../source3/smbd/files.c:77(fsp_new)
  fsp_new: allocated files structure (2 used)
[2024/01/23 09:38:27.270000, 5] ../../source3/smbd/files.c:179(file_new)
  file_new: new file fnum [invalid value]
[2024/01/23 09:38:27.270000, 5] ../../source3/smbd/files.c:321(openat_internal_dir_from_pathref)
  openat_internal_dir_from_pathref: fd_openat(".", ".") failed: NT_STATUS_NO_MEMORY
[2024/01/23 09:38:27.270000, 5] ../../source3/smbd/files.c:1985(file_free)
  file_free: freed files structure 0 (1 used)
[2024/01/23 09:38:27.270000, 3] ../../source3/smbd/filename.c:319(get_real_filename_full_scan_at)
  get_real_filename_full_scan_at: scan dir didn't open dir [.]: NT_STATUS_NO_MEMORY
[2024/01/23 09:38:27.270000, 5] ../../source3/smbd/files.c:1985(file_free)
  file_free: freed files structure 0 (0 used)
[2024/01/23 09:38:27.270000, 3] ../../source3/smbd/smb2_server.c:4033(smbd_smb2_request_error_ex)
  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_NO_MEMORY] || at ../../source3/smbd/smb2_create.c:360

file_new: new file fnum [invalid value] seems to be a furthy as there are multiple instance of it with no error.

Need to do some  thinking....

41
Networking / Re: Updated Samba Client
« on: January 23, 2024, 08:24:02 am »
OK, I attached 2 zip files - one with server logs and one with client logs with loglevel=8. I started the server and client at 16:28 and got the OOM condition at 16:31. It's  a bummer and surprising you can't easily get it...

Unfortunately, I don't think there is enough of the server log there,  due to the log being truncated at 2mb.  The first entry in the server log is already 16:31...

There are some interesting entries like:
Code: [Select]
[2024/01/22 16:31:11.616000,  5] ../../source3/smbd/files.c:1985(file_free)
  file_free: freed files structure 0 (1 used)
[2024/01/22 16:31:11.616000,  5] ../../source3/smbd/files.c:77(fsp_new)
  fsp_new: allocated files structure (2 used)
[2024/01/22 16:31:11.616000,  5] ../../source3/smbd/files.c:179(file_new)
  file_new: new file fnum [invalid value]
[2024/01/22 16:31:11.616000,  5] ../../source3/smbd/files.c:321(openat_internal_dir_from_pathref)
  openat_internal_dir_from_pathref: fd_openat(".", ".") failed: NT_STATUS_NO_MEMORY
[2024/01/22 16:31:11.616000,  5] ../../source3/smbd/files.c:1985(file_free)
  file_free: freed files structure 0 (1 used)
[2024/01/22 16:31:11.616000,  3] ../../source3/smbd/filename.c:319(get_real_filename_full_scan_at)
  get_real_filename_full_scan_at: scan dir didn't open dir [.]: NT_STATUS_NO_MEMORY
[2024/01/22 16:31:11.616000,  5] ../../source3/smbd/files.c:1985(file_free)
  file_free: freed files structure 0 (0 used)
[2024/01/22 16:31:11.616000,  3] ../../source3/smbd/smb2_server.c:4033(smbd_smb2_request_error_ex)
  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_NO_MEMORY] || at ../../source3/smbd/smb2_create.c:360

So - I'm going to take a look at my fd_openat implementation -  but I'm not sure if this is the original trigger of the issue, or a side effect...

edit: fd_openat is from samba (https://github.com/psmedley/samba-os2/blob/samba-os2-4.19.x/source3/smbd/open.c#L900), but ends up  calling openat() (I think,  via https://github.com/psmedley/samba-os2/blob/samba-os2-4.19.x/source3/modules/vfs_default.c#L653)

42
Networking / Re: Samba Users and Groups
« on: January 23, 2024, 07:29:46 am »
A few things of note from the logs:
Code: [Select]
[2024/01/22 18:46:52.954000,  2] ../../libcli/auth/ntlm_check.c:480(ntlm_password_check)
  ntlm_password_check: NTLMv1 passwords NOT PERMITTED for user Warp30
[2024/01/22 18:46:52.954000,  3] ../../libcli/auth/ntlm_check.c:487(ntlm_password_check)
  ntlm_password_check: NEITHER LanMan nor NT password supplied for user Warp30

Code: [Select]
[2024/01/22 18:46:52.958000,  5] ../../source3/auth/auth.c:265(auth_check_ntlm_password)
  auth_check_ntlm_password: sam_ignoredomain authentication for user [Warp30] FAILED with error NT_STATUS_WRONG_PASSWORD, authoritative=1
[2024/01/22 18:46:52.958000,  2] ../../source3/auth/auth.c:353(auth_check_ntlm_password)
  check_ntlm_password:  Authentication for user [Warp30] -> [Warp30] FAILED with error NT_STATUS_WRONG_PASSWORD, authoritative=1

So seems to be some kind of password mismatch.  Try resetting password with smbpasswd

43
Networking / Re: Updated Samba Client
« on: January 23, 2024, 03:30:01 am »
Thanks Dave, will review this evening. Much easier to fix if I could easily reproduce :(

44
Networking / Re: Updated Samba Client
« on: January 22, 2024, 09:11:02 pm »
Do you think Theseus might help in identifying what is running out of memory?

I'm not actually convinced that it's an out of  memory condition. There is a Samba error, that is converted to ENOMEM. I just wish I could easily duplicate the error.

What I really need, is a matching set of:
server smbd log with debug level 8
client logs - log.ndpsmb and log.smbc
with notes as to when the error started occuring (date/time)

I tried to reproduce over the weekend but couldn't easily trigger the error :(

45
Networking / Re: Samba Users and Groups
« on: January 22, 2024, 09:08:33 pm »
I'm starting the servers with the following command line:

smb.cmd start

I have not set libpathstrict. I'm attaching a testlog to this post in case that helps.

I started samba to check things on this post, and it did not generate any traps, but it also did not allow any client to connect. Browsing doesn't work, either. Samba creates logs in response to these actions, but the logs are zero length.

The default loglevel is low :) so doesn't produce many entries.

Can you try starting with:
smbd -d 8
then try to connect, then close  smbd - and send me a copy of \var\log\log.smbd*

Thanks,

Paul

Pages: 1 2 [3] 4 5 ... 140