9 More Discussions You Might Find Interesting
1. AIX
Hi all,
I am not sure whether anyone of you using XIV to copy vg from one host to another. After I managed to copy all the respective vg over to destination vg, and map all vg to destination and when come to varyonvg, I got the following error
0516-510 varyonvg: Physical volume not found for... (2 Replies)
Discussion started by: ckwan
2 Replies
2. Red Hat
Hi Masters,
How to find out the failed disk in redhat linux (OR)
How to decalare whether our hard disk goes bad ?
My option is:
dmesg | grep "failed"
check in /var/log/messages with the kernel error.
Please corrrect me if im wrong.
And also i heard "smartctl" command. But it's... (2 Replies)
Discussion started by: abhay1983
2 Replies
3. AIX
Hello,
On Aix 5.3, during importvg, the varyonvg fails:
importvg -y vgtest hdisk20
0516-013 varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
When i use manually the command varyonvg -u -b -t vgtest to force, the vg can... (3 Replies)
Discussion started by: dantares
3 Replies
4. Solaris
Dear all
Please can any one explain me how to replace failed disk in Solaris 10.
Please tell me the step by step procedure. (9 Replies)
Discussion started by: suneelieg
9 Replies
5. Windows & DOS: Issues & Discussions
Hi
The Autosys job that call DOS batch file which in turn calls java and this java program has successful completion though there are series of exception occurred in the data it handles and want the job to be set to Fail in its autosys, how could it be done?
a.bat
{
java sample.class
... (1 Reply)
Discussion started by: muthupus
1 Replies
6. Solaris
Hi All,
Seems to be one of the disk has failed on my Solaris server.
How do i confirm that disk has really failed or not?
Here are alert details.
-------
iostat -En out/put
c1t3d0 Soft Errors: 1884 Hard Errors: 153 Transport Errors: 54
Vendor: FUJITSU Product:... (3 Replies)
Discussion started by: Naresh Kommina
3 Replies
7. AIX
Good evening,
Thanks a lot for your help, we appreciate it a bunch. Heres basically a summary of what we have (sorry Im adding some extra history as well):
We have 2 Ibm Servers (Hag and Aki) that are running AIX Version 5. Each connect to a SAN device via 2 separate fiber paths. Hag seems to... (9 Replies)
Discussion started by: aix-olympics
9 Replies
8. UNIX for Advanced & Expert Users
Hello all,
Strange problem on p5 520 server. I've created two volume groups, filesystems, etc.. Everything working fine, without any problem. After some tests with a DS4300 unit I wanted to remove the volume groups, change the DS4300 configuration, and re-create a new volumegroup. However, I'm... (0 Replies)
Discussion started by: EricBE
0 Replies
9. UNIX for Advanced & Expert Users
My WS boot disk has failed so when i want to boot system (by OK boot -s or Ok boot disk0 ) i get these mesgs:
disk read error
boot :can not find misc/sparc9v/krtld
boot:error loading interperetor (misc/sparc9v/krtld)
Elf64 read error.
boot failed.
although it's probed ,finally i try... (1 Reply)
Discussion started by: nikk
1 Replies
qmail-log(5) File Formats Manual qmail-log(5)
NAME
qmail-log - the qmail activity record
DESCRIPTION
qmail-send prints a series of lines describing its activities. Each possible line is described below.
STATUS
status: local l/L remote r/R ...
qmail-send is waiting for l local deliveries and r remote deliveries. The concurrency limits are L and R.
status: exiting
qmail-send is done.
FATAL PROBLEMS
alert: cannot start: ...
qmail-send is unable to prepare itself for delivering messages; it is giving up. This normally indicates a serious configuration
error, but it can be caused by a temporary lack of resources.
alert: oh no! lost ...
One of the other daemons has died. qmail-send will exit as soon as possible.
SERIOUS PROBLEMS
alert: unable to append to bounce message...
qmail-send is unable to record a permanent failure, usually because the disk is full. This is a very serious problem; qmail-send
cannot proceed without recording the results. It will try again in ten seconds.
alert: out of memory...
qmail-send tried to allocate more memory and failed. It will try again in ten seconds.
alert: unable to opendir...
qmail-send is having trouble reading a file list from disk, usually because the system's file descriptor table is full, but possibly
because permissions are set incorrectly. It will try again in ten seconds.
alert: unable to switch back...
qmail-send was sent SIGHUP, and it is unable to reenter the queue directory. This is a very serious problem; qmail-send cannot pro-
ceed outside the queue directory. It will try again in ten seconds.
alert: unable to reread...
qmail-send was sent SIGHUP, but it is unable to read the new controls. It will continue operating with the original controls.
MESSAGES
new msg m
qmail-send is going to preprocess a queued message. The message number, m, is its disk inode number. After a message is removed
from the queue, its number can be reused immediately.
info msg m: bytes b from <s> qp q uid u
Message m contains b bytes; its envelope sender is s; it was queued by a user with user ID u. q is a long-term queue identifier,
the process ID of the qmail-queue that queued the message.
bounce msg m qp q
Message m had some delivery failures. The long-term queue identifier of the bounce (or double-bounce) message is q.
triple bounce: discarding ...
Message m had some delivery failures, but it is already a double-bounce message, so it must be thrown away. Triple-bounce messages
do not exist.
end msg m
qmail-send is about to remove message m from the queue.
DELIVERIES
starting delivery d: msg m to ...
qmail-send is telling qmail-lspawn or qmail-rspawn to deliver message m to one recipient. The delivery number, d, starts at 1 and
increases by 1 for each new delivery.
delivery d: success: ...
Delivery d was successful.
delivery d: failure: ...
Delivery d failed permanently. The message will bounce.
delivery d: deferral: ...
Delivery d failed temporarily. This recipient will be retried later.
delivery d: report mangled, will defer
There is a serious bug in qmail-lspawn or qmail-rspawn. This recipient will be retried later.
WARNINGS
internal error: delivery report out of range
qmail-lspawn or qmail-rspawn has supplied a report on a nonexistent delivery. This is a serious bug.
qmail-clean unable to clean up ...
For some reason qmail-clean is unable to remove the indicated file. It will try again later.
trouble fsyncing ...
qmail-send was unable to write to disk the results of preprocessing a queued message. It will try again later.
trouble in select
There is an operating system bug.
trouble injecting bounce message...
qmail-send was unable to queue a bounce message, usually because the disk is full. It will try again later.
trouble marking ...
qmail-send was unable to record the result of a successful or permanently unsuccessful delivery. This means that the delivery will
be tried again later.
trouble opening ...
qmail-send was unable to open the list of local or remote recipients for a message. It will try again later.
trouble reading ...
Either qmail-send is unable to read a recipient list, or it is unable to read the envelope of a queued message, or it is out of mem-
ory. Whatever it was doing, it will try again later.
trouble writing to ...
qmail-send was unable to preprocess a queued message, usually because the disk is full. It will try again later.
unable to create ...
qmail-send was unable to preprocess a queued message, usually because the disk is out of inodes. It will try again later.
unable to open ...
qmail-send is unable to read the envelope of a queued message for preprocessing. It will try again later.
unable to start qmail-queue...
qmail-send is unable to queue a bounce message, usually because the machine is almost out of memory. It will try again later. This
can also be caused by incorrect settings of $QMAILQUEUE or errors in a program or script which $QMAILQUEUE points to.
unable to stat ...
qmail-send is unable to obtain information about a file that should exist. It will try again later.
unable to unlink ...
qmail-send is unable to remove a file. It will try again later.
unable to utime ...
qmail-send is about to exit, and it is unable to record on disk the next scheduled delivery time for a message. The message will be
retried as soon as qmail-send is restarted.
unknown record type in ...
There is a serious bug in either qmail-queue or qmail-send.
SEE ALSO
qmail-send(8)
qmail-log(5)