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

    NUT 2.2.0 - pfSense 1.2b2 - not working

    Scheduled Pinned Locked Moved pfSense Packages
    21 Posts 7 Posters 8.7k 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.
    • Z
      z00te
      last edited by

      ok,

      i've found these two links maybe could be useful :

      http://lists.freebsd.org/pipermail/cvs-src/2007-November/084046.html
      http://groups.google.com/group/lucky.freebsd.questions/msg/1fa8564a3a000390

      tnx bye

      1 Reply Last reply Reply Quote 0
      • dotdashD
        dotdash
        last edited by

        I got nowhere with the perl lib, so I ended up finding a copy of nut 2.0.4 on a FreeBSD package mirror and loading that from the shell. This was after I had installed the 2.2.0 pfSense package. It's an ugly hack, but it works and the status page in the webgui looks fine.

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

          Trying to install on 1.2rc3 it keeps hanging at
          "nut-2.2.0  (extracting)"
          Any help appreciated.
          Thanks,
          Craig

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

            I had some time to test this out on 1.2 RC4. I experienced no problems with the package install or deinstall. The extracting nut-2.2.0 step does take 30 seconds or so to complete so give it a minute. However I did find an error when trying to start the daemon

            /usr/local/etc/rc.d/nut.sh start

            starting genericups
            Network UPS Tools - UPS driver controller 2.2.0
            /libexec/ld-elf.so.1: /usr/local/libexec/nut/upsdrvctl: Undefined symbol
            "__sbmaskrune"
            genericups failed to start

            I'm looking at how to resolve this and will update this thread when I figure it out.

            1 Reply Last reply Reply Quote 0
            • D
              dvserg
              last edited by

              Looking to the perl-5.8.8_1 port libperl.so
              May be this can help you?

              SquidGuardDoc EN  RU Tutorial
              Localization ru_PFSense

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

                Alright I've come to the bottom of this. The 6-stable folder nut-2.2.0 version is broken with the above error. The 6.3-release folder nut-2.2.0 version works. The 6.2-release folder nut-2.0.4 works as well. I'm not sure if we should just roll back to nut-2.0.4 or if there will be issues from using the 6.3 release version of nut-2.2.0.

                If we roll back to 2.0.4 I know nut-2.2.0 version replaces the newhidups driver with usbhid-ups. I'm not sure if this was just a name change or if it added support for more UPS's.

                1 Reply Last reply Reply Quote 0
                • Cry HavokC
                  Cry Havok
                  last edited by

                  The changelog can be found at: http://www.networkupstools.org/source/2.2/testing/ChangeLog.  It looks like newhidups and usbhid-ups are different drivers, so not a name change.  I'd expect that the newer one supported more UPSs.

                  I'd say that if pfSense 1.2 is based on 6.3 then go with the 6.3 version, otherwise stick with the (working) 6.2 version.

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

                    @Cry:

                    The changelog can be found at: http://www.networkupstools.org/source/2.2/testing/ChangeLog.  It looks like newhidups and usbhid-ups are different drivers, so not a name change.  I'd expect that the newer one supported more UPSs.

                    I'd say that if pfSense 1.2 is based on 6.3 then go with the 6.3 version, otherwise stick with the (working) 6.2 version.

                    I was just going by what was stated on the post months ago when 2.0.5 was updated to 2.2.0 in the 6-stable directory. pfSense is based on 6.2. I'll move the package back to 2.04 in the 6.2-release today.

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

                      To switch to the working 2.0.4 version you need to uninstall the package via the package manager and then install it again.

                      1 Reply Last reply Reply Quote 0
                      • Cry HavokC
                        Cry Havok
                        last edited by

                        That works - thanks.

                        1 Reply Last reply Reply Quote 0
                        • Z
                          z00te
                          last edited by

                          tnx now it work again  ;D
                          z

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