Changes between Version 33 and Version 34 of PS1_IPP_Czarlog_20130429

Timestamp:

May 4, 2013, 1:24:16 PM (13 years ago)

Author:

Serge CHASTEL

Comment:

--

PS1_IPP_Czarlog_20130429

@@ -114 +114 @@
  * 01:10 MEH: registration looks backed up, manually -revertprocessedimfile and clearing
  * 08:45 EAM: nebulous was having some trouble.  I was getting 'too many connection' errors.  'show processlist' had 1022 entries.  I shutdown all pantasks and stopped all apache servers.  the backlog on nebulous went away.  I started the apaches back up and things seem to be ok, but the number of sleeping processes seems high to me (~340).  I decided to not include ippc06 -- I wonder if it was added recently and if this caused our resource usage to exceed some limit...
- * 13:15 Serge. Couldn't access ippdb00 mysql ('too many connection' errors as well). Stopped all apache servers. Could get a connection to the mysql server then. ippdb00 was running as a slave of ippdb02 (Who/what restarted it?!) For safety, deleted all replication parameters from ippdb02 to ippdb00. Stopped the mysql server on ippdb00 to clean it up (and make sure the mysql server forgot everything about its slave condition). Restarted it. Restarted the apache servers. Did the usual "good health" test of nebulous: neb-touch, neb-ls, neb-less, neb-stat, neb-stat validate, neb-rm and everythign seems fine.
+ * 13:15 Serge. Couldn't access ippdb00 mysql ('too many connection' errors as well). Stopped all apache servers. Could get a connection to the mysql server then. ippdb00 was running as a slave of ippdb02 (Who/what restarted it?!) For safety, deleted all replication parameters from ippdb02 to ippdb00. Stopped the mysql server on ippdb00 to clean it up (and make sure the mysql server forgot everything about its slave condition). Restarted it. Restarted the apache servers. Did the usual "good health" test of nebulous: neb-touch, neb-ls, neb-less, neb-stat, neb-stat validate, neb-rm and everything seems fine.