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

    New package Apcupsd is available.

    Scheduled Pinned Locked Moved pfSense Packages
    57 Posts 13 Posters 25.5k 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.
    • D Offline
      dbaio
      last edited by

      @McFuzz:

      Config was as attached (of course service was enabled; I disabled it for now since I am using NUT). All other settings are left at default.

      When you have a chance, on UPSType / Device put just "usb" and try again.

      –
      Danilo G. Baio (dbaio)

      1 Reply Last reply Reply Quote 0
      • M Offline
        McFuzz
        last edited by

        @dbaio:

        @McFuzz:

        Config was as attached (of course service was enabled; I disabled it for now since I am using NUT). All other settings are left at default.

        When you have a chance, on UPSType / Device put just "usb" and try again.

        Unfortunately that did not help :\ still have the same problem:

        
2014-04-11 13:58:04 -0700  Lock file data error: X����
2014-04-11 13:58:04 -0700  apcupsd FATAL ERROR in apcupsd.c at line 285
Failed to acquire device lock file
2014-04-11 13:58:04 -0700  Lock file data error: ؋B
2014-04-11 13:58:04 -0700  apcupsd error shutdown completed
        1 Reply Last reply Reply Quote 0
        • D Offline
          dbaio
          last edited by

          Could you collect all the log?

          On Diagnostics –> Command Prompt

          cat /var/log/apcupsd.events

          Use a pastebin like pastebin.ca

          Thank you.

          @McFuzz:

          @dbaio:

          @McFuzz:

          Config was as attached (of course service was enabled; I disabled it for now since I am using NUT). All other settings are left at default.

          When you have a chance, on UPSType / Device put just "usb" and try again.

          Unfortunately that did not help :\ still have the same problem:

          
2014-04-11 13:58:04 -0700  Lock file data error: X����
2014-04-11 13:58:04 -0700  apcupsd FATAL ERROR in apcupsd.c at line 285
Failed to acquire device lock file
2014-04-11 13:58:04 -0700  Lock file data error: ؋B
2014-04-11 13:58:04 -0700  apcupsd error shutdown completed

          –
          Danilo G. Baio (dbaio)

          1 Reply Last reply Reply Quote 0
          • M Offline
            McFuzz
            last edited by

            @dbaio:

            Could you collect the log?

            On Diagnostics –> Command Prompt

            cat /var/log/apcupsd.events

            Use a pastebin like pastebin.ca

            Thank you.

            @McFuzz:

            @dbaio:

            @McFuzz:

            Config was as attached (of course service was enabled; I disabled it for now since I am using NUT). All other settings are left at default.

            When you have a chance, on UPSType / Device put just "usb" and try again.

            Unfortunately that did not help :\ still have the same problem:

            
2014-04-11 13:58:04 -0700  Lock file data error: X����
2014-04-11 13:58:04 -0700  apcupsd FATAL ERROR in apcupsd.c at line 285
Failed to acquire device lock file
2014-04-11 13:58:04 -0700  Lock file data error: ؋B
2014-04-11 13:58:04 -0700  apcupsd error shutdown completed

            Log here:

            http://pastebin.com/9e347baC

            The log is as-of yesterday.

            1 Reply Last reply Reply Quote 0
            • D Offline
              dbaio
              last edited by

              Thanks for the log.

              Could you check what is on this directory?

              ls -lha /var/spool/lock/

              Log here:

              http://pastebin.com/9e347baC

              The log is as-of yesterday.

              –
              Danilo G. Baio (dbaio)

              1 Reply Last reply Reply Quote 0
              • D Offline
                dbaio
                last edited by

                Also, this file exists?

                /var/run/apcupsd.pid

                @dbaio:

                Thanks for the log.

                Could you check what is on this directory?

                ls -lha /var/spool/lock/

                Log here:

                http://pastebin.com/9e347baC

                The log is as-of yesterday.

                –
                Danilo G. Baio (dbaio)

                1 Reply Last reply Reply Quote 0
                • M Offline
                  McFuzz
                  last edited by

                  @dbaio:

                  Also, this file exists?

                  /var/run/apcupsd.pid

                  @dbaio:

                  Thanks for the log.

                  Could you check what is on this directory?

                  ls -lha /var/spool/lock/

                  Log here:

                  http://pastebin.com/9e347baC

                  The log is as-of yesterday.

                  I enabled the service and checked /var/spool/lock - nothing there except LCK..:

                  [2.1.2-RELEASE][root@pfsense]/var/spool/lock(8): ls -la
total 4
drwxrwxr-x  2 uucp  dialer  512 Apr 10 21:37 .
drwxr-xr-x  8 root  wheel   512 Apr 10 23:37 ..
-rw-r--r--  1 root  dialer    0 Apr 10 19:46 LCK..

                  In /var/run - apcupsd.pid does not exist :\

                  1 Reply Last reply Reply Quote 0
                  • D Offline
                    dbaio
                    last edited by

                    remove this LCK and restart the service, please

                    I enabled the service and checked /var/spool/lock - nothing there except LCK..:

                    [2.1.2-RELEASE][root@pfsense]/var/spool/lock(8): ls -la
total 4
drwxrwxr-x  2 uucp  dialer  512 Apr 10 21:37 .
drwxr-xr-x  8 root  wheel   512 Apr 10 23:37 ..
-rw-r--r--  1 root  dialer    0 Apr 10 19:46 LCK..

                    In /var/run - apcupsd.pid does not exist :\

                    –
                    Danilo G. Baio (dbaio)

                    1 Reply Last reply Reply Quote 0
                    • M Offline
                      McFuzz
                      last edited by

                      @dbaio:

                      remove this LCK and restart the service, please

                      I enabled the service and checked /var/spool/lock - nothing there except LCK..:

                      [2.1.2-RELEASE][root@pfsense]/var/spool/lock(8): ls -la
