1829448 Members
1069 Online
109992 Solutions
New Discussion

Re: VUE login problem

 
SOLVED
Go to solution
George Liu_2
Frequent Advisor

VUE login problem

After fsck / partition followed by reboot, an HP 9000/700 (HP 10.20) workstation prompt an error window after X-login session, and login is killed and screen is back to normal login window.
No problem in no-xwindow login session.
How to fix that?
6 REPLIES 6
Allan Pincus
Frequent Advisor
Solution

Re: VUE login problem

George,

Do you mean VUE or CDE? I'll assume CDE.

I've seen login problems with CDE when the following occurs:

1. The /etc/hosts file is corrupt or incorrect. Either the hostname does not match the nfs.conf file or there is no loopback address set.
2. If using DNS, the resolve.conf file cannot be found.
3. The /etc/passwd file is wrong for the user logging
4. The home directory pointed to in the /etc/passwd file for the user logging in does not exist.

Go to single user mode, or start a failsafe session, and check these things out. Let me know.

- Allan

George Liu_2
Frequent Advisor

Re: VUE login problem

Allan,

It's VUE and all files mentioned to be checked were never touched by this fsck time. And a non-superuser can login in via X login. Thanks.
:-) George
Leif Halvarsson_2
Honored Contributor

Re: VUE login problem

Hi
Log in with no-window session (or failsafe session) and check the file $HOME/.vue/errorlog for error messages.
George Liu_2
Frequent Advisor

Re: VUE login problem

Leif,

Your info is very useful, Following are the error messages. Could that be a hardware problem?

Mon Sep 09 03:23:32 2002
vuesession: cannot find a message server
Make sure that there is a message server running and
that either $DISPLAY or $MSERVE were set correctly
both when softbench was started and also in the current environment.


Mon Sep 09 03:23:32 2002
vuesession: cannot find a message server
Make sure that there is a message server running and
that either $DISPLAY or $MSERVE were set correctly
both when softbench was started and also in the current environment.

Mon Sep 09 03:23:32 2002
vuesession: The '/usr/bms/config/softinit'
initialization file for the Execution Manager does not exist
or is not readable.


Mon Sep 09 03:23:32 2002
vuesession: Could not find the Execution Manager initialization file (softinit).

Mon Sep 09 03:23:32 2002
vuesession: cannot find a message server
Make sure that there is a message server running and
that either $DISPLAY or $MSERVE were set correctly
both when softbench was started and also in the current environment.

Mon Sep 09 03:23:32 2002
vuesession: Unable to start message server - exiting.

Mon Sep 09 03:23:32 2002
vuesession: Can't register callback pattern: "LOCK_DISPLAY" (no message server connection)

Mon Sep 09 03:23:32 2002
vuesession: Can't register callback pattern: "EXIT_SESSION" (no message server connection)

Mon Sep 09 03:23:32 2002
vuesession: Can't register callback pattern: "STOP" (no message server connection)

Mon Sep 09 03:23:32 2002
vuesession: Can't register callback pattern: "STATUS" (no message server connection)

Mon Sep 09 03:23:38 2002
Workspace Manager: I/O error on display:: gvas1:0.0

Alex Glennie
Honored Contributor

Re: VUE login problem

in no windows mode run /usr/bms/bin/softmsgsrv -norootwindow ...any errors ?

ensure correct perms on /etc/hosts and also run VUE diagnostic -> dr_vue (/usr/contrib/bin/X11 )

ll /opt/softbench/bin ?

in /usr/adm/inetd.sec the hostname MUST be allowed for 'mserve' and 'spc'.

ensure /usr/spool/sockets has correct permissions.

If only root afected mv roots .vueprofile and .profile and .vue directory out of the way and then attempt another login ...

If the following patches are not installed install them -> PHSS_11136 & PHSS_26788

George Liu_2
Frequent Advisor

Re: VUE login problem

I guess I need to install the patches. Thanks, folks.

:-) George