EVM daemon: configuration failure on startup

From: <stephane.moser_at_ruag.com>
Date: Mon, 08 Apr 2002 14:48:37 +0200

Hi everybody

Last week I installed TruCluster 5.1 A (+ Patchkit 1) on two DS20Es.

Now I have the following problem with EVM on both machine:

During the boot, I reveived this output...

Environmental Monitoring Daemon did not start...trying again
Environmental Monitoring Daemon did not start...trying again
Environmental Monitoring Daemon did not start after 3 tries.

I have equally this event...


============================ EVM Log event ===========================
EVM event name: sys.unix.evm.daemon.config_failure.startup

    This event is posted by the EVM daemon when it fails to configure
    itself at startup. Details of the failure are available from the
    daemon's log file, /var/evm/adm/logfiles/evmdaemon.log.

    Action: Review the daemon's log file to determine the reason for
    the failure. Once the problem has been corrected you can reload
    the configuration by running evmreload(8).

======================================================================

Formatted Message:
    EVM daemon: configuration failure on startup

Event Data Items:
    Event Name : sys.unix.evm.daemon.config_failure.startup
    Priority : 600
    PID : 1053947
    PPID : 1048577
    Event Id : 0
    Member Id : 2
    Timestamp : 08-Apr-2002 13:15:04
    Host IP address : 172.20.67.13
    Cluster IP address: 172.20.67.11
    Host Name : smpsm1
    Cluster Name : smpsm
    User Name : root
    Format : EVM daemon: configuration failure on startup
    Reference : cat:evmexp.cat:100

Variable Items:
    None

======================================================================


When I try to start EVM manually with "ewmstart" I receive this output...

2002-04-08 14:43:57 evmd: Failed to acquire lock
2002-04-08 14:43:57 evmd: Pathname of failed lock:
/var/evm/sockets/evmd.lck
evmstart: Daemon failed to start properly


I can manually delete the "/var/evm/sockets/evmd.lck" file and the evmstart
is working fine until the next reboot.

Any help are welcome.

Best regards,

Stéphane Moser
Received on Mon Apr 08 2002 - 12:49:11 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:43 NZDT