Hi All -

Help! I have a problem with logging into the system console.  Login
appears to proceed correctly, asking for Username and Password.
When successful the system welcome text is displayed but the user
("SYSTEM" in this case) is immediately logged out with the usual

SYSTEM logged out at 24-SEP-2011 18:23:14.32

but without any error message. Rebooting doesn't help. The system
is an Alpha with OVMS 6.2.  Network connections fail and does not
respond to pinging but had been working fine.

Thanks,
Ransom Fitch

In article <3fc82aea-f0b3-4c05-b47b-c32f17e41a66@j10g2000vbb.googlegroups.com>, RLFitch <rlfitch@gmail.com> writes:
>Hi All -
>
>Help! I have a problem with logging into the system console.  Login
>appears to proceed correctly, asking for Username and Password.
>When successful the system welcome text is displayed but the user
>("SYSTEM" in this case) is immediately logged out with the usual
>
>SYSTEM logged out at 24-SEP-2011 18:23:14.32
>
>but without any error message. Rebooting doesn't help. The system
>is an Alpha with OVMS 6.2.  Network connections fail and does not
>respond to pinging but had been working fine.

Have you tried conversationally booting to get in and see what's up?


-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.

RLFitch <rlfitch@gmail.com> wrote:

> Help! I have a problem with logging into the system console.  Login
> appears to proceed correctly, asking for Username and Password.
> When successful the system welcome text is displayed but the user
> ("SYSTEM" in this case) is immediately logged out with the usual

> SYSTEM logged out at 24-SEP-2011 18:23:14.32

Reminds me of the old trick from many years ago of putting
a LOGOUT command in someone's login file.  (Or, even more fun,
just print a fake logout message but not actually log them out.)

-- glen

On 9/24/2011 7:59 PM, RLFitch wrote:
> Hi All -
>
> Help! I have a problem with logging into the system console.  Login
> appears to proceed correctly, asking for Username and Password.
> When successful the system welcome text is displayed but the user
> ("SYSTEM" in this case) is immediately logged out with the usual
>
> SYSTEM logged out at 24-SEP-2011 18:23:14.32
>
> but without any error message. Rebooting doesn't help. The system
> is an Alpha with OVMS 6.2.  Network connections fail and does not
> respond to pinging but had been working fine.
>
> Thanks,
> Ransom Fitch

I'd make a small bet that someone has hacked your SYSTEM LOGIN.COM.

If you can boot from CD-ROM it might be interesting to check the key 
files in SYS$MANAGER e.g. LOGIN.COM.

Good luck and be more careful and less trusting!!!!!!

RLFitch wrote:
> ("SYSTEM" in this case) is immediately logged out with the usual
> 
> SYSTEM logged out at 24-SEP-2011 18:23:14.32


Try   Username: SYSTEM/NOCOMMAND



This bypasses the login.com processing if the username has the right to
bypass it.  This may work and if so, you edit the login.com to find out
why it would log your out.

On Sep 24, 7:59=A0pm, RLFitch <rlfi...@gmail.com> wrote:
> Hi All -
>
> Help! I have a problem with logging into the system console. =A0Login
> appears to proceed correctly, asking for Username and Password.
> When successful the system welcome text is displayed but the user
> ("SYSTEM" in this case) is immediately logged out with the usual
>
> SYSTEM logged out at 24-SEP-2011 18:23:14.32
>
> but without any error message. Rebooting doesn't help. The system
> is an Alpha with OVMS 6.2. =A0Network connections fail and does not
> respond to pinging but had been working fine.
>
> Thanks,
> Ransom Fitch

Ransom,

I would have to have more information. As has been mentioned, someone
could have made a modification to the LOGIN.COM file used by the
SYSTEM account (which is normally in SYS$COMMON:[SYSMGR]), but there
are also other possibilities.  Using a conversational boot to get into
the system is a start, but one must then locate precisely what is
going awry.

I suggest that this might be an appropriate time to call in an
experienced system manager to determine the precise nature of the
problem [Disclosure: We provide services in this area.]

- Bob Gezelter, http://www.rlgsc.com

In article <3fc82aea-f0b3-4c05-b47b-c32f17e41a66@j10g2000vbb.googlegroups.com>, RLFitch <rlfitch@gmail.com> writes:
> Hi All -
> 
> Help! I have a problem with logging into the system console.  Login
> appears to proceed correctly, asking for Username and Password.
> When successful the system welcome text is displayed but the user
> ("SYSTEM" in this case) is immediately logged out with the usual
> 
> SYSTEM logged out at 24-SEP-2011 18:23:14.32
> 
> but without any error message. Rebooting doesn't help. The system
> is an Alpha with OVMS 6.2.  Network connections fail and does not
> respond to pinging but had been working fine.

   Sounds like a license issue.  Many of us consider "console" to
   be OPA0:, where such login would be allowed.  But if you're connected
   via some other path, and there is no license, it would fail.

   There's also the possibility that SYSTEM is set DISUSER.  In this case
   VMS will still boot, and you can still log on as SYSTEM on OPA0:
   (At least it worked under VMS 6.1, the last system I tried it on).

   Or there may simply be something in sylogin or login.com that logs
   SYSTEM off.  Try logging in with /NOCOMMAND after the username.

"RLFitch"  wrote in message=20
news:3fc82aea-f0b3-4c05-b47b-c32f17e41a66@j10g2000vbb.googlegroups.com...=

>
>Hi All -
>
>Help! I have a problem with logging into the system console.  Login
>appears to proceed correctly, asking for Username and Password.
>When successful the system welcome text is displayed but the user
>("SYSTEM" in this case) is immediately logged out with the usual
>
>SYSTEM logged out at 24-SEP-2011 18:23:14.32
>
>but without any error message. Rebooting doesn't help. The system
>is an Alpha with OVMS 6.2.  Network connections fail and does not
>respond to pinging but had been working fine.
>
>Thanks,
>Ransom Fitch

We have once seen such behavior with a incorrectly wired modem. If the=20
terminal is set /MODEM and the carrier is dropped, the user is logged =
out.=20
This does not, however, explain the network problem.=20