Hi,
The original post is at the bottom of this email. I don't understand why
this worked, but re-booting the machines seemed to stop the excess errors on
the cd-rom device. So there you go, sorry not to be more informative.
regards
Mark
We had an engineer from Compaq configure AES/DSN Link on a couple of our
servers.
Since having this done we get regular errors appearing in the binary error
log relating to the cdrom devices on both machines, without the devices
being used (as far as we're aware!). Also when you issue the 'file' command
against the raw device it creates another error against the device and error
in the binary errorlog.
When we put a cdrom in the device, these errors stop and we've had no
problems reading from the cdroms. If you take the cd out, the errors
return.
I believe that the problem is not with the device, but with the way in which
AES/binlogd now reports errors; I don't think it has updated the binlogd
configuration, as the configuration file hasn't changed.
The messages in the binary error log are along the lines of medium not
present, or logical unit not ready, as shown at the end of this message.
We logged a call with Compaq, who have suggested rebooting the machine, and
running diagnostics at the SRM level. I don't think, at this stage, it's
the right way forward, especially as getting downtime is not an easy thing
to do.
Does anyone have any ideas?
Received on Mon Jan 29 2001 - 14:10:53 NZDT