Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Issues Starting Samba.

Randy Crawford
Occasional Visitor

Issues Starting Samba.

We are running OPENVMS 8.3-1H1.
Trying to install Samba. Downloaded the 2 patches and then installed Samba. We starting Samba get the following error
[2010/02/11 13:07:44, 1]
SAMBA$SRC:[SOURCE.LIB]UTIL_FILE.C;1:(292)
map_file: incorrect size for /SAMBA$ROOT/LIB/upcase.dat - got 132091 expected 131072
[2010/02/11 13:07:44, 1]
SAMBA$SRC:[SOURCE.LIB]UTIL_FILE.C;1:(292)
map_file: incorrect size for /SAMBA$ROOT/LIB/lowcase.dat - got 132083 expected 131072
[2010/02/11 13:07:44, 1]
SAMBA$SRC:[SOURCE.LIB]UTIL_UNISTR.C;1:(115)
creating lame upcase table
[2010/02/11 13:07:44, 1]
SAMBA$SRC:[SOURCE.LIB]UTIL_UNISTR.C;1:(130)
creating lame lowcase table
I am not sure how to change the size of the file or how I ended up with the wrong size. Any help would be apprecaited.
8 REPLIES
Steven Schweda
Honored Contributor

Re: Issues Starting Samba.

> Trying to install Samba.

_Which_ Samba? How?

> Downloaded the 2 patches [...]

If only my psychic powers were stronger...

I know nothing, but I'd start with DIRE /FULL
on the cited files, with an eye toward
conversion to Stream_LF record format.

> [...] how I ended up [...]

I don't even know how you started out.
Randy Crawford
Occasional Visitor

Re: Issues Starting Samba.

Sorry for being so vague..
We are in the process of upgrading to an Itanium server from an ES40. We are using Advanced server for external authenication
and shares. I am trying to duplicate the same services on the new server
using Samba.

Server Status
Refresh Interval:
version: 3.0.28a
smbd: running
nmbd: running

My current configuration is

# Samba config file created using SWAT
# from 10.40.5.188 (10.40.5.188)
# Date: 2010/02/11 15:20:32

# Global parameters
[global]
workgroup = NETLOGAN.INT
server string = Samba %v running on %h (OpenVMS)
security = DOMAIN
password server = 10.40.0.25
log level = 10
log file = /samba$root/var/log_%h.%m
load printers = No
local master = No
domain master = No
wins support = Yes
ldap ssl = no
admin users =

[homes]
comment = Home Directories
read only = No
create mask = 0750
browseable = No
vms ods5 volume = Yes

