Sponsored Content
Operating Systems AIX /var/adm/messages file is missing Post 302424226 by gkr747 on Monday 24th of May 2010 04:41:10 PM
Old 05-24-2010
I am talking about the messages file not WTMP file...The file should contain console messages...I think somebody may have deleted it by mistake...need to know the process to recreate it so that it works again

---------- Post updated at 04:41 PM ---------- Previous update was at 02:27 PM ----------

I have recreated the file and restarted the syslogd daemon...that fixed the issue and now messages are flowing just fine...issue is resolved...just thought of letting know here..thanks!
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Messages in /var/adm

Just want to check with all of you out there what does the following warning means in my "messages" file in /var/adm the warning is Prevous Time Adjustment Incomplete , does it mean my hard ware is faulty if so which piece of hardware it is ? (1 Reply)
Discussion started by: owls
1 Replies

2. Solaris

/var/adm/messages

I'm running a Solaris 9 box with Oracle databases on it. I'm getting the following messages in my /var/adm/messages log "Jun 24 12:30:32 sundb01 bootpd: IP address not found: xxx.xxx.xxx.xxx" ...where xxx.xxx.xxx.xxx is DHCP IP addresses of Windows 2000 workstations in the organisation. ... (2 Replies)
Discussion started by: soliberus
2 Replies

3. UNIX for Dummies Questions & Answers

/var/adm/messages

Hi, No log entry is found in messages files. The file size is 0. We are using Solaris 9. Anyone knows what could be wrong. (3 Replies)
Discussion started by: FrankC
3 Replies

4. Solaris

/var/adm/messages

Hello Friends, I am geting the folowing error in /var/adm/message is it disl related problem? if yes.. how to check all the disk are perfect or not? Sep 15 06:01:12 scsi: WARNING: /pci@1f,700000/scsi@2/sd@2,0 (sd7): Sep 15 06:01:12 Error for Command: write(10) Error Level:... (5 Replies)
Discussion started by: bullz26
5 Replies

5. Solaris

/var/adm/messages

Check message file and result posted below. Can anyone tell me what this is a sign of, what does it mean? server1% more messages.0 Dec 02 09:35:06 server1 bsd-gw: Inval id protocol request (65): AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA^\\2... (6 Replies)
Discussion started by: finster
6 Replies

6. Solaris

diff b/w /var/log/syslog and /var/adm/messages

hi sirs can u tell the difference between /var/log/syslogs and /var/adm/messages in my working place i am having two servers. in one servers messages file is empty and syslog file is going on increasing.. and in another servers message file is going on increasing but syslog file is... (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies

7. Solaris

/var/adm/messages file rotation

I have a solaris 10 machine, lately I had a drive error issue so the dmesg command would show a screen full, now that the drive issue is resolved I want to have a fresh start for my #dmesg command output. The root cron looks like this The /etc/logadm.conf file has this entry If I manually... (2 Replies)
Discussion started by: Tirmazi
2 Replies

8. UNIX for Advanced & Expert Users

/var/adm/messages vs /var/log/messages

The /var/adm/messages in Solaris seem to log more system messages/errors compared to /var/log/messages in Linux. I checked the log level in Linux and they seem OK. Is there any other log file that contains the messages or is it just that Linux doesn't log great many things? (2 Replies)
Discussion started by: gomes1333
2 Replies

9. Shell Programming and Scripting

trying get the last /var/adm/messages

grep \"^`date "+%b %d %T"`\" /var/adm/messages | egrep \"emerg|alert|crit|err|warning\ but get an output like this ksh: alert: not found ksh: crit: not found ksh: err: not found ksh: warning": not found grep: can't open "19" grep: can't open "16:27:16"" (1 Reply)
Discussion started by: arch12
1 Replies

10. Solaris

Difference between /var/log/syslog and /var/adm/messages

Hi, Is the contents in /var/log/syslog and /var/adm/messages are same?? Regards (3 Replies)
Discussion started by: vks47
3 Replies
esmd(1M)																  esmd(1M)

NAME
esmd - Essential Services Monitor (ESM) Daemon SYNOPSIS
retry_seconds] DESCRIPTION
The Essential Services Monitor (ESM) daemon, maintains the availability of essential system daemons by automatically restarting them if they terminate. The ESM daemon monitors the Event Manager daemon, The ESM daemon is started by the init process when the system is ini- tialized to run level 2 and continues to run until the system is shut down or returned to single user mode. Only one instance of can run at a time. Configuration information is sent to the ESM daemon by a control program, which is run at key points in the startup and shutdown proce- dures. As startup or shutdown progresses, the control program updates the ESM state file, The control program then signals the daemon to reconfigure itself. On startup, state transitions occur after has started. On shutdown, transitions occur after each of these monitored daemons has termi- nated. After each transition, the ESM daemon determines which of the monitored daemons should be running and adjusts its monitoring activ- ities accordingly. The ESM daemon reports all state change information, including notice of failures and restarts, through the system logging daemon, syslogd. Messages are displayed on the system console during periods when syslogd is not running. See syslogd(1M) for more information. If the ESM daemon fails to restart a monitored daemon, it reports the error by posting a high priority message through syslogd, and makes no further restart attempts. The system administrator should investigate the problem and restart the failed daemon. The ESM daemon peri- odically attempts to resume monitoring of the daemon, and posts an informational message when it succeeds. If the monitored daemon fails again once monitoring has resumed, the ESM daemon again attempts to restart it. The ESM daemon can be forced to restart a failed daemon by sending a SIGHUP signal to the process. If there is a need to temporarily disable the ESM daemon for test purposes, in order to prevent the monitored daemons from being restarted automatically, send a SIGSTOP signal to the process. To reactivate the ESM daemon, send a SIGCONT signal to the process. The ESM daemon should never be disabled on a production system. If the ESM daemon is terminated unexpectedly, it is restarted automatically by init. Options The command recognizes the following options: Limit the priority of any syslog messages posted by the ESM daemon to "alert." If this option is not specified, posts an "emergency" message if it cannot restart a failed daemon. A message may be sent to all users currently logged in to the system. The option should only be used if the system administrator is actively monitoring syslogd messages. Specify the interval between attempts to begin monitoring a daemon that has failed, and which has been unable to restart automatically. The default period is 30 seconds. Specifying a period of zero disables retrying. Notes To use the start options, you must add them to the startup command in the file. The daemon reports any invalid start options with a single generic message through syslogd. Restrictions The daemon terminates with an error message if it is started by any process other than init. The /sbin/init.d/esm program is intended to be run by the system startup and shutdown process and should not be run from the command line. Only one instance of can run at a time. RETURN VALUE
The following exit values are returned: 0 (Zero) Successful completion. not 0 An error occurred. FILES
Executable file Configuration control script Initialization process control file dispatched by boot init Monitoring state file Receives esmd status messages AUTHOR
was developed by Hewlett Packard Company. SEE ALSO
Commands kill(1), evmd(1M), init(1M), syslogd(1M). Files inittab(4). esmd(1M)
All times are GMT -4. The time now is 04:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy