CDE not starting on HPUX 10.20

[Craig Rants]

Check out this link

http://us-support.external.hp.com/cki/bin/doc.pl/sid=08bbc3ff097deb75c0/screen=ckiDisplayDocument?docId=200000024598791

GL,
C

[Roxworth Cornette]

Thanks Craig for the article. However this did not help. The problem is still there. The permissions are exactly as stated in the article. Help!

[S.K. Chan]

What changes/modification were made to the system before the last reboot/shutdown ?

[Roxworth Cornette]

One of our guys that wont be here till tomorrow, from what i understand had to kill a process. I know that we have been having problems with the network card but i can do nslookups and pings. Dr_dt is only giving warnings in reference to permissions and the permissions are fine. I have checked the xerrors log, and all revelant logs. I must be missing something simple.

[Charles Slivkoff]

Can the X server be started manually?

# /usr/bin/X11/X :0

If not, what errors are listed?

If it can, try running it as the non-privlidged "daemon" user:

# su - daemon
$ /usr/bin/X11/X :0

Any errors now?

[Heiner E. Lennackers]

Hi,

on HP-UX 10.20 i often had problems with restarting cde. Mostly it helps to remove the sockets in /var/spool/sockets (only the sockets, not the directories). I have always deleted all sockets in this and the subdirectories and rebooted the system.

Heiner

[Alex Glennie]

I don't think this is necessarily CDE's fault ... it looks like uucp & named are having problems ....

Your uucp open dld.sl error first ......

Check the permissions of the following directories and correct them as needed.
# ll -d / drwxr-xr-x 36 root root 1024 Nov 16 16:16 /
# ll -d /usr dr-xr-xr-x 24 bin bin 1024 Nov 10 12:03 /usr
# ll -d /usr/lib
dr-xr-xr-x 25 bin bin 5120 Oct 30 10:19 /usr/lib
# ll -d /usr/lib/dld.sl
-r-xr-xr-x 1 bin bin 77824 Jun 12 03:00 /usr/lib/dld.sl

Start name server daemon
Output from "/sbin/rc2.d/S370named start":
----------------------------
EXIT CODE: 1
Error in starting named. Recommend checking the
syslog file (usually /var/adm/syslog/syslog.log)
for possible reasons.
"/sbin/rc2.d/S370named start" FAILED

what's in the syslog ?

Also is this system configured as a DNS server or client ?

[K.Vijayaragavan.]

Hi,

run the command "dr_dt > diserror.txt"
"cat diserror.txt | pg" to see the cause of the problem.

note :
check the file permission of "/var/spool/sockets" and the files and subfolders uder it. all of them must have permission set with "rwxrwxrwx"

If there is any Name service swith problem may also create such problem.

what happens if you issue the command "nslookup

-Vijay

[Steve Steel]

Hi


This must be a permissions problem.


check /usr is ok.

find is there and I have seen the dld.sl caused by that

Should be 555


Steve Steel