Process for id [] [B] died unexpectedly
I did a new install of 7.1.3 and jobs are dying unexpectedly and showing as cancelled in the job logs. I have found a job where I can reproduce the error when I restart the job.
The log shows: Thu Sep 22 12:36:18 2011: CRRBF0467I: 4391190: Build: Build restarted. Can't call method "Error" on an undefined value at /PerlApp/BuildForge/Project/Step.pm line 397. Thu Sep 22 12:36:44 2011: CRRBF1253I: 5767228: BuildForge: Process for id died unexpectedly. When I use the new firehose debug settings I see that the step completed, then you get that perl error and the job dies. Here's the log with the firehose setting turned on: ed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Build: Unregistering trigger 44114569trigger17 Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Step: Calling Inline... TB Wed Sep 21 16:55:24 2011: CRRBF1597I: 5046284: Step: Job Step completed command part 3 of 3 .
Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Agent: SEND: quit Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Agent: ---- Disconnect Called from ,, Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Build: Unregistering trigger 431875856trigger1 Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Agent: WITHIN IN DESTROY: vidar Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Agent: WITHIN IN DESTROY: vidar Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Build: Unregistering trigger 978866556trigger5 Wed Sep 21 16:55:25 2011: CRRBF1253I: 5570746: BuildForge: Process for id died unexpectedly. Any ideas why the process is dying? |
2 answers
Which OS do you use? I have already found this issue When BuildForge is in running state by windows service, then I start BuildForge in foreground.
just FYI I did a new install of 7.1.3 and jobs are dying unexpectedly and showing as cancelled in the job logs. I have found a job where I can reproduce the error when I restart the job., : vidar Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Agent: SEND: quit Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Agent: ---- Disconnect Called from ,, Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Build: Unregistering trigger 431875856trigger1 Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Agent: WITHIN IN DESTROY: vidar Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Agent: WITHIN IN DESTROY: vidar Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Build: Unregistering trigger 978866556trigger5 Wed Sep 21 16:55:25 2011: CRRBF1253I: 5570746: BuildForge: Process for id died unexpectedly. Any ideas why the process is dying? |
The OS is AIX 7. It turns out this was a known defect (defect 23479). The summary of that defect was ".bset server followed by a conditional step results in a project dying unexpectedly". I got a newer build of 713 with the fix in it and it works now.
Which OS do you use? I have already found this issue When BuildForge is in running state by windows service, then I start BuildForge in foreground. I did a new install of 7.1.3 and jobs are dying unexpectedly and showing as cancelled in the job logs. I have found a job where I can reproduce the error when I restart the job., : vidar Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Agent: SEND: quit Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Agent: ---- Disconnect Called from ,, Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Build: Unregistering trigger 431875856trigger1 Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Agent: WITHIN IN DESTROY: vidar Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Agent: WITHIN IN DESTROY: vidar Wed Sep 21 16:55:24 2011: CRRBFEEEEE: 5046284: Build: Unregistering trigger 978866556trigger5 Wed Sep 21 16:55:25 2011: CRRBF1253I: 5570746: BuildForge: Process for id died unexpectedly. Any ideas why the process is dying? |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.