hi, fellows
So far I have received several response, all suggested checking permission
of
device file , such as /devices/cn@0:systty, /devices/cn@0:syscon ,
/devices/cn@0:console, /devices/log@0:conslog , /devices/log@0:log, and
the links point to them in /dev directory, or restart it through
/etc/init.d/syslog. I
have remove all these device file, and use drvconfig , devlinks to rebuild
them,
I also replaced the syslogd file from other workstation that running well,
and
restart syslogd several times . again , I install the newest kernel patch
105181-21 , and all other recommended patch. all no use.
Has anyone good idea ? what's bad address come from ? any suggestion ?
sincerely likun
original question:
Hi , all
ever anyone encounter such problem ?
OS: Solaris2.6 with kernel patch 105181-19
Platform: E3500
syslogd can't get started.
#syslogd -d got following error:
syslogd: cannot register to log console messages: Bad address
cannot register to log console messages (0)
from truss syslogd got :
19642: open("/dev/log", O_RDONLY) = 13
19642: ioctl(13, I_STR, 0xEE9C34CC) Err#14 EFAULT
19642: open("/dev/console", O_WRONLY|O_APPEND|O_NOCTTY) = 14
19642: llseek(14, 0, SEEK_END) = 0
19642: fstat64(14, 0xEE9C21B0) = 0
19642: ioctl(14, TCGETA, 0xEE9C213C) = 0
19642: write(14, " s y s l o g d : c a n".., 62) = 62
19642: close(14) = 0
19642: llseek(0, 0, SEEK_CUR) = 66333
19642: _exit(1)
any advise/hints will be greatly appreciated .
likun
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:10 CDT