Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    NanoBSD slow conf_mount_ro gives gateway timeout

    Scheduled Pinned Locked Moved 2.3-RC Snapshot Feedback and Issues - ARCHIVED
    2 Posts 2 Posters 853 Views
    Loading More Posts
    • 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.
    • P
      phil.davis
      last edited by

      If I have my nanoBSD system mounted read-only, when I try to save there is about a 60-second delay and then:

      504 Gateway Time-out

      This might be new in nginx - I think lighttpd was happy to wait a long time if conf_mount_ro took a long time.

      If I go to the webGUI again, it takes some time to display. The file system still shows it is RW. After waiting more… finally the file system goes back to RO, and the change is successfully applied. So the action is continuing in the background.

      Maybe the nginx timeout can be increased so that users who are willing to have their nanoBSD system in RO and put up with waiting to save can at least avoid being shown the gateway time-out.

      As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
      If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

      1 Reply Last reply Reply Quote 0
      • rbgargaR
        rbgarga Developer Netgate Administrator
        last edited by

        For slow drivers you should keep it always rw as noted in:
        https://doc.pfsense.org/index.php?title=2.2.4_New_Features_and_Changes

        It's because of forcesync patch removal

        Renato Botelho

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.