🚀 go-pugleaf

Data Processing - CCMD wrote:

> We had a problem on one of our Novell 4.1 servers:
>
> A routine, that a user was running, locked up the server and didn't
> allow for a normal shutdown.  After rebooting the server (reset
> button) I discovered the Admin account wasn't able to login to the
> Tree.
>
> The server we had the problem with, was a Time Reference
> Server and a Replica.
>
> I have DSTRACE running on the three servers (that make up our
> tree)...which appear to be completing synchronization, without
> incident.
>
> However, NWADMIN is showing an active connection for Admin--even
> though no Admin connection appears on any of our Consoles and
> I cleared all NOT-LOGGED-IN connections with the address NWADMIN is
> showing.
>
> I hesitate running DSREPAIR--this being the Admin account.
>
> - Is there a way to clear an 'active connection' that's doesn't appear
> on the Console?
>
> - Are there any concerns in running DSREPAIR, when an Admin
> account is corrupt?
>
> - If I run DSREPAIR, should it be on the server that went down, or
> the Master Replica?  (Or does it matter?)
>
> Steve Conrad
> City Center of Music and Drama, Inc.

If anything, I'd check NDS Manager to make sure there's still a problem
(when you go in tomorrow). If there's still a problem, you can force it to
receive an update which will wipe out the replica on that server and
receive it from the Master replica. Not sure if it would be more or less
adviseable than DSREPAIR.

I wouldn't worry about the effects DSRepair would have on the admin account.
I mean, if NDS is corrupt (which could manifest itself as users unable to
log in to the tree) there aren't any alternatives to NDSRepair.

I would agree that sending a fresh replica from the Master could help...
but I would advise DSRepair first - and run from the Master Replica server
(it would at least tell you about errors).  But as insurance you should make
sure that you have another account with Supervisor power to [Root]
(including file system supervisor rights).  Because the Admin account can be
deleted and recreated later.

If you do a "nlist user = admin /a" at a DOS prompt that returns a logged in
user it should show a connection number.  You can clear it at the console
with command: "clear station XXX" where XXX is the connection number.

By the way, could the account be locked out?  And it's a little strange
sounding that the Time Reference Server doesn't hold the Master replica (I
assume you mean the time server is a "Single Reference".

Hope this helps.


--

garyf


Akira <ayamanita.nospam@bigfoot.com> wrote in message
news:37BB3B79.3B33A5D5@bigfoot.com...
> Data Processing - CCMD wrote:
>
> > We had a problem on one of our Novell 4.1 servers:
> >
> > A routine, that a user was running, locked up the server and didn't
> > allow for a normal shutdown.  After rebooting the server (reset
> > button) I discovered the Admin account wasn't able to login to the
> > Tree.
> >
> > The server we had the problem with, was a Time Reference
> > Server and a Replica.
> >
> > I have DSTRACE running on the three servers (that make up our
> > tree)...which appear to be completing synchronization, without
> > incident.
> >
> > However, NWADMIN is showing an active connection for Admin--even
> > though no Admin connection appears on any of our Consoles and
> > I cleared all NOT-LOGGED-IN connections with the address NWADMIN is
> > showing.
> >
> > I hesitate running DSREPAIR--this being the Admin account.
> >
> > - Is there a way to clear an 'active connection' that's doesn't appear
> > on the Console?
> >
> > - Are there any concerns in running DSREPAIR, when an Admin
> > account is corrupt?
> >
> > - If I run DSREPAIR, should it be on the server that went down, or
> > the Master Replica?  (Or does it matter?)
> >
> > Steve Conrad
> > City Center of Music and Drama, Inc.
>
> If anything, I'd check NDS Manager to make sure there's still a problem
> (when you go in tomorrow). If there's still a problem, you can force it to
> receive an update which will wipe out the replica on that server and
> receive it from the Master replica. Not sure if it would be more or less
> adviseable than DSREPAIR.
>

If the admin is showing as an active connection. Just go the server monitor
screen and force a disconnection. Then run dsrepair.

Neil Frechette, CNA
Integration Support
MediaTouch
nfrechette@omt.net


Data Processing - CCMD <DP@mindspring.com> wrote in message
news:37baf47c.5458310@news.mindspring.com...
> We had a problem on one of our Novell 4.1 servers:
>
> A routine, that a user was running, locked up the server and didn't
> allow for a normal shutdown.  After rebooting the server (reset
> button) I discovered the Admin account wasn't able to login to the
> Tree.
>
> The server we had the problem with, was a Time Reference
> Server and a Replica.
>
> I have DSTRACE running on the three servers (that make up our
> tree)...which appear to be completing synchronization, without
> incident.
>
> However, NWADMIN is showing an active connection for Admin--even
> though no Admin connection appears on any of our Consoles and
> I cleared all NOT-LOGGED-IN connections with the address NWADMIN is
> showing.
>
> I hesitate running DSREPAIR--this being the Admin account.
>
> - Is there a way to clear an 'active connection' that's doesn't appear
> on the Console?
>
> - Are there any concerns in running DSREPAIR, when an Admin
> account is corrupt?
>
> - If I run DSREPAIR, should it be on the server that went down, or
> the Master Replica?  (Or does it matter?)
>
> Steve Conrad
> City Center of Music and Drama, Inc.
>

That's a question I'd like answered also:
I too have a process that occasionally hangs on the workstation (Access).
We then have to reboot the user's station (no choice) but then novell 4.11
shows no connection on the console and yet when the users tries to log back
in it says "too many connections, your supervisor has limited you to 1".
There is no way to force a clear of the user at the console level because it
doesn't show ... however, the connection does show in nuserlist!

Anyone shed any light?  How can I clear the user completely after such an
event?

-Robert McKone,

Neil Frechette wrote in message ...
>If the admin is showing as an active connection. Just go the server monitor
>screen and force a disconnection. Then run dsrepair.
>
>Neil Frechette, CNA
>Integration Support
>MediaTouch
>nfrechette@omt.net
>
>
>Data Processing - CCMD <DP@mindspring.com> wrote in message
>news:37baf47c.5458310@news.mindspring.com...
>> We had a problem on one of our Novell 4.1 servers:
>>
>> A routine, that a user was running, locked up the server and didn't
>> allow for a normal shutdown.  After rebooting the server (reset
>> button) I discovered the Admin account wasn't able to login to the
>> Tree.
>>
>> The server we had the problem with, was a Time Reference
>> Server and a Replica.
>>
>> I have DSTRACE running on the three servers (that make up our
>> tree)...which appear to be completing synchronization, without
>> incident.
>>
>> However, NWADMIN is showing an active connection for Admin--even
>> though no Admin connection appears on any of our Consoles and
>> I cleared all NOT-LOGGED-IN connections with the address NWADMIN is
>> showing.
>>
>> I hesitate running DSREPAIR--this being the Admin account.
>>
>> - Is there a way to clear an 'active connection' that's doesn't appear
>> on the Console?
>>
>> - Are there any concerns in running DSREPAIR, when an Admin
>> account is corrupt?
>>
>> - If I run DSREPAIR, should it be on the server that went down, or
>> the Master Replica?  (Or does it matter?)
>>
>> Steve Conrad
>> City Center of Music and Drama, Inc.
>>
>
>