Samba on V8.4-2L1 AXP

All types of networks, network stacks, and protocols supported by OpenVMS.
Post Reply

Topic author
cct
Contributor
Posts: 13
Joined: Sat Aug 15, 2020 9:00 am
Reputation: 0
Status: Offline

Samba on V8.4-2L1 AXP

Post by cct » Fri Oct 02, 2020 11:24 am

Looking at getting this installed - the product page says it should be Version 4.6-5E for OpenVMS I64 and Alpha servers, based on Samba 4.6.5

However when I try to get the install images it seems that only VSI-AXPVMS-SAMBA-V0406-5F-1 is available.

Is this the correct version for Alpha?

Regards


Chris


paul.nunez
VSI Expert
Contributor
Posts: 10
Joined: Tue Aug 27, 2019 11:46 am
Reputation: 0
Status: Offline

Re: Samba on V8.4-2L1 AXP

Post by paul.nunez » Fri Oct 02, 2020 12:02 pm

Hi Chris, That is the correct/current kit - it's version v4.6-5F, which supersedes v4.6-5E...


Topic author
cct
Contributor
Posts: 13
Joined: Sat Aug 15, 2020 9:00 am
Reputation: 0
Status: Offline

Re: Samba on V8.4-2L1 AXP

Post by cct » Fri Oct 02, 2020 12:11 pm

Thanks. I will give it a try!

Chris


Topic author
cct
Contributor
Posts: 13
Joined: Sat Aug 15, 2020 9:00 am
Reputation: 0
Status: Offline

Re: Samba on V8.4-2L1 AXP

Post by cct » Sun Nov 22, 2020 12:28 pm

Finally got around to installing Samba.

One 'feature' I noticed is that despite saying it will ruin with TCPWARE (I am running V6.0-0) the config utility fails with the message:
#### IP host name is unavailable. Start up IP network first. ####

Looking at the configure DCL I see that it is only checking logicals TCPIP$INET_HOST and UCX$INET_HOST. For TCPWare support that should include TCPWARE_DHCLIENT_HOSTNAME - not sure about Multinet

I tried working around this by manually defining TCPIP$INET_HOST, but the configuration fails quickly setting up SMBD services:

%TCPIP-E-SERVERROR, cannot process service request
-TCPIP-E-NOFILE, cannot access TCPIP$SERVICE database file
%TCPIP-E-SERVERROR, cannot process service request
-TCPIP-E-NOFILE, cannot access TCPIP$SERVICE database file
%TCPIP-E-SERVERROR, cannot process service request
-TCPIP-E-NOFILE, cannot access TCPIP$SERVICE database file
%TCPIP-E-CONFIGERROR, error processing configuration request
-TCPIP-E-NOFILE, cannot access TCPIP$CONFIGURATION database file
%TCPIP-E-CONFIGERROR, error processing configuration request
-TCPIP-E-NOFILE, cannot access TCPIP$CONFIGURATION database file
%TCPIP-E-SERVERROR, cannot process service request
-TCPIP-E-NOFILE, cannot access TCPIP$SERVICE database file
%TCPIP-E-CONFIGERROR, error processing configuration request
-TCPIP-E-NOFILE, cannot access TCPIP$CONFIGURATION database file
%TCPIP-E-CONFIGERROR, error processing configuration request
-TCPIP-E-NOFILE, cannot access TCPIP$CONFIGURATION database file

However these errors are not trapped, and it reports that all was OK. As a result a TESTPARM gethostname fails

Not sure what else is broken...

Chris


paul.nunez
VSI Expert
Contributor
Posts: 10
Joined: Tue Aug 27, 2019 11:46 am
Reputation: 0
Status: Offline

Re: Samba on V8.4-2L1 AXP

Post by paul.nunez » Mon Nov 23, 2020 7:41 am

Hi Chris,

Did you following the instructions in the release notes for TCPware:

Systems Running TCPware TCP/IP

For systems running the TCPware TCP/IP stack, Samba is not able to auto-detect the active TCPware IP interface addresses. Therefore, the list of interfaces available for use by Samba must be manually configured. To do this, initially use SMB$CONFIG to configure Samba as a standalone server, then edit SAMBA$ROOT:[LIB]SMB.CONF and add the appropriate parameters (explained below) to the [global] section. If desired, run SAMBA$CONFIG to reconfigure as a member server.
To make all active interface addresses available to Samba, list those addresses and their subnet masks in a comma or space delimited list using the “interfaces” global parameter. Be sure to always include the localhost address (127.0.0.1) in the list of allowed interfaces.

For example, you may add an entry similar to the following to SMB.CONF (setting address details as appropriate to your environment and being sure to include localhost):

interfaces = 10.100.10.1/24, 127.0.0.1

To make only a subset of active interface addresses available to Samba, include only the addresses (and their subnet) of the allowed interfaces in the interfaces list and also specify “bind interfaces only = yes”.

For example, if the host has the three interfaces 10.10.1.1/24, 192.168.0.10/16, and 44.4.1.1/10 and Samba is to use only interfaces 10.10.1.1/24 and 192.168.0.10/16 then you would specify the following in SMB.CONF:

interfaces = 10.10.1.1/24, 192.168.0.10, 127.0.0.1
bind interfaces only = yes


Topic author
cct
Contributor
Posts: 13
Joined: Sat Aug 15, 2020 9:00 am
Reputation: 0
Status: Offline

Re: Samba on V8.4-2L1 AXP

Post by cct » Mon Nov 23, 2020 9:00 am

Yes, I missed that. However SAMBA$CONFIG.COM is still well broken.

