Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #376496
    scorpioserve
    Participant

    Hi, everyone, I am fairly new here so hello. I hope I am posting this question in the correct place, so sysadmins please let me know if not.

    The question I have is this, I have 2 Leopard servers on my premisis, both run on intel Mac Pro type hardware, lets call them server1 and server2.

    Server1 specs: MacPro 2 x 2.0 ghz Dual-Core Intel Xeon, 3gb ram
    OS X Server 10.5.7 fully updated,
    Running Services are:
    AFP, DHCP, DNS, Firewall, Mail, NAT, NFS, Open Directory, SMB
    this is a secondary dns, and secondary mail server, the main task is to serve AFP, and share an internet connection with about 15 clients, mac and pc. SMB is set as a standalone server. It is also an open directory replica.

    Server2 specs: MacPro 2 x 2.8 ghz Quad-Core Intel Xeon, 6gb ram
    OS X Server 10.5.7 fully updated,
    Running Services are:
    AFP, DHCP, DNS, Firewall, Mail, MySQL, NAT, NFS, Open Directory, SMB, Software Update, Web, NTP, Time Machine Server
    this is a primary dns, and primary mail server, the main task is to share an internet connection with about 32 clients, mac and pc. SMB is set as a PDC. It is also an open directory master.

    Both servers run for 6 to 10 days before they get rebooted, but when they do, it just does not work, sometimes I can sit for over an hour with a spinning circle before I manually have to shut it down, sometimes after about 10 minutes the mouse arrow will reappear and I can go and open the terminal from the dock and type sudo reboot, this then does the job in a matter of seconds, my question is why? firstly and secondly would it be advisable for me to just always use the terminal or does it do a dirty job of rebooting. If it helps I can try get some logs together. let me know.

    Thanks to all 😳

    #376551
    guitar24t
    Participant

    sudo reboot definitely does a very dirty job of rebooting! it kills every process right where it is. I have had very weird startup issues with mac.

    Do a reboot the normal “clean” way and wait until you can get into the dock and then look in the console in system.log (in /var/log). If you see anything odd, post the log (obviously not all of it 😀 ). If you want to send me the whole log, go to

    [url]http://www.studiosoundandvision.com/contactus.php[/url]

    and email it as an attachment.

    Sometimes a startup issue is hard to find in the logs because they just are sometimes not logged, but if the system starts eventually, it will most likely be logged.

    Hope I can help you because I know how frustrating that is (I was trapped 7 hours away from my house where I keep my reinstall disks for a week!)

    Just out of curiosity, do you write your own shell scripts and put them in the bin folders? I destroyed my computer by two misplaced files.

    Good Luck, Robert

    #376557
    scorpioserve
    Participant

    Thanks Robert, sounds great, I will do a couple reboots and wait for it to start its trouble, get the logs and send you the relative section, thanks for taking the time to help

    Regards Paul

    #376558
    guitar24t
    Participant

    Anytime! Like I said, I know what a pain this is. 👿
    I will be happy to help.
    Robert

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.

Comments are closed