Migrating from 6.0 to 6.1

Deadline
1

Hello,

I have to migrate our Repository from 6.0 to 6.1.

Are there any procedures to do this smoothly?
The install setup will (re)install a mongoDB, is there a risk to loose all our current work ?
Or is there a way to recycle 6.0 mongoDB?

Is there a risk to loose all our Repository configuration? (pool, groups, super user password, …)

Shall we have to reinstall all our slaves? end users?

Thanks

2

Hello Nico,

If you run the 6.1 installer it will make the necessary updates, but none of your current settings or data should be effected by the upgrade. You can always back up your database just to be safe, though, just by copying the mongo data folder.

3

Hello,

I did the upgrade but our license server does not work anymore.
We read this message in the Monitor:
‘License server system does not support this version of this feature.’

We have valid licenses, where is the problem ?
Here is the available message from LMTools:

Users of deadline: (Total of XX licenses issued; Total of 1 license in use)

“deadline” v6.00, vendor: thinkbox
floating license

Thanks

4

you need to have a 6.1 license - sounds like you only have a v6.0 license. the fastest way to get this will be to contact sales - sales@thinkboxsoftware.com

5

What the boss said! Let us know if you weren’t able to get what you need and we’d be happy to help in support.

6

Hello,

Thanks for your help, you all were right, our previous problem was a simple licence problem. :blush:
I get a new LIC file, and it is referenced in our FLEX server.

Now I get the problem described here :http://forums.thinkboxsoftware.com/viewtopic.php?f=11&t=11282&p=49247&hilit=MainWindowSlaveStartup#p49247
So I have configured a pulse machine (Pulse is well upgraded, its about indicates ‘Deadline Pulse 6.1’), and it is referenced in ‘Configure Repository Options…’
From Monitor in ‘Super User Mode’ I can restart pulse remotely. But launching slave process from the same machine fails.

Unfortunatly I still get the problem. Full slave log trace below:

2014-03-17 14:22:50: BEGIN - [Machine]\[user] 2014-03-17 14:22:50: Deadline Slave 6.1 [v6.1.0.54665 R] 2014-03-17 14:22:51: Auto Configuration: A ruleset has been received 2014-03-17 14:22:51: Auto Configuration: Setting Launch Slave At Startup value to 'True' 2014-03-17 14:22:51: Traceback (most recent call last): 2014-03-17 14:22:51: File "DeadlineSlave\UI\Forms\MainWindowSlaveStartup.py", line 90, in Startup 2014-03-17 14:22:51: NullReferenceException: Object reference not set to an instance of an object. 2014-03-17 14:22:51: at Deadline.Slaves.AutoConfiguration.CheckAutoConfiguration(Boolean licenseOnly)
What should I do ?

Thanks

7

Hello,

Have you tried to upgrade clients automatically, aside from the Pulse machine you already updated manually, and verified if they still have the same issue? That would be the next step I would advise.

8

Hello,

First of all It works well now!!
Thank you very much.

My last report for this thread, is I got strange crashes (one or two shots)

  • Like the previous one, on a slave, I provide the LOG sample, and you might notice it was up to date.
Deadline Slave 6.1 [v6.1.0.54665 R]
  • And another in the pulse

2014-03-18 19:28:40: BEGIN - [Machine]\[user] 2014-03-18 19:28:40: Deadline Pulse 6.1 [v6.1.0.54665 R] 2014-03-18 19:28:42: Traceback (most recent call last): 2014-03-18 19:28:42: File "DeadlinePulse\UI\Forms\MainWindowPulseStartup.py", line 88, in Startup 2014-03-18 19:28:42: File "DeadlinePulse\UI\Forms\MainWindowPulseStartup.py", line 173, in ConnectToRepository 2014-03-18 19:28:42: SocketException: Une seule utilisation de chaque adresse de socket (protocole/adresse r\xe9seau/port) est habituellement autoris\xe9e 2014-03-18 19:28:42: at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) 2014-03-18 19:28:42: at System.Net.Sockets.Socket.Bind(EndPoint localEP) 2014-03-18 19:28:42: at FranticX.Net.SocketUtils.CreateTcpListeningSocket(Int32 port, Boolean localOnly, Boolean forceIPv4) 2014-03-18 19:28:42: at Deadline.Pulses.PulseServerThread.Connect() 2014-03-18 19:28:42: at Deadline.Pulses.Pulse..ctor(DataController dataController) 2014-03-18 19:28:42: at Deadline.Pulses.PulseManager.Connect()

You are now aware.
Thanks

9

So, that error means something is already listening on the port Pulse normally uses to listen for requests (default being 17062 in Deadline 6.x).

It’s unlikely, but could you first check to see if Pulse is somehow already running under a different account? If not, could you try setting the port number to 17063 in the “Pulse” section of “Configure Repository Options” in the Monitor’s “Tools” menu?