Sponsored Content
Full Discussion: Solaris I/O Error
Special Forums Cybersecurity Solaris I/O Error Post 302554125 by kkalyan on Saturday 10th of September 2011 06:38:58 AM
Old 09-10-2011
Solaris I/O Error

When i trying to open any exising floder iam unable to open it.It is showing the following error .
Can anyone help me out of this
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Solaris hardware error

hi guys, need some help on this error message. im running solaris 2.6 on a e3500 and lately i encountered this error:- lp: Warning: Received SIGPIPE; continuing last message repeated 1 time Multiple Softerrors: 2 Intermittent, 4 Persistent, and 0 Sticky Softerrors accumulated from... (4 Replies)
Discussion started by: giriplug
4 Replies

2. UNIX for Dummies Questions & Answers

error booting solaris 10

Hello experts, I have installed solaris 10 on x86. When I try to boot I get an error with ablue screen login failed please try again. I am new to this o.s. It used to work nicely before what did I do wrong? Any guidance advice will be highly appreciated Thanks, (5 Replies)
Discussion started by: deepak1
5 Replies

3. Solaris

Solaris : compilation error

Hi All, while building, i am receiving the following error...... Undefined first referenced symbol in file void os_directory::create(const std::string &) obj.release/BOConfig.o (symbol belongs to implicit dependency... (2 Replies)
Discussion started by: vinod_kumar_k
2 Replies

4. Solaris

[help] filesystem error on solaris 10

Hi All, please help me about filesystem error on sun fire 245 sparc solaris 10, i have installed solaris 10 os on sun fire 245 and done with mirroring disk. but after reboot the server i having this error below shown by system : checking ufs filesystems /dev/md/rdsk/d60: is logging.... (4 Replies)
Discussion started by: bucci
4 Replies

5. Solaris

application compiled on solaris 10 throwing error when executed on solaris 9

I have compiled my application on Solaris 10 with following description SunOS ldg1 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Blade-T6320 The compiler is Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25 But when installing the application on Solaris 9 SunOS odcarch02 5.9... (2 Replies)
Discussion started by: ash_bit2k2
2 Replies

6. Solaris

Solaris 10 Terminal Error

When in the terminal on Solaris 10 this terminal error keeps popping up and won't stop, how do I remove it? Nov 24 13:22:42 unknown sendmail: unable to qualify my own domain name (unknown) -- using short name Nov 24 13:22:42 unknown sendmail: oAOIMgqg017431: SYSERR(root): fill_fd:... (6 Replies)
Discussion started by: jastanle84
6 Replies

7. Solaris

pam_cracklib error on Solaris 10

Hello Everyone, I was able to successfully compile cracklib and pam_cracklib. But when I use it in /etc/pam.conf it fails to work. Error on CLI: # passwd testuser Unexpected failure. Password file/table unchanged. Error in /var/adm/messages: Mar 30 7:14:27 solaris10 passwd: dlsym... (1 Reply)
Discussion started by: pingmeback
1 Replies

8. Solaris

Solaris 10 flash installation - fatal error. Solaris installation program exited.

Not very helpful to say the least. Seems to read the flar file and go through the upgrade and then come up with this error. Any ideas? (1 Reply)
Discussion started by: psychocandy
1 Replies

9. Solaris

Solaris error

Hi, I am using solris 8 and i am unable to start my tomcat. I am getting the below error. Error occurred during initialization of VM Unable to load native library: ld.so.1: java: fatal: libscf.so.1: open failed: No such file or directory Please let me know. (1 Reply)
Discussion started by: Krrishv
1 Replies

10. Solaris

SUDO error in Solaris: auth.error] fork

I cannot solve the following error bellow. Can someone help me on this please? Mar 31 07:08:45 serverx sudo: fork Mar 31 07:18:50 serverx sudo: fork Mar 31 07:28:45 serverx sudo: fork Mar 31 07:38:47 serverx sudo: fork Mar 31 07:48:45 serverx sudo: fork Mar 31 07:58:45 serverx... (1 Reply)
Discussion started by: pangarano
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)
All times are GMT -4. The time now is 03:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy