envd startup message

[jmb]

This is a dev server, and I've been making various changes on it. Recently after reboot, during the startup checklist, I'm getting this message displayed on the console:

/usr/bin/envd[1267]: restart, and read the configuration file.

It does not appear to be related to a specific location in the checklist, and I've looked at the SL errors in the GSP and seen nothing.

How can I pursue this?

[Floyd Curtis]

look in /etc/rc.config.d/envd
for startup being set to 1

This is an environmental monitor daemon. Depending upon your model, it can be used/notify for certain hardware monitored enviromental conditions.. temperature for example...Since you have GSP - you may want to have it running (N, L, ) class? because those models do monitor temperature.

The envd.conf file configs what it monitors and such.

good luck,
fwc

[Hazem Mahmoud_3]

Check the /etc/envd.conf file to make sure it looks fine (mine is shown below). envd logs to syslog (/var/adm/syslog/syslog.log), so check there to see if you can find the root of the problem. Hope that helps!

-Hazem

/etc/envd.conf:

# more /etc/envd.conf
# @(#)B.11.11_LR
# envd reads its configuration information when the envd daemon
# starts, and when it receives a SIGHUP signal to restart itself.
#
# This configuration file contains comment lines, event lines,
# and action lines. Lines beginning with the # character in
# the first column are comment lines, and all characters
# up to the subsequent new-line character are ignored.
# The syntax of event lines and action lines are:
#
# event:message_indicator
# action
#
# The event line is composed of two fields: event and message_indicator;
# single colon separated, without any blanks interspersed. Recognized
# events include OVERTEMP_CRIT, OVERTEMP_EMERG, FANFAIL_CRIT, and
# FANFAIL_EMERG. The message indicator field takes only a binary value,
# and may be specified as either 'y' or 'n', indicating to log event messages,
# or not, upon the occurrence of an event. All event lines must start from
# the first column of the line. Invalid event lines will be taken
# as action lines.
#
# The action lines for an event may span across several lines,
# but the syntax of every line must be understood by /usr/bin/sh.
# No parsing or syntax checking is performed on the action lines.
#
# The example below configures envd to log the warning message at
# OVERTEMP_CRIT or FANFAIL_CRIT, and to log emergency messages and perform
# system shutdown immediately at OVERTEMP_EMERG or FANFAIL_EMERG, in order
# to preserve data integrity.

OVERTEMP_CRIT:y

OVERTEMP_EMERG:y
/usr/sbin/reboot -qh

FANFAIL_CRIT:y

FANFAIL_EMERG:y
/usr/sbin/reboot -qh

[Floyd Curtis]

BTW if you need a "pristine" copy of /etc/envd.conf look in /usr/newconfig/etc/envd.conf

This is a good place to get back to a known starting point on most config files.

fwc

[jmb]

In each of the above files, everything is looking 100%. The newconfig file matches exactly the file in /etc, and ENVD=1 is in the other file. None of them have been modiified.

I've made some syslog changes, and I'm wondering if there's any relationship between that and the envd message..

[Floyd Curtis]

Looking back at the original problem, its not a warning or error, so it looks to me like its informational. If you see many restart messages, then I suspect there is a problem, but as the previous poster stated, it logs to syslog, so it may well be being restarted normally. If you don't have messages related to what its monitoring.. (see the envd.conf file) then maybe not to worry....;)

fwc