total 4
drwxrwxr-x  2 uucp  dialer  512 Apr 10 21:37 .
drwxr-xr-x  8 root  wheel   512 Apr 10 23:37 ..
-rw-r--r--  1 root  dialer    0 Apr 10 19:46 LCK..

                      In /var/run - apcupsd.pid does not exist :\

                      Yup! That did it!

                      Thanks!!!

                      Now - the email functionality; I presume there's nothing to modify or change, right? Once it goes on battery power - an email is automatically dispatched?

                      1 Reply Last reply Reply Quote 0
                      • D Offline
                        dbaio
                        last edited by

                        Yup! That did it!

                        Thanks!!!

                        Now - the email functionality; I presume there's nothing to modify or change, right? Once it goes on battery power - an email is automatically dispatched?

                        Thank you McFuzz.

                        I will update the package for fix this problem.

                        About notifications.

                        Config:
                        System -> Advanced -> Notifications –> SMTP E-Mail

                        Install:
                        mailgraph package

                        And then, you can test apcupsd e-mail notifications:

                        /usr/pbi/apcupsd-i386/etc/apcupsd/onbattery
                        /usr/pbi/apcupsd-i386/etc/apcupsd/offbattery

                        or

                        /usr/pbi/apcupsd-amd64/etc/apcupsd/onbattery
                        /usr/pbi/apcupsd-amd64/etc/apcupsd/offbattery

                        Best Regards.

                        –
                        Danilo G. Baio (dbaio)

                        1 Reply Last reply Reply Quote 0
                        • W Offline
                          webdawg
                          last edited by

                          https://forum.pfsense.org/index.php?topic=91783

                          Sent you a PM about this.  I am having the same issue now where multiple instances of it get ran.

                          1 Reply Last reply Reply Quote 0
                          • D Offline
                            dbaio
                            last edited by

                            @webdawg:

                            https://forum.pfsense.org/index.php?topic=91783

                            Sent you a PM about this.  I am having the same issue now where multiple instances of it get ran.

                            Ok thanks.

                            I've sent a PR for adding apcupsd on pfSense 2.3.

                            https://github.com/pfsense/FreeBSD-ports/pull/128

                            On pfSense 2.3 the problem with emails won't happening.  ;D

                            –
                            Danilo G. Baio (dbaio)

                            1 Reply Last reply Reply Quote 0
                            • W Offline
                              webdawg
                              last edited by

                              Rockin…I am thinking I will have to install it.

                              1 Reply Last reply Reply Quote 0
                              • F Offline
                                flu
                                last edited by

                                Are  there plans to make Apcupsd available for PfSense 2.3.x ?

                                Sorry, forget my question above. I overlooked that you are already working on that. Great!

                                Greetings
                                flu

                                1 Reply Last reply Reply Quote 0
                                • N Offline
                                  Napsterbater
                                  last edited by

                                  Just posting to show interest.. Used this on a older install, immediately went to look for it on this new install and was sad when I didn't see it..

                                  Appreciate your work on this.

                                  1 Reply Last reply Reply Quote 0
                                  • R Offline
                                    Reanimator77
                                    last edited by

                                    How to install apcupsd on pfSense 2.3.2 ???
                                    This package is not available in the "Package Manager"  :-[

                                    1 Reply Last reply Reply Quote 0
                                    • D Offline
                                      dbaio
                                      last edited by

                                      @Reanimator77:

                                      How to install apcupsd on pfSense 2.3.2 ???
                                      This package is not available in the "Package Manager"  :-[
                                      [/quote]

                                      I think it will be available soon.
                                      A developer was assigned to the PR:
                                      https://github.com/pfsense/FreeBSD-ports/pull/128

                                      –
                                      Danilo G. Baio (dbaio)

                                      1 Reply Last reply Reply Quote 0
                                      • L Offline
                                        LucaTo
                                        last edited by

                                        But… should be "merged it only for 2.3.3-snapshots"? (https://github.com/pfsense/FreeBSD-ports/pull/128)
                                        I'm on 2.3.3 but apcupsd isn't listed on packages page.
                                        There is a way to get the pkg…?

                                        1 Reply Last reply Reply Quote 0
                                        • D Offline
                                          dbaio
                                          last edited by

                                          @LucaTo:

                                          But… should be "merged it only for 2.3.3-snapshots"? (https://github.com/pfsense/FreeBSD-ports/pull/128)
                                          I'm on 2.3.3 but apcupsd isn't listed on packages page.
                                          There is a way to get the pkg…?

                                          I've sent a message to the devs about this.
                                          I think it will be available very soon.

                                          –
                                          Danilo G. Baio (dbaio)

                                          1 Reply Last reply Reply Quote 0
                                          • L Offline
                                            LucaTo
                                            last edited by

                                            apcupsd is now published!  :)
                                            Service starts and on "Status information" I can see UPS parameters.
                                            But in system logs:

                                            Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided
Aug 10 09:35:18 	apcupsd 	58288 	apcupsd FATAL ERROR in newups.c at line 103 Mutex lock failure. ERR=Resource deadlock avoided

                                            My system:
                                            pfsense 2.3.3-DEVELOPMENT (amd64) built on Tue Aug 09 21:57:46 CDT 2016
                                            ups APC sua1000i controlled via network card AP9630

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