GrowlHelperApp WARNING: could not register Growl server

[joesap]

Network notifications do not work on 1.2, and in fact have never worked for me.

I performed a clean install of Growl 1.2 after removing the following:

~/Library/Preferences/com.Growl.GrowlHelperApp.plist
~/Library/Caches/com.Growl.GrowlHelperApp
~/Library/Application Support/Growl/
/Library/Receipts/growl.pkg

Anytime I check the box on the Network tab to "Listen for incoming notifications" it gives me the following warning message in the Console:

GrowlHelperApp WARNING: could not register Growl server.

Same result on three machines after performing a clean install as above: MacBook Air running 10.6.1, Mac mini (Intel Core 2 Duo) running 10.6.1 Server, and iMac (Core 2 Duo) running 10.5.8 Server.

Ideas?

I'm only just getting into Growl but it's very cool. I had hoped to do some cool things with network notifications so it's frustrating that I can't get it to work.

Thanks for any advice and assistance.

Joe

[boredzo]

Make sure you don't have two copies of Growl installed. Run the Uninstall Growl application on the Growl 1.2 disk image, then reinstall it.

[joesap]

It's only installed in /Library/PreferencePanes on all three machines.

Any other ideas? Is there a more verbose log that might provide a clue?

[boredzo]

Is there a more verbose log that might provide a clue?

Nope. When we log the message “Could not register Growl server”, it's because that's all we know.

Are you trying to run Growl under multiple user accounts at once? That won't work (for this reason).

[joesap]

Are you trying to run Growl under multiple user accounts at once? That won't work (for this reason).

No. In each case, it's only running under one user (actually it's installed in /Library/PreferencePanes/). I'm only logged into one user on each machine.

I should mention that I've never gotten network notifications to work under the previous two versions (the only two I've tried). Maybe it's some third-party software that's interfering? Maybe it's my network? I can't imagine what might be the reason it's not working. Any further thoughts would be appreciated.

Thanks.

[boredzo]

Yeah, you're not the first person to have this problem. Unfortunately, there's no way for us to find out any more about it.

[joesap]

Yeah, you're not the first person to have this problem. Unfortunately, there's no way for us to find out any more about it.

Hmm. Does it help that I have extensive troubleshooting experience and would be willing to help try to track it down? (I am an Apple Consultant.)

Please let me know if there is anything else I should try.

Thanks again.

[joesap]

I'm in the midst of troubleshooting this. I just tried it on a fourth machine, a plain white Core Duo MacBook running a relatively clean and almost brand new Snow Leopard installation (10.6.1). I installed Growl (1.2) for the first time ever on that machine, and it exhibited the same symptoms I've been experiencing up until now.

At this point, I'm having trouble believing that this feature even works. I tried everything I could think of, testing it again at each step by stopping and starting Growl using the System Preference pane. Each time, I got the dreaded "WARNING: could not register Growl server" message in the Console.

Here's a smattering of what I tried: uninstall UnderCover for Mac; turn off Remote Disc, Remote Management, and Remote Login; disassociate from Network Account Directory Server; turn AirPort off and unplug Ethernet cable; turn off secure virtual memory; perform Safe Boot; uninstall Growl and remove everything I could possibly find including the Growl-related files or folders in ~/Preferences, ~/Application Support, ~/Caches, /PreferencePanes, and even some crazily-named temp files I found in /var/folders/ that Growl seemed to be using and/or were using a Growl-ish name, and restart again for good measure. No luck.

And that's not all! I even moved Growl.prefPane from /Library to ~/Library. All without any impact or improvement.

At one point, I also turned ON the built-in Firewall, and then started Growl. Sure enough, I was asked whether to allow Growl through the firewall. I clicked Allow, and got these two lines in the Console:

9/30/09 10:08:09 PM Firewall[262] GrowlHelperApp is listening from 0.0.0.0:23052 proto=6
9/30/09 10:08:25 PM GrowlHelperApp[273] WARNING: could not register Growl server.

