With DL7 slaves on both windows and linux I’m getting this error all the time:
2015-01-29 11:19:57: Info Thread - Could not check if Pulse is running because: The requested address is not valid in its context 255.255.255.255:49250
As far as I can tell it doesn’t affect anything, Pulse is running fine, I can still successfully remote control the machines etc, but it muddies the log files and I’d like to solve it for peace of mind.
My first guess is it’s because hostnames don’t resolve on our network as we’re testing on aws, but I don’t think this should be an issue as the repo is set to use slave’s IP for remote control, Pulse is set to Use Pulse’s IP for remote control, and in the pulse properties I’ve removed the hostname leaving only the pulse IP. All firewalls are currently disabled, and I’ve never seen this error in DL6.
Can I have you verify whether the override is set properly and being recognized by opening the pulse panel? Go to View, New Panel, the Pulse. Once open, right click your Pulse machine and choose properties. Once there, verify that the IP is in the override seen in the attached image. Thanks.
I’ve got it in my plans to set up a test here, but while we wait for results of that, do you happen to have a firewall enabled on your Pulse machine? Version 7 chooses the listening port at random, so with the IP address are you still getting ‘address invalid’ or is it giving you a new error?
I can confirm that we’re testing this with no firewalls enabled in the slave or repo machines, also the security groups for each are set to allow all traffic between them. thanks for looking into this
