Oracle Solaris System Administration (MOSC)

MOSC Banner

another occurrence of time standing still and rocky return to normalcy

edited Jun 11, 2013 12:57PM in Oracle Solaris System Administration (MOSC) 2 commentsAnswered
I've had an infrequent but reoccurring problem with an X4500 after installing CPU_2013-04 on Solaris 10u10.
I believe the most common occurrence shows up in /var/adm/messages as:

Jun  4 07:38:08 beaker sshd[24479]: [ID 800047 auth.crit] fatal: Write failed: Broken pipe
Jun  4 07:38:08 beaker sshd[24499]: [ID 800047 auth.crit] fatal: Write failed: Broken pipe

but on two occasions Solaris appears to have been in a coma  for some length of time and then wakes up.

During the coma I see gaps in timestamps for /var/adm/messages.  sar records odd timestamps - here's a sample from today:
sar -u -f /var/adm/sa/sa04 -s 05:30 -e 08:00

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center