"E"
Encapsulation of root disk is not supported on systems with old PROM versions
Cause
When encapsulating the root disk with Volume Manager, this error message is printed.
Action
This error message probably has nothing at all to do with the user's system PROM version. It most likely is related to the fact that the file /dev/vx/config (and the pseudo device that it is linked to) does not exist on the system. A few things could contribute to this file not being created:
-
Make sure these lines are in the /etc/system file:
forceload: drv/vxdmp (only needed for SEVM 2.5 and above) forceload: drv/vxio forceload: drv/vxspec
-
Make sure the vx entries are in the /etc/name_to_major file.
This should come back with 2 or 3 lines (vxio and vxspec, also vxdmp, if running SEVM 2.5 and above). The major number values might be different from machine to machine; however, if the entries are in there, that should be sufficient.
grep vx /etc/name_to_major
-
If you have not performed a boot -r since doing a pkgadd to the Volume Manager software, this might have contributed to the problem.
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 the Solaris ISM (intimate shared memory)--which limits the number of shared memory segments that can be attached to a particular process--caused the ENOMEM failures to the Lotus Notes application.
There is a limit because all shared memory segments are attached in the intimate shared memory (ISM) mode by a system variable that is set in the shmsys:share_page_table system file.
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 among all attaching processes. To accomplish this, the OS requires that the virtual starting address of the segment be aligned on a 16 Mbytes (hex 0x1000000) = 16777216-bytes address boundary.
The NULL address lets the system decide what virtual address the segment should be attached to. The system also assigns addresses at 0x3000000 apart, unless forced to attach addresses at 0x1000000 apart.
A sun4d could create and attach up to 220 1-Mbyte ISM segments, and a sun4m could create and attach up to 235 1-Mbyte ISM segments, providing the segments were 0x1000000 apart.
Having established that ISM is the cause of the limit, below are some options:
First, the limit only gives Lotus Notes the ability to attach a total of 80 Mbytes of shared memory. By increasing the segment size to 10 Mbyte, as Lotus has already recommended, 8 ISM segments can handle the load previously needing 80 1-Mbyte segments. The load could conceivably grow to 800 Mbytes now without running into the ISM addressing limit.
Second, the share_page_table (ISM) flag could be turned off. This would give a sun4m the ability to create in excess of 3000 1-Mbyte segments. The problem here is that ISM does improve the performance of shared memory accesses, and, if the user intends to move up to 2.5.1, ISM is required to get around another set of problems related to shared memory loads of this kind.
Third, Lotus could change the Notes server so that it kept track of the attach addresses and always attached at 0x1000000 boundary addresses, instead of having the system default to the 0x3000000 address boundary. This would allow a Notes server to grow to 235 segments on a sun4m.
error 15 initializing
Cause
It is caused by a bad /boot or 4.1 on ss2 - level 15 interrupt.
Error 76
Cause
This error is RFS-specific. The server is telling 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
This error is caused by an illegal byte sequence.
Action
You need to handle multiple characters as a single character.
Technical Notes
The symbolic name for this error is EILSEQ, errno=88.
error code 2: access violation
Cause
The user receives this message when trying to do a tftp get.
Action
Do not use a relative path when using tftp. For example:
tftp> get /tftpboot/testfile |
tftp> get testfile |
error: DPS has not initialized or server connection failed
Cause
This message appears when trying to run AnswerBook on 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. Additionally, a complete LaserWriter II Type-1 font set (including Palatino) should be installed on the X server. To find out if the X server has DPS, run xdpyinfo(1) to verify the presence of an "Adobe-DPS-Extension" line. X servers without this line do not 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 environment and 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
As a workaround, remove the PPP 3.0.1 packages and replace them with the PPP packages from 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 information for restoration after the OS services have been installed. (pkgrm(1M) the 3 PPP packages installed from the 2.6 CD release, and againpkgadd(1M) all of the PPP packages from the Intranet Extension CD-ROM, then redo the configuration.) 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
In this case, the user is on Windows 95, running PC-NFS pro2.0. The user uses ping(1M) to reach another computer on the network. ping(1M) returns Host Unknown.
This happens when name services are not set up correctly.
Action
-
Click the Windows 95 Start button, click Programs, click PC-NFSpro, then click Configuration.
-
Click TCP/IP and make sure all settings are entered correctly.
-
If NIS is enabled, click Configure NIS and make sure the NIS domain and server names are correct.
-
If DNS is enabled, click Configure DNS and make sure the DNS domain and server names are correct.
-
Click edit hosts and add the name and IP address of the machine you are trying to ping(1M), along with the authentication server.
If you make any changes, click OK, then click Save and Exit on the Configuration dialog box. Shut down and restart Windows 95.
ERROR: missing file arg (cm3)
Cause
An attempt was made to run some sccs(1) operation that requires a file name, such as create, edit, delget, or prt.
Action
Supply the appropriate file name 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 was 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 was 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
The user tries to mount the /export file system with Volume Manager 2.1.1 and gets this 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 file system is not a vxfs file system.
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.
ether_hostton errors from cb_reset
Cause
You issue cb_reset on an SSP and get the following:
cb_reset Resetting host snax-cb0... warning: ether_hostton(SrcHost:beer): Bad file number warning: ether_hostton(SrcHost:beer): Bad file number warning: ether_hostton(SrcHost:beer): Bad file number Resetting host snax-cb1... warning: ether_hostton(SrcHost:beer): Resource temporarily unavailable warning: ether_hostton(SrcHost:beer): Resource temporarily unavailable warning: ether_hostton(SrcHost:beer): Resource temporarily unavailable snax-cb0 is ready... snax-cb1 is ready... |
Action
/etc/nodename is probably incorrect. The following details are from a machine getting this error message. Note that /etc/nodename contains an alias to the real name of the SSP. To correct the problem, edit /etc/nodename to match the true name and reboot.
# cat /etc/nodename beer # cat /etc/hostname.qfe0 snax-ssp # cat /etc/hosts 127.0.0.1 localhost 129.153.49.179 snax-ssp beer loghost # cat /etc/ethers 8:0:20:87:58:a5 snax-ssp beer |
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 file system from backup tapes.
See Also
For more information on bad blocks, see the section on checking file system integrity in the System Administration Guide, Volume 1. If you are using AnswerBook online documentation, "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 file system from backup tapes.
See Also
For more information on blocks, see the section on checking file system integrity in the System Administration Guide, Volume 1. If you are using AnswerBook online documentation, "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 the programs on a SunOS 4.1 system, or when trying to execute SPARC-specific programs on an IA machine. This error can also occur if the Binary Compatibility Package was not installed.
Action
Make sure that the software matches the architecture and system you are using. The file(1) command can help you determine the target architecture. If you are using SunOS 4.1 software on a later release, 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.
- © 2010, Oracle Corporation and/or its affiliates