Navigation

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

    PfSense 2.0.3 ntp time client giving error during boot

    Firewalling
    10
    20
    20376
    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.
    • A
      abdurrahman last edited by

      hi everybody,
      when i rebooted pfSense 2.0.3,
      starting ntp time client…. waiting 2 mibutes here and after waiting, an error message shows
      "hostname nor servname provided or not known"

      any ideas or solution?

      1 Reply Last reply Reply Quote 0
      • T
        TicoDePano last edited by

        reinstalled in hyper-v here and the same for me

        1 Reply Last reply Reply Quote 0
        • A
          abdurrahman last edited by

          I think, this is a bug of pfsense 2.0.3..
          I hope, the developers of pfsense fix this bug as soon as possible…

          1 Reply Last reply Reply Quote 0
          • T
            TicoDePano last edited by

            reinstalled again in hyper-v and it's working now

            i can't understand

            running wan in bridge mode (PPPoE) and changed rc.local only to put lan interface down and up

            1 Reply Last reply Reply Quote 0
            • jimp
              jimp Rebel Alliance Developer Netgate last edited by

              If you don't have a working WAN (no default route or no DNS) then it will fail at boot. If you have connectivity, it will work.

              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

              Need help fast? Netgate Global Support!

              Do not Chat/PM for help!

              1 Reply Last reply Reply Quote 0
              • A
                abdurrahman last edited by

                thanks for your reply..
                I installed pfSense 2.0.3 (amd64) on a sun server (sunfire x4150) which has 4 gigabit ethernets
                my interfaces are listed below
                em0 : LAN
                em1 : WAN
                em2 : DMZ
                and 6 ethernet vlans on em1 (WAN) interface…
                em1.114, em1.115,................. etc..

                WAN interface has a default gateway..And all of my interfaces are working....
                Even if i have connectivitiy, ntp time client fails at boot....for example in pfsense 2.0.2 this error doesn'e occur...
                ntp time client fails at boot and gives the error "hostname nor servname not provided, or not known"

                @jimp:

                If you don't have a working WAN (no default route or no DNS) then it will fail at boot. If you have connectivity, it will work.

                1 Reply Last reply Reply Quote 0
                • T
                  takada-id last edited by

                  Tried installing pfSense for the first time and encountered the same error message. However after waiting a few minutes.. less than 5 minutes I guess, it just continued the installation.. I didn't attach the wire to the WAN interface throughout the installation.

                  1 Reply Last reply Reply Quote 0
                  • RonpfS
                    RonpfS last edited by

                    It look like this https://github.com/pfsense/pfsense/commit/6e905c8a6fa2c84b99be2dad21d659e4c2f93395 has been fixed, after I gitsync the timeout is gone

                    2.4.5-RELEASE-p1 (amd64)
                    Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                    Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                    1 Reply Last reply Reply Quote 0
                    • A
                      ant2ne last edited by

                      @RonpfS:

                      It look like this https://github.com/pfsense/pfsense/commit/6e905c8a6fa2c84b99be2dad21d659e4c2f93395 has been fixed, after I gitsync the timeout is gone

                      I made those changes but it still hangs for a good while on ntp client.

                      1 Reply Last reply Reply Quote 0
                      • jimp
                        jimp Rebel Alliance Developer Netgate last edited by

                        Set a working DNS server under System > General and it should improve things.

                        The only reason it stops there is a lack of DNS in the system.

                        The people who see it stop there indefinitely are on DHCP/PPPoE (so the DNS servers are not known yet) or have no DNS configured on a static setup.

                        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                        Need help fast? Netgate Global Support!

                        Do not Chat/PM for help!

                        1 Reply Last reply Reply Quote 0
                        • RonpfS
                          RonpfS last edited by

                          I'm using PPPoE
                          The DNS servers is empty
                          Allow DNS server list to be overridden by DHCP/PPP on WAN is enabled
                          Using FQDN in NTP time server

                          It work fine.

                          2.4.5-RELEASE-p1 (amd64)
                          Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                          Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                          1 Reply Last reply Reply Quote 0
                          • F
                            francisuk22 last edited by

                            Tryed to upgrading to 2.0.3 RELEASE but i was getting this error no matter how many times i tryed, I replaced the NIC card (em0 and now using x10) but the WAN side wasnt registering my modem (cable modem) but the LAN side was fine, Try to input a DNS etc but no joys

                            Anyways dropped back to pfSense-LiveCD-2.0.2-RELEASE-amd64-20121207-2239 and it works not a problem!
                            http://www50.zippyshare.com/v/49344854/file.html

                            2.0.2-RELEASE (amd64) - Dell OptiPlex GX520 SFF @ Intel P4 HT 3.0GHz
                            Cisco SR224 24-port Switch (4 PCs, 1 Wireless AP, 2 Consoles)

                            1 Reply Last reply Reply Quote 0
                            • jimp
                              jimp Rebel Alliance Developer Netgate last edited by

                              If you upgrade to 2.0.3 and hit this, you can gitsync to RELENG_2_0 and the error should go away for sure.

                              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                              Need help fast? Netgate Global Support!

                              Do not Chat/PM for help!

                              1 Reply Last reply Reply Quote 0
                              • S
                                srynoname last edited by

                                So, how to fix this, if my pfsense does not Boot anymore because of this? Thanks!

                                1 Reply Last reply Reply Quote 0
                                • K
                                  kejianshi last edited by

                                  Try it with DNS:

                                  8.8.8.8
                                  8.8.4.4

                                  and NOT letting DHCP/PPP on wan override your server list.

                                  And 0.pfsense.pool.ntp.org in your NTP server.

                                  Also, if people are setting up some firewall rules that break NTP or DHCP, nothing will help.

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    srynoname last edited by

                                    @kejianshi:

                                    Try it with DNS:

                                    8.8.8.8
                                    8.8.4.4

                                    and NOT letting DHCP/PPP on wan override your server list.

                                    And 0.pfsense.pool.ntp.org in your NTP server.

                                    Also, if people are setting up some firewall rules that break NTP or DHCP, nothing will help.

                                    Thank you, but unfortunately with pfsense not booting correctly, even the webinterface is not available, so no real pfsense access!
                                    Personally I fixed the problem by restoring an backup, but I am wondering (and think of other people googling this post!) how tu successfully boot pfsense, while ntp hangs on boot? Personally I think a fixed release should have been available since that problem is known :

                                    1 Reply Last reply Reply Quote 0
                                    • K
                                      kejianshi last edited by

                                      My NTP only hangs when I have no internet, however - If I just sit patiently and wait it out a few minutes, it eventually will boot.  Yours wouldn't?  Even if you waited?

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        srynoname last edited by

                                        @kejianshi:

                                        My NTP only hangs when I have no internet, however - If I just sit patiently and wait it out a few minutes, it eventually will boot.  Yours wouldn't?  Even if you waited?

                                        do you also get the error message

                                        "hostname nor servname provided or not known"

                                        I didn't have the impression that NTP will give up after some time, but maybe I didn't wait long enough.

                                        1 Reply Last reply Reply Quote 0
                                        • K
                                          kejianshi last edited by

                                          Yes  - I do get that very same error.  If the web is down and I have to wait a while, but NTP eventually gives up.

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

                                            what i did is i set 0.pfsense.pool.ntp.org in my country
                                            aside from DNS, i set also NTP in dhcp (services/dhcp server)
                                            i put lan ip

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post