Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OS X Server Directory Service (?) unresponsive

I know you didn't post that to the list, but your message at least looked like it could contribute to the discussion, therefor I posted it to the list.

Dan,

If you see something in the log I posted, why not tell us what it is instead of slipping off the subject once again. The fact that you so often just go around telling people that there could be another problem and that one should read every ounce of documentation available to the world, is what I think pisses some people off.

It's like, if you ARE going to try to help, do it without noting words the extra strained comments regarding how people ended up asking the question. Sure, sometimes it's good to point out that one shouldn't ask questions without any research or logical thought behind it. But you still have to remember that there are a lot of people out there that try their best to keep a small business running, and many of us simply don't have the time/resources to read up on everything. Also, some of us come from a different background than plain Mac-stuff, and managing an OS X Server isn't THAT similar to managing a plain UNIX system, simply because Apple has made a lot of changes to their system compared to for example FreeBSD. You may think what you want about that and I already presume you don't agree, but that'll be your opinion. Remember, everyone have their own opinion, and who's to claim that one of them is the right one..

For example, in a response to this thread on the 4th of october, you replied to me after i asked if anyone knew of any reports for "this bug". What I was referring to was the problem that DirectoryService (or whatever it is, please don't start a war of words here..) kept dying on me, and as you've seen from the thread, this has been the case for many others as well, it's just not me that's having this problem.
You questioned what *bug* I was talking about, and you even asked me if I had any *proof* of a bug. All I can say about the latter is that of course I don't, the definition of a bug isn't definitive AFAIK. What I mean is that either I and some other administrators could have made a configuration error, causing the problematic behaviour we're experiencing with our servers, OR it's indeed a software bug. But are you really expecting anyone to be able to *prove* that it's a bug?
Let's say that there's a really screwed-up bug in some part of the operating system such as that the protection of memory areas in the kernel doesn't work as expected, and some other part of the system has a second bug on its own, which accidentally writes to a memory area that's part of DirectoryServices, and that this is what causes DirectoryServices to crash on us. It's an extreme and not very likely scenario, but my point is that your response to me that time was everything but helpful, and did not contribute to the discussion.

I know perfectly well that there are user errors and that I may very well do something wrong when setting up a server, but in this case - considering other people's similar reports and the fact that I feel I know what I'm doing at least to some extent - I chose to consider this a bug. I'm not blaming anyone for this, but if it IS a configuration error by me and the others with the same problem, then I'd be very interested to know how Apple managed to produce such a simple (GUI and stuff for services..) server operating system and yet we're not able to keep this running. I'm quite sure that together we have a fair amount of experience managing servers. And this really isn't any rocket science. Mine and probably others setup is really simple. Also, my server in question have had its DirectoryService crash with the symptoms discussed in this thread three times now over about 2 months time, last time it ran well over one of these months. Are you still saying that it's a configuration error on my part? Sorry, but I believe it isn't. Even more sorry to say, I don't have the time to go into depth about it. As part of trying to get it under control I wanted to see if others are experiencing the same problem, that's why I started this thread.

Anyhow, it would be great if you could do more into detail about the SSH logs I posted. Is there anything in there showing why I can't connect via SSH when DirectoryServices are down, while it works great when they aren't?

Regards, Leo


29 okt 2007 kl. 18.35 skrev Dan Shoop:

Excuse me, but I was not posting to that to the list. Remember I'm a fool. But I can read your log.

On Oct 29, 2007, at 1:24 PM, Leo R. Lundgren wrote:

29 okt 2007 kl. 18.17 skrev Dan Shoop: 

On Oct 29, 2007, at 6:18 AM, Leo R. Lundgren wrote:

10 okt 2007 kl. 01.13 skrev Dan Shoop: 

On Oct 8, 2007, at 5:39 AM, Leo R. Lundgren wrote:

6 okt 2007 kl. 23.20 skrev Dan Shoop:
Regarding SSH, I *think* that last time the authentication was down, I tried SSH and couldn't log into it 

As expected if you aren't using keys.

Dan suggested that perhaps SSH would work using key authentication, but I guess it's a no on that though, if I'm not mistaken.

I wasn't guessing. It doesn't need to use directory services for authentication.

I'll check it out for sure next time it happens. 

No, please don't bother...

-dhan 

Dan,

Before making a complete fool out of yourself the next time, please RTFMail that you are responding to. I'll paste part of what I wrote again, so you can correct your post.

The reason I mention it is that for this server, we use keys only. 

Or, come to think of it, please don't bother..

Next time the server screws up, I'll make sure to see whether keys work or not.

Which will not prove or disprove that key based authentication doesn't require Directory Services; it would just prove you have some third problem.

For the record ssh key based authentication does not authenticate through Directory Services. That's the point of the keys and all the methods ssh has incorporated.

-dhan

Today the server went down again, same problems with authentication as the other times it's happened. I tried logging in with keys, and it did not work. 

Not from what you've posted.

Oops, sorry, I'm, a fool... 

Sorry? What do you mean by "Not from what you've posted"?

What I meant is that what we experienced when the server "went down" were the same symptoms that has been discussed earlier in this thread. Same problems, the authentication ones where DirectoryService becomes unresponsive.

-|


-dhan

---------------------------------------------------------------------- --
Dan Shoop <email@hidden>
Tactical Operations Center: 1.866.901.8787 (24x7)
Ph: 714.363.1174
AIM: iWiring




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden

This email sent to email@hidden
References: 
 >Re: OS X Server Directory Service (?) unresponsive (From: Dave Pooser <email@hidden>)
 >Re: OS X Server Directory Service (?) unresponsive (From: David Minard <email@hidden>)
 >Re: OS X Server Directory Service (?) unresponsive (From: David Minard <email@hidden>)
 >Re: OS X Server Directory Service (?) unresponsive (From: "Leo R. Lundgren" <email@hidden>)
 >Re: OS X Server Directory Service (?) unresponsive (From: Dan Shoop <email@hidden>)
 >Re: OS X Server Directory Service (?) unresponsive (From: "Leo R. Lundgren" <email@hidden>)
 >Re: OS X Server Directory Service (?) unresponsive (From: Dan Shoop <email@hidden>)
 >Re: OS X Server Directory Service (?) unresponsive (From: "Leo R. Lundgren" <email@hidden>)
 >Re: OS X Server Directory Service (?) unresponsive (From: "Leo R. Lundgren" <email@hidden>)
 >Re: OS X Server Directory Service (?) unresponsive (From: Dan Shoop <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.