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 ... 109 110 [111] 112 113 ... 140
1651
Web applications / Re: Migrating Apache Web Server
« on: September 08, 2019, 12:13:07 am »
Hey Neil,

I selected Paul Smedley's latest Apache 2.2 HTTPD

https://os2ports.smedley.id.au/index.php?page=apache2

I adjusted the conf/httpd.conf, and the website is running.

But not all is well. The server stops serving after a few days. Is anyone running this software? The logs seem to show nothing unusual, and there isn't really very much traffic. What could cause the server to stop?

Lewis, Massimo and a few others are using the 2019 build on their server with reasonable success.

One of the keys is to make sure you have a valid setting for MaxRequestsPerChild - I suggest 1000 based on the below from Lewis...

Code: [Select]
I can report a similar experience.

I'm currently running with MaxRequestsPerChild of 1000, and have seen uptime of over 10 days, no more every-four-hour scheduled daemon restarts and no more every-three-days scheduled server reboots. Memory consumption seems generally low (under 1GB in use under normal operating conditions, and memory is returned to the pool when load decreases - wow!).

I had an issue yesterday where the server fell over, but I think we were being hammered. After the restart and the inevitable autocheck passes, the server has been up.

Nice work, Paul!

Cheers,

Paul

1652
Networking / Re: Samba - cached server IP address?
« on: September 05, 2019, 05:02:40 am »
Hi Dariusz,

That leads me to believe that the Samba client is maintaining a mapping of the actual IP address the alias was previously pointing to and re-using it instead of querrying it up each time.

I haven't seen this before, but I'm not disputing your results :) There's nothing I've added to do this - my guess would be that in one of the files in %ETC%\samba\* where there are various tdb files that something may be cached there?

Assuming you don't run the Samba server on this machine, you should be pretty safe to remove files from this tree and let the client re-create what it needs to.

Cheers,

Paul.

1653
Hello Ivan
It's lucky to arrive for a few days on vacation and find the solution to the problem.
 My case was a little different, but the solution has been the same.
After restoring the system, the ndfs program log said that the smbcli49.dll was missing, when I had the smbcli47.dll
Thank you all

Question to those that had the issue after upgrading to 5.0.4.  Had you installed any of my test builds of the Samba plugin, or were you running the version that came with ArcaOS?

If you can add your feedback to https://mantis.arcanoae.com/view.php?id=2592 it would help fix this for others.

Cheers,

Paul

1654
Hi Ivan,

Yes, they are old but they just keep on working.  I have 4 of them, 2 D-Link DNS-323 and 2 D-Link DNS-320, they are all on 24/7/365 and have been since late 2009.  Two are on the network and the other 2 are remote and backup the network pair overnight using rsync.

Since the system has been working without problems why change?


No reason to change what isn't broken, but security does become a concern. Presumably your two remote NAS are connected via VPN which will help mitigate any security issues from an old Samba release...

1655
I didn't see any bug reports for this in the Arca Noae bug tracker, so I raised https://mantis.arcanoae.com/view.php?id=2592

1656
Hey Ivan,

See attachment

Thanks... that must be a pretty old NAS:
"Server supports NT1 protocol"

Cheers,

Paul

1657
Hi Ivan,

Couldn't find the RP so I went to Paul's site and downloaded the zip from there, extracted the SMBCLN49.DLL put it in the programs\ndfs\ndplugs directory, rebooted and all is well, I have connection back to my NAS boxes.

I'd still be interested in a copy of the ndpsmb.log file to see what version of Samba your NAS is running.

Cheers,

Paul

1658
Quote
The only system files used by Netdrive and the Samba plugin are ndpsmb.dll and smbcln49.dll (and things like libc, et al).

Thanks Paul, I went looking in the NDFS directory and found NDCTL.LOG  which gave:

NetDrive for OS/2(R) Control Program version 3.1.5.865 Apr 06 2017

NDFSDIR environment variable found: E:\Programs\NDFS
NetDrive working directory is E:\Programs\NDFS
File system driver name is NDFS32.
NetDrive configuration file 'E:\Programs\NDFS\ndctl.cfg' has been processed.

Exclusive Samba Use

[   local] internal plugin has been initialized.
NDF0033: The system can't load the module: SMBCLN49
NDF0029: [  ndpsmb] plugin has not been loaded.
NDF0007: The system error is SYS0002
Initialization completed. The control program is running.

So it appears that  SMBCLN49.DLL is missing.  Searching for it brings up a blank, I can only assume that the ArcaOS 5.0.4 didn't install it when it updated the ndplugs directory unless it is supposed to be somewhere else.

Well that would explain the lack of log file, and the error connecting. smbcln49.dll should be in the same directory as ndpsmb.dll

1659
Quote
The smb.conf file is in two places in
C:\MPTN\ETC\samba\smb.conf
C:\var\temp\smb.conf

The file C:\var\temp\smb.conf Is a work file, in a temporary location. It is used by the program to fill out the defaulted (not defined) settings. Ignore it, although it can tell you what actual settings are being used. C:\MPTN\ETC\samba\smb.conf is the file that you would want to edit, to change default settings.

Note that C:\sys\apps\smbclnt contains the code used by the SAMBA client. It was updated with ArcaOS 5.0.4, and you will see a SYS0050 if that didn't get updated, or if your system has another copy somewhere, that isn't updated, or if your CONFIG.SYS points somewhere else (or...). The contents are:
Code: [Select]
[C:\SYS\APPS\SMBCLNT]dir

