Operating System - HP-UX
1836375 Members
2354 Online
110100 Solutions
New Discussion

Re: Cannot login into CDE

 
Joshua Goi
Frequent Advisor

Cannot login into CDE

Hi,

I have a user login named as operator. When I tried to login, I have the following error message

/home/operator/INVOKE[26] gbhconfig: not found
Warning: could not create /tmp/5841a

Anyone has any idea what's going on and how to fix this?

Thanks!
6 REPLIES 6
Steven E. Protter
Exalted Contributor

Re: Cannot login into CDE

Check /tmp filesystem

ll -d /tmp

/tmp should probably be 777

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Dave Hutton
Honored Contributor

Re: Cannot login into CDE

Can you log this user on via telnet? ghbconfig doesn't ring a bell. It could be a custom script?
Also is your /tmp full by chance? or wrong permissions on /tmp?

RAC_1
Honored Contributor

Re: Cannot login into CDE

Correcting SEP,

/tmp should be having perms 1777
There is no substitute to HARDWORK
Rick Garland
Honored Contributor

Re: Cannot login into CDE

To do additional checks,

/usr/contrib/bin/X11/dr_dt

Will provide errors/warnings as to configuration issues
Steven E. Protter
Exalted Contributor

Re: Cannot login into CDE

[8252#] ll -d /tmp
drwxrwxrwx 35 bin bin 90112 Apr 26 14:45 /tmp


HP-UX 11i v1 D class.

To change:

chmod 777 /tmp

or

chmod 1777 /tmp

Must be root

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
doug hosking
Esteemed Contributor

Re: Cannot login into CDE

There are some good suggestions above. In some versions of UNIX, this could also be caused by running out of inodes for /tmp, or running out of file descriptors in the program trying to create the file in /tmp. Less likely is that /tmp has a corrupted file system or is on a sick disk.

If this happened on my system, I would try to manually create a file by that name in /tmp and see what error messages (if any) I got. I'd also look at the output from running '/sbin/dmesg | more' and look at the last few lines of /var/adm/syslog/syslog.log for potential hints about the cause.