Error occurred while updating slave ping cache

Deadline
1

Hi guys!!

When i look at the console, i see that deadline is logging this error all the time. Any ideas?
Also, sometimes, some slaves that are not active dissapear’s from the slave list. Maybe there is a link with this error. I’ve tried to check about the coma , / . problem but i do not find where to check this in CentOs.

Deadline Version: 6.1.0.54178 R - CentOS 6.4
thanks a bunch !!
sly

2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:21: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:29: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:40: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:10:50: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:11:01: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:11:11: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:11:22: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:11:32: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:11:43: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:11:54: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)
2014-04-30 11:12:04: Error occurred while updating slave ping cache: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)

2

Hey Sly,

Looks like you guys are still running a Beta build of Deadline 6.1. There were some fixes made in subsequent builds that I believe should fix the issue you’re seeing. Can you guys try upgrading to the release build of 6.1 and see if this is still a problem?

Cheers,
Jon

3

Thanks for your help Jon!

Ok i will check to upgrade… I was about to upgrade to the latest 6.2 beta instead…
Will keep you posted of any findings then!

cheers!!!

sly

4

Hi!!!

After upgradinng to 6.2-0.32, we still have this being logged…
Any other clues?!

thank you

sly

5

Also got this log from pulse’s log:

Clean Up Thread - An exception occurred during clean up: The given SlaveInfo and SlaveSettings must be for the same Slave. (System.ArgumentException)

Exception Details
ArgumentException – The given SlaveInfo and SlaveSettings must be for the same Slave.
Exception.Data: ( )
Exception.TargetSite: Void .ctor(Deadline.Slaves.SlaveInfo, Deadline.Slaves.SlaveSettings)
Exception.Source: deadline
Exception.StackTrace:
at Deadline.Slaves.SlaveInfoSettings…ctor(SlaveInfo slaveInfo, SlaveSettings slaveSettings)
at Deadline.StorageDB.MongoDB.MongoSlaveStorage.GetSlaveInfoSettingsNoCache(String slaveInfoFields, String slaveSettingFields)
at Deadline.Pulses.PulseCleanUpThread.ThreadMain()
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

6

Can you try deleting and re-adding this slave to your queue?

7

Yes will try that!
But for some reasons, Deadline manager dont show up every slaves like before. It only show up present connected launchers.
Everytime I relaunch Manager, it just refreshes the current “LIVE” machines and not ALL machines that have already registered to the repo.

Is this normal behavior? I dont remember seeing this on 5.x

thanks!!

sly

8

Hi,
Could you submit a private support ticket as I think your DB is corrupt and we will need to help you run a repair command on your DB. Have you suffered a power outage at all on your DB?
support.thinkboxsoftware.com/tickets.php
Mike

9

thanks alot Mike!
my god this is scary!!
support ticket request #892955

see ya!

sly