aha! after digging further into the logs........
June 22nd -> 'waiting for UDP socket to open up' 50011
OK.... that makes sense... kinda.. how its now having that issue, im not sure.
So I opened up the firewall setting and turned the fire off.
No firewall running.
I have the log window open, and im watching it in real time as the worker keeps having the same issue: 'waiting for UDP socket to open up 50011'
Now, I have another worker that seems to be running smooth over that port to the supervisor. Also, when I do 'qbhosts' from the functional worker, both workers now show up as active... however, when i do 'qbping' on the problem worker, it cannot even verify that the super is running.. it cannot reach it, 'UDP socket timed out'
anyone have a suggestion as to how I can deal with this UDP socket? Im noobish with macs and unix at best.. if this were windows i'd try to open up the port specifically, however, as it stands right now the firewall is OFF. I don't get it. My next move is to see if perhaps the supervisor is blocking UDP traffic from this worker...
one other piece of info... on this problem worker i cannot connect to the rest of the internet either... when i do 'ifconfig' I do get assigned an IP address that normally works.. this worker does not return any packets when pinged either.
-n8
-----------------------
I think this particular computer is just crazy... now its working after reboot. Lets call this 'solved' for now.
