[00:56:45] nacht ts [00:57:14] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [01:57:14] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [02:57:13] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [03:57:14] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [04:57:14] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [05:57:14] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [06:57:14] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [07:57:14] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [08:57:13] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [09:57:14] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [10:57:14] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [11:57:13] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [12:31:40] hello [12:31:43] maintenance [12:31:50] in the datacenter [12:31:58] i have to shut down s3, s6 and s7 [12:32:48] dialing in from a data center [12:32:56] that's interesting [12:50:37] ok s4 will be shutdown now [13:00:43] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [13:01:03] MySQL on z-dat-s3-a is CRITICAL: Cant connect to MySQL server on z-dat-s3-a (146) [13:01:34] MySQL on z-dat-s7-a is CRITICAL: Cant connect to MySQL server on z-dat-s7-a (146) [13:03:34] MySQL on z-dat-s7-a is OK: Uptime: 560 Threads: 3 Questions: 9 Slow queries: 0 Opens: 17 Flush tables: 1 Open tables: 8 Queries per second avg: 0.16 [13:16:04] MySQL on z-dat-s3-a is OK: Uptime: 1311 Threads: 10 Questions: 156 Slow queries: 0 Opens: 77 Flush tables: 1 Open tables: 67 Queries per second avg: 0.118 [13:45:34] SSH on hemlock is CRITICAL: Connection refused [13:45:44] Environment IPMI on hemlock is CRITICAL: Connection refused by host [13:52:47] hello all [13:52:56] maintenance is runing I guess? [14:00:43] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [14:32:02] will shutdown wolfsbane [14:36:20] hyacinth s3,s6 and s7 will go away soon to for more memory [14:39:53] PostgreSQL on ptolemy is CRITICAL: CRITICAL - no connection to osm_mapnik (could not connect to server: Connection refused [14:46:04] MySQL on z-dat-s6-a is CRITICAL: Cant connect to MySQL server on z-dat-s6-a (146) [14:46:33] MySQL on z-dat-s7-a is CRITICAL: Cant connect to MySQL server on z-dat-s7-a (146) [14:47:46] wolfsbane is back [14:50:27] hyacinth is next [14:54:54] PostgreSQL on ptolemy is OK: OK - database osm_mapnik (0 sec.) [15:04:29] hyacinth is back [15:04:44] MySQL on z-dat-s6-a is OK: Uptime: 44 Threads: 3 Questions: 1201 Slow queries: 0 Opens: 124 Flush tables: 1 Open tables: 117 Queries per second avg: 27.295 [15:06:18] hardware maintenance done for today [15:06:26] *wave* [15:09:33] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [15:10:44] MySQL on z-dat-s3-a is CRITICAL: Cant connect to MySQL server on z-dat-s3-a (146) [15:22:44] MySQL on z-dat-s3-a is OK: Uptime: 1124 Threads: 31 Questions: 364 Slow queries: 8 Opens: 450 Flush tables: 1 Open tables: 443 Queries per second avg: 0.323 [15:28:53] @replag [16:09:33] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [17:09:33] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [18:09:34] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [19:09:34] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [19:53:48] @replag [19:53:49] DaBPunkt: s1-rr-a-wd: 7h 1m 48s [+1.00 s/s]; s1-user: 1h 2m 1s [-0.90 s/s]; s1-user-wd: 7h 1m 48s [+1.00 s/s]; s2-user-wd: 7h 1m 48s [+1.00 s/s]; s3-user: 57s [-0.14 s/s]; s4-user-wd: 7h 1m 48s [+0.65 s/s]; s5-user-wd: 7h 1m 49s [+1.00 s/s]; s6-user-wd: 7h 18m 56s [+1.00 s/s] [19:53:50] DaBPunkt: s7-user-wd: 7h 18m 56s [+1.00 s/s] [20:09:34] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [20:29:26] Is there a way to get a list of all rows in a table wihtout using COUNT(*)? [20:31:17] if there is a unique id (and there are no deletions) you can use select max(id) [20:38:53] MySQL has some estimate stuff if you need that. I'd offer help optimizing it for you, but EXPLAIN isn't working anymore [20:44:33] Ah well. I got a good estimate. [21:09:34] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [22:09:33] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [23:09:34] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146)