Trying to get notifications working over the network

[RealityMonster]

Is there anything that I have to do other than turn one machine on to listen and setting the other to forward notifications? Neither of my machines has the internal firewall turned on, though they're both plugged in through a linksys router.

Bonjour seems fully active on my network for everything, if that's an issue.

One machine is my headless Mac Mini mailserver. I'm trying to use the application Temperature Monitor to let me know if heat becomes a problem while it's sitting in my closet.

Any advice? I haven't seen much documentation about this.

[The_Tick]

There's not much documentation because it's just not right in general.

Can you show us screenshots of the network tab for both machines?

[RealityMonster]

It's not really much to look at.

[The_Tick]

Weird, it should be listing at least one host in one of those in that table.

Is Growl running on both?

[RealityMonster]

Yup, running on both. I just double checked on the remote machine; it's certainly running on my desktop machine.

I'm glad this looks weird to you; it seemed pretty straightforward, and I thought I might be getting dumber.

[The_Tick]

What OS/Growl version on each?

[bgannin]

At a glance it looks like 10.4.x and 1.1 on each.

[RealityMonster]

Good call. Both are as up to date as possible on revisions of OS X and Growl.

[PhilZombie]

I can confirm network problems in recent versions. I had networking setup and working well, until one of the recent betas. Not sure exactly which one, but I think it was working ok in beta2, but broken by beta 6.

Now I get no notifications between computers, although I CAN see the other computer names in the networking dialog.

[leoofborg]

Hello Folks...

I -finally- got networking WORKING in Growl... here's what I did:

Forwarder: The machine that's forwarding Growls to..a

Listener: The machine that 'Listens' and has a server password.

* Made sure that ports were set properly and Little Snitch allowed traffic from GrowlHelper.

* Did a complete de-install of Growl, prefs, and EVERYTHING in application support. GrowlHelper prefs, all tickets, plugins and any leftover installed 'views' like SoundView in /Application Support/Growl/

* DISABLED any sound settings in Growl/Applications/Settings/

For some reason, if you have a 'Sound' associated with a notification it WILL NOT forward to a machine that is listening.

I had Ribbit set with a sound from the forwarder, NO notifications went thru.

HOWEVER on the 'listening' machine you can run the same apps [like Azureus and Ribbit, -just- to register to the app list].. So on your LISTENING machine set the sound notification.

When the notification comes from the Forwarder it will play the sound via the setting on the 'Listener'.

* I also used numbers only for the 'Listener Password'

I don't know why the SoundView from .76, or the sound settings from the Forwarding machine cause the network to futz.. but this sounds like a bug to me.

Sorry for the verbose explanation.. I'll blog this a bit more coherently later...

-Leo [getting up for BORGwork in a couple hours]

[leoofborg]

Any advice? I haven't seen much documentation about this.

Okay, I've distilled what I've done in this blog entry:

http://expatleo.wordpress.com/2007/09/13/having-trouble-with-growl-over-the-network-disable-sound/

My humble suggestion to the Growl team is that the uninstaller should nuke all vestiges of Growl from the user's system, including all Growl prefs and anything in /Application Support/

Just my 2 yen. For the record I have network Grown working and sound set ONLY on the Listening Machine.....

[michno]

Man, do I wish I hadn't upgraded from 0.76. I've tried the delete-all tips but network notifications are not working anymore. Sigh...

I also wish I could help out with the coding of that part, but...

[The_Tick]

.7.6 is still available should you need it.

[dtich]

i have also had *many* probs with .7.6 and 1.1 and 1.1.1 over the network. i've found that even with firewalls disabled, somehow entering a service for the growl ports helps (??), odd but seems true...

ALSO, i have major issues with growl locking up the kernel on my server when it tries to deliver a notification to an offline/sleeping computer... this may or may not be an issue only for machines on a wireless network. not sure yet. i have wired and wireless machines and it seems only the wireless ones have a bearing on this..?

i get portforward errors and dictionary send and things like that in the console and the kernel/main thread hangs for several, like 10, seconds. really is screwing up my automation and in particular my phone messaging system since growl sends callerid around the house on incoming calls. my answer system then drops 10 secs of audio while the kernel halts trying to delivery the notification.

DRAG.

also, have a lot of coreendianflip errors, are these related to growl as well? anyone know?

any help on this would be much appreciated, tia.

os10.4.10; growl 1.1.1, intel mini server, various receiving machines

[dtich]

i have also had *many* probs with .7.6 and 1.1 and 1.1.1 over the network. i've found that even with firewalls disabled, somehow entering a service for the growl ports helps (??), odd but seems true...

ALSO, i have major issues with growl locking up the kernel on my server when it tries to deliver a notification to an offline/sleeping computer... this may or may not be an issue only for machines on a wireless network. not sure yet. i have wired and wireless machines and it seems only the wireless ones have a bearing on this..?

i get portforward errors and dictionary send and things like that in the console and the kernel/main thread hangs for several, like 10, seconds. really is screwing up my automation and in particular my phone messaging system since growl sends callerid around the house on incoming calls. my answer system then drops 10 secs of audio while the kernel halts trying to delivery the notification.

DRAG.

also, have a lot of coreendianflip errors, are these related to growl as well? anyone know?

any help on this would be much appreciated, tia.

os10.4.10; growl 1.1.1, intel mini server, various receiving machines

[leoofborg]

coreendianflip is not a common error, at least not one that I've seen on either of my Intel rigs.. they both now growl back and forth with impunity.

To the user, did you delete all your Apps and tickets and let them re-register? Did you replace all your 'Growl Extras' with the new ones?

To the Devs.. I found this thread on coreendianflip errors and guess what? They mention Growl. One user using GrowlNotify as of 13.Sept.07:

That error means someone (Growl?) isn't passing good arguments to the OS X call CoreEndianFlipData(). That call is used to flip Endian byte order for integers, and is used when running on Intel processors.

from this thread right here:

http://www.perceptiveautomation.com/phpBB2/viewtopic.php?p=13175

[MurphyMac]

Just to add another case. I've spent hours trying to get Growl working over my network. Many manual uninstalls. tried with rebuilt machines too.

Next step would be to try to add the ports in somewhere, not sure where. I don't use Mac firewall stuff. But I'll look at that next time I get the Growl urge. Right now I'm to irritated with it!