"L"

last message repeated int times

Cause

This message comes from syslogd(1M), the facility that prints messages on the console and records them in /var/adm/messages. To reduce the log size and minimize buffer usage, syslog collapses any identical messages it sees during a 20 second period, then prints this message with the number of repetitions.

Action

Look above this message to see which message was repeated so often. Then consider the repeated message and take action accordingly. If repeated log entries such as su ... failed appear, consider the possibility of a security breach.

ld.so.1 fatal: can't set protection on segment

Cause

Applications have recently begun to fail with this error: ld.so.1 fatal: can't set protection on segment. The failures are random.

Action

This was happening because of the recent introduction of a rogue application that consumed most of the swap space on the system. The other applications, which failed randomly, were doing so because of insufficient swap space to run. The error from ld.so.1 happened because there was no segment on which to set the protections.

ld.so.1: string: fatal: string: can't open file: errno=2

Cause

This message is produced in Solaris 2.5.1 and earlier releases. It is not produced in Solaris 2.6, or later releases.

See the next message, which has the same cause.

Action

See the next message, which can be resolved by the same action.

See Also

For more information about the Linker, see the Linker and Libraries Guide.

ld.so.1: string: fatal: string: open failed: No such file or directory

Cause

This message is produced in Solaris 2.6 and later releases. It is not produced in Solaris 2.5.1, or earlier releases.

This message indicates that the run time linker, ld.so.1(1), while running the program specified after the first colon, could not find the shared object specified after the third colon. (A shared object is sometimes called a dynamically linked library.)

Action

As a workaround, set the environment variable LD_LIBRARY_PATH to include the location of the shared object in question, for example:

/usr/dt/lib:/usr/openwin/lib

See Also

For more information about the Linker, see the Linker and Libraries Guide.

ld.so.1: string: fatal: relocation error: symbol not found: string

Cause

This message is produced in Solaris 2.5.1 and earlier releases. It is not produced in Solaris 2.6, or later releases.

See the next message, which has the same cause.

Action

See the next message, which can be resolved by the same action.

Technical Notes

This error does not necessarily occur when you first bring up an application. It could take months to develop, if ordinary use of the application seldom references the undefined symbol.

See Also

For more information about the Linker, see the Linker and Libraries Guide.

ld.so.1: string: fatal: relocation error: string: string: referenced symbol not found

Cause

This message is produced in Solaris 2.6 and later releases. It is not produced in Solaris 2.5.1, or earlier releases.

The message from the run time linker ld.so.1(1) indicates that in trying to execute the application given after the first colon, the specified symbol could not be found for relocation. The message goes on to say in what file the symbol was referenced. Since this is a fatal error, the application terminates with this message.

Action

Run the ldd -d command on the application to show its shared object dependencies and symbols that aren't found. Probably your system contains an old version of the shared object that should contain this symbol. Contact the library vendor or author for an update.

Technical Notes

This error does not necessarily occur when you first bring up an application. It could take months to develop, if ordinary use of the application seldom references the undefined symbol.

See Also

For more information about the Linker, see the Linker and Libraries Guide.

le0: Memory error!

Cause

This message indicates that the network interface encountered an access time-out from the CPU's main memory. There is probably nothing wrong except system overload.

Action

If the system is busy with other processes, this error can occur frequently. If possible, try to reduce the system load by quitting applications or killing some processes.

Technical Notes

The Lance Ethernet chip timed out while trying to acquire the bus for a DVMA transfer. Most network applications wait for a transfer to occur, so generally no data gets lost. However, data transfer might fail after too many time-outs.

See Also

For more information about the Lance Ethernet chip, see the le(7D) man page.

le0: No carrier-- cable disconnected or hub link test disabled?

Cause

Standalone machines with no Ethernet port connection get this error when the system tries to access the network. If the Ethernet cable is disconnected, SPARC machines with the sun4m architecture usually display this message, whereas machines with the sun4c architecture usually display the "le0: No carrier-- transceiver cable problem" message instead. If the Ethernet cable is connected, this message could result from a mismatch between the machine's NVRAM settings and the Ethernet hub settings.

Action

If this message is continuous, try to save any work to local disk.

When a machine is configured as a networked system, it must be plugged into the Ethernet with a twisted pair J45 connector.

If the Ethernet cable is plugged in, find out whether or not the Ethernet hub does a Link Integrity Test. Then become superuser to check and possibly set the machine's NVRAM. If the hub's Link Integrity Test is disabled, set this variable to false.

# eeprom | grep tpe
tpe-link-test?=true
# eeprom 'tpe-link-test?=false'

