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

    Ipsec_starter[xxx]: notifying watcher failed: Bad file descriptor

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    5 Posts 2 Posters 1.9k 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.
    • C
      charliem
      last edited by

      I noticed (4) of these errors are logged in system.log every time IPsec is started or 'forcefully reloaded'.  This is new since pfsense updated to strongswan 5.2 from 5.1.3

      The cause and fix are discussed in this ML message: https://lists.strongswan.org/pipermail/users/2014-July/006293.html and additional details are in the surrounding ML thread.

      One fix is this:

      diff --git a/src/starter/starter.c b/src/starter/starter.c
      index ef57808..71f33ae 100644
      --- a/src/starter/starter.c
      +++ b/src/starter/starter.c
      @@ -612,7 +612,6 @@ int main (int argc, char **argv)
                                      int fnull;
      
                                      close_log();
      -                               closefrom(3);
      
                                      fnull = open("/dev/null", O_RDWR);
                                      if (fnull >= 0)
      
      
      1 Reply Last reply Reply Quote 0
      • E
        eri--
        last edited by

        I do not see any issues from that log setting.
        Due you have any problems in general or just trying to clean your log?

        1 Reply Last reply Reply Quote 0
        • C
          charliem
          last edited by

          No problems related to that, just noise in the log.  I can understand you not wanting to patch strongswan, no problem, but it could generate some questions when 2.2 goes GA.

          1 Reply Last reply Reply Quote 0
          • C
            charliem
            last edited by

            Bug now opened here:

            https://redmine.pfsense.org/issues/3947

            1 Reply Last reply Reply Quote 0
            • C
              charliem
              last edited by

              @charliem:

              Bug now opened here:

              https://redmine.pfsense.org/issues/3947

              This is fixed by today's snapshot with strongswan updated to 5.2.1.  Thanks!

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