can't start errdemon

[rcbatlinux]

I believe at some point the /var/adm/ras/errlog file was removed. Anyone know how to recreate this? I can't get the errdemon to start (ie /usr/lib/errdemon) I've tried errdemon -ierrlog but no luck.

rcbatlinux

 

[aixqueen]

The /var filesystem may be full? If it is errlogging will stop....?

/var/adm/ras should have 3 files for errlogging

/var/adm/ras/errlog
/var/adm/ras/errtmplt #Error log templates
codepoint.cat # Contains the error log message catalog (sometimes in /usr/lib/nls/msg/$LANG/codepoint.cat

ARe any of these zero? If so restore from mksysb....Also if you issue the
command
To start the error-logging daemon, enter:
/usr/lib/errdemon

It will create a new errlog file...if it is deleted...

If there is enough space in /var, if the permissions on the directory have not been changed...and you are doing as root.......and the errtmplt file is there and not zero...

 

[rcbatlinux]

Ok... the /var has plenty of disk space. Unfortunately this I believe happened a long time ago. The last date on the errlog was in 1999! (customer's system) Any how the errtmplt is there and has size to it. I have tried the command within the /usr/lib errstop, errdemon but the demon process doesn't start, doesn't give an error or anything either. I'm trying to send a errlog file from another aix system there but not sure if that will work. hmmm


rcbatlinux

 

[aixqueen]

-rw-r--r-- 1 bin bin 197206 Apr 20 09:33 codepoint.cat
-rw-r--r-- 1 root system 47857 Jul 25 12:00 errlog
-r--r--r-- 1 bin bin 110900 May 21 17:01 errtmplt

you also tried errclear 0
then /usr/lib/errdemon to see if it started?
no errors? Is anything else full like root or /tmp?

If you have an old backup newer than 1999..you might consider restoring the 3 files...then do an errclear 0

Or if you have a similar one...I have done that as well..........
That is strange...........

 

[aixqueen]

http://www.rs6000.ibm.com/doc_link/en_US/a_doc_lib/cmds/aixcmds2/errdemon.htm#A243Y988af

The error logging daemon reads error records from the /dev/error file and creates error
log entries in the system error log. Besides writing an entry to the system error log each
time an error is logged, the error logging daemon performs error notification as specified
in the error notification database. The /etc/objrepos/errnotify file is the error
notification database. The default system error log is maintained in the
/var/adm/ras/errlog file. The last error entry is placed in nonvolatile random access
memory (NVRAM). During system startup, this last error entry is read from NVRAM
and added to the error log when the error logging daemon is started.

The error logging daemon does not create an error log entry for the logged error if the
error record template specifies Log=FALSE.

If you use the error logging daemon without flags, the system restarts the error logging
daemon using the values stored in the error log configuration database for the error log
file name, the error log file size, and the internal buffer size.

is /dev/error there and /etc/objrepos/errnotify there?

/dev>#ls -la err*
crw--w--w- 1 root system 6, 0 Jul 25 00:00 error
/etc/objrepos>#ls -la err*
-rw-rw-r-- 1 root system 49152 Jul 25 04:00 errnotify

last resort I guess is to find a patch for bos.rte.serv_aids