It cannot be run without first defining TCPIP$INET_HOST. It then fails to recognise any interfaces. Assuming one leaves that till later, it still fails with the errors above, and trying to start it returns:

$ smbstart

Creating NMBD Process...
%RUN-S-PROC_ID, identification of created process is 0000014D

Enabling SMBD services...
%DCL-I-SUPERSEDE, previous value of SYS$ERROR has been superseded

SMBD services are not registered in TCPIP database!
$



Chris

Added in 5 minutes 28 seconds:
Also the NMBD process fails with the following error:

Code: Select all

$ Set NoOn
$ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY"))
%SYSTEM-F-OPCCUS, opcode reserved to customer fault at PC=FFFFFFFF80B86F24, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
  image    module    routine             line      rel PC           abs PC
 DECC$SHR                                   0 00000000000ECF24 FFFFFFFF80B86F24
 SAMBA$LIBSAMBA-UTIL  FAULT  smb_panic_default
                                        27286 00000000000005A4 0000000000397D24
 SAMBA$LIBSAMBA-UTIL  FAULT             27299 0000000000397D24 0000000000000000
 SAMBA$LIBSAMBA-UTIL  FAULT  fault_report
                                        27209 000000000000020C 000000000039798C
 SAMBA$LIBSAMBA-UTIL  FAULT             27220 000000000039798C 0000000000000000
 DECC$SHR                                   0 0000000000203CC4 FFFFFFFF80C9DCC4
 DECC$SHR                                   0 000000000020398C FFFFFFFF80C9D98C
 DECC$SHR                                   0 00000000000346FC FFFFFFFF80ACE6FC
----- above condition handler called with exception 0000000C:
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000000000, PC=0000000001CFCCAC, PS=0000001B
----- end of exception message
                                            0 FFFFFFFF800A915C FFFFFFFF800A915C
 SAMBA$LIBSMBCONF  LOADPARM  lp_include
                                        97920 000000000000C2DC 0000000001CFCCAC
 SAMBA$LIBSAMBA-HOSTCONFIG  LOADPARM  handle_include
                                        57439 0000000000009EF4 0000000000BF5EF4
 SAMBA$LIBSAMBA-HOSTCONFIG  LOADPARM  set_variable
                                        57967 000000000000B654 0000000000BF7654
 SAMBA$LIBSAMBA-HOSTCONFIG  LOADPARM  lpcfg_do_global_parameter
                                        58019 000000000000BA68 0000000000BF7A68
 SAMBA$LIBSMBCONF  LOADPARM  do_parameter
                                        98204 000000000000CF4C 0000000001CFD91C
 SAMBA$LIBSAMBA-UTIL  TINI  parse_param
                                         7497 0000000000000684 00000000003A78E4
 SAMBA$LIBSAMBA-UTIL  TINI               7541 00000000003A78E4 0000000000000000
 SAMBA$LIBSAMBA-UTIL  PARAMS  pm_process
                                        27699 0000000000000084 000000000039DE74
 SAMBA$LIBSMBCONF  LOADPARM  lp_load_ex
                                        99382 000000000000FE0C 0000000001D007DC
 SAMBA$LIBSMBCONF  LOADPARM  lp_load_initial_only
                                        99502 0000000000010618 0000000001D00FE8
 SAMBA$NMBD  NMBD  main                 95712 0000000000001D48 00000000000420A8
 SAMBA$NMBD  NMBD  __main               95553 0000000000001734 0000000000041A94
 SAMBA$NMBD                                 0 000000000006C55C 000000000006C55C
 PTHREAD$RTL                                0 0000000000057718 FFFFFFFF80A79718
 PTHREAD$RTL                                0 0000000000030444 FFFFFFFF80A52444
                                            0 FFFFFFFF8037BC04 FFFFFFFF8037BC04
%TRACE-I-END, end of TRACE stack dump
  SYSTEM       job terminated at 23-NOV-2020 13:58:34.15

  Accounting information:
  Buffered I/O count:                899      Peak working set size:      28672
  Direct I/O count:                  807      Peak virtual size:         238800
  Page faults:                      2133      Mounted volumes:                0
  Charged CPU time:        0 00:00:49.59      Elapsed time:       0 00:00:54.77
Chris


paul.nunez
VSI Expert
Contributor
Posts: 10
Joined: Tue Aug 27, 2019 11:46 am
Reputation: 0
Status: Offline

Re: Samba on V8.4-2L1 AXP

Post by paul.nunez » Mon Nov 23, 2020 9:16 am

ok, I'll look into it further.

In the interim, see if you can just run:

$ @samba$root:[bin]samba$smbd_setup_tcpip

To create the tcp/ip services. The procedure checks for the existence of the logical name TCPWARE_DOMAINNAME to determine if the system is runnning TCPware.

Also, assuming problems continue, please post output from:

$ testparm -s --section-name=global


Topic author
cct
Contributor
Posts: 13
Joined: Sat Aug 15, 2020 9:00 am
Reputation: 0
Status: Offline

Re: Samba on V8.4-2L1 AXP

Post by cct » Mon Nov 23, 2020 9:47 am

Interesting - I did not have TCPWARE_DOMAINNAME. Set that in NETCU and ran samba$root:[bin]samba$smbd_setup_tcpip

After a false start I checked the global conf bits, and it was missing the interfaces. Redid that in smb,conf - it was on the same line as the [global] tag, and it started OK. I can now connect from a PC

Many thanks for your help here - I just need to remember for installation on my physical Alpha


Chris

Post Reply