XMPP Service Operators - 2024-11-03

  1. TheCoffeMaker

    Hi all! we are going to be offline for a while to do a few maintenance tasks... just ignore connection errors to cyberdelia.com.ar

  2. roughnecks

    👍️

  3. TheCoffeMaker

    done 😤

  4. Kris

    Great!

  5. roughnecks

    xmpp:discuss@conference.conversejs.org?join is giving me "this address is not reachable"

  6. roughnecks

    https://xmpp.woodpeckersnest.space/file_share/5WRVHTLjMJpepDb5XDM65ItI/ee20609e-dde9-4c12-ad52-7d378d88a677.png

  7. Menel

    DNS problems

  8. Menel

    No ip address found on some dns servers

  9. roughnecks

    conference.conversejs.org. 300 IN A 49.12.96.75

  10. roughnecks

    s2s works too, muc component seems borked

  11. Menel

    Hm. Dns is fine now for me too everywhere. I Alcan join the room and see nothing wrong ✎

  12. Menel

    Hm. Dns is fine now for me too everywhere. I can join the room and see nothing wrong ✏

  13. roughnecks

    now it's like this for me

  14. roughnecks

    https://xmpp.woodpeckersnest.space/file_share/37nOJrK3S4wmOVaerl9iH4ka/c66cf0b6-b966-4116-b9bc-95cf3d70c679.png

  15. roughnecks

    will check later

  16. roughnecks

    sorry for OT but this happened tonight to my VPS.. anyone has a clue? ``` Message from syslogd@pandora at Nov 3 05:37:13 ... kernel:[1586232.350737] Dazed and confused, but trying to continue Message from syslogd@pandora at Nov 3 05:37:24 ... kernel:[1586235.049143] Uhhuh. NMI received for unknown reason 30 on CPU 1. Message from syslogd@pandora at Nov 3 05:37:24 ... kernel:[1586235.049145] Dazed and confused, but trying to continue Message from syslogd@pandora at Nov 3 05:37:55 ... kernel:[1586273.642163] watchdog: BUG: soft lockup - CPU#2 stuck for 27s! [dockerd:526408] Message from syslogd@pandora at Nov 3 05:38:00 ... kernel:[1586278.545172] watchdog: BUG: soft lockup - CPU#1 stuck for 24s! [systemd-journal:257] Message from syslogd@pandora at Nov 3 05:38:02 ... kernel:[1586281.187611] watchdog: BUG: soft lockup - CPU#3 stuck for 35s! [lua5.4:1702] ```

  17. bean

    most likely overworked hypervisor did not allocate resources for a few dozen seconds to the guest. Your kernel is complaining about not being able to do its thing

  18. roughnecks

    not an HW issue, so?

  19. bean

    could also be hardware, but it is pretty much impossible to tell without access to the hypervisor host

  20. roughnecks

    yeah, I sent a ticket one hour ago.. probably tomorror or the next day someone will reply. I'll let you know, thanks

  21. roughnecks

    anyway, it started at around 3AM, then cooled off, the started again at 5AM, as you see in the logs ✎

  22. roughnecks

    anyway, it started at around 3AM, then cooled off, then started again at 5AM, as you see in the logs ✏

  23. roughnecks

    now it's been quiet so far

  24. alfred

    roughnecks: they could've also been migrating them across nodes

  25. roughnecks

    alfred, correct! It's a new CPU, better than the older, I'd say: EPIC 2.8Ghz vs a XEON 2.2Ghz 😃️