Cannot login to node

[Hoangles]

I tried to login to a node named ttles1 but I could not. The system reports an warning.
Logging in to this node was OK before.
Does any one know the reason why?

*************
Username: opif
Password:
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\ACTIVE_NODE\
%DCL-I-SUPERSEDE, previous value of SYS$INPUT has been superseded
Copyright Oracle Corporation 1986, 1996. All rights reserved.

Access Granted,Enrolling User: OPIF
%SYSTEM-F-LINKEXIT, network partner exited

[John McL]

Based on the message "undefined symbol ACTIVE_NODE", it looks like your SYLOGIN or something that it calls might be broken.

[Hoangles]

yes It might be, but what can I do now without restart the whole system?

[Volker Halle]

Hoangles,

if the problem is in your local LOGIN.COM, you can try to login with Username: xxx/NOCOMMAND or /CLI=MCR - if this account allows this type of login.

You can also try to connect with SYSMAN from another OpenVMS system: SYSMAN> SET ENV/NODE=xxx and try to fix the issue with commands issued via SYSMAN> DO ...

Volker.

[Jur van der Burg]

login as a privileged user:

Username: SYSTEM/NOCOMMAND
Password: enter system password

Then check the system login procedures. Someone probably changed it.

Jur.

[Hoangles]

Hi,
I solved the problem by restarting the whole
system, might be some applications was suspending.
but this way seems not be a perfect way because it affects to operation of the system.
In fact we could still then log in to server with another user TTLES2-TTCES 6_4 $.
Any one can show me some commands to solve the problem without resart the server?

[Steven Schweda]

> Any one can show me some commands to solve
> the problem without resart the server?

Someone already has, to the extent possible:

> Then check the system login procedures.

My psychic powers are too weak to show me
what happens on your system when you log in.

[Steve Reece_3]

Your best bet Hoangles is to login using /NOCOMMAND on your username, then when you get to your VMS prompt do something like:

$ SPAWN
$ SPAWN
$ SET VERIFY
$ @LOGIN

The LOGIN.COM is likely to be the culprit since you can login successfully with a different account. Any user on the system will run SYS$SYLOGIN whereas you can usually choose not to run your own login command procedure with the /NOCOMMAND qualifier on the username.
This will give you the location of the error and what syntax is causing the problem. It's then up to your DCL skills to put it right.

The breaking of the connection is likely to be due to the Network Partner Exited error rather than the ACTIVE_NODE symbol error. Network Partner Exited normally means that the other end of the link (whatever the link is) closed the connection before this end thought it had finished. It's a, "he's gone away and I didn't expect him to" kind of error. It's likely that the problem there was spurious and could have been either due to the other end having a comms problem or else this end wasn't ready for the communication that should have happened.

Steve

[Jan van den Ende]

Hoangles,

Steve gave a very good way into solving this issue.

One potential problem MAY be a restriction on user OPIF. If that useraccount in SYSUAF has the FLAG Captive or Restricted, then /NOCOMM is not allowed.
Use some privileged user to (TEMPORARILY!!) remove that flag; solve the issue according to Steve's advise; and reset the SYSUAF flag.

hth

Proost.

Have one on me.

jpe