From: Shaun.Racine@intier.com
Date: Mon Sep 22 2003 - 04:27:55 EDT
Dear Managers,
Tru64 5.1A PK4 (T64V51AB21AS0004-20030206 OSF520)
Checking the logs on our development server I have found this (first
occurrence since upgrade to 5.1A in April 2003);
svrMgt_mib[681]: svrMgt_mib **ERROR svrMgt_mib.c line 332: Could not start.
Last error was:
Is it anything to worry about? (server appears to be running OK)
I did find this on the archives;
http://www.ornl.gov/cts/archives/mailing-lists/tru64-unix-managers/1998/07/msg00055.html
which suggested errors like these are meant to be suppressed?
TIA for any guidance.
Viewing more details on our system showed this only;
bob:root> evmget -f "[time 2003:09:20:*:02:27:25]"|evmshow -d
============================ Syslog event ============================
EVM event name: sys.unix.syslog.daemon
Syslog daemon events are posted by system daemons to alert the
administrator to an unusual condition. The user name field usually
indicates which daemon posted the event. The text of the message
indicates the reason for the event.
======================================================================
Formatted Message:
svrMgt_mib[681]: svrMgt_mib **ERROR svrMgt_mib.c line 332: Could not
start. Last error was:
Event Data Items:
Event Name : sys.unix.syslog.daemon
Priority : 300
PID : 364
PPID : 1
Event Id : 8076
Timestamp : 20-Sep-2003 02:27:25
Host IP address : 172.28.32.19
Host Name : bob
User Name : root
Format : svrMgt_mib[681]: svrMgt_mib **ERROR svrMgt_mib.c
line
332: Could not start. Last error was:
Reference : cat:evmexp.cat:200
Variable Items:
None
======================================================================
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:36 EDT