Server Admin relay host field bug?

I noticed something curious when attempting to specify a relay host via Server Admin 10.4.3 (157.5) application.
If I specify xxx.com in "Relay outgoing mail through host" field, the value will appear as entered in MailServicesOther.plist. However, it will NOT appear in main.cf, there is only a line 'relay='.
When I manually edited main.cf to add 'relay=xxx.com' then relaying started working...however, if I use Server Admin after that to edit the value, it reverts back to an empty value again. Rather annoying, really.
Is this a known bug?

Honestly, I've had trouble with ServerAdmin and Postfix's main.cf from the beginning of 10.3.x I've given up on using SA for anything to do with the mail. I've tried everything from having someone send me a default main.cf and reseting everything in SA.
I can't get it back into sync, and since my backup MX server is running Postfix on FC3 I learned the CLI and got over the SA. I still use SA for looking at Account Quotas under the Maintenance tab, everything else is dorked anyway now.
Xserve G4 1ghz   Mac OS X (10.4.3)   OSXS 10.4.3

Similar Messages

  • Mail Server Relay Authentication Failure in Server Admin

    I need to set up Mail Server to relay through my ISP.  I know that I can authenticate to smtp.comcast.net:587 using my account and TLS usnig a mail client.
    However, when I use Server Admin to configure my server's SMTP to send all outgoing email through this relay (Server Admin>Mail>Settings>General>
    Rely outgoing mail through host: smtp.comcast.net:587
             Authenticate to rely with user name: user
    I get the SMTP error:
    SASL authentication failed: cannot authenticate to server smtp.comcast.net[76.96.62.117]: no mechanism available
    There are no toggles on Server Admin to specify TLS or SSL or anything for authentication.
    Does anyone know how to tell Server Admin how to authenticate an SMTP relay to smtp.comcast.net using TLS, which is apparently what comcast expects?

    Wow, this is an obscure solution, but it works. According to this thread, the problem is that:
    Although Comcast advertises "AUTH LOGIN PLAIN", the Postfix SASL library won't do plain text auth by default. It needs to be told it's okay with:
    smtp_sasl_security_options = noanonymous
    Solution:
    $ su -
    $ cd /etc/postfix
    $ cp main.cf main.cf.no_smtp_sasl_security_options
    $ echo 'smtp_sasl_security_options = noanonymous' >> ./main.cf
    $ serveradmin stop mail
    $ serveradmin start mail
    I'm not sure how often /etc/postfix/main.cf is overwritten, but presumably this happens every time you change and save Mail settings in Server Admin, so you must redo these steps every time you change the Mail server if you want to use smtp.comcast.net as your mail relay.
    AAPL, would you please add a toggle to handle this in Server Admin?

  • Server Admin 10.6 bug: Realms are completely messed up

    After upgrading Server Admin to 10.6, I completely lost control over the Realm configuration with Server Admin. This happens regardless if the Server is 10.5 or 10.6.
    Example: For a given Realm the permissions for "Everyone" should read "None" instead nothing is displayed (the field is empty). The permissions for a given Group should read "Browse and Read WebDAV", instead "None" is displayed.
    If I try to change permissions, or give permissions to a new Realm, the popup menu shows the following choice:
    *Browse Only*
    *Browse Only*
    None
    Normally it should look like this:
    *Browse Only*
    *Browse and Read WebDAV*
    *Browse and Read/Write WebDAV*
    None
    I can't say for sure if this has consequences for the actual access rights. I found this problem after upgrading to 10.6 and tested it by connecting from a 10.6 client computer via WebDAV as Guest. The Server gave me full access instead of none. Later I found in the logfile, that I have been connected with my current user name instead of being a Guest, with I explicitly choose to be, in the Finders connect dialog on a 10.6 client.
    After that I lost all trust into 10.6 Server so far. Also it was late yesterday, so I decided to restart the Server as 10.5 from a backup disk. I'll give 10.6 a second try if I got some answers first.
    Remark: I'm using Server Admin in German Language. I have translated the menu items above for this post. Is this a localization bug? Could anyone confirm, this behavior of Server Admin in other language versions?
    _Further question:_ Is this "choose to be a Guest, and be connected as the curred user" behavior a bug in 10.6 Finder?
    Message was edited by: root 66

    This appears to be a problem with the German-language strings present in SnowLeopard Server. You can try fixing them yourself as a workaround. As an administrative user, make a backup copy of the following file (just in case), and open the file with a text editor:
    "/Applications/Server/Server Admin.app/Contents/PlugIns/Web.bundle/Contents/Resources/German.lproj/Localizab le.strings"
    That file contains lines that map user interface items to displayed strings. For the popup values of the Permissions section of the Realms display, you will find the following incorrect lines:
    "kBrowseOnly" = "Ansehen";
    "kBrowseAndReadWebDAV" = "Ansehen ";
    "kBrowseAndReadWriteWebDAV" = "Ansehen ";
    Change each "Ansehen" to a more meaningful German string - I think you can infer a correct string from the context - and save the changes, and then relaunch Server Admin.

  • Server Admin suddenly cannot find the host it runs on

    I am running mac osx server, snow leopard. It ran fine until just recently. Suddenly Server App is unable to find the host it runs on.
    I enter the hosts IP address on the local network, log in with my administrator username and password, and the system comes back telling me
    Could not connect to <ip address>
    Server Admin was unable to connect to the server at <~ip address>
    Server Preferences tells me that this host cannot be found on the network too.
    Point is however that both these apps run on the host with that very IP address. It is set up in System Preferences > Network, and is hardcoded, not given by the DHCP server in the router. I can also connect to the web server running on this host using the laptop and an ipad.
    This is quite annoying, especially as Server Admin is the only app that lets you manage the host it runs.
    Mac mini, OS X Server, version os os x server is 10.6.8

    relais:~ locadmin$ sudo changeip -checkhostname
    Password:
    Primary address     = 192.168.39.200
    Current HostName    = relais.local
    The DNS hostname is not available, please repair DNS and re-run this tool.
    dirserv:success = "success"
    and
    relais:~ locadmin$ sudo lsof -i -P | grep ':311'
    relais:~ locadmin$
    The log is telling about a crash in servermgrd, which is restarted and crashing every ten seconds, a bit from the crash report
    Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
    0   com.apple.CoreFoundation                0x00007fff89aa244f __CFTypeCollectionRetain + 191
    1   com.apple.CoreFoundation                0x00007fff89aabca5 __CFBasicHashAddValue + 53
    2   com.apple.CoreFoundation                0x00007fff89ab3688 CFBasicHashSetValue + 184
    3   com.apple.CoreFoundation                0x00007fff89ab34a7 CFDictionarySetValue + 199
    4   com.apple.servermgr_dns                 0x00000001031bbd66 addDataToDictionary + 2549
    5   com.apple.servermgr_dns                 0x00000001031bc6ec yyparse + 2324
    6   com.apple.servermgr_dns                 0x00000001031bd7a6 parseFile + 384
    7   com.apple.servermgr_dns                 0x00000001031dac19 optionsParser_lex_destroy + 104800
    8   com.apple.servermgr_dns                 0x00000001031d6406 optionsParser_lex_destroy + 86349
    9   com.apple.servermgr_dns                 0x00000001031d6468 optionsParser_lex_destroy + 86447
    10  com.apple.servermgr_dns                 0x00000001031ce904 optionsParser_lex_destroy + 54859
    11  com.apple.servermgr_dns                 0x00000001031cea41 optionsParser_lex_destroy + 55176
    12  com.apple.servermgr_dns                 0x00000001031d19c8 optionsParser_lex_destroy + 67343
    13  com.apple.servermgr_dns                 0x00000001031c1f78 optionsParser_lex_destroy + 3263
    14  com.apple.servermgr_dns                 0x00000001031c67db optionsParser_lex_destroy + 21794
    15  com.apple.servermgr_dns                 0x00000001031c254b optionsParser_lex_destroy + 4754
    16  libservermgrcommon.dylib                0x000000010003ec18 -[BundleManager init] + 402
    17  libservermgrcommon.dylib                0x000000010003dd9d +[BundleManager defaultManager] + 51
    18  com.apple.ServerManagerDaemon           0x0000000100003bcb 0x100000000 + 15307
    19  com.apple.ServerManagerDaemon           0x00000001000014c0 0x100000000 + 5312
    So it looks like there is some t=file that is now not exactly like the parser wants it.

  • How to DHCP Server with NO ROUTER on Server Admin panel field?

    Hi all!
    I'm having a little problem.
    I have two completely different networks, with different purposes, one is 10.0.10.X and the other is 192.168.10.X. My networks is like this:
    Internet------Wifi Router (192.168.10.250) -----iMacs AirPoirt (192.168.10.X)
    MacPro (10.0.10.100)-----iMacs Ethernet (10.0.10.X)
    Great, is so simple. So I had a DHCP server (Windows blerg) on the 10.0.10.X (NOT MAC OS X SERVER) and everything works perfect, since on the Windows DHCP Server I'm not forced to fill the router/gateway and leaving it blank makes the iMacs have just one router/gateway from the 192.168.10.X lease from the Wifi Router.
    Now I'm planning to migrate the DHCP Service to the Mac OS X Server (Snow Leopard Server), I fiddled a bit and found that I can't use DHCP Server on Mac OS Server leaving router field blank and if I type ANYTHING, my iMacs will NOT access the internet through 192.162.10.X since now there's two gateways (from 10.0.10.X that Server Admin panel forced me to fill and from 192.168.10.X that HAS to have one gateway and it's the correct one).
    I've tried to fill with the 192.168.10.X gateway but throws a warning saying that is not on the same subnet.
    I really don't want to re-route or mix the traffic for many reasons.
    So I ask, is there any possible way to NOT fill or bypass or do anything to make DHCP Server service from Mac OS X Server not have a gateway/router?
    The only way I'm managing to do it now is to use manually entered IPs on the iMacs, but it's 10 iMacs and I guess for some services like netboot etc I need DHCP.
    Cheers,

    Lets assume that before you had computers with both Ethernet and WiFi connections, they were able to access the Internet via WiFi and talk amongst themselves via Ethernet. The Ethernet addresses were not (in theory) accessible from the WiFi network and hence not accessible from the Internet. Presumably you intended this for security reasons.
    If so, you were completely mistaken. Even if you turned on a Software firewall on each of these iMacs to in theory block traffic going between the two networks you still have a potentially insecure setup. This is because traffic can reach the iMacs via WiFi. Once hypothetical malicious traffic has invaded an iMac via WiFi it can take control over the computer and within that computer reach out via its Ethernet port to other Ethernet computers.
    The only way to ensure complete security is not to have any link between the two networks at all. If one of the computers is linked to both then you have a potential path for attacks to travel across.
    So what are you really trying to do? If you want two totally separate networks with one having absolutely no link to the outside world then this is simple and is as follows.
    NETWORK1 Internet------Wifi Router (192.168.10.250) -----iMacs AirPoirt (192.168.10.X)
    NETWORK2 MacPro (10.0.10.100)-----different iMacs Ethernet (10.0.10.X) with WiFi turned off
    You could define the default gateway for NETWORK2 as being the DHCP server itself. No computer on NETWORK2 would be able to access the Internet and hence it would be totally secure.
    If however you want all computers to be able to access the Internet then you need a link between them. Are you merely wanting to segregate WiFi traffic as it might be insecure and evesdropped on? If so then the following is a better approach
                             WiFi clients (192.168.10.x)
    Internet ----- AirPort Extreme (192.168.10.250) ------ Hardware FireWall does NAT (10.0.10.1) ---- MacPro (10.0.10.100) ---- iMacs via Ethernet (10.0.10.x)
    The WiFi clients would not be able to directly access your 10.0.10.x network as they are blocked by the FireWall. However if you have say a Laptop that you want ot use on WiFi but still access your server on your internal secure LAN you would do this by having the server run the VPN server component. The WiFi client would then connect via the VPN server and this would ensure all the network traffic going over the WiFi is encrypted using industry standard IPSec encryption. In this second scenario the MacPro (presumably your server) would have the FireWall as the default gateway, and the FireWall would have the Internet router as its default gateway. You could set the Firewall to forward VPN traffic to the server or use the second Ethernet port on the server to accept VPN traffic on the 192.168.10.x LAN.
    This is my own setup is something like
                            AirPort
                               |
    Internet router --- Public IP range --- (WAN) FireWall (LAN) --- LAN Switch --- Server Port1 for normal traffic
                                                     |(DMZ)                                    |
                                                     +----------------------------- Server Port2 for VPN

  • OSX Server 10.6.3 - (Multiple) Website hosting via Server Admin

    Has anyone else experienced/had this problem? I am posting this hear in hopes that someone else has experienced this as well and may know how to correct/resolve this problem.
    We currently have purchased a collaboration software I have installed and I am running via OSX. The files are stored in /Library/WebServer/Documents/collab. OSX comes with a default website built in at /Library/WebServer/Documents. I intend to install the collab website in anticipation of adding more sites in the future and possibly utilizing the default OSX web services as well. I have set up our internal DNS server to route collab.company.com to the internal ip address of our OSX server. The default OSX webpage is currently hosted on port 80, I am running our collab site on port 8x (we are already hosting websites on a different server on port 80, and the router can only forward port requests to a single ip address).
    With this configuration, if I enter the address of collab.company.com, I get the default OSX server running on port 80. If I enter collab.company.com/collab, I then get our collab website (on port 8x). Essentially I want collab.company.com to open the collab website, not the OSX website. What is odd is, it seems that if I uncheck the default OSX webpage in server admin and disable it, change the collab site to port 80 as a test and go to collab.company.com I get a failed connection that the site is down or doesn't exist, like it is offline. It seems almost as if OSX is completely shutting down the entire directory of /Library/WebServer/Documents which is where the collab website exits inside of (Documents/collab). If I re-enable the default OSX website, then both websites become live again.
    So I guess my question is, is there a different structure/architecture that should be followed to prevent this behaviour? If so, how do I get multiple websites installed and configured properly in server admin to respond to their appropriate dns requests. I also forgot to mention for my collab site entry in server admin I have the host name in the general tab as collab.company.com, as well as the alias collab.company.com, but when I enter collab.company.com I am getting the default OSX site.

    I agree, this seems to make sense in theory, but here is the result I am getting.
    I have my internal (not my osx server) dns server containing a host entry of collab.company.com = 192.168.1.xx. I have a virtual host entry in OSX in the aliases area (correct?) of collab.company.com for my collab site. However, whenever I enter the url in my browser of collab.company.com, I keep getting the default Mac OSX Server website page. I even put an alias in the OSX server site of mainpage to try and differenciate it, but it doesn't seem to take or matter.
    So once again, in theory I think "oh, just uncheck the enable button next to the default OSX website", I uncheck it, and then both of my websites are offline, or appear to be? For my collab site, the link redirects, but I get the error page.
    Safari:
    Not Found
    The requested URL /collab/public/index.php was not found on this server.
    Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
    Apache/2.2.14 (Unix) PHP/5.3.1 Server at collab.company.com Port 80
    Google Chrome:
    Oops! This link appears to be broken.
    Thing is, I even changed my collab site to be running on port 80 as well as a test. I check enable for my osx default page, and they are both back online. If I change the default osx sites port to say 87 or something, and leave the collab at 80, I then get the same bad request messages etc. If I put the osx site back to port 80, they both work.

  • SMTP Relay Username and password disappear when I close Server Admin

    Hello,
    I have a mail server that was working properly with SMTP relay until last week, when it started to bounce back to itself. I checked the settings and the SMTP relay username and password were erased. I type them in again, click on save, close and reopen and it's erased. Is there a way to enter this information other than the Server Admin application. If so, where is it located and what should I change? Thanks!

    Here is the result of postconf -n:
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    content_filter = smtp-amavis:[127.0.0.1]:10024
    daemon_directory = /usr/libexec/postfix
    debugpeerlevel = 2
    enableserveroptions = yes
    html_directory =
    inet_interfaces = localhost
    mail_owner = postfix
    mailbox_transport = cyrus
    mailq_path =
    manpage_directory =
    mydestination = $myhostname,localhost.$mydomain,localhost
    mydomain = spikenet.homedns.org
    myhostname = spikenet.homedns.org
    newaliases_path =
    queue_directory = /var/spool/postfix
    readme_directory =
    relayhost =
    sample_directory =
    sendmail_path =
    setgid_group =
    smtpdpw_server_securityoptions = login,plain,gssapi,cram-md5
    smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
    smtpdsasl_authenable = yes
    smtpduse_pwserver = yes
    unknownlocal_recipient_rejectcode = 550
    The log changed to:
    Apr 13 11:05:19 spikenet postfix/sendmail[74525]: fatal: bad string length 0 < 1: mydomain_fallback = .

  • Leopard Server Admin bugs

    Is it just me or:
    Gateway Setup Assistant creates setting that I can't do manually.
    Specifically:
    1. Network Address/Range styles invalid in Firewall
    under Server Admin - Firewall - Settings
    under Address Groups,
    there are groups 192.168.1-net 192.168.1.1:255.255.255.0
    and VPN-net 192.168.1.1:255.255.255.0
    BUT if you try to create a new group using this pattern of
    network address, such as 172.16.0.1:255.255.255.0
    it says this is an invalid network.
    The style that is accepted is 172.16.0.1/24, but
    I have to say, I'm not sure that is working as an address group.
    2. DHCP-> DNS "search domain" not allowed empty
    Again after Gateway Setup Assistant
    under Server Admin - DHCP - Settings
    under DNS
    Gateway Setup sets the DNS server to 192.168.1.1
    and leaves the "search domain" empty
    If I try to create an other DHCP range, it doesn't
    allow an empty "search domain"
    Anyone make any sense of these?

    Same for me with all of them. If you really don't want anything in the 'search domain' box for DHCP you can always enter something like 'fake.com', go to /etc/bootpd.plist and remove 'fake.com' from the file. Then restart DHCP from Server Admin and you'll be fine.
    For the firewall I've just been using the 192.168.0.0/16 style of addressing, but it is likely just to be misreporting rather than unable to use other methods. That's my guess, anyway.
    Andy.

  • Server admin overwriting virtual host conf file

    For some reason the website crashed this morning. The error log pointed to the virtual_host conf file. It crashes each time the we attempt to create an alias and then save changes.
    The only way to fix it is to go back and edit the conf file and then web service starts on its own.
    When I look at the file, it says: This file is auto generated by the Server Admin Web backend plugin whenever server settings are saved.
    Is there a way to configure this so the file does not change?
    Thanks!

    The best way to do this is to take the contents of /Library/Collaboration and put it in a location accessible from your newly set up Lion install.  In Server.app, enable Wiki, and run:
         sudo wikiadmin migrate -r /Path/To/Library/Collaboration
    After that, start the wiki and you should be good to go.  You should bind your Lion server to the same Directory as the Snow Leopard server, to ensure permissions and users carry across successfully.
        A.

  • Os X Server 10.6.5 Server Admin iChat not Editable

    Hello All,
    I upgraded my server to the most recent release 10.6.5. Previously my Ichat (or so I thought) was set correctly and we modifiable in Server Admin. ONce I updated all fields are greyed out and un-editable. I tried to reinitialize the plist with the PlistBuddy option suggested in this forum with no success.
    Here is the output to changeip -checkhostname
    bash-3.2$ sudo changeip -checkhostname
    Password:
    Primary address = 192.168.1.210
    Current HostName = appleXserver.local
    The DNS hostname is not available, please repair DNS and re-run this tool.
    dirserv:success = "success"
    This is obviously wrong. appleXerver.local is the local name of the server. This was working before the update. In server admin it shows that 192.168.1.210 resolves to server.679ave.com. (FDNQ) as it should.
    The name server that the primary zone 679ave.com. points to is dns.679ave.com.
    Any suggestions? Why did this change (did I have a bug to begin with?).

    ok figured out the dns problem...looks like in the system preferences the dns wasn't setup after the update. now sudo changeip -checkhostname gives
    bash-3.2$ sudo changeip -checkhostname
    Password:
    Primary address = 192.168.1.210
    Current HostName = server.679ave.com
    DNS HostName = server.679ave.com
    The names match. There is nothing to change.
    dirserv:success = "success"
    bash-3.2$
    now sudo serveradmin settings jabber gives
    bash-3.2$ sudo serveradmin settings jabber
    Password:
    jabber:s2sRestrictDomains = no
    jabber:authLevel = "ANYMETHOD"
    jabber:savedChatsLocation = "/var/jabberd/message_archives"
    jabber:dataLocation = ""
    jabber:enableAutoBuddy = yes
    jabber:enableXMPP = yes
    jabber:sslKeyFile = "/etc/certificates/server.679ave.com.7C3ACC0386ADFDE3A70C53C861BFA1BC85281421.c oncat.pem"
    jabber:initialized = yes
    jabber:logLevel = "ALL"
    jabber:sslCAFile = "/etc/certificates/server.679ave.com.7C3ACC0386ADFDE3A70C53C861BFA1BC85281421.c hain.pem"
    jabber:requireSecureS2S = no
    jabber:serviceMode = "ALL"
    jabber:savedChatsArchiveInterval = 7
    jabber:jabberdDatabasePath = "/private/var/jabberd/sqlite/jabberd2.db"
    jabber:hosts:arrayindex:0 = "server.679ave.com"
    jabber:eventLogArchiveInterval = 7
    jabber:enableSavedChats = yes
    jabber:s2sAllowedDomains = emptyarray
    bash-3.2$
    My ichat is now up and running again too!
    Message was edited by: darnelld

  • IChat server admin Service Running, status not available

    X-Serve running 10.6.8
    I noticed the other day thaat when I look at the iChat service in Server Admin, I observed the following:
    iChat service is: Running
    Start Time: Not Available
    Domain: Not Available
    Client Connections: Not Available
    The log screen says No Log Files exist
    I have seen similar screens when there was a slight lag in server admin gathering information to display on screen.  This stays this way indefinately.  The service is working as far as I can tell, IE people can log in, add each other, and chat.  A log file is in fact being used and updated (/var/jabberd/message_archive/)
    I noticed this because I was trying to autobuddy.sh, I script I use often to update when I add new users to the organization so they show up in everyones group list.  I attempted to stop the service from the command line using:
    #:serveradmin stop jabber
    #:jabber: state = RUNNING
    and was never able to stop iChat.  The system behaves the same after a reboot.  I am not sure what to do, or what the actual problem is.  The only thing besides a reboot that I tried was a permission repair from within the OS.
    In the log below I removed some user specific information because they are user names for users on my network.  This server and service is internal only.
    the console logs I have this:
    Nov 30 10:29:55 aphrodite jabberd/router[353]: message_log received a message with empty body
    Nov 30 10:30:15: --- last message repeated 2 times ---
    Nov 30 10:30:19 aphrodite jabberd/router[353]: message_log received a message with empty body
    Nov 30 10:31:05 aphrodite jabberd/router[353]: message_log received a message with empty body
    Nov 30 10:49:17 aphrodite com.mycompany.autobuddy[83710]: /usr/local/Scripts/auto_buddy.sh: line 2: /usr/sbin/jabber_autobuddy: No such file or directory
    Nov 30 11:12:34 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: mbr_check_service_membership returned 2
    Nov 30 11:12:34 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: no access restrictions found
    Nov 30 11:19:17 aphrodite com.mycompany.autobuddy[87010]: /usr/local/Scripts/auto_buddy.sh: line 2: /usr/sbin/jabber_autobuddy: No such file or directory
    Nov 30 11:49:17 aphrodite com.mycompany.autobuddy[90323]: /usr/local/Scripts/auto_buddy.sh: line 2: /usr/sbin/jabber_autobuddy: No such file or directory
    Nov 30 11:54:37 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: checking user "jimrumrillcotaoilcom" access for service "chat"
    Nov 30 11:54:37 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: mbr_check_service_membership returned 2
    Nov 30 11:54:37 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: no access restrictions found
    Nov 30 12:03:14 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: mbr_check_service_membership returned 2
    Nov 30 12:03:14 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: no access restrictions found
    Nov 30 12:03:32 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:04:26: --- last message repeated 2 times ---
    Nov 30 12:05:25 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:06:26: --- last message repeated 1 time ---
    Nov 30 12:06:26 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:06:57: --- last message repeated 1 time ---
    Nov 30 12:07:27 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:08:28: --- last message repeated 1 time ---
    Nov 30 12:08:28 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:09:26: --- last message repeated 1 time ---
    Nov 30 12:09:29 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:09:59: --- last message repeated 1 time ---
    Nov 30 12:10:30 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:11:30: --- last message repeated 1 time ---
    Nov 30 12:11:30 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:12:00: --- last message repeated 1 time ---
    Nov 30 12:12:31 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:13:32: --- last message repeated 1 time ---
    Nov 30 12:13:32 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:14:26: --- last message repeated 1 time ---
    Nov 30 12:14:33 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:15:34: --- last message repeated 1 time ---
    Nov 30 12:15:34 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:16:35: --- last message repeated 1 time ---
    Nov 30 12:16:35 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:17:05: --- last message repeated 1 time ---
    Nov 30 12:17:36 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:18:37: --- last message repeated 1 time ---
    Nov 30 12:18:37 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:19:17: --- last message repeated 1 time ---
    Nov 30 12:19:17 aphrodite com.mycompany.autobuddy[94140]: /usr/local/Scripts/auto_buddy.sh: line 2: /usr/sbin/jabber_autobuddy: No such file or directory
    Nov 30 12:19:38 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:19:53: --- last message repeated 1 time ---
    Nov 30 12:20:39 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:20:45: --- last message repeated 1 time ---
    Nov 30 12:21:40 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:22:10: --- last message repeated 1 time ---
    Nov 30 12:22:41 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:22:47: --- last message repeated 1 time ---
    Nov 30 12:23:42 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:24:26: --- last message repeated 1 time ---
    Nov 30 12:24:43 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:25:10: --- last message repeated 1 time ---
    Nov 30 12:25:44 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:26:45: --- last message repeated 1 time ---
    Nov 30 12:26:45 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:27:16: --- last message repeated 1 time ---
    Nov 30 12:28:24 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:29:00: --- last message repeated 3 times ---
    Nov 30 12:29:00 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Any help on what might be going on or a push in a direction would be greatly appreciated.
    Thanks!

    Well I searched the forums here and I found some similar issues, however the fix's I was directed too did not resolve the problem. 
    I did notice this today after reading a post regarding the use of the .local domain name, and fixing that fixes this issue:
    When i selected my server on the left hand side of server admin, click on settings at the top (the gear) then on Network, I see:
    Ethernet 1 (eth0) IPv4 192.1.1.4 Aphrodite.local
    I am not sure where the .local is coming from.  This is an internal server and has been configured with a FQDN for 2 years now, aphrodite.cotaoil.net.  On the server, the only other place I see the .local, is in system preferences, sharing, at the top it has my fqdn, but when I click on edit, it has a local host field that says Aphrodite, with a .local greyed out after, or ghosted.
    When I use the command changeip -checkhostname I recieve:
    changeip -checkhostname
    Primary address     = 192.1.1.4
    Current HostName    = aphrodite.cotaoil.net
    The DNS hostname is not available, please repair DNS and re-run this tool.
    dirserv:success = "success"
    the hostname not available message is new (well I know at some point in the not too distant past I did not have this message) so I am not sure if an update broke this or not but basically I am not sure where to go from here.
    The DNS settings are set the same as they were when I originally set up the server.  Reviewing DNS logs, I do not see anything abnormal.
    additionally when I run scutil i get:
    aphrodite:~ root# scutil --get LocalHostName
    Aphrodite
    aphrodite:~ root# scutil --get ComputerName
    Aphrodite.cotaoil.net
    I am a little stumped as to where to go from here.  I believe based on some other posts Ive read that this may have something to do with why I cannot see any iChat status and am recieving the dreaded "detailed service status not available until network configuration completed"
    Thanks for any and all thoughts.  Currently reviewing Hoffs tutorials, but I used combined Hoff tutorials and apple server guides when originally set up the server.  Please let me know what I did wrong (besides my internal IP range)

  • Server Admin only shows 201 messages in Mail Queue

    This issue has been haunting me since 10.5.0 and I can't seem to get rid of it. It's not crucial, but very obnoxious. In Server Admin (from multiple computers) the mail queue will only show a maximum of 201 messages. If there are more than that I have a cryptic "message" at the end of the list that has a message ID of "FFFFFFFFFFFF" and the Recipients Field has [...]
    I would love to be able to see all the messages in my queue if possible, but haven't found anywhere to fix this.
    Any help would be very appreciated.

    Thanks Alex. We aren't bouncing spam on our mail server, but I do notice that a lot of the mail is from MAILER-DAEMON. I'm assuming it's "User not Found" messages from hosts that don't really exist. I've tweaked the server using some suggestions from osx.topicdesk.com to clear some of those out, but it hasn't been 100% effective.
    I think part of the issue is that the server is a dual G4 Xserve and is scanning junk mail on all messages. I assume that those two factors contribute to the backup of mail in the queue.
    As for volume of mail, we receive 100k a month.

  • Server Admin's proxy configuration... whacked? (Doesn't seem to work)

    I just upgraded to Apache2 so that I could, sensibly, use the Server Admin app to manage all my web sites. Previously, my various httpd conf files were too complicated and I had resorted to hand coding them.
    The good news is Server Admin and Apache2 are much closer to functional.
    One bit of bad news: I can't get the reverse proxies to work consistently. Once set up, I get the most peculiar mix of success and failure -- almost at random. For example, some URIs load; others don't; sometimes a page loads, but it's style sheet doesn't.
    What I want is simply this:
    */confluence (proxy to) localhost:8081/confluence
    Using hand-edited config files, I'd usually do something along these lines (and this works great, by the way, if I stick it into 0000any_80www.mydomain.com.conf:
    ProxyRequests Off
    ProxyPassReverse /confluence http://localhost:8081/confluence
    ProxyPass /confluence http://localhost:8081/confluence
    So, off to Server Admin to make this work. I tried checking "Enable Reverse Proxy" and specifying a Proxy Path of "/confluence" and a Worker URL of http://localhost:8081/confluence. This ended up created the following entry in my 0000_...conf file:
    <IfModule modproxybalancer.c>
    ProxyPass /confluence balancer://balancer-group/
    ProxyPassReverse /confluence balancer://balancer-group/
    <Proxy "balancer://balancer-group">
    BalancerMember http://localhost:8081/confluence
    </Proxy>
    </IfModule>
    I wasn't able to figure out what a Sticky Session Identifier, Route or Load Factor would be used for... so I left those blank. Perhaps that's why it's not working... sure would be nice if there was some help in Server Admin...
    Hm. Anyhow, Ok, looks alright. I'm not totally sure about the balancer bits (like why they are there), but I don't see why it wouldn't work. But... IT DOES NOT. I get totally inconsistent results. Some pages load, some don't. Sometimes I get some page assets, while others don't come through. Bah. However, if I get rid of the above, and simply put this in:
    ProxyRequests Off
    ProxyPassReverse /confluence http://localhost:8081/confluence
    ProxyPass /confluence http://localhost:8081/confluence
    It works great. Only problem is, anytime I edit a server configuration, Server Admin goes and deletes those lines! I think I've found a way around it though. I put the above lines into a "0000.proxy" file (in /etc/apache2/sites/0000.proxy) and now I've added this line:
    Include "/etc/apache2/sites/0000.proxy"
    At the bottom of my 0000_...conf file. So far, Server Admin hasn't deleted that line... and it seems to be working.
    BUT, I'd just LOVE it if someone could tell me how to make this work without hacking around in the command line! Very annoying -- and of course, my proxies are showing up in Server Admin, and I really wish that would work.

    Hi there
    For the benefit of anyone looking at this thread, what is meant here is that if you choose to open the help for RoboHelp, you have an abiliity to add a comment. That comment may be kept private or shared with others. If you elect to share it with others, it is generally added as a comment into the pages that provide the help. If approved, Adobe may amend the help topic to reflect the new information.
    @Jared - Was that information missing in your file? I thought when you elected to use this file that it was automatically populated with all available settings. And unfortunately (IMNSHO) the settings don't immediately reflect the settings in the dialog. (I think they should, as a starting point. At least, that's the behavior *I* expected the first time I played with the feature. I was admittedly taken aback when it didn't work that way.)
    Assuming the setting was missing, how did you manage to sort what setting should be added?
    Cheers... Rick
    Helpful and Handy Links
    RoboHelp Wish Form/Bug Reporting Form
    Begin learning RoboHelp HTML 7, 8 or 9 within the day!
    Adobe Certified RoboHelp HTML Training
    SorcerStone Blog
    RoboHelp eBooks

  • Share point in server admin not working correctly... I think

    I suspect that the share point in server admin is not working correctly. In workgroup manager when I click on a user and then click on the "home" tab, under the full path field I see a file path of:
    afp://server.mydomain.com/Users
    However if I go to Server Admin -> AFP -> Share Points then click on the Users share and then click on the share point tab below, enable auto mount is disabled. How can this be possible? I thought for a directory to show up in home in workgroup manager it had to be set as an auto mount. Has something possibly corrupted? And what?

    Here's a bit more information about our setup and our experiences with Apple's CUPS implementation:
    On the server, all printer queues are set up with only lpr and ipp sharing enabled with the PPD setting for each printer set to Generic Postscript. We found that setting the PPD to the printer specific one on the server caused problems when clients tried to use printer specific options, like paper tray selection, etc.. The selection would be undone, apparently because the driver on the server would override the previous settings. Using Generic Postscript allows the client PPD settings to go through unmodified. Our printers are general a mix of HP LaserJets and some Sharp Copiers.
    All clients use lpd to the server queues with the printers' actual PPDs configured. Using ipp is superior in that printer feedback (jams, out of toner, etc) makes it back to the clients, but ipp only works when the client, the server, and the printer are on the same network. If the ipp client is not on the same network, the client spooler immediately goes into a paused state and the print job is stuck on the client.
    Using lpd to the server queues works reliably, but there is no feedback to the client. Jobs disappear from the client queue and go to the server, appearing to the user as a successful print. If the printer is down, there's nothing they can see or do about it.

  • Server admin doesn't display info

    I'm experiencing slow network logons for our 10.6.8 Mac Mini server (circa 2009). 
    I can't get server admin to display any info - the fields are blank - both logged on locally and remotely. 
    I looked in some logs, but don't know which ones are useful as a starting point for this issue.
    Can you help point me in the right direction?
    Thanks

    Do you get any errors or indications that changes are required when issuing the following (non-destructive, informational) Terminal.app command?
    sudo changeip -checkhostname
    Is the domain a real and registered domain, or is it a ".local" domain?
    Is the configured server at a static IP address?  (Either a static address on a private LAN, or a public static address.)
    Is there exactly one DNS server or one pool of DNS servers, and is that DNS server or pool local?  (Are there any references to other non-local-LAN DNS servers?)
    Logs?  Assuming the server isn't all that busy when you test, launch Console.app, start your connection test with the Server Tools, and look at the aggregate log display for errors.  (If it's busier box and can't be quiesced for testing, then yes, you can have to drill down into individual logs, or grep -R the /var/log directory for server or such...)  But without knowing what (else) is wrong, it's difficult to predict.

Maybe you are looking for