Pulse Connection Problem

Deadline
1

I am having a pulse connection problem on my machine.

Pulse is running fine on our windows 2008 server. Most of the workstations connect and behave fine.

My workstation however connects (according to the little icon in the corner of Monitor) but when I do a jobs refresh it loses the connection and does a sloooooow refresh.
Doing an all slaves refresh seems to keep the pulse connection and is fast.

Things I have tried:

Restarting Pulse
Reinstalling my installation of deadline client.

Details:
Windows 7
Deadline 5.2
~40 render slaves at the moment

Any ideas what I should try next?

Regards,
Rhys.

2

Can you send us the Monitor log after a slow refresh? You can find the log by selecting Help -> Explore Log Folder in the Monitor. We can check to see if there are any errors.

Thanks!

  • Ryan
3

2012-10-23 03:20:26: BEGIN - RHYS-WS\owner
2012-10-23 03:20:26: Enqueing: &Refresh
2012-10-23 03:20:26: Dequeued: &Refresh
2012-10-23 03:20:26: Attempting to contact Deadline Pulse (Seahorse)…
2012-10-23 03:20:26: Requesting jobs update from Deadline Pulse…
2012-10-23 03:20:27: Invalid response received from Deadline Pulse. ‘Invalid’ recieved when expecting ‘JobsUpdate’
2012-10-23 03:20:27: Attempting to contact Deadline Pulse (Seahorse)…
2012-10-23 03:20:27: Requesting jobs update from Deadline Pulse…
2012-10-23 03:20:27: Invalid response received from Deadline Pulse. ‘Invalid’ recieved when expecting ‘JobsUpdate’
2012-10-23 03:20:29: Attempting to contact Deadline Pulse (Seahorse)…
2012-10-23 03:20:29: Requesting slaves update from Deadline Pulse…
2012-10-23 03:20:32: Update received from Deadline Pulse.
2012-10-23 03:20:32: Received Update for 43 slaves.
2012-10-23 07:20:32: Enqueing: &Refresh
2012-10-23 07:20:32: Dequeued: &Refresh

I guess that is somewhere to start looking!
What should I do now?

I tried re-installing pulse - that didn’t work either.

R

4

That’s the suspicious part. Can you confirm that both your machine and the Pulse server are running the same version of Deadline?

5

Yes they are.

I re-installed both from the same installer just to be sure.

R

6

Weird…

I guess the next thing to do would be to enable Pulse verbose logging, which can be done from the Application Logging section of the Repository Options. After enabling the option, restart Pulse so that it recognizes the changes right away. Then while Pulse is running, check if it prints out any errors when responding to the JobsUpdate request from your machine.

Hopefully Pulse is printing out something that explains why it’s sending an Invalid message.

7

I get:

Listener - TIMEOUT (unknown client): received no request
Listener - TIMEOUT (unknown client): received no request

It’s hard to know if anything else is relevant - it’s really tricky to figure out what is what when hundreds of lines stream past every few seconds on the log.

I’m certain that those lines are relevant to my problem because they only appear the second I press refresh

If this problem is consuming too much time, forget about it. We’re planning to upgrade to 6.0 once this current job finishes in a months time and I can just grit my teeth till then.

R

8

If you don’t mind waiting until 6, when we don’t mind either. :slight_smile:

It definitely won’t be a problem in 6 since Pulse isn’t used as a proxy.

9

just as an update to this problem,

I restarted the machine that the pulse server runs on for an unrelated reason. When it came back up, Pulse was suddenly working for me again.
I like problems that get fixed like that.

R