Deadline Pulse x64 5.2.0.47700 not launching on Centos.

Deadline
1

I’ve built and compiled mono 2.6.7 and when I run the

mono deadlinepulse -nogui

from within the repo’s /bin/linux folder it’s crashing out saying the below:

System.Net.Sockets.SocketOptionName 0x1b is not supported at IPv6 level

Now IPv6 is ‘set to be ignored’ as method on this server so I’m looking for help tracing this one back further.

We’ve not got a spare windows box equipped well enough to be the studio’s pulse system and I have to make this one work.

Anyone been in a similar situation before with pulse on Centos?

The share is mounted locally and I’ve put that onto the path (NetworkRoot=/media/deadline) of the deadline.ini file it’s looking for is that wrong?

2

That is actually just some debugging info from Mono that we can’t suppress. It’s harmless. Is that the only thing that gets printed out to the console?

Also, you shouldn’t have to prefix your command with “mono”. The “deadlinpulse” file in the bin folder is actually a shell script that wraps the mono call of “mono deadlinepulse.exe”.

3

Thanks Ryan, that actually helped me a lot. Would seem that the mono build process was missing some final commands.

I spotted the post compile info I was missing from here:
github.com/ThinkboxSoftware/Dea … ld_mono.sh

Namely the part on the script of #post flight goodies which I missed have missed off when I had built it. Looks to be working ok now, so thanks for the help Ryan!

[size=85]update: I’m getting this : ERROR: 42P01: relation “Repository” does not exist
as it loops through things… anything worth worrying about?
[/size]

Cheers

4

Glad you got it working.

Do you have Deadline set up to log stats to a postgres database? That error appears to come from the postgres library we ship with Deadline. If this is the case, it sounds like the tables weren’t created properly:
thinkboxsoftware.com/deadlin … a_Database

5

That sounds like it very well could be the problem/solution in one. I’ll come back to this tomorrow and push on into the Postgre side of things :smiley:

Cheers!