Thoughts on live chat 
Filed under

error

 

Ejabberd2 Upgrade

We upgraded our version of ejabberd to ejabberd 2.0.3 today from 1.6. The new upgrade should insure that bugs kicking around in ejabberd do not cause problems with Hab.la. There were also a few backend fixes wrapped in there, but we’ll talk about them in a few days after the next feature release.

UPDATE:

Some of you might have noticed some issues with Gtalk and Hab.la shortly after I posted this notice, I managed to fix these issues on monday, but apparently there are some problems with ejabberd 2.0.3 and openssl 0.9.8j. (See Bug report 877). Interestingly this is a bug that may be fixed in subversion, but is definitely still an issue for the source download from the ejabberd website.

Filed under  //   ejabberd2   erlang   error   gtalk   sasl   ttls   upgrade  
Posted by Olark 

Comments [0]

Tracked down one of the diskspace problems

The problem with Hab.la is there are too many distinct services running. In this case the server that handles routing connections to MSN and AOL was essentially multiplexing the log files, because there was still some debugging code kicking around in the codebase that was having the affect of opening multiple log files, and sending extra data to these log files. – this also made tracing the log files very strange because you would have the same entry multiple times.

And I was wondering why things were being sent to stdout in duplicate, ha.

In addition to just writing much more data than it needed to write, it was also logging to directory without a log rotation facility on a relatively small partition (i.e. /tmp)

Needless to say, when / fills up, a lot of things go crazy.

I would just add a log rotate rule to /tmp, but I am not sure how well logrotate places with python’s logging facility.

(Looks like we should start using WatchedFileHandler if we are going to play nice with log rotate - http://docs.python.org/library/logging.html, that seems like a high priority todo :-) )

Filed under  //   error   logging   space  
Posted by Olark 

Comments [0]

A fix to a weird error

Ok, this is hardly blog worthy, in that it is going to not be very interesting to most of our visitors. However, I tracked down a really weird Firefox bug, I haven’t figured out exactly why it was occurring, but here’s the error message I was receiving:

uncaught exception: [Exception... "Illegal operation on WrappedNative prototype object"
nsresult: "0x8057000c (NS_ERROR_XPC_BAD_OP_ON_WN_PROTO)"
 location: "native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0"  data: no]

That’s a pretty scary message. This problem was caused by a line that looked like:

setTimeout(this.wcsend.focus, 10)

My only theory is that somehow the function reference doesn’t like the fact that “this” is part of the function reference, even though it should just be some real place in memory, assuming javascript references work anything like c++. (Of course more likely, there’s a weird scope issue with the this. , I digress)

So the fix.

setTimeout(function() { habla_window.wcsend.focus(); }, 10)

Replace the function reference with a virtual function, and a full reference to the focus call. Hopefully, this will be somewhat useful to people who run into this problem in the future.

Of course, on the plus side, Firefox users should no longer see those ugly error messages (which might only show up in firebug) while using Hab.la :-)

Filed under  //   error   firebug   firefox   frontend   hab.la   javascript   mozilla   weird   wrappednative  
Posted by Olark 

Comments [0]