"E"

ENOMEM The available data space is not large enough to accommodate the shared memory segment

Cause

ENOMEM errors occur after 80 segments have been allocated by Lotus Notes.

Action

The design and implementation of Solaris ISM (Intimate Shared Memory) is what caused the ENOMEM failures, from the Lotus Notes application, besause of the limit reached on the number of shared memory segments that can be attached to a particular process.

The limit occurs because all shared memory segments are attached in the Intimate Shared Memory (ISM) mode courtesy of a system variable they have set in the system file called shmsys:share_page_table.

When a shared memory segment is attached in ISM mode, the OS locks that segment into physical memory and arranges the virtual/physical address mappings such that only one copy of the mapping information is shared amongst all attaching processes. To accomplish this, the OS requires the virtual starting address of the segment be aligned on a 16 Meg (hex 0x1000000) = 16777216-bytes address boundary.

The NULL address lets the system decide what virtual address the segment should be attached at. The system also assigns addresses 0x3000000 apart unless forced to attach addresses at 0x1000000 apart.

Doing a few calculations, a sun4d could create and attach up to 220 1-Meg ISM segments and a sun4m could create and attach up to 235 1-Meg ISM segments, providing the segments were 0x1000000 apart.

Given that ISM is what causes the limit, what can we do about it?

First, the limit only gives Lotus Notes the ability to attach a total of 80 Meg of shared memory total. By increasing the segment size to 10 Meg, as Lotus has already recommended, 8 ISM segments will take care of the load previously needing 80 1-Meg segments. The load could conceivably grow to 800-meg now without running into the ISM addressing limit.

Secondly, we could have turned off the share_page_table (ISM) flag. This would give a sun4m the ability to create in excess of 3000 1-Meg segments. The problem here is that ISM does improve the performance of shared memory accesses and if your customer intends to move up to 2.5.x, ISM is required to get around another set of problems that were discovered with shared memory loads of this kind.

Thirdly, Lotus could change the Notes server so that it kept track of the attach addresses and always attached at 0x1000000 boundary addresses instead of letting the system default to the 0x3000000 address boundary. As I've already shown, this would allow a Notes server to grow to 235 segments on a sun4m.

error 13

Cause

Diskless client boot gave NFS mount error 13 Diskless client boot failed with error: nfs mount failed: permission denied error 13

Cause

Diskless client fails to boot, NFS error 13 Diskless client fails to boot giving the error message: nfs error 13

error 15 initializing

Cause

Bad /boot or 4.1 on ss2 - level 15 interrupt

Error 76

Cause

This error is RFS specific. This is a way for the server to tell the client that a process has transferred back from mount point.

Technical Notes

The symbolic name for this error is EDOTDOT, errno=76.

Error 88

Cause

Illegal byte sequence. Handle multiple characters as a single character.

Technical Notes

The symbolic name for this error is EILSEQ, errno=88.

error: DPS has not initialized or server connection failed

Cause

This message appears when trying to run AnswerBook with a generic X11 window server or on a generic X terminal.

Action

Running AnswerBook requires Display PostScript (DPS), or a NeWS server, or the Adobe DPS NS remote display software. In addition, a complete LaserWriterII Type-1 font set (including Palatino) should be installed on the X server. To find out if your X server has DPS, run xdpyinfo(1) to verify the presence of an "Adobe-DPS-Extension" line. X servers without this line don't know about DPS.

Error: Error adding OS service Solaris 2.6 sparc sun4u:

Cause

While trying to add OS services to a newly installed Solaris 2.6 system using Solstice Adminsuite 2.3, the process fails with the following error message:

Error: Error adding OS service Solaris 2.6 sparc sun4u:
inconsistent revision, installed package SUNWpppk revision 3.0.1
does not match revision 11.6.0,REV=1997.07.15.21.46 for sparc
architecture.

Action

The workaround is to remove the PPP 3.0.1 packages and replace them with the PPP packages off of the Solaris 2.6 release CD-ROM. For example:

# pkgrm SUNWlicsw SUNWlit SUNWpppk SUNWpppm SUNWpppr SUNWppps SUNWpppu
:
:  {package remove info}
:
# cd /cdrom/cdrom0/s0/Solaris_2.6/Product
# pkgadd -d . SUNWapppr SUNWapppu SUNWpppk
:
:  {package add info}
:

NOTE: If the Solstice PPP 3.0.1 package is configured and currently in use on the system, the user should save any of the previously entered PPP configuration info so that it may be restored after the OS services have been installed. (pkgrm(1M)the 3 ppp packages installed from the 2.6 release CD, and pkgadd(1M) all of the ppp packages from the Intranet Extension cdrom again, then redo config.). If the Solstice PPP 3.0.1 package was not used on the system, there is no reason to reinstall it. Use /usr/bin/pkginfo to check the installed packages.

