Closed Bug 750044 (talos-r3-fed64-030) Opened 13 years ago Closed 12 years ago

talos-r3-fed64-030 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Unassigned)

References

Details

(Whiteboard: [buildduty][buildslaves][capacity] clock issues)

Needs a reboot.
grey screen | rebooted
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 760958
Resolution: FIXED → ---
grey screen | rebooted
Status: REOPENED → RESOLVED
Closed: 13 years ago12 years ago
Resolution: --- → FIXED
Please reboot.
Status: RESOLVED → REOPENED
Depends on: 762545
Resolution: FIXED → ---
grey screen | rebooted
Up and running.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
[56] talos-r3-fed64-030.build.scl1:PING is CRITICAL: PING CRITICAL - Packet loss = 100%
Status: RESOLVED → REOPENED
Depends on: 768520
Resolution: FIXED → ---
Back in production.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 772905
Resolution: FIXED → ---
Machine seems to be unavailable on the network today.
Depends on: 775496
https://tbpl.mozilla.org/php/getParsedLog.php?id=14238884&tree=Mozilla-Aurora Looks like maybe the system clock is set to the wrong date.
Disabled in slavealloc while I take a quick look.
I fixed the date up with ntpdate (it thought it was 2001), but there's may be a puppet issue to follow up on.
rebooted it and it re-puppetized correctly.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 793221
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 798394
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Reboot needed.
Status: RESOLVED → REOPENED
Depends on: 811486
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
[18:12:13] nagios-releng Wed 15:12:36 PST [437] talos-r3-fed64-030.build.scl1.mozilla.com is DOWN :PING CRITICAL - Packet loss = 100%
Depends on: 814216
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Needs a reboot.
Status: RESOLVED → REOPENED
Depends on: 819799
Resolution: FIXED → ---
Back in action.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 822136
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Just like comment 10, the clock is 13 years behind.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
disabled in slavealloc
It seems that we still have clock issues and puppet issues. I recreated the certs and cleaned around but I get this error. [cltbld@talos-r3-fed64-030 ~]$ date Wed Jan 3 18:14:25 PST 2001 [cltbld@talos-r3-fed64-030 ~]$ su - Password: [root@talos-r3-fed64-030 ~]# puppetd --test --server scl-production-puppet.build.scl1.mozilla.com notice: Lock file /var/lib/puppet/state/puppetdlock exists; skipping catalog run [root@talos-r3-fed64-030 ~]# ls -l /var/lib/puppet/state/puppetdlock -rw-r--r-- 1 root root 0 2012-12-17 10:27 /var/lib/puppet/state/puppetdlock [root@talos-r3-fed64-030 ~]# vi /var/lib/puppet/state/puppetdlock [root@talos-r3-fed64-030 ~]# rm /var/lib/puppet/state/puppetdlock rm: remove regular empty file `/var/lib/puppet/state/puppetdlock'? y [root@talos-r3-fed64-030 ~]# puppetd --test --server scl-production-puppet.build.scl1.mozilla.com warning: Certificate validation failed; consider using the certname configuration option err: Could not retrieve catalog: Certificates were not trusted: certificate verify failed warning: Not using cache on failed catalog [root@talos-r3-fed64-030 ~]# puppetd --test --server scl-production-puppet.build.scl1.mozilla.com warning: Certificate validation failed; consider using the certname configuration option err: Could not retrieve catalog: Certificates were not trusted: certificate verify failed warning: Not using cache on failed catalog You have new mail in /var/spool/mail/root [root@talos-r3-fed64-030 ~]# rm -rf /var/lib/puppet/ssl/certs/* [root@talos-r3-fed64-030 ~]# puppetd --test --server scl-production-puppet.build.scl1.mozilla.com warning: peer certificate won't be verified in this SSL session notice: Did not receive certificate notice: Set to run 'one time'; exiting with no certificate [root@talos-r3-fed64-030 ~]# puppetd --test --server scl-production-puppet.build.scl1.mozilla.com warning: peer certificate won't be verified in this SSL session notice: Got signed certificate warning: Certificate validation failed; consider using the certname configuration option err: Could not retrieve catalog: Certificates were not trusted: certificate verify failed warning: Not using cache on failed catalog
Whiteboard: [buildduty][buildslaves][capacity] → [buildduty][buildslaves][capacity] clock issues
Back in production.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
And I should note that I found no clock issues on this machine even after multiple reboots.
needs a reboot
Status: RESOLVED → REOPENED
Depends on: 828016
Resolution: FIXED → ---
Back in production.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 831288
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
01:11 < nagios-releng> Tue 01:11:28 PST [494] talos-r3-fed64-030.build.scl1.mozilla.com is DOWN :PING CRITICAL - Packet loss = 100%
Status: RESOLVED → REOPENED
Depends on: 834922
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 842538
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 843590
Resolution: FIXED → ---
Depends on: 847472
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: 854240
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.