To serve or not to serve… Not to server!
Written by Arnan on May 18, 2008 – 3:04 am
So last thursday a small disaster happened in what later turned out an epic week of failure.
I lost communication with my server. Fearing the worst i called my mom, if she could see if the server was powered and perhaps reboot the thing.
She restarted the thing and all seemed well. The monitor wasn’t connected so there wasn’t much else she could do. But me from work could ping the machine again so i assumed it was ok. My mom went on downstairs, still on the phone, to test the internet connection. Nothing worked.
We then proceeded to bypass the server, which handled DNS and DHCP to set things manually and use openDNS. This did not work either. Frustrated we ended the conversation. I had to rush home after work to fix things.
Because the server seemed messed up i started there, rebooted. Found out the network cable wasn’t connected. Or so did OS X Server tell me. Ofcourse it was connected just fine. While pondering what would be wrong then i noticed my switch acted weird. All 8 ports were blinking in a rapid pace. “oh hell! it’s buffer messed up” i thought and went on to pull the power from it to reboot the switch. Which seemed well, the leds went as normal, for 5 seconds then they started blinking again. So i disconnected all Ethernet cables, restarted it again and noticed it was good. Then i connected all cabling one by one noting it went crazy at cable 2, which is going to my Lacie Etherdisk. Leaving that one out things went normal, but nothing could connect. I also noted the switch made a high pitched hissing noise that shouldn’t be there. I then declared the switch dead and angrily thought about a sollution. Which turns out to be a 3Com switch and my Airport Extreme. Hooked everything up… and voila. My LAN was working again. Mom rejoiced, she could read her email. I was more or less happy because the LAN was online and i could read my mail and chat with Catarina again. Life was good!
The next day, the server hung, and after a reboot no-one could connect to it. Remote desktop wasn’t working, shares seemed unreachable. Yet the machine seemed online as it responded to PINGs normally. GRRR! Climbing the stairs to the attic to go local on the monster it quickly turned out the LDAP database was gone. Which means that all users and access rights are either deleted or revoked. Thus no one could login. Luckily Root (admin) isn’t stored there so i could save all files and move them to my Lacie Etherdisk. Again, very angry and frustrated i decided for now i would use the Etherdisk and declared the server an unreliable piece of crap. Worst server OS ever!! Being completely through with OSX Server i decided i would reinstate the Lacie Etherdisk as the main data storage thing and my router would handle DNS and DHCP from here on in.
No more iCal server and no more LDAP hassle. I was so ready to throw it out the window as this was the 3rd or 4th time it lost its LDAP stuff in less than 6 months. With no direct access or a backup present this means i have to re-install the whole thing, set everything up again with only a backupped config file to go on. Lots of time would be lost, AGAIN!
OSX Leopard Server is stupid and sucks and is completely crap and even more unreliable… Aaand i dunno, some other nasty words!
I’m still not sure if i’m going to reinstall the server or not, probably not… maybe a Tiger server or even Linux PPC… We’ll see!
Tags: broken, image, Leopard, linux, network, osx, server |