This is documented in Chapter 9 of the Solaris Server Intranet Extension Installation and Release Notes Solaris 2.6 manual.

Error Host Unknown:

Cause

On Windows95, running PC-NFSpro2.0, use ping(1M) to reach another computer on the network. ping(1M) returns Host Unknown.

Cause: Name services are not set up correctly.

Action

1: Click the Windows 95 Start button, point to Programs, point to PC-NFSpro, then click Configuration.

2: Click TCP/IP and make sure all settings are entered correctly.

3: If NIS is enabled click Configure NIS and make sure the NIS domain and server names are correct.

4: If DNS is enabled, click Configure DNS and make sure the DNS domain and server names are correct.

5: Click on edit hosts and add the name and IP address of the machine you are trying to ping(1M), along with that of your authentication server.

If you make any changes, click OK, then click Save and Exit on the Configuration dialog box. Shut down and restart Windows95.

ERROR: missing file arg (cm3)

Cause

An attempt was made to run some sccs(1) operation that requires a filename, such as create, edit, delget, or prt.

Action

Supply the appropriate filename after the SCCS operation.

ERROR [SCCS/s.string]: `SCCS/p.string' nonexistent (ut4)

Cause

An attempt was made to sccs(1) edit or sccs get a file that is not yet under SCCS control.

Action

Run sccs(1) create on that file to place it under SCCS control.

ERROR [SCCS/s.string]: writable `string' exists (ge4)

Cause

An attempt was made to sccs(1) edit a file that is writable, probably because it is already checked out.

Action

Run sccs(1) info to see who has the file checked out. If it is you, go ahead and edit it. If it is somebody else, ask that person to check in the file.

Error: you don't have a license to run this program

Cause

Customer tries to mount the /export file system with Volume Manager 2.1.1, getting the message.

Action

Run vxserial -p to print the available volume manager licenses in the system.

Also, check the /etc/vfstab file to make sure that the filesystem is not a vxfs filesystem.

esp0: data transfer overrun

Cause

When a user tries to mount a CD-ROM on a third-party CD drive, mount(1M) fails with the above error, followed by the sr0: SCSI transport failed message. The CD drive probably comes from a vendor unknown to the system.

Action

Third-party CD drives generally have an 8192 block size, as opposed to the 512 block size on supported Sun drives. Check with the vendor to see if any special configuration is possible to allow the drive to operate on a Sun workstation.

Event not found

Cause

This C shell message indicates that a user tried to repeat a command from the history list, but that command or number does not exist in the list.

Action

Run the C shell history(1) command to display recent events in the history list. If a user often tries to run commands that have disappeared from the history list, make the list longer by setting history(1) to a higher value.

See Also

For more information about the C shell, see csh(1).

EXCESSIVE BAD BLKS I=int CONTINUE?

Cause

During phase 1, fsck(1M) found more than 10 bad (out-of-range) blocks associated with the specified inode number.

Action

With this many bad blocks, it might be preferable to restore the filesystem from backup tapes.

See Also

For more information on bad blocks, see the section on checking filesystem integrity in the System Administration Guide, Volume I. If you are using the AnswerBook, "bad blocks" is a good search string.

EXCESSIVE DUP BLKS I=int CONTINUE?

Cause

During phase 1, fsck(1M) found more than 10 duplicate (previously claimed) blocks associated with the specified inode number.

Action

With this many duplicate blocks, it might be preferable to restore the filesystem from backup tapes.

See Also

For more information on blocks, see the section on checking filesystem integrity in the System Administration Guide, Volume I. If you are using the AnswerBook, "bad blocks" is a good search string.

Exec format error

Cause

This often happens when trying to run software compiled for different systems or architectures, such as when executing Solaris 2 programs on a SunOS 4.1 system, or when trying to execute SPARC-specific programs on an x86 machine. On a Solaris 2 system, it can also occur if the Binary Compatibility Package was not installed.

Action

Make sure that the software matches the architecture and system you're using. The file(1) command can help you determine the target architecture. If you're using SunOS 4.1 software on a Solaris 2 system, make sure that the Binary Compatibility Package is installed. You can check for it using this command:

$ pkginfo | grep SUNWbcp

Technical Notes

A request was made to execute a file that, although it has the appropriate permissions, does not start with a valid format.

The symbolic name for this error is ENOEXEC, errno=8.

See Also

See the a.out(4) man page for a description of executable files.