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

    No Web Interface on Thu May 29 08:48:37 CDT 2014

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    54 Posts 12 Posters 14.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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      3rd of June 64bit Nano updates are still far too small.  :(

      Steve

      1 Reply Last reply Reply Quote 0
      • Raul RamosR
        Raul Ramos
        last edited by

        @stephenw10:

        3rd of June 64bit Nano updates are still far too small.  :(

        Steve

        Maybe to speed up full snaps. Better to anyone play a bell on devs to start compile nanobsd normally again.

        pfSense:
        ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
        Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
        NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

        1 Reply Last reply Reply Quote 0
        • I
          ingmthompson
          last edited by

          @stephenw10:

          3rd of June 64bit Nano updates are still far too small.

          Tried applying one anyway? Maybe try it in a VM, it could still be a valid update.

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

            The update files for NanoBSD are an image of the slice that is to be replaced. The usual size for the compressed image (for the 1GB Nano type) is ~68MB, the current update files are ~0.8MB. Now I'm willing to accept the compression algorithm may have been updated but it would be impressive if it can get 100X smaller!  ;)

            Steve

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

              The GUI works on the latest snapshot.  SSHD is down now though which was working in the snapshot from a day ago.  Trying to start it from the GUI doesn't work.  Staring it manually at the console with '/etc/sshd start' works though.  I would much rather have to start sshd manually than the GUI stop working at times.  This is definitely progress! :).

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

                I found the issue and pushed a fix few minutes ago. Please wait for the new snapshot.

                Renato Botelho

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

                  @Renato:

                  I found the issue and pushed a fix few minutes ago. Please wait for the new snapshot.

                  Seems that all is working now, thanks for the fixes!  In my test VM: webgui is up, sshd starts (once it's enabled), and check_reload_status returns to zero cpu usage after a reasonable amount of time.  Though the nano image sizes still seem to be too small.

                  [2.2-ALPHA][admin@pfSense.localdomain]/etc(5): cat version.buildtime
Tue Jun 03 07:27:23 CDT 2014
                  1 Reply Last reply Reply Quote 0
                  • A
                    adam65535
                    last edited by

                    Php-fpm and check_reload_status is working for me except sshd.  Sshd doesn't start for me through the gui or at startup.  I can manually start it with '/etc/sshd start' at the console though.

                    1 Reply Last reply Reply Quote 0
                    • Raul RamosR
                      Raul Ramos
                      last edited by

                      built on Tue Jun 03 07:27:23 CDT 2014

                      • Gui - Yes

                      • sshd - yes

                      • ntpd - no

                      pfSense:
                      ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
                      Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
                      NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

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

                        I noticed the new version of 7am.  I am on the 3am version so I am updating again to fix sshd.

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

                          @mais_um:

                          built on Tue Jun 03 07:27:23 CDT 2014

                          • Gui - Yes

                          • sshd - yes

                          • ntpd - no

                          Hmm, ntpd works for me.  Can you post details and logs … in a new thread?

                          1 Reply Last reply Reply Quote 0
                          • Raul RamosR
                            Raul Ramos
                            last edited by

                            NTP logs after restart

                            Jun 3 15:16:15	ntpd[89750]: ntpd 4.2.7p443@1.2483-o Thu May 29 20:00:00 UTC 2014 (1): Starting
Jun 3 15:16:15	ntpd[89750]: Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid
Jun 3 15:16:15	ntpd[89829]: proto: precision = 0.500 usec (-21)
Jun 3 15:16:15	ntpd[89829]: unable to bind to wildcard address :: - another process may be running - EXITING
Jun 3 15:23:04	ntpd[53617]: ntpd 4.2.7p443@1.2483-o Thu May 29 20:00:00 UTC 2014 (1): Starting
Jun 3 15:23:04	ntpd[53617]: Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid
Jun 3 15:23:04	ntpd[53837]: proto: precision = 0.500 usec (-21)
Jun 3 15:23:04	ntpd[53837]: unable to bind to wildcard address :: - another process may be running - EXITING
Jun 3 15:26:39	ntpdate[76657]: sendto(194.117.9.136): No error: 0
Jun 3 15:26:41	ntpdate[44690]: sendto(194.117.9.136): No error: 0
Jun 3 15:26:41	ntpdate[44690]: sendto(193.136.60.172): No error: 0
Jun 3 15:26:46	ntpdate[44690]: sendto(194.117.9.136): No error: 0
Jun 3 15:26:46	ntpdate[44690]: sendto(193.136.60.172): No error: 0
Jun 3 15:29:07	ntpdate[95503]: sendto(194.117.9.136): No error: 0
Jun 3 15:29:07	ntpdate[95503]: sendto(193.136.60.172): No error: 0
Jun 3 15:29:12	ntpdate[95503]: sendto(194.117.9.136): No error: 0
Jun 3 15:29:12	ntpdate[95503]: sendto(193.136.60.172): No error: 0
Jun 3 15:29:12	ntpdate[95503]: step time server 194.117.9.136 offset -5.067841 sec
Jun 3 15:29:12	ntp: Successfully synced time after 1 attempts.
Jun 3 15:29:12	ntp: Starting NTP Daemon.
Jun 3 15:29:12	ntpd[86413]: ntpd 4.2.7p443@1.2483-o Thu May 29 20:00:00 UTC 2014 (1): Starting
Jun 3 15:29:12	ntpd[86413]: Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid
Jun 3 15:29:12	ntpd[86544]: proto: precision = 0.500 usec (-21)
Jun 3 15:29:12	ntpd[86544]: Listen and drop on 0 v6wildcard [::]:123
Jun 3 15:29:12	ntpd[86544]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Jun 3 15:29:12	ntpd[86544]: Listen normally on 2 de0 [fe80::215:5dff:fe00:6412%1]:123
Jun 3 15:29:12	ntpd[86544]: setsockopt IPV6_MULTICAST_IF 0 for fe80::215:5dff:fe00:6412%1 fails: Can't assign requested address
Jun 3 15:29:12	ntpd[86544]: Listen normally on 3 de1 192.168.1.1:123
Jun 3 15:29:12	ntpd[86544]: Listen normally on 4 de1 [fe80::215:5dff:fe00:6413%2]:123
Jun 3 15:29:12	ntpd[86544]: setsockopt IPV6_MULTICAST_IF 0 for fe80::215:5dff:fe00:6413%2 fails: Can't assign requested address
Jun 3 15:29:12	ntpd[86544]: Listen normally on 5 de2 [fe80::215:5dff:fe00:6414%3]:123
Jun 3 15:29:12	ntpd[86544]: setsockopt IPV6_MULTICAST_IF 0 for fe80::215:5dff:fe00:6414%3 fails: Can't assign requested address
Jun 3 15:29:12	ntpd[86544]: Listen normally on 6 lo0 127.0.0.1:123
Jun 3 15:29:12	ntpd[86544]: Listen normally on 7 lo0 [::1]:123
Jun 3 15:29:12	ntpd[86544]: Listen normally on 8 lo0 [fe80::1%6]:123
Jun 3 15:29:12	ntpd[86544]: setsockopt IPV6_MULTICAST_IF 0 for fe80::1%6 fails: Can't assign requested address
Jun 3 15:29:12	ntpd[86544]: Listen normally on 9 pppoe0 192.168.3.96:123
Jun 3 15:29:12	ntpd[86544]: Listen normally on 10 pppoe0 [fe80::215:5dff:fe00:6412%8]:123
Jun 3 15:29:12	ntpd[86544]: setsockopt IPV6_MULTICAST_IF 0 for fe80::215:5dff:fe00:6412%8 fails: Can't assign requested address
Jun 3 15:29:12	ntpd[86544]: Listening on routing socket on fd #31 for interface updates
Jun 3 15:29:12	ntpd[86544]: refclock_open /dev/gps0: Is a directory
Jun 3 15:29:12	ntpd[86544]: 127.127.20.0 local addr 127.0.0.1 -> <null>
Jun 3 15:31:04	ntpd[86544]: Deleting interface #9 pppoe0, 192.168.3.96#123, interface stats: received=0, sent=0, dropped=0, active_time=112 secs
Jun 3 15:31:04	ntpd[86544]: Deleting interface #10 pppoe0, fe80::215:5dff:fe00:6412%8#123, interface stats: received=0, sent=0, dropped=0, active_time=112 secs
Jun 3 15:31:28	ntpd[86544]: Listen normally on 11 pppoe0 [fe80::215:5dff:fe00:6412%8]:123
Jun 3 15:31:28	ntpd[86544]: setsockopt IPV6_MULTICAST_IF 0 for fe80::215:5dff:fe00:6412%8 fails: Can't assign requested address
Jun 3 15:31:28	ntpd[86544]: Listen normally on 12 pppoe0 192.168.3.80:123
Jun 3 15:31:28	ntpd[86544]: new interface(s) found: waking up resolver
Jun 3 15:31:30	ntpd[86544]: ntpd exiting on signal 15 (Terminated)
Jun 3 15:31:31	ntpdate[47657]: Can't find host 0.pfsense.pool.ntp.org: hostname nor servname provided, or not known (8)
Jun 3 15:31:31	ntpdate[47657]: no servers can be used, exiting
Jun 3 15:31:38	ntpdate[53747]: Can't find host 0.pfsense.pool.ntp.org: hostname nor servname provided, or not known (8)
Jun 3 15:31:38	ntpdate[53747]: no servers can be used, exiting
Jun 3 15:31:59	ntpdate[63387]: adjust time server 194.117.9.136 offset -0.000754 sec
Jun 3 15:31:59	ntp: Successfully synced time after 3 attempts.
Jun 3 15:31:59	ntp: Starting NTP Daemon.
Jun 3 15:31:59	ntpd[64059]: ntpd 4.2.7p443@1.2483-o Thu May 29 20:00:00 UTC 2014 (1): Starting
Jun 3 15:31:59	ntpd[64059]: Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid
Jun 3 15:31:59	ntpd[64376]: proto: precision = 1.300 usec (-19)
Jun 3 15:31:59	ntpd[64376]: Listen and drop on 0 v6wildcard [::]:123
Jun 3 15:31:59	ntpd[64376]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Jun 3 15:31:59	ntpd[64376]: Listen normally on 2 de0 [fe80::215:5dff:fe00:6412%1]:123
Jun 3 15:31:59	ntpd[64376]: setsockopt IPV6_MULTICAST_IF 0 for fe80::215:5dff:fe00:6412%1 fails: Can't assign requested address
Jun 3 15:31:59	ntpd[64376]: Listen normally on 3 de0 10.0.0.152:123
Jun 3 15:31:59	ntpd[64376]: Listen normally on 4 de1 192.168.1.1:123
Jun 3 15:31:59	ntpd[64376]: Listen normally on 5 de1 [fe80::215:5dff:fe00:6413%2]:123
Jun 3 15:31:59	ntpd[64376]: setsockopt IPV6_MULTICAST_IF 0 for fe80::215:5dff:fe00:6413%2 fails: Can't assign requested address
Jun 3 15:31:59	ntpd[64376]: Listen normally on 6 de2 [fe80::215:5dff:fe00:6414%3]:123
Jun 3 15:31:59	ntpd[64376]: setsockopt IPV6_MULTICAST_IF 0 for fe80::215:5dff:fe00:6414%3 fails: Can't assign requested address
Jun 3 15:31:59	ntpd[64376]: Listen normally on 7 lo0 127.0.0.1:123
Jun 3 15:31:59	ntpd[64376]: Listen normally on 8 lo0 [::1]:123
Jun 3 15:31:59	ntpd[64376]: Listen normally on 9 lo0 [fe80::1%6]:123
Jun 3 15:31:59	ntpd[64376]: setsockopt IPV6_MULTICAST_IF 0 for fe80::1%6 fails: Can't assign requested address
Jun 3 15:31:59	ntpd[64376]: Listen normally on 10 pppoe0 [fe80::215:5dff:fe00:6412%8]:123
Jun 3 15:31:59	ntpd[64376]: setsockopt IPV6_MULTICAST_IF 0 for fe80::215:5dff:fe00:6412%8 fails: Can't assign requested address
Jun 3 15:31:59	ntpd[64376]: Listen normally on 11 pppoe0 192.168.3.80:123
Jun 3 15:31:59	ntpd[64376]: Listening on routing socket on fd #32 for interface updates
Jun 3 15:31:59	ntpd[64376]: refclock_open /dev/gps0: Is a directory
Jun 3 15:31:59	ntpd[64376]: 127.127.20.0 local addr 127.0.0.1 -> <null>
Jun 3 15:32:15	ntpd[64376]: Deleting interface #10 pppoe0, fe80::215:5dff:fe00:6412%8#123, interface stats: received=0, sent=0, dropped=0, active_time=16 secs
Jun 3 15:32:15	ntpd[64376]: Deleting interface #11 pppoe0, 192.168.3.80#123, interface stats: received=0, sent=0, dropped=0, active_time=16 secs
Jun 3 15:32:19	ntpd[64376]: Listen normally on 12 pppoe0 192.168.3.81:123
Jun 3 15:32:19	ntpd[64376]: Listen normally on 13 pppoe0 [fe80::215:5dff:fe00:6412%8]:123
Jun 3 15:32:19	ntpd[64376]: setsockopt IPV6_MULTICAST_IF 0 for fe80::215:5dff:fe00:6412%8 fails: Can't assign requested address
Jun 3 15:32:19	ntpd[64376]: new interface(s) found: waking up resolver
Jun 3 15:32:20	ntpd[64376]: ntpd exiting on signal 15 (Terminated)
Jun 3 15:32:27	ntpdate[54262]: sendto(194.117.9.136): No error: 0
Jun 3 15:32:28	ntpdate[54262]: sendto(193.136.60.172): No error: 0
Jun 3 15:32:38	ntpdate[54262]: adjust time server 194.117.9.136 offset 0.000048 sec
Jun 3 15:32:38	ntp: Successfully synced time after 1 attempts.
Jun 3 15:32:38	ntp: Starting NTP Daemon.
Jun 3 15:32:38	ntpd[96136]: ntpd 4.2.7p443@1.2483-o Thu May 29 20:00:00 UTC 2014 (1): Starting
Jun 3 15:32:38	ntpd[96136]: Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid
Jun 3 15:32:38	ntpd[96437]: proto: precision = 0.500 usec (-21)
Jun 3 15:32:38	ntpd[96437]: Listen and drop on 0 v6wildcard [::]:123
Jun 3 15:32:38	ntpd[96437]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Jun 3 15:32:38	ntpd[96437]: Listen normally on 2 de0 [fe80::215:5dff:fe00:6412%1]:123
Jun 3 15:32:38	ntpd[96437]: setsockopt IPV6_MULTICAST_IF 0 for fe80::215:5dff:fe00:6412%1 fails: Can't assign requested address
Jun 3 15:32:38	ntpd[96437]: Listen normally on 3 de0 10.0.0.152:123
Jun 3 15:32:38	ntpd[96437]: Listen normally on 4 de1 192.168.1.1:123
Jun 3 15:32:38	ntpd[96437]: Listen normally on 5 de1 [fe80::215:5dff:fe00:6413%2]:123
Jun 3 15:32:38	ntpd[96437]: setsockopt IPV6_MULTICAST_IF 0 for fe80::215:5dff:fe00:6413%2 fails: Can't assign requested address
Jun 3 15:32:38	ntpd[96437]: Listen normally on 6 de2 [fe80::215:5dff:fe00:6414%3]:123
Jun 3 15:32:38	ntpd[96437]: setsockopt IPV6_MULTICAST_IF 0 for fe80::215:5dff:fe00:6414%3 fails: Can't assign requested address
Jun 3 15:32:38	ntpd[96437]: Listen normally on 7 lo0 127.0.0.1:123
Jun 3 15:32:38	ntpd[96437]: Listen normally on 8 lo0 [::1]:123
Jun 3 15:32:38	ntpd[96437]: Listen normally on 9 lo0 [fe80::1%6]:123
Jun 3 15:32:38	ntpd[96437]: setsockopt IPV6_MULTICAST_IF 0 for fe80::1%6 fails: Can't assign requested address
Jun 3 15:32:38	ntpd[96437]: Listen normally on 10 pppoe0 192.168.3.81:123
Jun 3 15:32:38	ntpd[96437]: Listen normally on 11 pppoe0 [fe80::215:5dff:fe00:6412%8]:123
Jun 3 15:32:38	ntpd[96437]: setsockopt IPV6_MULTICAST_IF 0 for fe80::215:5dff:fe00:6412%8 fails: Can't assign requested address
Jun 3 15:32:38	ntpd[96437]: Listening on routing socket on fd #32 for interface updates
Jun 3 15:32:38	ntpd[96437]: refclock_open /dev/gps0: Is a directory
Jun 3 15:32:38	ntpd[96437]: 127.127.20.0 local addr 127.0.0.1 -> <null>
Jun 3 15:33:46	ntpd[96437]: ntpd exiting on signal 15 (Terminated)
Jun 3 15:33:52	ntpdate[15630]: sendto(194.117.9.136): No error: 0
Jun 3 15:34:03	ntpdate[73276]: sendto(194.117.9.136): No error: 0</null></null></null>

                            Updating my home pfsense box. This is a hyper-v server can have some wan problems

                            Edited:
                            It works. In my VM i set-up my wan as DHCP, for some reason the interface connect and disconnect intermittently, maybe something to do with settings on VM legacy advanced options.

                            Create a PPPoE server in my home box and configured VM box WAN interface type to PPPoE after that it work. One bug with PPPoE (at least), i have to save gateway settings to have internet, otherwise nothing. This happens in my home box to, in snapshots one or two weeks ago.  Topic for another forum.

                            pfSense:
                            ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
                            Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
                            NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

                            1 Reply Last reply Reply Quote 0
                            • R
                              reverson
                              last edited by

                              For those of us that don't have SSH, and the webgui doesn't work, is there anyway to update without a console connection?  I'm guessing not, but thought I'd check.

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

                                No SSH, GUI or Console? Probably not.

                                If you have any one of the three you could run an update. SSH or console use option 13, then option 1, try 'auto' if that fails try the auto URL but with http instead of https.

                                Otherwise you'll need to get a new snap and then reinstall/reload the OS.

                                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
                                • First post
                                  Last post
                                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.