The volume label in drive C is ARCAOS.
The Volume Serial Number is DFDA:75BB.
Directory of C:\SYS\APPS\SMBCLNT

 8-26-18 12:34p         <DIR>      0 ----  .
 8-26-18 12:38p         <DIR>      0 a---  ..
 8-26-18 12:34p         <DIR>      0 ----  codepages
 7-09-17 12:39a     4,128,772      0 a---  net.exe
 7-09-17 12:39a       765,956      0 a---  nmblookup.exe
 7-09-17 12:39a     3,739,652      0 a---  rpcclient.exe
 7-09-17 12:39a           199      0 a---  smb.conf.sample
 7-09-17 12:39a     3,567,620      0 a---  smbclient.exe
 7-09-17 12:39a     1,867,780      0 a---  smbspool.exe
 7-09-17 12:39a     3,481,604      0 a---  smbtree.exe
 7-09-17 12:39a       716,804      0 a---  testparm.exe
       11 file(s)  18,268,387 bytes used
                    2,651,516 K bytes free

Note that some of these file names are used in the SAMBA server too, but they are not, necessarily, the same files.

Correction. The files in C:\sys\apps\smbclnt are NOT used by Netdrive or the Samba plugin. They are used for other ArcaOS components, like arcamapper and for printing support.

The only system files used by Netdrive and the Samba plugin are ndpsmb.dll and smbcln49.dll (and things like libc, et al).

Cheers,

Paul.

1660
Hello Paul,
Just for trying to clarify
Some comments about arca504 and samba client.
The smb.conf file is in two places in
C:\MPTN\ETC\samba\smb.conf
C:\var\temp\smb.conf
The debug file is rooted in the system,C:\ndpsmb.dbg, but does not show anything or in my case a single line:
NDPSMB debug flag file


Marking the log, and debug option, in the arcamap shows a window that allows copy paste, which I know is the only way to get a log-file.

I have no idea why there's a smb.conf in c:\var\temp\smb.conf - the Samba code will only look in %ETC%\samba\smb.conf

If C:\ndpsmb.dbg exists - and ndctl.exe is restarted (this can be done in Arcamapper - the menu option is something like restart control daemon) then logs should be put into %LOGFILES%\ndpsmb.log - IIRC (I don't have an ArcaOS nearby) by default this is c:\var\log\ndpsmb.log

Hope this helps,

Paul.

1661
Hi Paul,

I did as you asked and all I get is an empty file even after rebooting the computer.

Did you check in X:\var\log\ndpsmb.log ?

1662
Hi Ivan,

All the small D-Link NAS boxes are using SMB v1 with no possibility of wver changing that to anything higher.  There were a lot of problems on the the various NAS forums when MS  changed the default to SMB v2  in win 10 hence my asking how to do that in ArcaOS v5.0.4

Samba still defaults to allowing SMB1. Can you enable debug logging for the Netdrive plugin (create a file NDPSMB.DBG in the root directory of your boot drive), restart ndctl using Arcamapper, try to connect to the D-Link NAS then send me the resulting ndpsmb.log ?

Cheers,

Paul

1663
Hey Ivan,

All I know is that I used the 'update' option of the ArcaOS 5.0.4 DVD on one of my test machines and now I can't connect to my NAS boxes from that machine (always get a SYS0050 error message).  I also know a number of friends also lost connection to their NAS boxes when MS updated win 10 to default to SMB v2 and the workround was to reset SMB back to v1.

I suppose I could copy over a working Samba from another of my computers but that doesn't solve the problem (all the other un-updated computers have no problem connecting to the NAS boxes).

Something has changed but the question is what!

There was a change to authentication around Samba 4.7 or 4.8 timeframe if I recall correctly (I'll try remember what it was).

IIRC the version of the Samba client in used changed from v4.4.x to v4.9.x in 5.0.4....

Meanwhile, logs would be useful....

I suspect this change could be the reason for Ivan's issue (from Samba 4.7 changelog)

Code: [Select]
The 'ntlm auth' option default is renamed to 'ntlmv2-only', reflecting
the previous behaviour.  Two new values have been provided,
'mschapv2-and-ntlmv2-only' (allowing MSCHAPv2 while denying NTLMv1)
and 'disabled', totally disabling NTLM authentication and password
changes.

@Ivan do you know what Samba version your NAS is running? Connecting to it with smbclient should show it.

Cheers,

Paul

1664
Hey Ivan,

All I know is that I used the 'update' option of the ArcaOS 5.0.4 DVD on one of my test machines and now I can't connect to my NAS boxes from that machine (always get a SYS0050 error message).  I also know a number of friends also lost connection to their NAS boxes when MS updated win 10 to default to SMB v2 and the workround was to reset SMB back to v1.

I suppose I could copy over a working Samba from another of my computers but that doesn't solve the problem (all the other un-updated computers have no problem connecting to the NAS boxes).

Something has changed but the question is what!

There was a change to authentication around Samba 4.7 or 4.8 timeframe if I recall correctly (I'll try remember what it was).

IIRC the version of the Samba client in used changed from v4.4.x to v4.9.x in 5.0.4....

Meanwhile, logs would be useful....

Cheers,

Paul.

1665
Hi All,

Is this a new install using ArcaOS 5.0.4?  If it is you have hit the SMB update problem since most small NAS boxes are setup to use SMB v1and the AOS 5.0.4 is now set to use some other version the two won't communicate hence the error message.

There has to be a way of setting SMB back to using v1 but I haven't found it yet.

I really doubt the Samba client has been set to use SMB2+ only in AOS 5.0.4. There's nothing in my code to do this. If they have done this, the only place it could be is in %ETC%\samba\smb.conf

Look for something like:
min protocol = SMB2

Cheers,

Paul

Pages: 1 ... 109 110 [111] 112 113 ... 140