Operating System - OpenVMS
1826123 Members
4591 Online
109690 Solutions
New Discussion

CIFS (Samba) Installation problem

 
Paul Beaudoin
Regular Advisor

CIFS (Samba) Installation problem

Hi,

Now that I got to VMS8.2, the main reason for doing this upgrade is in focus - I installed and configed CIFS as per instuction and up to the pdbedit stage, it seems to work fine. This is the result of testparm:

TESTPARM
Load smb config files from /SAMBA_ROOT/LIB/SMB.CONF
Processing section "[homes]"
Processing section "[laptop]"
Loaded services file OK.
Server role: ROLE_DOMAIN_PDC
Press enter to see a dump of your service definitions

# Global parameters
[global]
server string = Samba %v running on %h (OpenVMS)
passdb backend = tdbsam
log file = /samba_root/var/log.%m
domain logons = Yes
domain master = Yes
create mask = 0755

[homes]
comment = Home Directories
read only = No
create mask = 0750
browseable = No

[laptop]
comment = PC Directories
path = /das3/laptop/192.168.1.46
force user = paul
read only = No
guest ok = Yes

It is the last one I am trying to access. The path is to an existing directory and the ip address is the laptop. The force user entry is from a Linux implementation that works here in an attempt to bypass the (apparently) broken access controls. In this environment, I am happy for the PCs to access without security. What I am after is two distict areas for 2 PCs to backup to. The laptop connects but can't log in, probably because I can't create an entry using pdbedit. It ACCVIOs on most operations:

pdbedit -A PAUL
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=0000000000000000, PC=0000000000284E88, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
SAMBA$SHR VMS_HACKS vms_fake_setuid 69608 00000000000026D8
0000000000284E88
SAMBA$SHR VMS_HACKS vms_fake_stat 68952 0000000000000774
0000000000282F24
SAMBA$SHR VMS_HACKS vms_fcntl 70194 0000000000004420
0000000000286BD0
SAMBA$SHR TDB tdb_brlock 61015 000000000000034C
000000000023F23C
SAMBA$SHR TDB tdb_open_ex 62587 0000000000004C7C
0000000000243B6C
SAMBA$SHR TDBUTIL tdb_open_log 61566 0000000000001E64
0000000000246AA4
SAMBA$SHR SECRETS secrets_init 60809 000000000000014C
00000000001F0BEC
SAMBA$SHR SECRETS secrets_fetch 60839 000000000000026C
00000000001F0D0C
SAMBA$SHR SECRETS secrets_fetch_domain_sid
60902 0000000000000588
00000000001F1028
SAMBA$SHR MACHINE_SID pdb_generate_sam_sid
60850 000000000000018C
00000000003636CC
SAMBA$SHR MACHINE_SID get_global_sam_sid
60946 0000000000000A68
0000000000363FA8
SAMBA$SHR PDBEDIT new_user 61176 00000000000012BC
00000000001A98AC
SAMBA$SHR PDBEDIT pdbedit_main 61625 00000000000028F8
00000000001AAEE8
PDBEDIT PDBEDIT_MAIN main 6 00000000000000D4
00000000000300D4
PDBEDIT PDBEDIT_MAIN __main 0 000000000000006C
000000000003006C
PDBEDIT 0 0000000000030310
0000000000030310
0 FFFFFFFF80325F94
FFFFFFFF80325F94

I have tried a few other pdbedit operations and some claim not to be able to open the passdb.tdb (IIRC) file. The file exists at the location it is complaining about and is empty. I set it to W:RWED just to see if that was the problem. It wasn't.

I have set the DECC$ logicals as instructed and can't seem to progress beyond this.

Most grateful for any suggestions.

Thanks

Paul
2 REPLIES 2
Paul Beaudoin
Regular Advisor

Re: CIFS (Samba) Installation problem

Wow!

Not a lot of interest in this one... Not to worry. I put the same issue to VMS engineering via the CIFS site and got the following back. (This can close this thread rather than just leave it hanging)


A bug has been identified in code common to pdbedit and some other
utilities that will occasionally cause these access violations to occur.

An updated evaluation release for CIFS is being tested now as a fix, and
HP is planning on making it available when the testing is complete.

Regards,
John Malmberg
HP OpenVMS Engineering.
Volker Halle
Honored Contributor

Re: CIFS (Samba) Installation problem

Paul,

thanks for posting detailled information about the problem and the upcoming solution. This should allow anybody, who is seeing the same problem, to find this entry and read about the solution.

Volker.