[06:25] *** kiska1 has quit IRC (Read error: Operation timed out) [08:52] *** kbtoo_ has joined #warrior [08:53] *** kbtoo has quit IRC (Ping timeout: 255 seconds) [09:06] *** kbtoo has joined #warrior [09:14] *** kbtoo_ has quit IRC (Read error: Operation timed out) [15:16] *** chimyatta has joined #warrior [19:30] *** DrScriptt has joined #warrior [19:30] HI, [19:31] My ATW is failing stating "The tracker needs and operator for manual maintenance." [19:31] Are the operators aware of the current need? [19:31] I'm guessing this is related to the "Exporting our ..." message I was getting recently. [20:15] DrScriptt: That's the URLTeam project. The correct channel is #urlteam . And no, the 507 error is not related to exporting. [20:19] DrScriptt: Resolved now. [20:31] Thank you JAA. [20:33] *** ivan_ has quit IRC (Leaving) [21:14] *** ivan_ has joined #warrior [21:14] *** Smiley has joined #warrior [21:15] *** SmileyG has quit IRC (Read error: Operation timed out) [21:24] *** Smiley has quit IRC (Read error: Operation timed out) [21:29] *** Smiley has joined #warrior [22:06] Heya all. Some time ago I noticed a few errors showing up on my Warrior virtual machine. This is likely explained by the host being under heavy load. Messages were along the lines of 'transport error', 'the connection is unavailable', 'decoding init error' and 'broken pipe'. Has this affected the jobs done at that time? Thanks.