Hi all.
We have just re-installed a couple of our production servers, from DU 3.2G to DU
4.0D. We didn't do upgrade, but fresh install. I'm seeing some error messages
that look benign, but I'd like some advice, nevertheless.
Some intro data:
MACHINE1: AlphaServer 4100, AXP 21164 300 MHz, 512 MB RAM
MACHINE2: AlphaServer 4100, AXP 21164 350 MHz (I think),
RAM: 512 MB RAM
VGA: #9 S3 Trio64
SCSI: RRD45 (CDROM), TLZ09 (DDS2 DAT)
DISK: KZPSC (Mylex RAID)
-------
The two machines are definitely different series, I'm not sure about the speed.
Well, MACHINE1 (older) gives the following in it's logs:
daemon.log:
Nov 11 19:05:44 EDSO [400]: **ERROR svrsys_fru_parse.c line 1031: FRU Table
revision 2.0 is not supported
kern.log:
Nov 11 19:05:34 EDSO vmunix: Created FRU table binary error log packet
This last message appears just below "trio0" entry. On DU3.2G I used to get an
error message "CAM Error... LUN=06", which regarded to DAT. FRU, now that is
something that belongs to the firmware, right?
Should I upgrade firmware?
------
On both machines I'm getting this message. It is for Environment Monitoring
daemon (envmond). It seams to be configured, it is running, but why is it
complaining?
Nov 8 19:24:38 EDRU [404]: Initializing the thresold structure
Nov 8 19:24:38 EDRU [404]: WARNING svrMgt_persist.c line 364: error m opening
/etc/thresholds.dat
Nov 8 19:24:38 EDRU [404]: WARNING svrMgt_persist.c line 127: error m linking
/etc/thresholds.dat and /etc/thresholds.dat.bak
------
Nov 9 09:46:54 EDRU telnetd[4637]: ttloop: peer died: Error 0 occurred.
I reckon this is due to bad network, but is there a comprehensive explanation of
telnetd error messages?
TYIA, I'll summarize.
Nix.
--
... And there were plagues of locusts and frogs and MS-DOS, ...
Received on Fri Nov 12 1999 - 07:34:42 NZDT