Deadline Monitor is terribly slow, suddenly.

Deadline
1

I have no idea what this could be, but, here are the steps I performet two days ago:

  1. I installed a new server, a dedicated license server + pulse server.
  2. I stopped Pulse running on the file server
  3. I installed the client apps on the license server and ran Pulse
  4. Suddenly I got over 600 Deadline reports of “Corrupted JOB XXXXXXXX”
  5. So I fired up the monitor and noticed it takes AGES to perform even basic functions, or even connecting to the Repository.
  6. I managed to delete all the finished jobs (there are no currently active jobs)
  7. Then I even restarted the File server (where the repository sits), due to a different reason, but still it didn’t change anything.
  8. Still, the monitor not only is extremely slow (takes a minute to refresh, or over a minute to simply change a job property etc…), but also it doesn’t recognize Pulse running on the new server.

The config is fairly straight forward. Everything is on the same subnet. Everything is discoverable. The servers (file and license) both run Windows Server 2008 Standard. It’s all a part of the same one domain. I had previously run Pulse on the file server where the Repository is installed.

I have no idea what it is, what happened or what could be the cause of such a mess, but even on my 1gbps local LAN network the Monitor performs this terribly slow.

Any hints or tips would be much appretiated.

2

Hmm, interesting, I just found out that the Monitor actually doesn’t like searching for Pulse on the other server.

When, in the Repository Options, I set to search for Pulse on the File Server (even though the Pulse is not running), the Monitor performs perfectly fine and fast. However, as soon as I put there the other server’s name to search for Pulse (again, even though the Pulse is not running), the tasks take ages to be performed by the Monitor. :frowning:

3

Is there any firewall/antivirus software running on the new Pulse machine that could be interfering with the communication between the Monitor and Pulse? Also, when you refresh in the Monitor when it’s connected to this new Pulse, does the Pulse icon at the bottom of the Monitor light up, or does it remain grayed out? If it’s grayed out, that means that the Monitor isn’t able to connect to Pulse.

Cheers,

  • Ryan
4

Ah! Yes! It was a firewall! It got turned on automatically again after I joined the server to the domain.

Sorry for this stupid question, I didn’t realize the FW got turned on again after I manually switched it off. :blush:

Thanks a lot for the help!