Workgroup Manager... Authenticaion issues..

Came into work this morning, but wasn't able to log in to my network account.

I opened the workgroup manager and there didn't appear to be any errors.

I logged into my local account and checked my System Prefrences, Accounts, Login Options and noticed that there was a red light beside the name of the the Network Account Server... Usually it is green.

However what does that mean? Is this an LDAP communications issue?

I can ping the server and ssh into it.. however I think the server has issues, but not telling me much...

Running Mac OS X Server V 10.6.5
Workgroup Manager 10.6.3

In the server admin I do notice and error that says slapd[66]: could not load the replica file...

This is repeating itself.

In article
<10808469.410.1334337155396.JavaMail.geo-discussion-forums@ynma1>,
SpreadTooThin <> wrote:

> Came into work this morning, but wasn't able to log in to my network account.
>
> I opened the workgroup manager and there didn't appear to be any errors.
>
> I logged into my local account and checked my System Prefrences, Accounts,
> Login Options and noticed that there was a red light beside the name of the
> the Network Account Server... Usually it is green.
>
> However what does that mean? Is this an LDAP communications issue?
>
> I can ping the server and ssh into it.. however I think the server has
> issues, but not telling me much...
>
> Running Mac OS X Server V 10.6.5
> Workgroup Manager 10.6.3
>
> In the server admin I do notice and error that says slapd[66]: could not load
> the replica file...
>
> This is repeating itself.

Is this workgroup the master or is it using a replicant of the data from
some other source. This is just a SWAG, but maybe the file got
seriously corrupted. I've seen this happen with bidirectional LDAP
setup on Solaris and PCs. We had a similar problem and ended up with
the entire company down for 24 hours while we figured out that something
bad in M$'s version of Active Directory had walked all over the LDAP
database. Once we restored it from backups and turned of bisynch
replication, it ran just fine.

That may not be your problem or issue. But I thought I'd mention it.

--
DeeDee, don't press that button! DeeDee! NO! Dee...
[I filter all Goggle Groups posts, so any reply may be automatically ignored]

On Friday, April 13, 2012 4:03:58 PM UTC-6, Michael Vilain wrote:
> In article
> <10808469.410.1334337155396.JavaMail.geo-discussion-forums@ynma1>,
> SpreadTooThin <> wrote:
>
> > Came into work this morning, but wasn't able to log in to my network account.
> >
> > I opened the workgroup manager and there didn't appear to be any errors.
> >
> > I logged into my local account and checked my System Prefrences, Accounts,
> > Login Options and noticed that there was a red light beside the name of the
> > the Network Account Server... Usually it is green.
> >
> > However what does that mean? Is this an LDAP communications issue?
> >
> > I can ping the server and ssh into it.. however I think the server has
> > issues, but not telling me much...
> >
> > Running Mac OS X Server V 10.6.5
> > Workgroup Manager 10.6.3
> >
> > In the server admin I do notice and error that says slapd[66]: could not load
> > the replica file...
> >
> > This is repeating itself.
>
> Is this workgroup the master or is it using a replicant of the data from
> some other source.

There is only one WorkGroup Manager in my network as I was aware..
However now that you bring it up... I wonder if someone else in my network is running OS X Server....

> This is just a SWAG, but maybe the file got
> seriously corrupted.

It would appear so... We had to go back to a backup of the server and recreate several account.

Once we were done we tried to make a backup of the Configuration, however the save utility didn't appear to do anything.


> I've seen this happen with bidirectional LDAP
> setup on Solaris and PCs. We had a similar problem and ended up with
> the entire company down for 24 hours while we figured out that something
> bad in M$'s version of Active Directory had walked all over the LDAP
> database. Once we restored it from backups and turned of bisynch
> replication, it ran just fine.
>
> That may not be your problem or issue. But I thought I'd mention it.
>

Many thanks... It remains a mystery why things were corrupted.

> --
> DeeDee, don't press that button! DeeDee! NO! Dee...
> [I filter all Goggle Groups posts, so any reply may be automatically ignored]