Currently Being ModeratedAug 6, 2012 2:12 AM (in response to Tho615)
I've had the problem from the start; after nearly every boot (max. 3) I get the alert that the hostname was changed from servername to servername.domain.com. No matter how many time I run through "update" or try to redo the Server.app Network settings (even though I'm not really changing anything), I still get the alert.
I did a clean install (I wiped the HD) of Mountain Lion + Server. After adding Server.app, I followed through setting that up correctly the first time:
- computer name: servername
- hostname: servername.domain.com
- IP address: I have decated IP address, and the Mini connects manually my Time Capsule.
The domain is my registered domain, of the form "domain.com". I'm not using .private or .local.
DNS got setup automatically and correctly; I can connect to Profile Manager from clients and bind to OD.
Using Cteam's notes, I verified that these checkout:
nslookup <server's IP address>
This one didn't until I added my domain to the search domain.
Checking the system.log, I can see that configd is setting the hostname at boot.
8/6/12 10:40:25.543 AM configd: setting hostname to "servername.domain.com"
I suspect that's what's generating the errors; for whenever I don't see that entry, I don't get an alert. The problem it seems is getting that FQDN to stick as the hostname. I haven't been successful.
Here's a list of what I've tried, none with success:
sudo scutil --set HostName servername.domain.com
as well as
sudo changeip - IPaddress IPaddress servername.local servername.domain.com
sudo changeip - IPaddress IPaddress servername.domain.com servername.domain.com
I've also tried turning off the DNS, trashing the settings; and then running through Server.app Network again, which redoes the DNS. nslookup checks out, as does OD binding and profile manager from clients. I see the alerts after 1-3 reboots.
I've even tried the radical method, of turning off the DNS and trashing the settings. Then deleting:
which as far as I can tell is the 'master' network config file. Trash that and you lose all Network interfaces, computer name, hostname, IP, etc. After trashing that I had to go into System Preferences: Network to create a new location, which generated new network protocals, particularly ethernet. Then did the Server.app: Network to set once again, computername and hostname, which again redid my DNS settings.
2-3 reboots later I'm still seeing the alert and I see configd doing it's thing at startup.
Currently Being ModeratedAug 6, 2012 1:36 PM (in response to Gary Finch)
I did many fresh installs, the moment this alert start to occur in my setup is straight after installing Server app when I modify DNS zone records. So it should has nothing to do with directory or anything else that are turned off at that point.
I feel this has something to do with the way bonjour works after a server's changes to .private (which I use) or a public domain. Probably a bug. I also have experienced very slow handshakes for AFP/screen sharing connections using the side bar of Finder (again bonjour here is a bit wried), but connect using CMD+K with fqdn works fluently.
Currently Being ModeratedAug 6, 2012 2:04 PM (in response to tcpudp)
I think you may be right about the bug, I had to shut down and replace the UPS today and the alert came back and never went away. I might have got luck it stay away for awhile. I too now need to find a fix.
Currently Being ModeratedAug 7, 2012 3:42 PM (in response to tcpudp)
After installing Parallels Desktop 7 in my server, this problem started to happen.
The only programs I've installed on my ML Server are Plex Media Server and Parallels Desktop 7.
Currently Being ModeratedAug 8, 2012 12:14 PM (in response to tcpudp)
It's already being worked on. Let's hope it'll be in the next update.
This is a follow up to Bug ID# 12041267. This bug has been closed as a Duplicate. The issue is being tracked under the original Bug ID# 11922353 which is also listed in the Related Problem section of your bug report. To check the status of the original bug report, please visit the Related Problem section of the Problem Detail view of your closed duplicate bug.
Submitted a bug report 12041267 for now.
Currently Being ModeratedAug 21, 2012 1:50 PM (in response to Tho615)
I think I actually found a solution ... yes it does not fix the bug, however it gets rid of the oh so annoying "red badge" appearing on the Server App icon in the dock and the push notifications appearing in Message center.
1) Open Server App
2) Click on Alarms
3) Click on the Delivery tab
4) Uncheck the two boxes next to "Network Configuration Change"
5) Close Server App
6) Try a reboot ... the nagging "cosmetic" bug should be gone now
Currently Being ModeratedSep 12, 2012 7:08 PM (in response to pjp_1976)
I just did a fresh re-install of OS X Server, and I'm getting this error again - BUT I think I might know the cause! When I was setting the server up a few minutes ago, I entered server.<mydomain>.com as the host name, leaving the already filled "server" as the local host name.
I think the key may be to change the local host name to match the host name!
Anyone know how to change the local host name?
Currently Being ModeratedSep 16, 2012 9:54 AM (in response to Tho615)
Hello it's appear that i have this message alert too, when i reboot my router with or with out ipv6 and try with nativ or tunneling options.I'm ok with that and know what I do.so nevermind the alert.
Considering that, see your pref system pannel and go to network,
perrhups are you on dhcp? turn it off and stay with a ip fix...