| | <<<Back 1 day (to 2014/02/28) | 2014/03/01 |
| ray_laptop | marcosw: I NEED to find out how to reproduce (and debug) the 4 persistent pxlcolor segfaults. I was never able to reproduce one pair on peeved, but could reproduce the 693079 ones on Windwos and peeved and my recent patch fixed those. | 00:56.45 |
| | marcosw: but I still see them showing up on the nightly runs. How do I get the command lines and or the binaries on the same machine that fails ? | 00:57.35 |
| | progress on the multi-bit halftoning in gxht_thresh.c | 04:10.00 |
| | but still a way to go | 04:11.26 |
| sebras | ghostbot: good morning! are you having a tough time staying online? | 10:07.34 |
| ghostbot | sebras: okay | 10:07.34 |
| kens | sebras we changed the cron so that if nothing is written to the logs for 15 minutes ghostbot gets restarted | 10:07.59 |
| | Because we were having trouble with ghostbot running but not logging | 10:08.13 |
| sebras | kens: ah, and you were testing this just now? | 10:09.10 |
| kens | Nope, but I NOTICED THE BEHAVIOUR | 10:09.22 |
| | sorry hit caps lock | 10:09.27 |
| sebras | kens: I was just surprised to see a log full of quit/join from ghostbot. | 10:10.46 |
| kens | I don't think our logs show that, but obviouslu you will see it in your own, potentially | 10:11.13 |
| | Its a recent change, I htink marcosw did it because of the logging problem | 10:11.35 |
| sebras | kens: yes, irssi shows login/logouts. | 10:11.37 |
| kens | OK well then you will see many of those. | 10:11.50 |
| sebras | kens: probably mostly during night. ok, then I know why. I was just surprised and though that ghostbot might be malfunctioning. | 10:12.22 |
| kens | Yeah it'll happen a lot during idle times, weekends and middle of the night I guess. | 10:12.53 |
| ray_laptop | guess I better say something before ghostbot restarts :-( | 18:04.40 |
| | there has to be a better way to detect problems, but the infobot scripts are perl (not my favorite by far) | 18:05.17 |
| sebras | ray_laptop: I think it is enough for someone to login/-out to prevent ghostbot from restarting. | 18:06.15 |
| ray_laptop | sebras: maybe. but I'm going to have a look and see what I can about a better detection. Like maybe have a cron job that sends a special request to ghostbot that it doesn't put in the html logs (and doesn't show up to others) and if that doesn't show up in thee raw logs triggers the restart | 18:09.10 |
| | having a whole mess of ghostbot has quit / ghostbot has joined messages doesn't seem ideal | 18:09.49 |
| sebras | ray_laptop: agred, I though ghostbot was malfunctioning this morning. | 18:30.56 |
| Robin_Watts | Well, ghostbot could whisper to itself. | 18:39.28 |
| | oh, wait, that wouldn't work. | 18:39.48 |
| | Still no power chez ray? | 19:12.27 |
| ray_laptop | Robin_Watts: sorry, was away. | 19:28.28 |
| | I have power, (peeves is up) but for some reason peeved isn't connecting to the net | 19:28.52 |
| Robin_Watts | ray_laptop: Ah. | 19:41.04 |
| marcosw | ray_laptop: there shouldn't be any more ghostbot leaving/entering messages. | 20:35.17 |
| ray_laptop | marcosw: thanks. I haven't seen any, but my client hasn't been on continuously | 20:36.11 |
| marcosw | I had turned out the threshold to test to make sure the restart code was working; I had meant to set it back after testing but forgot. At least the code is well tested now :-) | 20:37.00 |
| | ^out^down | 20:37.14 |
| | bbiaw, lunch time. | 20:37.36 |
| | Forward 1 day (to 2014/03/02)>>> | |
IRC Logs