[dkb1:[000000.data.logs]
comment = SPSUPR files
path = dkb1:[000000.data.logs]
username = @users
valid users =
guest only = Yes
available = No
set directory = Yes
vms path names = No



When I run the samba$startup
The log looks like

SAMBA
sd $ Set NoOn
$ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY"))

<--- SYLOGIN.COM

---> SYLOGIN.COM
[2010/02/11 13:07:44, 1] SAMBA$SRC:[SOURCE.LIB]UTIL_FILE.C;1:(292)
map_file: incorrect size for /SAMBA$ROOT/LIB/upcase.dat - got 132091 expected 131072
[2010/02/11 13:07:44, 1] SAMBA$SRC:[SOURCE.LIB]UTIL_FILE.C;1:(292)
map_file: incorrect size for /SAMBA$ROOT/LIB/lowcase.dat - got 132083 expected 131072
[2010/02/11 13:07:44, 1] SAMBA$SRC:[SOURCE.LIB]UTIL_UNISTR.C;1:(115)
creating lame upcase table
[2010/02/11 13:07:44, 1] SAMBA$SRC:[SOURCE.LIB]UTIL_UNISTR.C;1:(130)
creating lame lowcase table
SAMBA$SMBD job terminated at 11-FEB-2010 13:07:44.55
Accounting information:
Buffered I/O count: 200 Peak working set size: 12192
Direct I/O count: 130 Peak virtual size: 202336
Page faults: 661 Mounted volumes: 0





The dir/full shows the files

SPSUPR_SYS>dir/full *.dat

Directory DKB0:[SYS0.SYSCOMMON.SAMBA.LIB]

LOWCASE.DAT;1 File ID: (2232,2,0)
Size: 258/272 Owner: [SYSTEM]
Created: 9-FEB-2009 13:18:34.92
Revised: 9-FEB-2009 13:18:35.11 (3)
Expires:
Backup: 5-FEB-2010 16:29:26.19
Effective:
Recording:
Accessed:
Attributes:
Modified:
Linkcount: 1
File organization: Sequential
Shelved state: Online
Caching attribute: Writethrough
File attributes: Allocation: 272, Extend: 0, Global buffer count: 0, No version limit
Record format: Stream_LF, maximum 0 bytes, longest 32767 bytes
Record attributes: Carriage return carriage control
RMS attributes: None
Journaling enabled: None
File protection: System:RWED, Owner:RWED, Group:RE, World:RE
Access Cntrl List: None
Client attributes: None

UPCASE.DAT;1 File ID: (2245,2,0)
Size: 258/272 Owner: [SYSTEM]
Created: 9-FEB-2009 13:18:35.26
Revised: 9-FEB-2009 13:18:35.44 (3)
Expires:
Backup: 5-FEB-2010 16:29:26.19
Effective:
Recording:
Accessed:
Attributes:
Modified:
Linkcount: 1
File organization: Sequential
Shelved state: Online
Caching attribute: Writethrough
File attributes: Allocation: 272, Extend: 0, Global buffer count: 0, No version limit
Record format: Stream_LF, maximum 0 bytes, longest 32767 bytes
Record attributes: Carriage return carriage control
RMS attributes: None
Journaling enabled: None
File protection: System:RWED, Owner:RWED, Group:RE, World:RE
Access Cntrl List: None
Client attributes: None

VALID.DAT;1 File ID: (2247,2,0)
Size: 0/0 Owner: [SYSTEM]
Created: 9-FEB-2009 13:18:35.59
Revised: 9-FEB-2009 13:18:35.65 (3)
Expires:
Backup: 5-FEB-2010 16:29:26.19
Effective:
Recording:
Accessed:
Attributes:
Modified:
Linkcount: 1
File organization: Sequential
Shelved state: Online
Caching attribute: Writethrough
File attributes: Allocation: 0, Extend: 0, Global buffer count: 0, No version limit
Record format: Stream_LF, maximum 0 bytes, longest 32767 bytes
Record attributes: Carriage return carriage control
RMS attributes: None
Journaling enabled: None
File protection: System:RWED, Owner:RWED, Group:RE, World:RE
Access Cntrl List: None
Client attributes: None

Total of 3 files, 516/544 blocks.

Steven Schweda
Honored Contributor

Re: Issues Starting Samba.

> [...] We are using Advanced server [...]

Does that mean that you're eligible for HP
support? If so, an official request for
official support might be work better than
asking here.

> [2010/02/11 13:07:44, 1] SAMBA$SRC:[SOURCE.LIB]UTIL_FILE.C;1:(292)
> map_file: incorrect size for /SAMBA$ROOT/LIB/upcase.dat - got 132091 expected 131072

> UPCASE.DAT;1 File ID: (2245,2,0)
> : 258/272 Owner: [SYSTEM]
Created: 9-FEB-2009 13:18:35.26

So, are these files being created (not
supplied in the kit)?

> Record format: Stream_LF, [...]

There goes my hypothesis.
Paul Jerrom
Valued Contributor

Re: Issues Starting Samba.

Hi Randy,

What version of Samba?? (use $@samba$root:[bin]samba$define_commands then $smbver).
The HP CIFS/Samba webpage does not contain a link to the latest version - for that you need to be a member of a secret society and pass through the 15 gates. Latest patch is PS009 dated December 2009. That, and the latest ACRTL (V4.0 for me) patch fixed a number of my problems (but not the ones about lack of documentation...)
[FTP address is ftp.usa.hp.com, username pathwork, password Support9]

Your file attributes are exactly the same as mine (except backup dates...).

BTW, I loved "One Day I'll Fly Away"!

Have fun
PJ
Have fun,

Peejay
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If it can't be done with a VT220, who needs it?
Paul Nunez
Respected Contributor

Re: Issues Starting Samba.

Hi Randy,

While I can't address the map_file errors, there are some lines in the smb.conf that should be changed or removed:

workgroup = NETLOGAN.INT

while "NETLOGAN.INT" is a valid NetBIOS name, I suspect that it is really the DNS name of the Active Directory domain you wish to join? If so, the NetBIOS name is likely just NETLOGAN. If you're not sure, post the output from:

$ nmblookup "-A" 10.40.0.25

Unless the domain contains only one domain controller, I recommend you either remove the "password server" line or modify to be:

password server = 10.40.0.25, *

The %m in the line:

log file = /samba$root/var/log_%h.%m

The client NetBIOS name is not available/provided when the client connects using SMB over TCP/IP (connects on TCP port 445 instead of the NetBIOS over TCP/IP port - TCP port 139), so no debug log gets created/updated. If the device where the logs are stored is an ODS-5 volume, %I is probably the best alternative to ensure a debug log gets created/updated w/o exception, but %U is another decent option (but not in all environments).

Remove the line:

wins support = Yes

CIFS for OpenVMS doesn't support being a WINS server; enabling wins support will result in major issues for the nmbd (or smbd processes?) - it's in the documentation - it either crashes or goes compute bound.

If you want the CIFS server to be a WINS _client_, use the "wins server" parameter and specify the IP address of one or more WINS servers.

As of V1.1 ECO1 PS006, the "mask" and "mode" parameters should be removed or modified (per the patch set release notes). For example, remove lines such as:

create mask = 0750

You may want to add the following line to the [global] section so Windows users can rename/delete folders they create (this will be the default in the v1.2 release)

force directory mode = 04000

When creating shares, the name of the share, not its path, is specified within the brackets. No idea what the result of using:

[dkb1:[000000.data.logs]

will be, but you probably want to change it to something like:

[logs]

Then users would map the share by specifying:

\\server-name\logs

Then there is:

username = @users

please see the smb.conf MAN page for details on the "username" parameter. Don't think this is what you intend, but not sure what you intend :).

The following will prevent access to the share by anyone (but that may be the intent until you get the darn thing to function at all ;o):

available = No

If you want to grant guest access to shares and the role is Member server, include

map to guest = bad uid

in the [global] section and include

guest ok = yes

in the share section. "guest only = yes" indicates ONLY guest access is allowed (which may be desired), but it has no effect unless "guest ok = yes" is also set.

As for:

set directory = Yes

it's pretty much obsolete since the "Digital Pathworks client" isn't around any longer and, thus, won't likely have any affect; the MAN page states:

If set directory = no, then users of the service may not use the setdir command to change directory.

The setdir command is only implemented in the Digital Pathworks client. See the Pathworks documentation for details.

Default: set directory = no

HTH,

Paul
Peter Barkas
Regular Advisor

Re: Issues Starting Samba.

I recited the invocations and installed patch set 009 and yes the error messages about the file sizes went away.

I tried installing T1.2 but the install failed without telling me why.

My current setup is working, so I am waiting for V1.2 before I investigate the other error/informational messages that still appear.

IMHO SAMBA/CIFS seems to work but doesn't inspire confidence.
Shilpa K
Valued Contributor

Re: Issues Starting Samba.

Hi Peter,

You mention CIFS T1.2 installation failed. Can you please mention the VMS version on your system, whether it is Alpha or IA64 and the version of Kerberos on your system? Also, if you still have a screen shot, can you post it?

Thanks,
Shilpa
Peter Barkas
Regular Advisor

Re: Issues Starting Samba.

Shilpa, thank you for your interest, however, I don't want to hijack this thread and don't wish to spend any more time on SAMBA CIFS issues until V1.2 is released.