AFP548 Changing the world one server at a time.

servermgrd & SMB access

Home › Forums › OS X Server and Client Discussion › Questions and Answers › servermgrd & SMB access

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #366067
    Richard
    Participant

    I am running an XServe 10.4.4 at a local school and I am looking for some help with a recent issue. I opened an Apple Bug Reporter ticket but I’m not sure they *ever* look at those things. 🙁 So, I thought I would repost to you guys and see if anyone has a clues for me.

    Thanx!
    Richard

    ========= SNIP =========

    At a little after 3:00pm this afternoon all of our Windows users started complaining about not being able to use the network. Some troubleshooting was done (reboot the firewall, etc.) and a short while later (10mins) everything returned to normal. However, when we tried to connect to our XServe using Server Admin or Server Monitor from the iBook we received an error about not being able to find the server. Workgroup Manager still worked fine.

    Doing a little more digging I found out that servermgrd was not running and that the system.log contained quite a few messages about launchd throttling it at about the same time as the network "went down". I have included a snippet of the system.log file and would like to know what more I can do? I re-added the servermgrd process to launchd (using launchdctl) and everything seems to be working OK now.

    We had a similar network outage a couple of months ago but could never attribute it to any particular thing. What would cause this error? Is there something going on with our Windows network (SMB) stuff?

    Thanx!
    Richard

    ============== SNIP ==============

    system.log:Apr 27 15:03:49 xserve1 servermgrd: [40] error in getAndLockContext: flock(servermgr_smb) FATAL time out
    system.log:Apr 27 15:03:49 xserve1 servermgrd: [40] process will force-quit to avoid deadlock
    system.log:Apr 27 15:03:49 xserve1 launchd: com.apple.servermgrd: exited with exit code: 1
    system.log:Apr 27 15:03:49 xserve1 launchd: com.apple.servermgrd: 9 more failures without living at least 60 seconds will cause job removal
    system.log:Apr 27 15:03:49 xserve1 launchd: com.apple.servermgrd: exited with exit code: 1
    system.log:Apr 27 15:03:49 xserve1 launchd: com.apple.servermgrd: respawning too quickly! throttling
    system.log:Apr 27 15:03:49 xserve1 launchd: com.apple.servermgrd: 8 more failures without living at least 60 seconds will cause job removal
    system.log:Apr 27 15:03:49 xserve1 launchd: com.apple.servermgrd: will restart in 10 seconds
    system.log:Apr 27 15:03:59 xserve1 launchd: com.apple.servermgrd: exited with exit code: 1
    system.log:Apr 27 15:03:59 xserve1 launchd: com.apple.servermgrd: respawning too quickly! throttling
    system.log:Apr 27 15:03:59 xserve1 launchd: com.apple.servermgrd: 7 more failures without living at least 60 seconds will cause job removal
    system.log:Apr 27 15:03:59 xserve1 launchd: com.apple.servermgrd: will restart in 10 seconds
    system.log:Apr 27 15:04:09 xserve1 launchd: com.apple.servermgrd: exited with exit code: 1
    system.log:Apr 27 15:04:09 xserve1 launchd: com.apple.servermgrd: respawning too quickly! throttling
    system.log:Apr 27 15:04:09 xserve1 launchd: com.apple.servermgrd: 6 more failures without living at least 60 seconds will cause job removal
    system.log:Apr 27 15:04:09 xserve1 launchd: com.apple.servermgrd: will restart in 10 seconds
    system.log:Apr 27 15:04:19 xserve1 launchd: com.apple.servermgrd: exited with exit code: 1
    system.log:Apr 27 15:04:19 xserve1 launchd: com.apple.servermgrd: respawning too quickly! throttling
    system.log:Apr 27 15:04:19 xserve1 launchd: com.apple.servermgrd: 5 more failures without living at least 60 seconds will cause job removal
    system.log:Apr 27 15:04:19 xserve1 launchd: com.apple.servermgrd: will restart in 10 seconds
    system.log:Apr 27 15:04:29 xserve1 launchd: com.apple.servermgrd: exited with exit code: 1
    system.log:Apr 27 15:04:29 xserve1 launchd: com.apple.servermgrd: respawning too quickly! throttling
    system.log:Apr 27 15:04:29 xserve1 launchd: com.apple.servermgrd: 4 more failures without living at least 60 seconds will cause job removal
    system.log:Apr 27 15:04:29 xserve1 launchd: com.apple.servermgrd: will restart in 10 seconds
    system.log:Apr 27 15:04:40 xserve1 launchd: com.apple.servermgrd: exited with exit code: 1
    system.log:Apr 27 15:04:40 xserve1 launchd: com.apple.servermgrd: respawning too quickly! throttling
    system.log:Apr 27 15:04:40 xserve1 launchd: com.apple.servermgrd: 3 more failures without living at least 60 seconds will cause job removal
    system.log:Apr 27 15:04:40 xserve1 launchd: com.apple.servermgrd: will restart in 10 seconds
    system.log:Apr 27 15:04:50 xserve1 launchd: com.apple.servermgrd: exited with exit code: 1
    system.log:Apr 27 15:04:50 xserve1 launchd: com.apple.servermgrd: respawning too quickly! throttling
    system.log:Apr 27 15:04:50 xserve1 launchd: com.apple.servermgrd: 2 more failures without living at least 60 seconds will cause job removal
    system.log:Apr 27 15:04:50 xserve1 launchd: com.apple.servermgrd: will restart in 10 seconds
    system.log:Apr 27 15:05:00 xserve1 launchd: com.apple.servermgrd: exited with exit code: 1
    system.log:Apr 27 15:05:00 xserve1 launchd: com.apple.servermgrd: respawning too quickly! throttling
    system.log:Apr 27 15:05:00 xserve1 launchd: com.apple.servermgrd: 1 more failure without living at least 60 seconds will cause job removal
    system.log:Apr 27 15:05:00 xserve1 launchd: com.apple.servermgrd: will restart in 10 seconds
    system.log:Apr 27 15:05:10 xserve1 launchd: com.apple.servermgrd: exited with exit code: 1
    system.log:Apr 27 15:05:10 xserve1 launchd: com.apple.servermgrd: respawning too quickly! throttling

    system.log:Apr 27 15:05:10 xserve1 launchd: com.apple.servermgrd: too many failures in succession

    #367077
    Richard
    Participant

    Just to wrap up this question. I don’t really remember what we did to “fix” it. I’m thinking that a reboot and making sure that servermgrd was in launchd (using launchdctl) was all it took. We haven’t had any problems with it since – at least none that they told me about. 😕

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