Shared volume is disconnecting nightly

Discussion in 'Mac OS X Server, Xserve, and Networking' started by Moof1904, Jul 4, 2012.

  1. macrumors 65816

    Joined:
    May 20, 2004
    #1
    Beginning three days ago (with no changes to the server) a single user on our network has been greeted each morning with a dialog reporting that the main shared volume on our 10.5.8 server has been disconnected. "Server connections interrupted. Ignore. Disconnect All." Choosing any option results in the server volume staying mounted but the files are unavailable (spinning gear forever when browsing the mounted volume). Only restarting the client and remounting the shared volume fixes the problem.

    The other user on our network sees no such message, though this Mac is set to go to sleep during the night whereas the one receiving the message does not sleep.

    Both clients are running the latest version of Lion.

    I'm not sure where to begin diagnosing this. Is it likely a server issue or a client issue? The behavior points to a client problem. What logs should I examine to get a clue?

    I appreciate any suggestions.

    Thanks!
     
  2. thread starter macrumors 65816

    Joined:
    May 20, 2004
    #2
    Any ideas?

    Any ideas why a single computer on the network would be greeted every morning with a "Server connection interrupted. Ignore. Disconnect All" dialog?

    And whether the user clicks Ignore or Disconnect All, the mounted volume stays mounted but shows the spinning gear forever when browsing. The only fix is rebooting the client.

    Anything?
     
  3. macrumors 601

    Joined:
    Aug 15, 2005
    #3
    If this suddenly started, then something changed, whether it be on the client or the network gear connecting it.

    I would start with the client, as it is more likely something has changed there. Has any new program or security patches been installed? What does the console log state (found in Applications -> Utilities)?
     
  4. thread starter macrumors 65816

    Joined:
    May 20, 2004
    #4
    Possibly CronoSync?

    Now that I ponder it, I did update CronoSync on the client last week and CS is set to automatically back up certain client data files to the server volume each night.

    I wonder if CronoSync is somehow causing the issue?

    Exactly what logs should I be examining in the console? I note that CronoSync has not written any logs. There's a heading for it, but no logs underneath.
     
  5. macrumors 601

    Joined:
    Aug 15, 2005
    #5
    I'm not at a Mac at the moment but we're interested in the system logs on the client. Does it say anything is happening during the off business hours?
     
  6. thread starter macrumors 65816

    Joined:
    May 20, 2004
    #6
    Still looking at the logs.

    One thing that's jumping out is that this is appearing a ton of times:


    com.apple.launchd.peruser.501[161] (com.akamai.client.plist[19741]): Bug: launchd_core_logic.c:4753 (25693):13

    here are some entries discussing chronosync:

    ChronoAgentLocal[19693]: ChronoAgentLocal v1.3.3 Init.
    Jul 6 01:00:00 Mac-Pro [0x0-0x1be1be].com.econtechnologies.chronosync[19689]: 2012-07-06 01:00:00.776 ChronoAgentLocal[19693:107] ChronoAgentLocal v1.3.3 Init.
     
  7. macrumors 601

    Joined:
    Aug 15, 2005
    #7
    That's Adobe. Here's how to get rid of that; I don't think it is required for your Adobe product.
     
  8. thread starter macrumors 65816

    Joined:
    May 20, 2004
    #8
    Thanks. I'll take care of that.

    (Curse Adobe for all their bloatware...)

    Meanwhile, I've disabled Chronometer's nightly scripts to see if that's the problem.
     
  9. macrumors 6502

    wetrix

    Joined:
    Dec 1, 2006
    Location:
    Auckland, New Zealand
    #9

Share This Page