Happening on both servers, OES2 sp3 on SLES10 sp4 64 bit, both as guests on XEN SLES10 sp4 64 bit. 8GB
RAM, 4CPUs, 100GB root with lots unused. They have had issues previously with LUM, but I got that all
sorted out with only getting NetStorage to behave left to figure out, but that will be on the new boxes
we'll be migrating to next month (new VMware deployment)

SLES2:/var/log # cat /etc/*release
SUSE Linux Enterprise Server 10 (x86_64)
VERSION = 10
PATCHLEVEL = 4
LSB_VERSION="core-2.0-noarch:core-3.0-noarch:core-2.0-x86_64:core-3.0-x86_64"
Novell Open Enterprise Server 2.0.3 (x86_64)
VERSION = 2.0.3
PATCHLEVEL = 3
BUILD


/Var/log/messages is showing a steady stream (~20/second) of following

Jan 23 18:00:48 SLES2 [XTCOM]: novell-xsrvd: Server re-started after it terminated unexpectedly
Jan 23 18:00:48 SLES2 [XTCOM]: novell-xsrvd: Server re-started after it terminated unexpectedly
Jan 23 18:00:48 SLES2 novell-xsrvd-7[5930]: XSrvD -ServiceConnections- Unable to bind socket, error =
13
Jan 23 18:00:48 SLES2 novell-xsrvd-1[5935]: XSrvD -ServiceConnections- Unable to bind socket, error =
13

the change: applying the past 100 days or so of interactive patches along with applicate reboots.

CPU utilization is normal unless 'System Log Viewer' is launched, then gnome-system-log sucks up
most/all of one CPU and never displays the viewer that then needs to be killed. No other issues have
been seen other than /var/log/messages getting big (>100MB!)

The closest I can find is TID 7002867
http://www.novell.com/support/viewCo...2867&sliceId=1
that describes it exactly is happening except that all those rights are what they should be (that
wasn't the case a year ago, but I fixed them then)

SLES2:/usr/novell/sys # ls -la /var/opt/novell/xtier
total 2
drwxrwx--- 4 novlxregd novlxtier 416 Sep 12 01:21 .
drwxr-xr-x 22 root root 560 Nov 10 12:46 ..
drwxrwx--- 3 novlxregd novlxtier 104 Jan 23 09:49 xregd
drwxrwx--- 3 novlxsrvd novlxtier 1224 Sep 12 01:21 xsrvd

SLES2:/usr/novell/sys # ls -la /var/opt/novell/xtier/xsrvd/
total 125
drwxrwx--- 3 novlxsrvd novlxtier 1224 Sep 12 01:21 .
drwxrwx--- 4 novlxregd novlxtier 416 Sep 12 01:21 ..
drwx------ 2 novlxsrvd novlxtier 80 May 19 2009 .ssh
-rwx------ 1 novlxsrvd novlxtier 571 Jan 21 11:54 srv-cur-sessions-0.xml
-rwx------ 1 novlxsrvd novlxtier 571 Jan 21 11:54 srv-cur-sessions-1.xml
-rwx------ 1 novlxsrvd novlxtier 571 Jan 21 11:54 srv-cur-sessions-2.xml
...
-Rwx------ 1 novlxsrvd novlxtier 571 Jan 21 11:54 srv-cur-sessions-9.xml
-rwx------ 1 novlxsrvd novlxtier 4306 Jan 21 11:54 srv-ncpl-stats-0.xml
-rwx------ 1 novlxsrvd novlxtier 4306 Jan 21 11:54 srv-ncpl-stats-1.xml
...
-Rwx------ 1 novlxsrvd novlxtier 4306 Jan 21 11:54 srv-ncpl-stats-9.xml
srwxrwxrwx 1 novlxsrvd novlxtier 0 Nov 8 23:38 srv-socket-0
srwxrwxrwx 1 novlxsrvd novlxtier 0 Nov 8 23:38 srv-socket-1
...
Srwxrwxrwx 1 novlxsrvd novlxtier 0 Nov 8 23:38 srv-socket-9
-rw------- 1 novlxsrvd novlxtier 699 Mar 14 2011 xtier-stats

March 14th is when I started the patch process with taking OES2 sp0 to sp1 (they had been a neglected
set of systems that had a rough start to life)
LUM repairs were done in August/September along with getting OES up to sp3
November 8th was minor patching while adding new drive allocations that forced a XEN level reboot. But
you can clearly see that was the last time those socket files got updated.


Any ideas anyone? Even with XsrvD stopped, the System Log View won't come up.



Andy Konecny
KonecnyConsulting.ca in Toronto
------------------------------------------------------------------------
Andy's Profile: http://forums.novell.com/member.php?userid=75037