10-13-2008
That is not much help for us...
From that we could guess FC driver/port/adapter issue perhaps...
What was above and what follows in the log?
Did they do what was suggested " Execute the following command to obtain event details..."
And what did they see?
10 More Discussions You Might Find Interesting
1. IP Networking
I checked my syslog for errors and the error I got was
alert;kern.err;daemon.err
I know the error deals with the daemon but I don't know exactly what it means. (2 Replies)
Discussion started by: Deuce
2 Replies
2. Solaris
Hi there, I have upgraded my explorer (SUNWexplo) on a solaris 10 Sparc box from version 3.4 to the latest version (5.5) . However im a little concerned, whenever I run the new explorer either manually or scheduled, I get a syslog event as follows
1 in 0:08:31: Sep 22 17:00:15 fmy.machine.com... (8 Replies)
Discussion started by: hcclnoodles
8 Replies
3. HP-UX
Hello,
I am New to Unix.
I am Using HP-UX 9000 Series for my Application.
I am Currently Facing an Issue that the error messages are being written in the syslog file instead of the Application Log File. The Codes for that Syslog.h is written in Pro*C.
I want to know how to Redirect these... (3 Replies)
Discussion started by: balasubramaniam
3 Replies
4. HP-UX
Hi,
I'm using HP-UX 11.11 on HP9000/800 PA-RISC system.I am getting the below messages daily in /var/adm/syslog/syslog.log file.Can someone help me out in this regard, why I am getting this messages & how to resolve it. I am using SSH version(HP-UX Secure Shell-A.04.20.004)
Messages:
Nov 26... (2 Replies)
Discussion started by: Mike1234
2 Replies
5. Programming
When I compile this i get the following error
"error: expected declaration specifiers or '...' before syslog"
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <errno.h>
#define __LIBRARY__
#include <linux/unistd.h>
/* define the system call, to override the library... (6 Replies)
Discussion started by: dragonpoint
6 Replies
6. UNIX for Dummies Questions & Answers
im kinda new to shell scripting so i need some help
i try to run this script and get the error code
> 5 ")syntax error: operand expected (error token is "
the code for the script is
#!/bin/sh
#
# script to see if the given value is correct
#
# Define errors
ER_AF=86 # Var is... (4 Replies)
Discussion started by: metal005
4 Replies
7. Solaris
All,
I'm getting the following error in syslog when picld starts up:
Jul 22 13:07:15 adl0845 picld: ld.so.1: picld: fatal: libpri.so.1: open failed: No such file or directory
And I look, and lo, there is no such file. Despite the word 'fatal', picld is still running. On other systems, I... (2 Replies)
Discussion started by: james.dean
2 Replies
8. AIX
Hi,
Can you please look into the below errors from syslog in AIX?
And let me know is this a issue? How can I avoid these errors with out affecting my LPAR.
Detail Data
SYSLOG MESSAGE
<27>Aug 23 08:24:28 syslog: slp: 0660-084 The SA failed to decode and compute received message:... (0 Replies)
Discussion started by: System Admin 77
0 Replies
9. Solaris
Hi Community
Which are the available entries to forward syslog in syslog.conf
i have put
*.err;kern.debug;daemon.notice;mail.crit;user.alert;user.emerg;kern.notice;auth.notice;kern.warning @172.16.200.50
and it's not going through.giving error message like below:
syslogd:... (2 Replies)
Discussion started by: bentech4u
2 Replies
10. AIX
Hi everyone,
I am trying to configure AIX 6.1 using syslogd to send syslog event to syslog server configured on RHEL. However, RHEL never receives the events.
I have tried to redirect the syslog event on AIX to a local file and successful. Only forwarding to remote server fails.
Firewall... (10 Replies)
Discussion started by: michael_hoang
10 Replies
TRM(4) BSD Kernel Interfaces Manual TRM(4)
NAME
trm -- Tekram TRM-S1040 ASIC based PCI SCSI host adapter driver
SYNOPSIS
trm* at pci? dev ? function ?
scsibus* at trm?
DESCRIPTION
The trm driver supports PCI SCSI host adapters based on the Tekram TRM-S1040 SCSI ASIC.
HARDWARE
Supported SCSI controllers include:
Tekram DC-315 PCI Ultra SCSI adapter without flash BIOS and internal SCSI connector
Tekram DC-315U PCI Ultra SCSI adapter without flash BIOS
Tekram DC-395U PCI Ultra SCSI adapter with flash BIOS
Tekram DC-395UW PCI Ultra-Wide SCSI adapter with flash BIOS
Tekram DC-395F PCI Ultra-Wide SCSI adapter with flash BIOS and 68-pin external SCSI connector
For Tekram DC-390 PCI SCSI host adapter, use pcscp(4) driver.
For Tekram DC-310/U and DC-390U/UW/F PCI SCSI host adapters, use siop(4) driver.
SEE ALSO
cd(4), ch(4), intro(4), pci(4), scsi(4), sd(4), ss(4), st(4), uk(4), scsipi(9)
http://www.tekram.com/
AUTHORS
The trm driver was originally written for NetBSD 1.4/i386 by Erich Chen of Tekram Technology, and Rui-Xiang Guo rewrote the driver to use
bus_space(9) and bus_dma(9) for NetBSD 1.6.
BSD
November 6, 2001 BSD