After installing the 6.2 beta I have no more jobs that are displayed (properly) in the deadline monitor.
There are 2 jobs running, of which 1 job shows the task progress.
Also, all the other jobs are gone.
Could this be caused by installing the 6.2 repository on the old location while there was still 1 job running (it was a realflow job that I didn’t want to interrupt)?
Console message:
2014-03-28 13:55:22: Error occurred while updating job cache: Value was either too large or too small for a Single. (System.OverflowException)
2014-03-28 13:55:22: WARNING: disabling profiling because of error begin profiling section twice without ending the first one (Job Importer).
2014-03-28 13:55:22: Error occurred while updating task cache: Object reference not set to an instance of an object. (System.NullReferenceException)
This is quite strange. We upgraded our farm which had thousands of jobs to 6.2 from 6.1 without incident.
Which 6.2 beta did you install?
Would you be willing to zip up your database and send it to us? You can just zip up the data folder in the database folder and put it somewhere where we could download it from. Or if necessary, we could set up a place where you could upload it. We could then drop your database here and see if we can reproduce.
I’ve installed the 6.2.0.11 version.
I did notice that just before I installed it over the 6.1 that the 6.1 applied it’s auto update (overlooked that, but think it was done installing)
Will PM you in a bit with a link to the database file.
The half shown job was added a few minutes after the update, the other jobs before updating (think there are ~50 orso that are now unreachable via the monitor)
As said before there was 1 realflow job still running during the 6.2 installation.
During archiving of the DataBase I did get these errors as Deadline is still running… is that a problem?
! C:\DeadlineDatabase6.rar: Cannot open C:\DeadlineDatabase6\mongo\data\deadlinedb.0
The process cannot access the file because it is being used by another process.
! C:\DeadlineDatabase6.rar: Cannot open C:\DeadlineDatabase6\mongo\data\deadlinedb.1
The process cannot access the file because it is being used by another process.
! C:\DeadlineDatabase6.rar: Cannot open C:\DeadlineDatabase6\mongo\data\deadlinedb.ns
The process cannot access the file because it is being used by another process.
! C:\DeadlineDatabase6.rar: Cannot open C:\DeadlineDatabase6\mongo\data\journal\j._1
The process cannot access the file because it is being used by another process.
! C:\DeadlineDatabase6.rar: Cannot open C:\DeadlineDatabase6\mongo\data\local.0
The process cannot access the file because it is being used by another process.
! C:\DeadlineDatabase6.rar: Cannot open C:\DeadlineDatabase6\mongo\data\local.ns
The process cannot access the file because it is being used by another process.
! C:\DeadlineDatabase6.rar: Cannot open C:\DeadlineDatabase6\mongo\data\logs\log.txt
The process cannot access the file because it is being used by another process.
! C:\DeadlineDatabase6.rar: Cannot open C:\DeadlineDatabase6\mongo\data\mongod.lock
The process cannot access the file because it is being used by another process.
Yes, you should definitely always update the slaves. Keeping the repository and all the clients on the same version ensures there are no unexpected issues.
Thanks, indeed installing the latest version work and everything is back to normal again
I should have looked on the forum to get the latest straight away.
