Sponsored Content
Full Discussion: Xserver doesn't allow log in
Operating Systems Solaris Xserver doesn't allow log in Post 302424144 by solaris_user on Monday 24th of May 2010 10:32:36 AM
Old 05-24-2010
Tried , no luck I am still unable to log in
 

10 More Discussions You Might Find Interesting

1. Solaris

Xserver won't come up on Solaris 8

Hi all, My Ultra 10, running Solaris 8, is giving me problems :( Currently, whenever it boots, the Xserver will not come up, saying "Xserver cannot be started on display 0". I thought this might have something to do with OWconfig, and so poked it a little (moving params onto different... (5 Replies)
Discussion started by: Gravity
5 Replies

2. UNIX for Dummies Questions & Answers

Xserver not running in Solaris x86

I have just installed Solaris 10 x86 version on a Compaq Evo desktop station with a Sun 19" SVGA monitor model # CM751U. The desktop has 256MB RAM. The video card is a nVidia Riva TNT2 64. If I do a scanpci command; it returns the card as a nVidia Corporation NV6 (Vanta/Vanta LT) The Xserver... (1 Reply)
Discussion started by: sjteng
1 Replies

3. UNIX for Advanced & Expert Users

XServer Fails to start

I've recently patched my AIX box from ML02 to ML06 and somehow along the way the monitor no longer starts up in GUI mode. Running the command xinit gives me the following errros ioctl Bad file Number 1356- Unable to start the X server I've checked the path variables, the monitor, the lai0... (0 Replies)
Discussion started by: mahartle
0 Replies

4. UNIX for Dummies Questions & Answers

Looking for recommendations for free Xserver

Hello , im not sure if its the right forum... im sorry if not im working with putty allot , but now I started to work with more graphical applications and im looking for free simple and fast Xserver to remote connection, can someone recommend me if there is something like that ? (3 Replies)
Discussion started by: umen
3 Replies

5. Solaris

xserver problem - hang

Dear When I restart the Xserver it works fine for less than half an hour and throw this error afterward. After setting the display DISPLAY=10.195.2.13:0.0, I tried to run xclock. After few minutes it throws this error message "X connection to 10.195.2.13:0.0 broken (explicit kill or... (0 Replies)
Discussion started by: tanvirscsa
0 Replies

6. UNIX for Advanced & Expert Users

Xserver

Hi, From my workstation (win XP)I open a telnet session on Linux(Red Hat) server. When I issue : # xclock I have : Error: Can't open display: Then : # export DISPLAY=192.16.1.87:0.0 # xclock Error: Can't open display: 192.16.1.87:0.0 Do you have an idea ? Many thanks. (6 Replies)
Discussion started by: big123456
6 Replies

7. Solaris

Xserver

I have problem with my V490 server which running on solaris 8. The error show on log file X_mkdir: nosuch file or directory Fatal server error: Failed to establish all listening sockets error (pid 299): server unexpectedly died error (pid 299): server for display :0 cant be started ... (1 Reply)
Discussion started by: shamsul
1 Replies

8. UNIX for Dummies Questions & Answers

Help setting up XServer in Centos 5.4

Hi, After I remove the external video card after setup, Centos 5.4 upon boot cannot start the XServer for the onboard video card. How can I configure XServer to get it working? Machine is a DELL OPTIPLEX 745 (1 Reply)
Discussion started by: mojoman
1 Replies

9. Solaris

Xserver not display

I have this Xserver not display issues, I try search from the forum but found out it can have different errors from the Xerrors logs. Here I upload and hope admin can help. root@ccs # more Xerrors The loadable module for the display device SUNWast is not installed. Fatal server error:... (1 Reply)
Discussion started by: mailbox80
1 Replies

10. UNIX for Advanced & Expert Users

Xserver shared library link is gone

I am administering an Xserver v10.6.8 and I updated the ports using Macports self update. I received this error when calling the program R dyld: Library not loaded: /opt/local/lib/libicuuc.48.dylib Referenced from: /opt/local/lib/R/lib/x86_64/libR.dylib Reason: image not found Trace/BPT... (2 Replies)
Discussion started by: godzilla07
2 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 12:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy