topic Re: Error messages in the syslog.log file in Operating System - HP-UX

Error messages in the syslog.log file

Deborah Ellis — Wed, 14 Jun 2000 18:01:50 GMT

I keep getting the following messages in the syslog.log file and I would like to find out what the problem is.

1. Jun 14 14:47:27 fn_osar vmunix: SCSI: asense data-done -- lbolt: 25985636, dev:
cb0d2000, tag: 7c

2. Jun 14 14:47:27 fn_osar bootpd[1507]: stat on "/etc/dhcptab": No such file or di
rectory

3. Jun 14 14:47:27 fn_osar bootpd[1507]: boot_bootrequest: request from hardware ad
dress 0090270B069C

4. Jun 14 14:48:05 fn_osar bootpd[1507]: stat on "/etc/dhcptab": No such file or di
rectory

5. Jun 14 14:48:05 fn_osar bootpd[1507]: vendor option(43): 4 btyes of vendor speci
fic data (0x37020000) not parsed.

Re: Error messages in the syslog.log file

Berlene Herren — Wed, 14 Jun 2000 18:20:42 GMT

#touch /etc/dhcptab

Berlene

Re: Error messages in the syslog.log file

Albert E. Whale, CISSP — Wed, 14 Jun 2000 18:30:46 GMT

That one's just too easy Berlene!

I would almost recommend that she disable the bootp protocol .... apppears like she getting requests from DHCP Clients on her network. Darn Windows machines trying to suck up DHCP Licenses I suspect.

Re: Error messages in the syslog.log file

Deborah Ellis — Thu, 15 Jun 2000 14:12:05 GMT

Thanks to both people that replied to my question. However, it did not work.
I touched the /etc/dhcptab file and then I looked in all of the files where bootp is referenced and I uncomment the entry. I am still getting the error. Do you have any other suggestions?

Re: Error messages in the syslog.log file

Ray Krupinski — Thu, 15 Jun 2000 17:55:36 GMT

The SCSI lbolt messages sometime represent a lack of termination on the bus. Ensure that the last device is properly terminated or use a self-terminating cable.

rusone@aent.com

Re: Error messages in the syslog.log file

Albert E. Whale, CISSP — Thu, 15 Jun 2000 18:09:50 GMT

She may have to either restart the init (or inetd) services in order for that to take effect.

When in doubt, reboot.

Let's see if the reboot picks up the change.

Re: Error messages in the syslog.log file

Berlene Herren — Thu, 15 Jun 2000 18:45:14 GMT

Deborah, try re-reading the inetd.conf file

#inetd -c

Berlene

Re: Error messages in the syslog.log file

Stefan Stechemesser — Fri, 16 Jun 2000 13:51:29 GMT

I think the first SCSI message points to another problem than the following.
I saw a system with an unsupported tape library which showed the same message and it seemed to be a driver problem on the tape library. dev cb0d2000 means device on SCSI bus 13, SCSI ID 2, LUN 0, where 13 is the instance number of the SCSI bus
(look for column "I" in ioscan -fnkC ext_bus)
The error message may be only informational and maybe the device works without problems. In this case I would ignore it ...

Re: Error messages in the syslog.log file

Eddie Warren — Fri, 16 Jun 2000 17:22:05 GMT

Deborah,
What concerns me is the "lbolt" error. It might be causing SCSI buss reset's. Which could mean: a) improper SCSI termination
b) bad terminator c) drive hanging the buss.
d) SCSI controller. Are there new drives you have installed recently?