[00:49:11] nacht ts [00:49:24] @replag [00:49:24] DaBPunkt: s1-rr-a-wd: 15s [+0.00 s/s]; s1-user: 5h 1m 53s [-0.42 s/s]; s1-user-wd: 15s [+0.00 s/s]; s2-user: 10s [-]; s2-user-wd: 15s [+0.00 s/s]; s3-user: 11s [-0.01 s/s]; s4-user-wd: 15s [+0.00 s/s]; s5-user-wd: 15s [+0.00 s/s] [00:49:25] DaBPunkt: s6-user-wd: 2d 2h 6m 29s [-0.38 s/s]; s7-user-wd: 11s [-0.00 s/s] [00:56:18] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [01:56:18] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [02:56:18] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [03:56:17] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [04:56:18] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [05:56:18] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [06:56:18] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [07:56:17] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [08:56:18] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [09:56:18] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [10:56:18] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [11:48:33] @replag [11:48:34] Merlissimo: s1-rr-a-wd: 20s [+0.00 s/s]; s1-user: 9h 52m 50s [+0.44 s/s]; s1-user-wd: 16s [+0.00 s/s]; s2-user: 1m 19s [+0.00 s/s]; s2-user-c: 25s [-]; s2-user-wd: 25s [+0.00 s/s]; s3-user: 2m 20s [+0.00 s/s]; s4-user-wd: 17s [+0.00 s/s] [11:48:35] Merlissimo: s5-user-c: 26s [-]; s5-user-wd: 26s [+0.00 s/s]; s6-user-wd: 1d 9h 37m 19s [-1.50 s/s]; s7-user-wd: 20s [+0.00 s/s] [11:56:17] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [12:56:17] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [13:56:17] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [14:36:47] Why doesn't LOAD XML LOCAL INFILE work? LOAD DATA works [14:38:57] hello all [14:39:00] @replag [14:39:02] DaBPunkt: s1-rr-a-wd: 40s [+0.00 s/s]; s1-user: 6h 33m 22s [-1.17 s/s]; s1-user-wd: 41s [+0.00 s/s]; s2-user-c: 11m 6s [+0.06 s/s]; s2-user-wd: 41s [+0.00 s/s]; s3-user: 15s [-0.01 s/s]; s4-user-wd: 41s [+0.00 s/s]; s5-user-c: 11m 6s [+0.06 s/s] [14:39:03] DaBPunkt: s5-user-wd: 41s [+0.00 s/s]; s6-user-wd: 1d 3h 49m 50s [-2.04 s/s]; s7-user-wd: 41s [+0.00 s/s] [14:53:36] Oh, LOAD XML is something new in 5.5 [14:56:17] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [15:57:13] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [16:37:44] How do I prevent my 10 hour queries from being killed? I'm about 72/144 done. [16:57:12] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [17:57:12] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [18:57:13] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [19:09:52] DaBPunkt: https://wiki.toolserver.org/view/Database_access#Slow_queries_and_the_query_killer The killing has been consistently 15m for me [19:10:06] would you mind updating? [19:57:14] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [20:38:04] Marlen Caemmerer * [Toolserver-announce] Datacenter Maintenance tomorrow [20:57:13] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [21:57:14] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [22:57:14] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146) [23:57:14] MySQL on z-dat-s4-a is CRITICAL: Cant connect to MySQL server on z-dat-s4-a (146)