le0: No carrier-- transceiver cable problem?

Cause

Standalone machines with no Ethernet port connection get this error when the system tries to access the network.

Action

If this message is continuous, try to save any work to local disk.

When a machine is configured as a networked system, it must be plugged into the Ethernet with either a twisted pair J45 connector or thicknet 10Base-T connector (depending on the building's Ethernet cable type).

Technical Notes

Older workstations have a thicknet connection on the back instead of a twisted pair Ethernet connection, so they require a thicknet to twisted pair transceiver to translate between cabling types.

level 15 interrupt

Cause

on an SS20

.lib section in a.out corrupted

Cause

Trying to exec(2) an a.out(4) that requires a static shared library (to be linked in) and there was erroneous data in the .lib section of the a.out(4). The .lib section tells exec(2) which static shared libraries are needed. The a.out(4) is probably corrupted.

Technical Notes

The symbolic name for this error is ELIBSCN, errno=85.

LINK COUNT FILE I=i OWNER=o MODE=m SIZE=s MTIME=t COUNT... ADJUST?

Cause

During phase 4, fsck(1M) determined that the inode's link count for the specified file is wrong, and asks if you want to adjust it to the value given.

Action

Generally you can answer yes to this question without harming the filesystem.

See Also

For more information on fsck(1M), see the section on checking filesystem integrity in the System Administration Guide, Volume I.

Link has been severed

Cause

This error occurs when the connection to a remote machine is gone, for example after a remote procedure call is interrupted.

Technical Notes

The symbolic name for this error is ENOLINK, errno=67.

LL105W: Protocol error detected.

Cause

This error message comes from Lifeline Mail, an unbundled PC compatibility application.

Action

The likeliest cause for this problem is that someone set up a user account without a password. Assign the user a password to solve this problem.

ln: cannot create /dev/fb: Read-only file system

Cause

During device reconfiguration at boot time, the system cannot link to the frame buffer because /dev is on a read-only filesystem.

Action

Check that /dev/fb is a symbolic link to the hardware frame buffer, such as cgsix(7D) or tcx(7D). Ensure that the filesystem containing /dev is mounted read-write.

lockd[int]: create_client: no name for inet address 0xhex

Cause

This lock daemon message usually indicates that the NIS hosts.byname and hosts.byaddr maps are not coordinated.

Action

Wait a short time for the maps to synchronize. If they don't, take steps to coordinate them.

See Also

For information on updating NIS data, see the section on NIS maps in the NIS+ and FNS Administration Guide. If you are using the AnswerBook, "hosts.byaddr" is a good search string.

Login incorrect

Cause

This message from the login(1) program indicates an incorrect combination of login name and password. There is no way to tell whether what's wrong is the login name, the password, or both. Other programs such as ftp(1), rexecd(1M), sulogin(1M), and uucp(1C) also give this error under similar conditions.

Action

Check the /etc/passwd file and the NIS or NIS+ passwd map on the local system to see if an entry exists for this user. If a user has simply forgotten the password, su(1M) and set a new one with the passwd(1) username command. This command automatically updates the NIS+ passwd map, but with NIS you'll need to coordinate the update with the passwd map.

The "Login incorrect" problem can also occur with older versions of NIS when the user name has more than eight characters. If this is the case, edit the NIS password file, change the user name to have eight or fewer characters, and then remake the NIS passwd map.

If you cannot log in to the system as root, despite knowing the proper password, it is possible that the /etc/passwd file is corrupted. Try to log in as a regular user and su(1M) to root.

If that doesn't work, see the message "su: No shell" and follow most of the instructions given there. Instead of changing the default shell, make the password field blank in /etc/shadow.

lp hang

Cause

On a print server, the queue continues to grow but nothing comes out of the printer. The printer daemon is hung.

Action

Here is a simple procedure for flushing a hung printing queue: 1. Login or switch user to root; 2. Issue the reject(1M) printername command to make sure no one sends any job to the printer; 3. Turn off power to the printer; 4. If the active job appears to be causing the hang, remove it from the print queue with the cancel(1) jobnumber command, and ask the owner to requeue that print job; 5. Shut down the print queue with the /usr/lib/lpshut command; 6. Remove the lock file /var/spool/lp/SCHEDLOCK and the temporary files /var/spool/lp/tmp/*/*; 7. Turn the printer back on; 8. Restart the print queue with the /usr/lib/lpsched command.

See Also

For more information on print queuing, see the System Administration Guide, Volume II. If you are using the AnswerBook, "print server" is a good search string.