Recent downtimes

Posted by – November 11, 2013

flattr this!

Just in case you haven’t noticed: We’re experiencing quite a nasty bug (maybe, not proven yet) inside ejabberd which leads to a) ejabberd eating all of the available memory and b) afterwards having one thread run at 100% CPU. At this time, ejabberd stops forwarding packets and accepting new connections.

Just to keep you informed.

P.S.: We do have a Twitter account that might (!) have more up-to-date information than you can find in this blog: @jabberccc.de

28 Comments on Recent downtimes

  1. pa-hul says:

    Do you prefer donations via bank transfer or via Flattr?

    I’d like to honour your work and efforts and help to see the service up and running :)

  2. vt100 says:

    If you want to help keeping the server infrastructure uptodate (and, if you need tax deductions), bank transfer is your answer :-)

  3. pa-hul says:

    Then bank transfer it is!

    But no tax deductions for me, for I am Austrian (hello neighbour)

    ;)

  4. Anon says:

    Dear CCC jabber support,

    could you keep us updated on this?
    I appreciate all your work but since days I have trouble to connect.

    Cheers,
    Anon

  5. vt100 says:

    Dear Anon,

    I already mentioned the twitter feed.

    Thanks.

  6. Pseudomonas says:

    Since these downtimes started, I noticed an additional phenomenon – if I write a message to an offline buddy from my contact list (using Pidgin 2.10.7 on Ubuntu 12.04), I get the following error message (but only if his account is also a jabber.ccc.de one):

    XMPP Message Error
    Message delivery to X@jabber.ccc.de failed: (Code 503)

  7. panzi says:

    Yeah, so since a few days (week?) jabber.ccc.de is no usable for me. Failures to connect and if connections work failures to deliver messages. Do you have any news on that bug? Otherwise I have to switch the jabber provider.

  8. SammysHP says:

    @Pseudomonas

    I have the same problem since some days/weeks ago and already wrote a mail to vt100 yesterday morning (no answer yet).

    PS: My real email address seems to be blocked.

  9. vt100 says:

    The (from time to time) non-functioning offline messages seem to be fixed now.

  10. SammysHP says:

    Nope, still not working.

  11. schurl says:

    hello and thank you for our service :)

    i just tried to send offline message to my contacts (also jabber@ccc.de) and get same error as Pseudomonas:

    XMPP Message Error
    Message delivery to X@jabber.ccc.de failed: (Code 503)

  12. Pseudomonas says:

    Bei mir hat sich auch immer noch nichts geändert.

  13. SammysHP_2 says:

    Strange, my comment from 08.12. wasn’t published, but others are.

  14. SammysHP_2 says:

    Leider habe ich immer noch Probleme mit dem Senden von Nachrichten an Kontakte, die offline sind. Bis vor einige Wochen hat es doch problemlos funktioniert, warum jetzt nicht mehr?

  15. Pseudomonas says:

    Is there any better way to communicate with the administrators than this? (Not Twitter.)

  16. SammysHP_2 says:

    @Pseudomonas

    I tried it via email (see “Impressum”) two times (02. dec. and 08. dec.), no response yet.

  17. SammysHP_2 says:

    Meanwhile it works again.

  18. schurl says:

    also here, it works, thank you!

  19. Pseudomonas says:

    Oh no, the offline messages stopped working again… :-(

  20. SammysHP_2 says:

    Verified.

  21. fuckCCC says:

    Take your fucking jabber service down so that people dont use it anymore. It’s annoying that i cant send them offline messages because you are too stupid to configure your ejabberd right…

  22. SammysHP_2 says:

    There’s something true in it …

  23. SammysHP_2 says:

    Einmal neu gestartet wie es scheint und es geht auch wieder.

  24. Pseudomonas says:

    And it stopped working again. It is the third time I have to change my Jabber account because the server is not run properly. Not an advertisment for FLOSS…

  25. SammysHP_2 says:

    Verified. Stopped working last night. Also I got 15+ messages that a message could not be delivered after my login (why? I was offline).

    This is a free project, maintained by someone in his free time. I know how it feels. If it works, you won’t get any thanks. If it not works, all people will start writing bad things about you or the project. That’s the bad side about FLOSS. But IMHO many people are using jabber.ccc.de and some of them might have an idea how to fix it. A little bit more communication might help.

  26. ItSucks says:

    I use jabber.ccc.de with the recent pidgin Version Pidgin 2.10.9 (libpurple 2.10.9) under linux 64bit. I cannot send messages to offline users of jabber.ccc.de. Other jabber server work. Everytime I get Error code 503. This happens since a short while 2-3 weeks or so. Tryed Web jabber over ssl port 443 193.110.90.42 and normal jabber over port 5222. Plz fix this its really annoying.

    Pidgin Error Konsole:
    (18:28:07) jabber: Sending (ssl) (xxxx@jabber.ccc.de/Home):
    (18:28:07) jabber: Recv (ssl)(274):
    (18:28:08) offlinemsg: Account “xxxx@jabber.ccc.de/Home” supports offline messages.
    (18:28:08) jabber: Unable to find caps: buddy might be offline
    (18:28:08) jabber: Sending (ssl) (xxxx@jabber.ccc.de/Home): test
    (18:28:08) jabber: Sending (ssl) (xxxx@jabber.ccc.de/Home):
    (18:28:08) util: Writing file prefs.xml to directory /home/xxxx/.purple
    (18:28:08) util: Writing file /home/xxxx/.purple/prefs.xml
    (18:28:08) jabber: Recv (ssl)(320): test
    (18:28:08) jabber: Recv (ssl)(271):
    (18:28:10) util: Writing file blist.xml to directory /home/xxxx/.purple
    (18:28:10) util: Writing file /home/xxxx/.purple/blist.xml
    (18:28:14) jabber: Sending (ssl) (xxxx@jabber.ccc.de/Home):
    (18:28:14) accels: accel changed, scheduling save.
    (18:28:14) accels: accel changed, scheduling save.
    (18:28:14) accels: accel changed, scheduling save.
    (18:28:14) accels: accel changed, scheduling save.
    (18:28:14) accels: accel changed, scheduling save.
    (18:28:14) jabber: Recv (ssl)(271):
    (18:28:19) accels: saving accels to /home/xxxx/.purple/accels
    (18:28:37) jabber: Recv (ssl)(263):
    (18:28:37) jabber: Discovered bytestream proxy server: jid=’proxy.eu.jabber.org’ host=” port=’0′ zeroconf=”

  27. ItSucks says:

    The log with Port 5222

    (18:49:16) util: Writing file prefs.xml to directory /home/xxxxx/.purple
    (18:49:16) util: Writing file /home/xxxxx/.purple/prefs.xml
    (18:49:16) GLib-GObject: value “-191070047″ of type ‘gint’ is invalid or out of range for property ‘weight’ of type ‘gint’
    (18:49:16) GLib-GObject: value “-191070047″ of type ‘gint’ is invalid or out of range for property ‘weight’ of type ‘gint’
    (18:49:17) gtkconv: setting active conversation on toolbar 0x7f12f55db6b0
    (18:49:17) gtkconv: setting active conversation on toolbar 0x7f12f55db6b0
    (18:49:17) prefs: /pidgin/conversations/toolbar/wide changed, scheduling save.
    (18:49:17) gtkconv: setting active conversation on toolbar 0x7f12f55db6b0
    (18:49:18) jabber: Sending (ssl) (xxxxx@jabber.ccc.de/Home):
    (18:49:18) jabber: Recv (ssl)(274):
    (18:49:21) offlinemsg: Account “xxxxx@jabber.ccc.de/Home” supports offline messages.
    (18:49:21) jabber: Unable to find caps: buddy might be offline
    (18:49:21) jabber: Sending (ssl) (xxxxx@jabber.ccc.de/Home): test
    (18:49:21) jabber: Sending (ssl) (xxxxx@jabber.ccc.de/Home):
    (18:49:21) jabber: Recv (ssl)(320): test
    (18:49:21) GLib-GObject: value “-191070047″ of type ‘gint’ is invalid or out of range for property ‘weight’ of type ‘gint’
    (18:49:21) jabber: Recv (ssl)(271):

  28. peace says:

    I have the same Problem. I cannot send offline-messages to @jabber.ccc.de-accounts.

    Pidgin says (in german):
    XMPP-Nachrichtenfehler: Nachrichtenzustellung an ***@jabber.ccc.de fehlgeschlagen: (Code 503)

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>