Pulse stalled / crashed

celluloidvfx · November 12, 2014, 3:46pm

We just had a “Stalled Pulse” event this morning. Thought you guys might be interested.
We got the mail notification around 2014-11-12, 10:09. When i checked the machine running it (around 16:30) the Pulse window was still there and i exited Pulse and the Launcher. The latter then crashed and i had to kill the process and restart both.
I did this so late because i thought it’s a false positive as the app was still running. We only noticed something must be wrong when we tried to render a job.
Logs attached.
I did not yet re-install the Client package as you suggested over here
http://forums.thinkboxsoftware.com/viewtopic.php?f=205&t=12495&start=20#p56199
I’ll do this later today. But i guess this issue is not related anyway.

Cheers,
Holger
Deadline_logs_2014-11-12.zip (674 KB)

rrussell · November 12, 2014, 8:31pm

Strange… there aren’t any error messages in either of these logs to indicate what the problem was.

After you get a chance to reinstall the client on this machine, let us know if this happens again.

Thanks!
Ryan

celluloidvfx · November 13, 2014, 12:51pm

Just did so and will definitely let you know in case it happens again.

Cheers,
Holger

M25k · December 4, 2014, 3:10pm

I experecne the same Problem. Everytime a Monitor is started all Pulse Instance crash/ stop to respond.

rrussell · December 4, 2014, 3:13pm

Which version of Deadline 7 are you on? Can you upgrade all your machines (slaves, pulse, workstations) to RC4, which is the latest version, and see if you still have this problem?

Thanks!
Ryan

M25k · December 4, 2014, 4:03pm

I was on .49 but just updated to .50 same problem. As soon as a monitor starts puls crashes.

rrussell · December 4, 2014, 4:05pm

Thanks for confirming. Can you upload the Pulse log from the session that it crashed? To find the log folder, you can use the Launcher’s menu and select Explore Log Folder. You can find the same option in Pulse’s help menu as well. Maybe just sort by date/time and grab the last few pulse logs and upload them as attachments.

Thanks!
Ryan

M25k · December 4, 2014, 4:20pm

Hey just found and fixxed the Problem, there was an Error in the Autoconfiguration.

2014-12-04 17:15:08: BEGIN - ND-SV-STORE02\admin.joachim
2014-12-04 17:15:08: Deadline Pulse 7.0 [v7.0.0.50 R (a79b3fb44)]
2014-12-04 17:15:12: Auto Configuration: Picking configuration based on: nd-sv-store02 / 192.168.50.108
2014-12-04 17:15:12: Auto Configuration: Unexpected exception: parsing “nd-sv-rn**” - Nested quantifier *. (System.ArgumentException)
2014-12-04 17:15:12: at System.Text.RegularExpressions.RegexParser.ScanRegex()
2014-12-04 17:15:12: at System.Text.RegularExpressions.RegexParser.Parse(String re, RegexOptions op)
2014-12-04 17:15:12: at System.Text.RegularExpressions.Regex…ctor(String pattern, RegexOptions options, TimeSpan matchTimeout, Boolean useCache)
2014-12-04 17:15:12: at Deadline.Slaves.AutoConfiguration.PickConfiguration(DataController dataController, IPAddress objClientAddress, String hostname, GenericDelegate1`1 logLine)
2014-12-04 17:15:12: at Deadline.Slaves.AutoConfiguration.AutoConfigLocalSettings(DataController dataController, Boolean licenseServerOnly, Boolean verbose)
2014-12-04 17:15:12: Server Thread - Auto Configuration: Listening for auto configuration requests on [::]:17071:17071
2014-12-04 17:15:12: Web Service - Web Service is disabled. It can be enabled in the Pulse Settings in the Repository Options.
2014-12-04 17:15:12: Web Service - If the Web service is enabled while Pulse is running, Pulse must be restarted for the changes to take effect.

rrussell · December 4, 2014, 4:24pm

Ah, okay, glad you were able to fix it. We should definitely make sure that auto-config issues don’t cause crashes though! We’ll look into that.

Cheers,
Ryan