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

    Bad fd number problem

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 2 Posters 1.3k 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.
    • ?
      Guest
      last edited by

      Hi
      When i reboot  pfsense 2.1-release, bad fd number error occurs. What's wrong?

      pfSense will reboot. This may take a few minutes, depending on your hardware.
      
      Do you want to proceed [y|n]? y
      
      pfSense is rebooting now.
       Stopping package Sarg...done.
       Stopping package HAVP antivirus...done.
       Stopping package LCDproc...done.
       Stopping package snort...done.
       Stopping package squid3...done.
       Stopping /usr/local/etc/rc.d/havp.sh...done.
       Stopping /usr/local/etc/rc.d/sqp_monitor.sh...done.
      Syntax error: Bad fd number
      
      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Hmm, should be fixed in 2.1. It's not a problem though it used to do that all the time in 2.0.x. See:
        http://forum.pfsense.org/index.php/topic,60410.0.html

        Steve

        1 Reply Last reply Reply Quote 0
        • ?
          Guest
          last edited by

          It is not fixed in 2.1….i got this error in 2.1-release installed on vmware workstation.

          1 Reply Last reply Reply Quote 0
          • ?
            Guest
            last edited by

            Is there any solution?

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Well reading what JimP said in the linked thread it's caused by the shutdown scripts running in the wrong order so you'd have to re-arrange them. There should be some clues in the code changes to 2.0.x that fixed it. Or just ignore it, it's doing no harm. I would imagine it will be fixed in a future update anyway.

              Steve

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