Wait times have improved after the last batch of slaves were added, but we're still seeing jobs waiting >15mins. Lets add another batch and see if thats enough. From looking at inventory, it seems the next names available are: moz2-win32-slave40.build.m.o ... moz2-win32-slave49.build.m.o
9 years ago
Last I heard (early last week) there was some IP address space issues. Any ETA on these?
These are all online on vlan90.
(In reply to comment #2) > These are all online on vlan90. RDP to moz2-win32-slave40.build.m.o timed out... also, linux VMs not accessible ... maybe firewall still needs work?
After firewall fixed, asked to try again. Still unsuccessful. Phong figured out that these machines are: moz2-win32-slave*.m.o (note missing ".build"). He expects to have this fixed sometime today.
Please add nagios checks for these new VMs, and make that part of the standard cloning procedure. The same set as moz2-win32-slave29.build thanks.
added to nagios.
I went around and correct the ~cltbld/.ssh/config files on 40 -> 44 slaves. They had lines like: IdentityFile "/c/Documents\ and\ Settings..." which is wrong, because of the escaping attempt inside of the quotes. Caused at least one nightly to burn.
(In reply to comment #6) > added to nagios. Can't see moz2-win32-slave40 thru 49 in nagios, could you take a second look ? Also need checks for 30 thru 39.
Shyam: Can you take a look at nagios on bm-admin01 for me and see what is wrong?
looks like Shyam took care of this in bug 510601
Added 30-39 as well, as per comment #8
They all look good except 30, which only has a ping check.
Nick, Good catch, this should be fixed too. We had a messed up rDNS entry for 30 and 31 and once I fixed that, the relevant checks got added into Nagios.
You're going to love this - 30 looks good, 32 is just PING now.