530119 - production-master02 is in a weird (not critical) state (restart might be required)

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Armen [:armenzg]]

Attachment: [twistd.log] exception that appears upon reconfig

I was trying to reschedule a Maemo nightly build but after each reconfig it would not pick the new set time (remaining at 1AM).
Builds are still happening.

bhearsum is looking into this.

Comment 1

[[e-mail] (:bhearsum)]

It appears that this is being caused by a hung slave, but I'm not certain.

Comment 2

[Nick Thomas [:nthomas] (UTC+12)]

We had a quiet time for pm02 so I went ahead and restarted the buildbot master there (at 14:45 PST). It came back up without any exceptions.

Before I did that there were 12 builds which were hung doing a sendchange - most of them on Nov 12 and 19th, so after the changes from bug 523904. I didn't note which master they were having problems talking to, and the restart lost the copy of that info.

FIXED ?

Comment 3

[[e-mail] (:bhearsum)]

Yup, sounds good to me.

Thanks Nick.

Comment 4

[Armen [:armenzg]]

I was able to reschedule a Maemo nightly and Coop's desktop L10n builds were triggered.

Thanks Nick.