Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Cloudron Forum

Apps | Demo | Docs | Install

update 6.3.3 left apps not responding & firewall inactive after reboot

Scheduled Pinned Locked Moved Solved Support
firewall
4 Posts 3 Posters 289 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • chymian 0C Offline
    chymian 0C Offline
    chymian 0
    wrote on last edited by girish
    #1

    the latest update to 6.3.3 left nextcloud & wallabag not responding/restarting.
    the pbl. was access to the pgsql container, which was fixed by a manual restart of the container...

    the necessary system reboot left the firewall down: (due to a race condition?)

    Jun 30 08:27:20 my.eb8.org cloudron-firewall.sh[5559]: ==> Setting up firewall
    Jun 30 08:27:20 my.eb8.org cloudron-firewall.sh[5613]: iptables: Bad rule (does a matching rule exist in that chain?).
    Jun 30 08:27:22 my.eb8.org cloudron-firewall.sh[5828]: Another app is currently holding the xtables lock. Perhaps you want to use the -w option?
    Jun 30 08:27:22 my.eb8.org cloudron-firewall.sh[5833]: iptables: No chain/target/match by that name.
    Jun 30 08:27:22 my.eb8.org systemd[1]: cloudron-firewall.service: Main process exited, code=exited, status=1/FAILURE
    Jun 30 08:27:22 my.eb8.org systemd[1]: cloudron-firewall.service: Failed with result 'exit-code'.
    Jun 30 08:27:22 my.eb8.org systemd[1]: Failed to start Cloudron Firewall.
    

    manual restating the FW brought it back online.

    nebulonN 1 Reply Last reply
    1
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    replied to chymian 0 on last edited by
    #2

    @chymian-0 do you have any additional firewall/iptables rules put manually?

    chymian 0C 1 Reply Last reply
    0
  • girishG Do not disturb
    girishG Do not disturb
    girish Staff
    wrote on last edited by
    #3

    I have seen this happens when we try to add a lot of iptable rules quickly. Do you have a lot of IP address in your firewall (i.e added via Cloudron) ? I remember we hit this before and I converted the code to use ipset based on the suggestion in https://serverfault.com/questions/935272/another-app-is-currently-holding-the-xtables-lock but looks like we hit this anyway... Is this easily reproducible?

    1 Reply Last reply
    0
  • chymian 0C Offline
    chymian 0C Offline
    chymian 0
    replied to nebulon on last edited by
    #4

    hey @nebulon,
    no, only 2-3 ports tcp/udp (wireguard/snmp/ssh)
    and it happened inbetween again, without any reboots/upgrades/etc. I got notfied by network mgmgt system, that my cloudron server is down - luckily it was just the firewall…

    1 Reply Last reply
    0

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Login

  • Don't have an account? Register

  • Login or register to search.