Thanks to
LHERCAUD_at_bouyguestelecom.fr
"Lavelle, Bryan" <Bryan.Lavelle_at_compaq.com>
Jem Treadwell <Jem.Treadwell_at_compaq.com>
The definitive answer comes from Jem:
> Hi, the event is posted by the EVM startup script, /sbin/init.d/evm.
> When the system goes to level 3, EVM, binlogd and syslogd should all
> be running, and binlogd and syslogd should normally be forwarding
> their events to EVM, for any further distribution. The script checks
> this by subscribing to EVM for binlog and syslog events, then posting
> test events to both daemons by using the "logger" and "logger -b"
> commands. If it doesn't get the events back via EVM, it posts the
> message you saw.
> You can check whether there really is a problem with communication
> using Bryan's suggestion, but run evmwatch to see if EVM is able to
> get the events:
> evmwatch -f '[name *.binlog]' -A &
> logger -b "test message"
> If forwarding is working correctly, evmwatch will display the event.
> If it doesn't, there may be a problem, so let me know and we'll try to
> figure it out.
> FYI, we've removed this check in Tru64 UNIX 5.1a (coming soon),
> because the message can show up incorrectly occsasionally, as a result
> of a timing issue. If it turns out that there's no problem, but
> you're seeing the message frequently, let me know, and we'll resolve
> it for you.
> Thanks, Jem Treadwell Tru64 UNIX Event Management Tech Lead
BTW, every Tru64 5.1 seems to give errors at each boot, just before
working well:
root> cat /var/evm/adm/logfiles/evmdaemon.log
2001-03-19 01:01:54 evmd: Authorization database built successfully.
2001-03-19 01:01:55 evmd: HostName at daemon is janon.univ-st-etienne.fr
2001-03-19 01:01:55 evmd: HostIp at daemon is 2a0103a1
2001-03-19 01:01:55 evmd: socket binding failed, errno - 49.
2001-03-19 01:01:55 evmd: Could not open remote accept socket
2001-03-19 01:01:55 evmd: Remote accept socket IN_ADDR_ANY is not open
2001-03-19 01:03:33 evmd: Received remote port activation event.
2001-03-19 01:03:33 evmd: HostName at daemon is janon.univ-st-etienne.fr
2001-03-19 01:03:33 evmd: HostIp at daemon is 2a0103a1
2001-03-19 01:03:33 evmd: Remote accept socket IN_ADDR_ANY is open
2001-03-19 01:03:33 evmd: Authorization database built successfully.
Suggestions were:
>From LHERCAUD_at_bouyguestelecom.fr:
> Try "logger -b ...." to see if that logs correctly.
> It may need to restart binlogd
and later:
> In fact binlogd uses 2 sinks for comm:
> 1. socket /dev/binlogdmb
> 2. UDP port 706 (binlogd per /etc/services)
> You can check with lsof that those sinks are well in use with the
> binlogd process and check which other process may have the same sink
> in use.
>From Bryan.Lavelle_at_compaq.com:
> Just because binlogd exists doesn't mean 1) it's working and 2) evm
> can communicate with it. Use the logger -b command to try and send a
> message to the binary.errlog, if that works, then it's just
> communication with EVM. If it doesn't work, then restart binlogd.
> In fact, restart it anyway. kill -HUP, and check it out again.
Original question:
Managers,
This morning I got this message:
--- CUT ---
Date: Mon, 19 Mar 2001 01:03:33 +0100 (CET)
Subject: EVM ALERT [600]: EVM admin msg: S97evm: Communication with binlogd is not functioning
============================ EVM Log event ===========================
EVM event name: sys.unix.evm.msg.admin
The administrator's "quick message" event is posted by evmpost(1)
when it is run with the "-a" option. The event is intended to be
used to add a message entry in the event log. Authorization to
post this event is restricted through EVM's authorization
database.
The priority of the event can be specified by the administrator
when the event is posted.
======================================================================
Formatted Message:
EVM admin msg: S97evm: Communication with binlogd is not functioning
Event Data Items:
Event Name : sys.unix.evm.msg.admin
Priority : 600
PID : 3191
PPID : 3154
Event Id : 99
Timestamp : 19-Mar-2001 01:03:33
Host IP address : 161.3.1.42
Host Name : janon.univ-st-etienne.fr
User Name : root
Format : EVM admin msg: $message
Reference : cat:evmexp.cat:100
Variable Items:
message (STRING) = "S97evm: Communication with binlogd is not functioning"
======================================================================
--- CUT ---
This is an XP1000 running Tru64 5.1 PK2 for weeks, rebooting every Monday.
I never got the message before and don't understand what it means.
I can see with ps:
root 302 1 0.0 01:01:58 ?? 0:00.02 /usr/sbin/binlogd
and everything seems to be working fine.
Thanks for your help,
--
_______________________________________________________________________
Magali BERNARD (Magali.Bernard_at_univ-st-etienne.fr)
CRITeR - 23 rue du Dr Paul Michelon - 42023 St-Etienne Cedex 2 - FRANCE
Tel: 04.77.48.50.62 Fax: 04.77.48.50.69
Received on Tue Mar 20 2001 - 08:57:46 NZST