We have been having a lot of trouble lately with relying on jbott to record the team meetings on irc. A few times jbott has not been in the room. A few times it refuses to start/end meetings. Max, is there anything to be done to make jbott more stable?

so I found whats wrong - the jbott been running for 4 years and one of the things it does when ending meetings is regenerating indexes ....that was fast the first couple of years....now its turned "slow" because it happens sequentially ;) I'll see what I can do to fix that dumb logic. /max On 21 Jan 2014, at 14:36, Max Rydahl Andersen wrote: >> We have been having a lot of trouble lately with relying on jbott to >> record the team meetings on irc. A few times jbott has not been in the >> room. A few times it refuses to start/end meetings. >> >> Max, is there anything to be done to make jbott more stable? > > jbott had been running for months without problems (at least none > known to me) - then there was > a network disconnect at neuchatel office which meant it was off for a > bit and then came back on. > > I know that it has gotten slower at ending meetings, i.e. it now > takes some minutes > for it to upload instead of seconds as in past. I can look into > speeding that up if that is the > problem you are seeing. > > Is that what you are seeing ? > > /max

On 21/01/2014, at 21.35, Steve Ebersole <steve(a)hibernate.org&gt; wrote: So for today's meeting, jbott has still not ended the meeting. And that was 4 hours ago. At least it has not responded with the URLs. Is it still going? > On Tue 21 Jan 2014 09:11:08 AM CST, Steve Ebersole wrote: > The issue with slowness of ending the meeting was annoying yes. > Thanks for finding that. > > The other issue is that jbott is sometimes just not there. It drops > off quite a bit. To give you a flavor, here is its drops from just > yesterday: > > 01:44 *** jbott <jbott!supybot@nat/redhat/x-kcdixxnxtyoqqrjn> has quit > IRC (Ping timeout: 272 seconds) > 14:03 *** jbott <jbott!supybot@nat/redhat/x-bftkgoghfxdwibyf> has quit > IRC (Ping timeout: 272 seconds) > 22:19 *** jbott <jbott!supybot@nat/redhat/x-wxdxevjybbitcevv> has quit > IRC (Ping timeout: 252 seconds) > 23:23 *** jbott <jbott!supybot@nat/redhat/x-cafuloaglxdbvmqg> has quit > IRC (Ping timeout: 265 seconds) > > There has been at least one occasion when we had a meeting and jbott > was simply not in the room the entire time. > > >> On Tue 21 Jan 2014 07:45:08 AM CST, Max Rydahl Andersen wrote: >> >> so I found whats wrong - the jbott been running for 4 years and one of >> the things it does when ending meetings is regenerating indexes >> ....that was fast the first couple of years....now its turned "slow" >> because it happens sequentially ;) >> >> I'll see what I can do to fix that dumb logic. >> >> /max >> >> >> On 21 Jan 2014, at 14:36, Max Rydahl Andersen wrote: >> >>>> We have been having a lot of trouble lately with relying on jbott to >>>> record the team meetings on irc. A few times jbott has not been in >>>> the >>>> room. A few times it refuses to start/end meetings. >>>> >>>> Max, is there anything to be done to make jbott more stable? >>> >>> jbott had been running for months without problems (at least none >>> known to me) - then there was >>> a network disconnect at neuchatel office which meant it was off for a >>> bit and then came back on. >>> >>> I know that it has gotten slower at ending meetings, i.e. it now >>> takes some minutes >>> for it to upload instead of seconds as in past. I can look into >>> speeding that up if that is the >>> problem you are seeing. >>> >>> Is that what you are seeing ? >>> >>> /max