can't start x-server on 10.2

[JakeKn]

can't start x-server on 10.2

Wed Feb 4 15:39:35 2004
error (pid 1949): Server unexpectedly died

Wed Feb 4 15:39:40 2004
error (pid 1949): Server for display pir1:0 can't be started

Xerrors

[T G Manikandan]

Run dr_dt

and check /var/adm/Xerrors.

check for the permissions of /tmp,/var/spool/sockets.They should be 777.

Also make sure no process is using 177 which is used by CDE

you can do a
#lsof -i tcp:177

to check whether any other process is using the port

[JakeKn]

Run dr_dt
and check /var/adm/Xerrors.

I'm using VUE not CDE and dr_vue run without any errors

check for the permissions of /tmp,/var/spool/sockets.They should be 777.

drwxrwxrwx 6 bin bin 5120 Feb 4 16:01 tmp
drwxrwxrwx 5 bin bin 2048 Feb 4 14:27 sockets

Also make sure no process is using 177 which is used by CDE

you can do a
#lsof -i tcp:177

to check whether any other process is using the port

and no process is using 177

[Steven E. Protter]

Sounds like the xfs server crashed.

echo $DISPLAY

Is it valid?

Can you ping it?

Some major errors might show up in /var/adm/syslog/syslog.log

Those would indicate a networking issue.

SEP

[JakeKn]

Sounds like the xfs server crashed.

echo $DISPLAY

Is it valid?

root@pir1:/var/adm/syslog> echo $DISPLAY

root@pir1:/var/adm/syslog>


Can you ping it?

ping work ok

Some major errors might show up in /var/adm/syslog/syslog.log

I check through log but not any major problems

Those would indicate a networking issue

[Kenneth Platz]

Try su'ing to daemon, and start the X server manually:

/usr/bin/X11/X :0

You should get a grey screen with an X in the middle. If you get this, then go ahead and do a ctrl-shift-break to get out of it. If this fails, then post your error message here.