I can see that it is listening on the TCP port listed at the bottom of the Network tab in the Growl preference. What about the UDP port (9887)? Should the firewall report that Growl is listening on that port? Perhaps this is a clue?

I'm in the process of clean installing Snow Leopard on a blank hard drive. When it's finished, I'm going to install Growl and see what happens.

I will report back.

P.S. If anyone read this whole thing, please feel free to chime in with any thoughts. Does it work for you? (If so, I would like to know what your secret is.)

[joesap]

Yeah, you're not the first person to have this problem.

Well, that about does it for me.

I performed a clean, default installation of Snow Leopard on a blank hard drive, fully patched it with all the Apple Software Updates, and then installed Growl 1.2... I turned on network notifications by checking the boxes to listen for incoming notifications and allow remote application registration... wait for it...

It did not work. Same error message in the Console. So... this is obviously a bug in Growl, right?

For the record, I tried it on an Ethernet connection to my network, an AirPort connection to a different open wireless network, and with the network interfaces disabled. The machine I installed 10.6.1 on was a MacBook Core Duo with 2 GB of RAM.

Please confirm this is bug and let me know when/if it will be fixed, and if you need any more info from me. I would be happy to test the next beta release.

[boredzo]

So... this is obviously a bug in Growl, right?

Nope. Here's the relevant code:

Code: Select all

			socketPort = [[NSSocketPort alloc] initWithTCPPort:GROWL_TCP_PORT];
			serverConnection = [[NSConnection alloc] initWithReceivePort:socketPort sendPort:nil];
			[serverConnection setRootObject:self];
			[serverConnection setDelegate:self];

			// register with the default NSPortNameServer on the local host
			if (![serverConnection registerName:@"GrowlServer"])
				NSLog(@"WARNING: could not register Growl server.");

There is nothing wrong with that code that we're aware of, and no way to get any further information about why it could not register that name.

I can add some nil checks, but that's about it.

[joesap]

Here's the relevant code: (snip)

Well, does it work for you? Anyone else?

(Forgive me if this is a stupid question, but after trying it and seeing it fail on a clean install I find it hard to believe that it works for anyone.)

[boredzo]

Well, does it work for you?

Nope. Which is good, in that I can try my nil-check idea without having to post a build. But if that doesn't work out, and I don't think it will, I'll still be stuck for a reason why that registerName: message fails.

[pokernut]

I too am seeing the problem: "01/10/09 2:03:10 PM GrowlHelperApp[19071] WARNING: could not register Growl server." This is with Growl 1.2 installed.

I tried going back in my system.log history but my last boot was too long ago and I don't have the logs any more so can not verify that it was happening with the prior version.

joesap, I appreciate your tenacity to try this on a clean install. I have anything but a clean install. I'm running 10.5.8 (fully patched) on a well used install that's had Growl on it for quite some time. I'm holding off on a clean install and 10.6 until I buy one of those fancy new Intel X25 G2 SSD's.

[BlueFrog]

Ohhhhh maaaaan! I had network notifications working fine with 1.1.6, but they broke after upgrading to 1.2. I've gone back to 1.1.6 but the network notifications haven't come back. Blah!

[BlueFrog]

Well, I got my network notifications back by installing 1.1.5 and messing around with it on two machines for about an hour. Looks like I'm sticking with this setup, at least for awhile.

[boredzo]

I believe I've fixed it. This change will be in 1.2.1.

[joesap]

I believe I've fixed it. This change will be in 1.2.1.

Thanks, boredzo. Is there any word when 1.2.1 might be released? Any way to get it sooner, assuming it works and there are no regressions in your testing?

[boredzo]

Since 1.2.1 is now out, I'd appreciate it any of you who had this problem could report to us through the discussion list (this forum being closed) whether 1.2.1 fixed it for you.