AFP548 Changing the world one server at a time.

Very strange AFP & Server Admin issue

Home › Forums › OS X Server and Client Discussion › File Serving › Very strange AFP & Server Admin issue

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • October 11, 2007 at 9:06 pm #370186
    anthonyd
    Participant

    Server is OS X 10.3.9 running on a single CPU 1.8GHz G5 PowerMac.

    The only services running on the machine is Apache and AFP.

    The machine had an uptime of nearly 80 days and was obviously in need of some updates recently. After updating and rebooting, we noticed AFP did not come back. So unfortunately the machine has been up so very long that I can’t even imagine all the changes that may have taken place between then and now to really know where to begin with this…

    Anyway, I fire up Server Admin and AFP is greyed out. Press start service, spins a second, then nothing… no error, but the service doesn’t show as running. Can not connect.

    Try from the command line and get this:

    serveradmin start afp

    afp:command = “setState”
    afp:state = “STOPPED”
    afp:status = 0

    Look in /Library/Logs/AppleFileService/AppleFileService.log and see this explanation:
    11/Oct/2007:16:38:41 -0500: The server wasn’t able to start (Unable to bind port 548)
    11/Oct/2007:16:38:41 -0500: The server wasn’t able to start (TCP error).

    Check, and port 548 is *not* in use by any other process. I wouldn’t expect it to be, but confirmed it wasn’t, so that’s a bit puzzling. Don’t see any related messages in system.log/console.log etc.

    For the heck of it, try to simply execute /usr/sbin/AppleFileServer, which immediately exits silently (though remains active as a background process), and low and behold we’re serving files on AFP again, looking totally normal to the end users. ps confirms the active PID number is the same as is recorded in /private/var/run/AppleFileServer.pid.

    Check back in Server Admin however, and it still does not show as running (which I assume is related to the fact I didn’t start it “properly”)

    Any ideas of what to look for/where to check/etc as to why I can not start the service via the “serveradmin start afp” command, or via Server Admin for that matter? Are there any other negative side effects I should be aware of to running it as-is by having launched the AppleFileServer binary for the time being until I solve this?

    Thanks in advance.

    October 12, 2007 at 2:01 pm #370190
    anthonyd
    Participant

    Just wanted to add, a day later, its still serving files OK. Still not showing anywhere else.

    Despite several users now connected and working normally, I’m still seeing this too:

    anthony$ sudo serveradmin fullstatus afp
    afp:command = “getState”
    afp:guestAccess = “NO”
    afp:logging = “NO”
    afp:currentConnections = 0
    afp:currentThroughput = 0
    afp:state = “STOPPED”
    afp:logPaths:accessLog = “/Library/Logs/AppleFileService/AppleFileServiceAccess.log”
    afp:logPaths:errorLog = “/Library/Logs/AppleFileService/AppleFileServiceError.log”
    afp:readWriteSettingsVersion = 1
    afp:setStateVersion = 2
    afp:startedTime = “”

    (Which is totally off, guest access is enabled, it is logging at the very moment, there are active connections and throughput etc etc…)

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