"R"

Read error from network: Connection reset by peer

Cause

This message appears when a user logs in remotely to a machine that crashes or is rebooted during the rlogin(1) or rsh(1) session. Any data changes that were not saved are probably lost. Sometimes this message appears only when the user types some data, even though the system failed hours before.

Action

Try to rlogin(1) again, perhaps after waiting a few minutes for the system to reboot.

Reading configuration data

Cause

In this situation, the user loaded SunPC 4.1 on a SPARCstation 5 machine. The Solaris 2.5 operating environment is patched to the Solaris 2.5.1. The user also has a SunPC accelerator card installed. When starting SunPC, the user gets this error message on the SunPC splash screen. If the user clicks anywhere in the screen, the whole console locks. The user has to move to another machine and use rlogin and then kill the SunPC process. In an effort to resolve the problem, the user had installed and removed SunPC and the 102924-25 patch with the same results. The user also removed the accelerator card, performed a boot -r and still SunPC 4.1 hung at the splash screen. The following error was found in the /var/adm file:

modrput() sdos_mbsigolint failed -1

Action

In this situation, the user had wiped the operating system off the SPARCstation 5 machine and, at that point, was not sure which patches had been applied. The user installed a copy of the Solaris 2.5.1 software and, then, performed the SunPC installation. That solved the problem. SunPC worked without the Accelerator card. The user added the Accelerator card, performed a boot -r, and ran SunPC with no problems.

Read-only file system

Cause

Files and directories on file systems that are mounted read-only cannot be changed.

Action

If you only modify these files and directories occasionally, use rlogin(1) to log in to the servers of the mounted file systems and change the files or directories from there.

If you change these files and directories frequently, use mount(1M) to make the file systems read-write.

Technical Notes

The symbolic name for this error is EROFS, errno=30.

rebooting...

Cause

This message appears on the console to indicate that the machine is booting, either after the superuser issued a reboot(1M) command, or after a system panic, if the EEPROM's watchdog-reboot? variable is set to true.

Action

Allow the machine to boot itself. In case of a system panic, look above this message for other indications of what went wrong.

Recipient names must be specified

Cause

Someone sent mail without a valid recipient in the To: field. Thus, sendmail(1M) could not deliver the mail message. Using mail(1), the recipient's address might have been specified using spaces or non-alphanumeric characters. The mailtool(1) and mailx(1) commands try to prevent such problems by issuing Please specify a recipient or No recipients specified messages instead. If at least one valid recipient exists, each invalid recipient address will generate a User unknown message.

Action

Look in the sender's dead.letter file for the automatically saved message, and have the originator send it again; this time the sender specifies a recipient.

See Also

For more information about sendmail(1M), see the System Administration Guide, Volume 3.

refused connect from hostIP to callit(ypserv)

Refer to "connect from hostIP to callit(ypserv): request from unauthorized host".

Reset tty pgrp from int to int

Cause

The C shell sometimes issues this message when it clears away the window process group after the user exits the window system. This clearing can happen when the window system does not clean up after itself.

Action

Proceed with your work. This message is only informational.

Resource temporarily unavailable

Cause

This error indicates that the fork(2) system call failed because the system's process table is full, or that a system call failed because of insufficient memory or swap space. Also, a user might not be allowed to create more processes.

Action

Simply waiting often gives the system time to free resources. However, if this message occurs often on a system, reconfigure the kernel and allow more processes. To increase the size of the process table, increase the value of MAXUSERS in the /etc/system file. The default MAXUSERS value is the amount of main memory in Mbytes, minus 2.

If one user is not allowed to create any more processes, that user has probably exceeded the memory size limit; see the limit(1) man page for details.

Technical Notes

The symbolic name for this error is EAGAIN, errno=11.

Restartable system call

Action

Restart the interrupted system call.

Technical Notes

The symbolic name for this error is ESTART, errno=91.

Result too large

Cause

This is a programming error or a data input error.

Action

Ask the program's author to fix this condition.

Technical Notes

This error indicates an attempt to evaluate a mathematical programming function at a point where its value would overflow or underflow. The value of a programming function in the math package (3M) is not representable within machine precision. This error could occur after floating point overflow or underflow (either single or double precision), or after total loss of numeric significance in Bessel functions.

This message can indicate Result too small in the case of floating point underflow.

To help pinpoint a program's math errors, use the matherr(3M) facility.

The symbolic name for this error is ERANGE, errno=34.

rlogin: no directory! connection closed

Cause

When a user tries to remotely log in to a machine, the user gets this error.

The machine that the user was trying to access with rlogin(1) had permissions of 700 on its root directory. The permissions on root should be 755.

After the permissions on the root file system were changed to 755, the user was able to proceed farther when attempting to execute an rlogin, but it still failed with the following:

Last login: Fri Aug 29 10:24:43 from machinename
no shell
connection closed

Action

The machine that the user was trying to access with rlogin had the permissions set to 700 on both the root and /usr/bin directories. For both directories, the permissions should be 775. Once the user changed the permissions to 775, rlogin(1) was successful.

Also, check the user's passwd(1) entry in the NIS/NIS+ map. A login shell such as /usr/dist/exe/tcsh or /net/lab/.../csh could cause the failure because of NFS mount permission.

rmdir: string: Directory not empty

Cause

The rmdir(1) command can only remove empty directories. The directory with the name appearing after the first colon in the message still contains some files or directories.

Action

Use rm(1) instead of rmdir(1). To remove this directory and everything underneath it, use the rm -ir command to descend the directory recursively, and respond to requests to delete each element. To remove the directory and all its contents without prompts for approval, use the rm -r command.

ROOT LOGIN /dev/console

Cause

This syslog message indicates that someone has logged in as root on the system console.

Action

If you have just logged in as root, take no action. If you are not root, consider the possibility of a security breach. The best site-wide policy is for all system administrators to use su(1M) instead of logging in as root.

ROOT LOGIN /dev/pts/int FROM string

Cause

This syslog message indicates that someone has logged in remotely as root on a pseudo-terminal from the system specified after the FROM keyword.

Action

For security reasons, it is a bad practice to allow root logins from anywhere other than the console. To restrict superuser logins to the console, remove the comment from the CONSOLE line in /etc/default/login.

route: socket: Protocol not supported

Cause

During a boot, this error is displayed and the multicast is not configured.

Action

An inittab(4) from a previous release of the operating environment was used. Thus, the following entry, which is required for the route command in the Solaris 2.6 release, was missing from /etc/inittab.

ap::sysinit:/sbin/soconfig -f /etc/sock2path

RPC: Program not registered

Cause

Check the rpc.bynumber NIS map.

rx framing error

Cause

Usually this error indicates a hardware problem.

Action

Check the Ethernet cabling and connectors to locate a problem.

Technical Notes

A framing error occurs when the Ethernet I/O driver receives a non-integral unit of octets, such as 63 bytes and then 3 bits. (Ethernet specifies the use of octets.) Framing errors are caused by corruption of the starting or ending frame delimiters. These delimiters can be corrupted by some violation of the encoding scheme.

Framing errors are a subset of CRC errors, which are usually caused by anomalies on the physical media. An alignment/framing error is a type of CRC error where octet boundaries do not align.