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

    NUT package (2.8.0 and below)

    Scheduled Pinned Locked Moved
    UPS Tools
    128
    1.2k
    2.9m
    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.
    • K
      kevindd992002
      last edited by

      Last 10/3/2019 there was a power failure and I received a message from my Syno:

      Dear user,

The UPS connected to Synology has reached low battery. All services are shut down. The services will be restarted once the UPS is recovered.

Sincerely,
Synology DiskStation

      This is expected. It happened 5:47PM and then at 10:39PM I received this:

      Dear user,

Synology suffered from power failure and was shut down improperly.

Sincerely,
Synology DiskStation

      I then checked my Syno's upsmon.conf and it is 0 bytes again! I don't know what could've caused this but I'll report back to Syno support as they requested last time. So between 5:47PM and 10:39PM, that conf file got corrupted again for some reason, and was the cause of the improper shutdown.

      dennypageD 1 Reply Last reply Reply Quote 0
      • dennypageD
        dennypage @kevindd992002
        last edited by

        @kevindd992002 Did you have the HOSTSYNC setting in the upsmon.conf section?

        K 1 Reply Last reply Reply Quote 0
        • K
          kevindd992002 @dennypage
          last edited by

          @dennypage said in NUT package:

          @kevindd992002 Did you have the HOSTSYNC setting in the upsmon.conf section?

          Yes I did, for 120 seconds. That's what I thought at first but digging through the logs of pfsense, the power went out again at 8:15PM and came back at 10:39PM. And what I think happened is the upsmon.conf file was reverted to 0 bytes right after the Syno turned on when the power went back on at 6:15PM. So at 6:15PM, the Syno never was able to connect to the NUT master.

          dennypageD 1 Reply Last reply Reply Quote 0
          • dennypageD
            dennypage @kevindd992002
            last edited by

            @kevindd992002 That's pretty strange (scary). Other than talking with Synology, the only thing I can think to suggest is to double check that your Synology can easily shut down in 120 seconds. Mine used to shutdown in under 60 seconds. I just retested (glad I did) and I'm seeing it now at 90 seconds. I don't know if the change is due to a newer DSM or because of changes I've made with Surveillance Station.

            K 1 Reply Last reply Reply Quote 0
            • K
              kevindd992002 @dennypage
              last edited by

              @dennypage said in NUT package:

              @kevindd992002 That's pretty strange (scary). Other than talking with Synology, the only thing I can think to suggest is to double check that your Synology can easily shut down in 120 seconds. Mine used to shutdown in under 60 seconds. I just retested (glad I did) and I'm seeing it now at 90 seconds. I don't know if the change is due to a newer DSM or because of changes I've made with Surveillance Station.

              I thought of that and it was fine when there was a blackout like a few days ago before Oct 3. So it's got to be the upsmon.conf issue again.

              dennypageD 1 Reply Last reply Reply Quote 0
              • dennypageD
                dennypage @kevindd992002
                last edited by

                @kevindd992002 said in NUT package:

                I thought of that and it was fine when there was a blackout like a few days ago before Oct 3. So it's got to be the upsmon.conf issue again.

                Cool. Just checking.

                Seems pretty clear that Synology has a bug in their nut configuration management.

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

                  Hello All,
                  The issue I am having may have been answered already but there are several posts here and I haven't been able to find my answer. Anyways....I have a Tripp Lite SMART1500LCD. It is plugged into my pfsense router; it is an old Dell R210 server running just pfsense. It appears I have everything set up correctly and pfsense is seeing my UPS. I also have my FreeNAS set up as a slave and it can see the UPS through the pfsense box. When I cut the power to test the shutdown process, FreeNAS shuts down after 60 seconds; which is how I have it setup. FreeNAS is working how I want it to. The issue I am having is my pfsense box IS NOT shutting down. When I tested it, the UPS completely ran out of battery and pfsense never initiated the shutdown sequence. I tried using the commands suggested on here in the ups.conf but they don't do anything. I attached some screenshots. of my pfsense UPS settings.

                  Ups_settings_pg1.JPG
                  Ups_settings_pg2.JPG
                  Ups_status_pg1.JPG
                  Ups_status_pg2.JPG

                  dennypageD 1 Reply Last reply Reply Quote 0
                  • dennypageD
                    dennypage @tensi0n519
                    last edited by

                    @tensi0n519 You have the UPS configured to ignore the low battery signal, and to not initiate a shutdown until the ups is under 5% or 60 seconds of runtime. Note that the 5% and 60 second values are determined by polling (every 30 seconds) rather than by signal from the UPS. This ends up being a very narrow margin for conducting a shutdown.

                    NUT provides no native way to initiate shutdown within X seconds of going on battery. You can initiate shutdown based on a low battery signal from the UPS (default), or values such as % or runtime calculated from the UPS status.

                    Things to do:

                    1. Remove ignorelb from configuration. ignorelb is used to work around UPSs that send an immediate low battery signal as soon as the UPS goes on battery. The Tripp Lite does not do this.
                    2. Either remove the % or increase it to a minimum of 15-20%. If it were me, I would simply delete this parameter.
                    3. Either remove the runtime or increase it to a minimum of 120. If it were me, I would use a value of 300.

                    The higher the values for % and runtime, the easier it is on the battery. And the safer it is for shutdown.

                    K 1 Reply Last reply Reply Quote 0
                    • K
                      kevindd992002 @dennypage
                      last edited by

                      @dennypage said in NUT package:

                      @tensi0n519 You have the UPS configured to ignore the low battery signal, and to not initiate a shutdown until the ups is under 5% or 60 seconds of runtime. Note that the 5% and 60 second values are determined by polling (every 30 seconds) rather than by signal from the UPS. This ends up being a very narrow margin for conducting a shutdown.

                      NUT provides no native way to initiate shutdown within X seconds of going on battery. You can initiate shutdown based on a low battery signal from the UPS (default), or values such as % or runtime calculated from the UPS status.

                      Things to do:

                      1. Remove ignorelb from configuration. ignorelb is used to work around UPSs that send an immediate low battery signal as soon as the UPS goes on battery. The Tripp Lite does not do this.
                      2. Either remove the % or increase it to a minimum of 15-20%. If it were me, I would simply delete this parameter.
                      3. Either remove the runtime or increase it to a minimum of 120. If it were me, I would use a value of 300.

                      The higher the values for % and runtime, the easier it is on the battery. And the safer it is for shutdown.

                      @dennypage , how do you totally delete the %? Can you put a blank value in the charge.low parameter in the extra arguments for the driver field?

                      dennypageD 1 Reply Last reply Reply Quote 0
                      • dennypageD
                        dennypage @kevindd992002
                        last edited by

                        @kevindd992002 said in NUT package:

                        @dennypage , how do you totally delete the %? Can you put a blank value in the charge.low parameter in the extra arguments for the driver field?

                        Delete the line that says "override.battery.charge.low = 5" from the Additional configuration lines for ups.conf text input box. Be sure to delete the "ignorelb" line as well.

                        When you are done, the Additional configuration lines for ups.conf section should either be completely empty, or have a single line that says "override.battery.runtime.low = 300"

                        1 Reply Last reply Reply Quote 1
                        • H
                          huuur
                          last edited by

                          Greetings everyone!
                          Sorry for the noob question, but I tried to find an answer in the past days with no luck!
                          I just got an APC ups with network card, I installed NUT package, I can read my ups data via pfsense but I couldn't find a way to manually configure the package so (for example) I can setup when to shutdown pfsense with respect to the remaining ups battery, I noticed a few old guides which inapplicable to the current NUT package release.
                          Thanks for your kind time

                          dennypageD 1 Reply Last reply Reply Quote 0
                          • dennypageD
                            dennypage @huuur
                            last edited by

                            @huuur This is discussed several times earlier in this thread. The previous 4 posts were specifically about this topic.

                            If you leave NUT alone (default configuration), it will perform a shutdown on the local system when the UPS signals a low better situation. In 90% of the cases, this is the desired behavior. If you have a USB based UPS and are only supporting pfSense with it, I would recommend staying with the default configuration.

                            If you have a more complicated configuration, such as multi-system, an exotic UPS, etc., and need to change the way NUT behaves, the best way to start is with the NUT User Manual located here. It's important to understand the trade-offs when making changes to the NUT configuration. You can easily create configurations in which NUT will not successfully shut down the system(s) when mains fail, or will not recover them after mains return.

                            1 Reply Last reply Reply Quote 2
                            • D
                              DurUser
                              last edited by

                              I recently migrated my pfsense to some different hardware. I made a backup of all pfsense settings, installed pfsense on the new machine, then restored all pfsense settings.
                              Now I am seeing issues with my ups which I also moved over from the old machine to the new one. Once in a while I get an email saying it is disconnected but the logs are showing more issues.

                              Oct 28 17:29:45 kernel ugen1.3: <CPS CP 1500C> at usbus1
                              Oct 28 17:29:44 usbhid-ups 11742 Got disconnected by another driver: Device not configured
                              Oct 28 17:29:44 kernel ugen1.3: <CPS CP 1500C> at usbus1 (disconnected)
                              Oct 28 17:19:53 kernel ugen1.3: <CPS CP 1500C> at usbus1
                              Oct 28 17:19:52 kernel ugen1.3: <CPS CP 1500C> at usbus1 (disconnected)
                              Oct 28 15:55:15 kernel ugen1.3: <CPS CP 1500C> at usbus1
                              Oct 28 15:55:15 usbhid-ups 11742 Got disconnected by another driver: Device not configured
                              Oct 28 15:55:14 kernel ugen1.3: <CPS CP 1500C> at usbus1 (disconnected)
                              Oct 28 15:27:01 kernel ugen1.3: <CPS CP 1500C> at usbus1
                              Oct 28 15:27:00 kernel ugen1.3: <CPS CP 1500C> at usbus1 (disconnected)
                              Oct 28 13:55:06 kernel ugen1.3: <CPS CP 1500C> at usbus1
                              Oct 28 13:55:06 kernel ugen1.3: <CPS CP 1500C> at usbus1 (disconnected)
                              Oct 28 13:23:06 kernel ugen1.3: <CPS CP 1500C> at usbus1
                              Oct 28 13:23:06 kernel ugen1.3: <CPS CP 1500C> at usbus1 (disconnected)
                              Oct 28 10:25:39 kernel ugen1.3: <CPS CP 1500C> at usbus1
                              Oct 28 10:25:38 kernel ugen1.3: <CPS CP 1500C> at usbus1 (disconnected)
                              Oct 28 08:07:07 kernel ugen1.3: <CPS CP 1500C> at usbus1
                              Oct 28 08:07:07 kernel ugen1.3: <CPS CP 1500C> at usbus1 (disconnected)
                              Oct 28 07:25:38 kernel ugen1.3: <CPS CP 1500C> at usbus1
                              Oct 28 07:25:38 usbhid-ups 11742 Got disconnected by another driver: Device not configured

                              dennypageD 1 Reply Last reply Reply Quote 0
                              • dennypageD
                                dennypage @DurUser
                                last edited by

                                @DurUser I would recommend the following:

                                • Delete the NUT package
                                • Re-Install the NUT package
                                • Go to Services / UPS / UPS Settings and press Save
                                • Reboot the system
                                1 Reply Last reply Reply Quote 0
                                • K
                                  kevindd992002
                                  last edited by kevindd992002

                                  @dennypage

                                  I swtich from using an APC BR1500GI to an APC SUA750I( Smart-UPS) and here are my NUT logs:

                                  Nov 18 17:55:45 	upsmon 	36031 	Startup successful
Nov 18 17:55:46 	upsd 	68133 	listening on 192.168.55.1 port 3493
Nov 18 17:55:46 	upsd 	68133 	listening on 192.168.10.1 port 3493
Nov 18 17:55:46 	upsd 	68133 	listening on ::1 port 3493
Nov 18 17:55:46 	upsd 	68133 	listening on 127.0.0.1 port 3493
Nov 18 17:55:46 	upsd 	68133 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 18 17:55:46 	upsd 	69406 	Startup successful
Nov 18 17:55:46 	usbhid-ups 	87095 	Startup successful
Nov 18 17:55:48 	upsmon 	24376 	Startup successful
Nov 18 17:55:49 	upsd 	45686 	listening on 192.168.55.1 port 3493
Nov 18 17:55:49 	upsd 	45686 	listening on 192.168.10.1 port 3493
Nov 18 17:55:49 	upsd 	45686 	listening on ::1 port 3493
Nov 18 17:55:49 	upsd 	45686 	listening on 127.0.0.1 port 3493
Nov 18 17:55:49 	upsd 	45686 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 18 17:55:49 	upsd 	47292 	Startup successful
Nov 18 17:55:50 	usbhid-ups 	53100 	Startup successful
Nov 18 17:55:51 	upsd 	47292 	Connected to UPS [ups]: usbhid-ups-ups
Nov 18 17:55:51 	upsd 	47292 	User local-monitor@::1 logged into UPS [ups]
Nov 18 17:55:51 	upsmon 	25365 	UPS ups battery is low
Nov 18 17:56:06 	upsmon 	25365 	Signal 15: exiting
Nov 18 17:56:06 	upsd 	47292 	User local-monitor@::1 logged out from UPS [ups]
Nov 18 17:56:06 	upsd 	47292 	mainloop: Interrupted system call
Nov 18 17:56:06 	upsd 	47292 	Signal 15: exiting
Nov 18 17:56:06 	usbhid-ups 	53100 	Signal 15: exiting
Nov 18 17:56:06 	upsmon 	70819 	Startup successful
Nov 18 17:56:07 	upsd 	40389 	listening on 192.168.55.1 port 3493
Nov 18 17:56:07 	upsd 	40389 	listening on 192.168.10.1 port 3493
Nov 18 17:56:07 	upsd 	40389 	listening on ::1 port 3493
Nov 18 17:56:07 	upsd 	40389 	listening on 127.0.0.1 port 3493
Nov 18 17:56:07 	upsd 	40389 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 18 17:56:07 	upsd 	41504 	Startup successful
Nov 18 17:56:07 	usbhid-ups 	65623 	Startup successful
Nov 18 17:56:09 	upsd 	41504 	Connected to UPS [ups]: usbhid-ups-ups
Nov 18 17:56:09 	upsd 	41504 	User local-monitor@::1 logged into UPS [ups]
Nov 18 17:56:09 	upsmon 	71439 	UPS ups battery is low
Nov 18 17:56:09 	upsmon 	76764 	Startup successful
Nov 18 17:56:10 	upsd 	35747 	listening on 192.168.55.1 port 3493
Nov 18 17:56:10 	upsd 	35747 	listening on 192.168.10.1 port 3493
Nov 18 17:56:10 	upsd 	35747 	listening on ::1 port 3493
Nov 18 17:56:10 	upsd 	35747 	listening on 127.0.0.1 port 3493
Nov 18 17:56:10 	upsd 	35747 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 18 17:56:10 	upsd 	36536 	Startup successful
Nov 18 17:56:10 	usbhid-ups 	62071 	Startup successful
Nov 18 17:56:12 	upsd 	36536 	Connected to UPS [ups]: usbhid-ups-ups
Nov 18 17:56:12 	upsd 	36536 	User local-monitor@::1 logged into UPS [ups]
Nov 18 17:56:12 	upsmon 	77359 	UPS ups battery is low
Nov 18 17:56:14 	upsmon 	77359 	Signal 15: exiting
Nov 18 17:56:14 	upsd 	36536 	User local-monitor@::1 logged out from UPS [ups]
Nov 18 17:56:14 	upsd 	36536 	mainloop: Interrupted system call
Nov 18 17:56:14 	upsd 	36536 	Signal 15: exiting
Nov 18 17:56:14 	usbhid-ups 	62071 	Signal 15: exiting
Nov 18 17:56:14 	upsmon 	14837 	Startup successful
Nov 18 17:56:15 	upsd 	46596 	listening on 192.168.55.1 port 3493
Nov 18 17:56:15 	upsd 	46596 	listening on 192.168.10.1 port 3493
Nov 18 17:56:15 	upsd 	46596 	listening on ::1 port 3493
Nov 18 17:56:15 	upsd 	46596 	listening on 127.0.0.1 port 3493
Nov 18 17:56:15 	upsd 	46596 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 18 17:56:15 	upsd 	46857 	Startup successful
Nov 18 17:56:15 	usbhid-ups 	53353 	Startup successful
Nov 18 17:56:17 	upsmon 	57789 	Startup successful
Nov 18 17:56:18 	upsmon 	67055 	Startup successful
Nov 18 17:56:18 	upsd 	68555 	listening on 192.168.55.1 port 3493
Nov 18 17:56:18 	upsd 	68555 	listening on 192.168.10.1 port 3493
Nov 18 17:56:18 	upsd 	68555 	listening on ::1 port 3493
Nov 18 17:56:18 	upsd 	68555 	listening on 127.0.0.1 port 3493
Nov 18 17:56:18 	upsd 	68555 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 18 17:56:18 	upsd 	68612 	Startup successful
Nov 18 17:56:20 	upsd 	68612 	User monuser@192.168.10.10 logged into UPS [ups]
Nov 18 17:56:21 	upsmon 	83467 	Startup successful
Nov 18 17:56:22 	upsd 	85178 	listening on 192.168.55.1 port 3493
Nov 18 17:56:22 	upsd 	85178 	listening on 192.168.10.1 port 3493
Nov 18 17:56:22 	upsd 	85178 	listening on ::1 port 3493
Nov 18 17:56:22 	upsd 	85178 	listening on 127.0.0.1 port 3493
Nov 18 17:56:22 	upsd 	85178 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 18 17:56:22 	upsd 	85326 	Startup successful
Nov 18 17:56:22 	usbhid-ups 	85426 	Startup successful
Nov 18 17:56:24 	upsd 	85326 	Connected to UPS [ups]: usbhid-ups-ups
Nov 18 17:56:24 	upsd 	85326 	User local-monitor@::1 logged into UPS [ups]
Nov 18 17:56:24 	upsmon 	84121 	UPS ups battery is low
Nov 18 17:56:30 	upsd 	85326 	User monuser@192.168.10.10 logged into UPS [ups]
Nov 18 18:39:29 	upsmon 	84121 	UPS ups battery is low
Nov 18 18:40:44 	upsmon 	84121 	UPS ups battery is low
Nov 18 18:48:42 	upsmon 	84121 	Signal 15: exiting
Nov 18 18:48:42 	upsd 	85326 	User local-monitor@::1 logged out from UPS [ups]
Nov 18 18:48:42 	upsd 	85326 	mainloop: Interrupted system call
Nov 18 18:48:42 	upsd 	85326 	Signal 15: exiting
Nov 18 18:48:42 	usbhid-ups 	85426 	Signal 15: exiting
Nov 18 18:48:42 	upsmon 	67763 	Startup successful
Nov 18 18:48:43 	upsd 	68475 	listening on 192.168.55.1 port 3493
Nov 18 18:48:43 	upsd 	68475 	listening on 192.168.10.1 port 3493
Nov 18 18:48:43 	upsd 	68475 	listening on ::1 port 3493
Nov 18 18:48:43 	upsd 	68475 	listening on 127.0.0.1 port 3493
Nov 18 18:48:43 	upsd 	68475 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 18 18:48:43 	upsd 	68594 	Startup successful
Nov 18 18:48:43 	usbhid-ups 	68878 	Startup successful
Nov 18 18:48:45 	upsd 	68594 	Connected to UPS [ups]: usbhid-ups-ups
Nov 18 18:48:45 	upsd 	68594 	User local-monitor@::1 logged into UPS [ups]
Nov 18 18:48:51 	upsd 	68594 	User monuser@192.168.10.10 logged into UPS [ups]
Nov 19 08:22:51 	upsmon 	29107 	Startup successful
Nov 19 08:22:51 	upsd 	90116 	listening on 192.168.55.1 port 3493
Nov 19 08:22:51 	upsd 	90116 	listening on 192.168.10.1 port 3493
Nov 19 08:22:51 	upsd 	90116 	listening on ::1 port 3493
Nov 19 08:22:51 	upsd 	90116 	listening on 127.0.0.1 port 3493
Nov 19 08:22:51 	upsd 	90116 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 08:22:51 	upsd 	90860 	Startup successful
Nov 19 08:22:52 	usbhid-ups 	91043 	Startup successful
Nov 19 08:22:53 	upsmon 	22457 	Startup successful
Nov 19 08:22:54 	upsd 	41880 	listening on 192.168.55.1 port 3493
Nov 19 08:22:54 	upsd 	41880 	listening on 192.168.10.1 port 3493
Nov 19 08:22:54 	upsd 	41880 	listening on ::1 port 3493
Nov 19 08:22:54 	upsd 	41880 	listening on 127.0.0.1 port 3493
Nov 19 08:22:54 	upsd 	41880 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 08:22:54 	upsd 	44338 	Startup successful
Nov 19 08:22:55 	usbhid-ups 	48894 	Startup successful
Nov 19 08:22:56 	upsd 	44338 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 08:22:56 	upsd 	44338 	User local-monitor@::1 logged into UPS [ups]
Nov 19 08:22:56 	upsmon 	22924 	UPS ups battery is low
Nov 19 08:23:12 	upsmon 	22924 	Signal 15: exiting
Nov 19 08:23:12 	upsd 	44338 	User local-monitor@::1 logged out from UPS [ups]
Nov 19 08:23:13 	upsd 	44338 	mainloop: Interrupted system call
Nov 19 08:23:13 	upsd 	44338 	Signal 15: exiting
Nov 19 08:23:13 	usbhid-ups 	48894 	Signal 15: exiting
Nov 19 08:23:13 	upsmon 	68556 	Startup successful
Nov 19 08:23:14 	upsd 	26073 	listening on 192.168.55.1 port 3493
Nov 19 08:23:14 	upsd 	26073 	listening on 192.168.10.1 port 3493
Nov 19 08:23:14 	upsd 	26073 	listening on ::1 port 3493
Nov 19 08:23:14 	upsd 	26073 	listening on 127.0.0.1 port 3493
Nov 19 08:23:14 	upsd 	26073 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 08:23:14 	upsd 	27731 	Startup successful
Nov 19 08:23:14 	usbhid-ups 	40789 	Startup successful
Nov 19 08:23:16 	upsmon 	45882 	Startup successful
Nov 19 08:23:17 	upsd 	6319 	listening on 192.168.55.1 port 3493
Nov 19 08:23:17 	upsd 	6319 	listening on 192.168.10.1 port 3493
Nov 19 08:23:17 	upsd 	6319 	listening on ::1 port 3493
Nov 19 08:23:17 	upsd 	6319 	listening on 127.0.0.1 port 3493
Nov 19 08:23:17 	upsd 	6319 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 08:23:17 	upsd 	7547 	Startup successful
Nov 19 08:23:17 	upsd 	7547 	User local-monitor@127.0.0.1 logged into UPS [ups]
Nov 19 08:23:17 	upsmon 	46896 	Poll UPS [ups] failed - Driver not connected
Nov 19 08:23:17 	upsmon 	46896 	Communications with UPS ups lost
Nov 19 08:23:17 	upsmon 	46896 	upsmon parent process died - shutdown impossible
Nov 19 08:23:17 	upsmon 	46896 	Parent died - shutdown impossible
Nov 19 08:23:17 	upsd 	7547 	mainloop: Interrupted system call
Nov 19 08:23:17 	upsd 	7547 	Signal 15: exiting
Nov 19 08:23:17 	upsmon 	17635 	Startup successful
Nov 19 08:23:18 	upsd 	50913 	listening on 192.168.55.1 port 3493
Nov 19 08:23:18 	upsd 	50913 	listening on 192.168.10.1 port 3493
Nov 19 08:23:18 	upsd 	50913 	listening on ::1 port 3493
Nov 19 08:23:18 	upsd 	50913 	listening on 127.0.0.1 port 3493
Nov 19 08:23:18 	upsd 	50913 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 08:23:18 	upsd 	52181 	Startup successful
Nov 19 08:23:19 	usbhid-ups 	96749 	Startup successful
Nov 19 08:23:20 	upsmon 	79823 	Startup successful
Nov 19 08:23:21 	upsd 	9372 	listening on 192.168.55.1 port 3493
Nov 19 08:23:21 	upsd 	9372 	listening on 192.168.10.1 port 3493
Nov 19 08:23:21 	upsd 	9372 	listening on ::1 port 3493
Nov 19 08:23:21 	upsd 	9372 	listening on 127.0.0.1 port 3493
Nov 19 08:23:21 	upsd 	9372 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 08:23:21 	upsd 	10431 	Startup successful
Nov 19 08:23:21 	usbhid-ups 	14189 	Startup successful
Nov 19 08:23:21 	upsd 	10431 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 08:23:21 	upsd 	10431 	User local-monitor@127.0.0.1 logged into UPS [ups]
Nov 19 08:23:21 	upsmon 	80016 	UPS ups battery is low
Nov 19 08:23:21 	upsmon 	80016 	upsmon parent process died - shutdown impossible
Nov 19 08:23:21 	upsd 	10431 	mainloop: Interrupted system call
Nov 19 08:23:21 	upsmon 	80016 	Parent died - shutdown impossible
Nov 19 08:23:21 	upsd 	10431 	Signal 15: exiting
Nov 19 08:23:21 	usbhid-ups 	14189 	Signal 15: exiting
Nov 19 08:23:21 	upsmon 	21643 	Startup successful
Nov 19 08:23:22 	upsd 	49642 	listening on 192.168.55.1 port 3493
Nov 19 08:23:22 	upsd 	49642 	listening on 192.168.10.1 port 3493
Nov 19 08:23:22 	upsd 	49642 	listening on ::1 port 3493
Nov 19 08:23:22 	upsd 	49642 	listening on 127.0.0.1 port 3493
Nov 19 08:23:22 	upsd 	49642 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 08:23:22 	upsd 	50785 	Startup successful
Nov 19 08:23:23 	usbhid-ups 	54253 	Startup successful
Nov 19 08:23:24 	upsmon 	66531 	Startup successful
Nov 19 08:23:25 	upsd 	74409 	listening on 192.168.55.1 port 3493
Nov 19 08:23:25 	upsd 	74409 	listening on 192.168.10.1 port 3493
Nov 19 08:23:25 	upsd 	74409 	listening on ::1 port 3493
Nov 19 08:23:25 	upsd 	74409 	listening on 127.0.0.1 port 3493
Nov 19 08:23:25 	upsd 	74409 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 08:23:25 	upsd 	75669 	Startup successful
Nov 19 08:23:26 	upsmon 	77068 	Startup successful
Nov 19 08:23:27 	upsd 	80805 	listening on 192.168.55.1 port 3493
Nov 19 08:23:27 	upsd 	80805 	listening on 192.168.10.1 port 3493
Nov 19 08:23:27 	upsd 	80805 	listening on ::1 port 3493
Nov 19 08:23:27 	upsd 	80805 	listening on 127.0.0.1 port 3493
Nov 19 08:23:27 	upsd 	80805 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 08:23:27 	upsd 	80929 	Startup successful
Nov 19 08:23:27 	upsd 	80929 	User monuser@192.168.10.10 logged into UPS [ups]
Nov 19 08:23:29 	upsd 	80929 	User local-monitor@::1 logged into UPS [ups]
Nov 19 08:23:29 	upsmon 	77815 	Poll UPS [ups] failed - Driver not connected
Nov 19 08:23:29 	upsmon 	77815 	Communications with UPS ups lost
Nov 19 08:23:29 	upsmon 	95189 	Startup successful
Nov 19 08:23:30 	upsd 	97587 	listening on 192.168.55.1 port 3493
Nov 19 08:23:30 	upsd 	97587 	listening on 192.168.10.1 port 3493
Nov 19 08:23:30 	upsd 	97587 	listening on ::1 port 3493
Nov 19 08:23:30 	upsd 	97587 	listening on 127.0.0.1 port 3493
Nov 19 08:23:30 	upsd 	97587 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 08:23:30 	upsd 	97751 	Startup successful
Nov 19 08:23:30 	usbhid-ups 	97913 	Startup successful
Nov 19 08:23:32 	upsd 	97751 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 08:23:32 	upsd 	97751 	User local-monitor@::1 logged into UPS [ups]
Nov 19 08:23:32 	upsmon 	95933 	UPS ups on battery
Nov 19 08:23:32 	upsmon 	95933 	UPS ups battery is low
Nov 19 08:23:32 	upsd 	97751 	Client local-monitor@::1 set FSD on UPS [ups]
Nov 19 08:23:32 	upsmon 	95933 	Executing automatic power-fail shutdown
Nov 19 08:23:32 	upsmon 	95933 	Auto logout and shutdown proceeding
Nov 19 08:23:37 	upsd 	97751 	User monuser@192.168.10.10 logged into UPS [ups]
Nov 19 09:10:39 	upsmon 	32184 	Startup successful
Nov 19 09:10:40 	upsd 	11447 	listening on 192.168.55.1 port 3493
Nov 19 09:10:40 	upsd 	11447 	listening on 192.168.10.1 port 3493
Nov 19 09:10:40 	upsd 	11447 	listening on ::1 port 3493
Nov 19 09:10:40 	upsd 	11447 	listening on 127.0.0.1 port 3493
Nov 19 09:10:40 	upsd 	11447 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 09:10:40 	upsd 	14108 	Startup successful
Nov 19 09:10:40 	usbhid-ups 	22621 	Startup successful
Nov 19 09:10:41 	upsd 	14108 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 09:10:41 	upsd 	14108 	User local-monitor@::1 logged into UPS [ups]
Nov 19 09:10:41 	upsmon 	86595 	Startup successful
Nov 19 09:10:42 	upsd 	17802 	listening on 192.168.55.1 port 3493
Nov 19 09:10:42 	upsd 	17802 	listening on 192.168.10.1 port 3493
Nov 19 09:10:42 	upsd 	17802 	listening on ::1 port 3493
Nov 19 09:10:42 	upsd 	17802 	listening on 127.0.0.1 port 3493
Nov 19 09:10:42 	upsd 	17802 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 09:10:42 	upsd 	19226 	Startup successful
Nov 19 09:10:43 	usbhid-ups 	38107 	Startup successful
Nov 19 09:10:44 	upsd 	19226 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 09:10:44 	upsd 	19226 	User local-monitor@::1 logged into UPS [ups]
Nov 19 09:10:59 	upsmon 	87107 	Signal 15: exiting
Nov 19 09:10:59 	upsd 	19226 	User local-monitor@::1 logged out from UPS [ups]
Nov 19 09:10:59 	upsd 	19226 	mainloop: Interrupted system call
Nov 19 09:10:59 	upsd 	19226 	Signal 15: exiting
Nov 19 09:10:59 	upsmon 	77014 	Startup successful
Nov 19 09:11:00 	upsd 	8779 	listening on 192.168.55.1 port 3493
Nov 19 09:11:00 	upsd 	8779 	listening on 192.168.10.1 port 3493
Nov 19 09:11:00 	upsd 	8779 	listening on ::1 port 3493
Nov 19 09:11:00 	upsd 	8779 	listening on 127.0.0.1 port 3493
Nov 19 09:11:00 	upsd 	8779 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 09:11:00 	upsd 	8973 	Startup successful
Nov 19 09:11:00 	usbhid-ups 	21319 	Startup successful
Nov 19 09:11:02 	upsmon 	44295 	Startup successful
Nov 19 09:11:03 	upsd 	32630 	listening on 192.168.55.1 port 3493
Nov 19 09:11:03 	upsd 	32630 	listening on 192.168.10.1 port 3493
Nov 19 09:11:03 	upsd 	32630 	listening on ::1 port 3493
Nov 19 09:11:03 	upsd 	32630 	listening on 127.0.0.1 port 3493
Nov 19 09:11:03 	upsd 	32630 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 09:11:03 	upsd 	32999 	Startup successful
Nov 19 09:11:04 	usbhid-ups 	68543 	Startup successful
Nov 19 09:11:05 	upsd 	32999 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 09:11:05 	upsd 	32999 	User local-monitor@::1 logged into UPS [ups]
Nov 19 09:11:08 	upsmon 	46200 	Signal 15: exiting
Nov 19 09:11:08 	upsd 	32999 	User local-monitor@::1 logged out from UPS [ups]
Nov 19 09:11:08 	upsd 	32999 	mainloop: Interrupted system call
Nov 19 09:11:08 	upsd 	32999 	Signal 15: exiting
Nov 19 09:11:08 	usbhid-ups 	68543 	Signal 15: exiting
Nov 19 09:11:08 	upsmon 	72447 	Startup successful
Nov 19 09:11:09 	upsd 	8296 	listening on 192.168.55.1 port 3493
Nov 19 09:11:09 	upsd 	8296 	listening on 192.168.10.1 port 3493
Nov 19 09:11:09 	upsd 	8296 	listening on ::1 port 3493
Nov 19 09:11:09 	upsd 	8296 	listening on 127.0.0.1 port 3493
Nov 19 09:11:09 	upsd 	8296 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 09:11:09 	upsd 	8513 	Startup successful
Nov 19 09:11:10 	usbhid-ups 	8888 	Startup successful
Nov 19 09:11:11 	upsd 	8513 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 09:11:11 	upsd 	8513 	User local-monitor@::1 logged into UPS [ups]
Nov 19 09:11:11 	upsmon 	52115 	Startup successful
Nov 19 09:11:12 	upsmon 	63390 	Startup successful
Nov 19 09:11:12 	upsd 	64189 	listening on 192.168.55.1 port 3493
Nov 19 09:11:12 	upsd 	64189 	listening on 192.168.10.1 port 3493
Nov 19 09:11:12 	upsd 	64189 	listening on ::1 port 3493
Nov 19 09:11:12 	upsd 	64189 	listening on 127.0.0.1 port 3493
Nov 19 09:11:12 	upsd 	64189 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 09:11:12 	upsd 	64531 	Startup successful
Nov 19 09:11:15 	upsmon 	82265 	Startup successful
Nov 19 09:11:16 	upsd 	84626 	listening on 192.168.55.1 port 3493
Nov 19 09:11:16 	upsd 	84626 	listening on 192.168.10.1 port 3493
Nov 19 09:11:16 	upsd 	84626 	listening on ::1 port 3493
Nov 19 09:11:16 	upsd 	84626 	listening on 127.0.0.1 port 3493
Nov 19 09:11:16 	upsd 	84626 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 09:11:16 	upsd 	84968 	Startup successful
Nov 19 09:11:17 	usbhid-ups 	85254 	Startup successful
Nov 19 09:11:18 	upsd 	84968 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 09:11:18 	upsd 	84968 	User local-monitor@::1 logged into UPS [ups]
Nov 19 09:11:18 	upsd 	84968 	User monuser@192.168.10.10 logged into UPS [ups]
Nov 19 09:11:18 	upsmon 	82925 	UPS ups battery is low
Nov 19 09:12:09 	upsmon 	82925 	UPS ups on battery
Nov 19 09:12:09 	upsd 	84968 	Client local-monitor@::1 set FSD on UPS [ups]
Nov 19 09:13:33 	upsmon 	82925 	Executing automatic power-fail shutdown
Nov 19 09:13:33 	upsmon 	82925 	Auto logout and shutdown proceeding
Nov 19 12:00:23 	upsmon 	23307 	Startup successful
Nov 19 12:00:24 	upsd 	34806 	listening on 192.168.55.1 port 3493
Nov 19 12:00:24 	upsd 	34806 	listening on 192.168.10.1 port 3493
Nov 19 12:00:24 	upsd 	34806 	listening on ::1 port 3493
Nov 19 12:00:24 	upsd 	34806 	listening on 127.0.0.1 port 3493
Nov 19 12:00:24 	upsd 	34806 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 12:00:24 	upsd 	35343 	Startup successful
Nov 19 12:00:24 	usbhid-ups 	35640 	Startup successful
Nov 19 12:00:26 	upsmon 	38032 	Startup successful
Nov 19 12:00:27 	upsd 	59041 	listening on 192.168.55.1 port 3493
Nov 19 12:00:27 	upsd 	59041 	listening on 192.168.10.1 port 3493
Nov 19 12:00:27 	upsd 	59041 	listening on ::1 port 3493
Nov 19 12:00:27 	upsd 	59041 	listening on 127.0.0.1 port 3493
Nov 19 12:00:27 	upsd 	59041 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 12:00:27 	upsd 	59323 	Startup successful
Nov 19 12:00:27 	usbhid-ups 	59888 	Startup successful
Nov 19 12:00:29 	upsd 	59323 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 12:00:29 	upsd 	59323 	User local-monitor@::1 logged into UPS [ups]
Nov 19 12:00:29 	upsmon 	38267 	UPS ups battery is low
Nov 19 12:00:31 	upsd 	59323 	User monuser@192.168.10.10 logged into UPS [ups]
Nov 19 12:57:46 	upsmon 	38267 	UPS ups on battery
Nov 19 12:59:02 	upsmon 	38267 	UPS ups on line power
Nov 19 13:00:28 	upsmon 	38267 	UPS ups on battery
Nov 19 13:01:08 	upsmon 	38267 	UPS ups on line power
Nov 19 13:06:32 	upsmon 	38267 	UPS ups on battery
Nov 19 13:06:58 	upsmon 	38267 	UPS ups on line power
Nov 19 13:23:35 	upsmon 	38267 	UPS ups on battery
Nov 19 13:23:40 	upsmon 	38267 	UPS ups on line power
Nov 19 13:26:52 	upsmon 	38267 	UPS ups on battery
Nov 19 13:27:32 	upsmon 	38267 	UPS ups on line power
Nov 19 13:27:37 	upsmon 	38267 	UPS ups on battery
Nov 19 13:28:23 	upsmon 	38267 	UPS ups on line power
Nov 19 13:40:38 	upsmon 	38267 	Signal 15: exiting
Nov 19 13:40:38 	upsd 	59323 	User local-monitor@::1 logged out from UPS [ups]
Nov 19 13:40:38 	upsd 	59323 	mainloop: Interrupted system call
Nov 19 13:40:38 	upsd 	59323 	Signal 15: exiting
Nov 19 13:40:38 	usbhid-ups 	59888 	Signal 15: exiting
Nov 19 13:40:38 	upsmon 	60670 	Startup successful
Nov 19 13:40:39 	upsd 	68564 	listening on 192.168.55.1 port 3493
Nov 19 13:40:39 	upsd 	68564 	listening on 192.168.10.1 port 3493
Nov 19 13:40:39 	upsd 	68564 	listening on ::1 port 3493
Nov 19 13:40:39 	upsd 	68564 	listening on 127.0.0.1 port 3493
Nov 19 13:40:39 	upsd 	68564 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 13:40:39 	upsd 	68618 	Startup successful
Nov 19 13:40:39 	usbhid-ups 	69988 	Startup successful
Nov 19 13:40:41 	upsd 	68618 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 13:40:41 	upsmon 	89394 	Startup successful
Nov 19 13:40:42 	upsd 	41304 	listening on 192.168.55.1 port 3493
Nov 19 13:40:42 	upsd 	41304 	listening on 192.168.10.1 port 3493
Nov 19 13:40:42 	upsd 	41304 	listening on ::1 port 3493
Nov 19 13:40:42 	upsd 	41304 	listening on 127.0.0.1 port 3493
Nov 19 13:40:42 	upsd 	41304 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 13:40:42 	upsd 	42481 	Startup successful
Nov 19 13:40:42 	usbhid-ups 	47998 	Startup successful
Nov 19 13:40:44 	upsd 	42481 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 13:40:44 	upsd 	42481 	User monuser@192.168.10.10 logged into UPS [ups]
Nov 19 13:40:44 	upsd 	42481 	User local-monitor@::1 logged into UPS [ups]
Nov 19 13:40:49 	upsmon 	89966 	Signal 15: exiting
Nov 19 13:40:49 	upsd 	42481 	User local-monitor@::1 logged out from UPS [ups]
Nov 19 13:40:49 	upsd 	42481 	mainloop: Interrupted system call
Nov 19 13:40:49 	upsd 	42481 	Signal 15: exiting
Nov 19 13:40:49 	usbhid-ups 	47998 	Signal 15: exiting
Nov 19 13:40:49 	upsmon 	54508 	Startup successful
Nov 19 13:40:51 	upsd 	56996 	listening on 192.168.55.1 port 3493
Nov 19 13:40:51 	upsd 	56996 	listening on 192.168.10.1 port 3493
Nov 19 13:40:51 	upsd 	56996 	listening on ::1 port 3493
Nov 19 13:40:51 	upsd 	56996 	listening on 127.0.0.1 port 3493
Nov 19 13:40:51 	upsd 	56996 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 13:40:51 	upsd 	57755 	Startup successful
Nov 19 13:40:51 	usbhid-ups 	58048 	Startup successful
Nov 19 13:40:53 	upsmon 	71507 	Startup successful
Nov 19 13:40:54 	upsd 	73436 	listening on 192.168.55.1 port 3493
Nov 19 13:40:54 	upsd 	73436 	listening on 192.168.10.1 port 3493
Nov 19 13:40:54 	upsd 	73436 	listening on ::1 port 3493
Nov 19 13:40:54 	upsd 	73436 	listening on 127.0.0.1 port 3493
Nov 19 13:40:54 	upsd 	73436 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 13:40:54 	upsd 	73569 	Startup successful
Nov 19 13:40:54 	usbhid-ups 	73668 	Startup successful
Nov 19 13:40:56 	upsd 	73569 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 13:40:56 	upsd 	73569 	User local-monitor@::1 logged into UPS [ups]
Nov 19 13:40:59 	upsd 	73569 	User monuser@192.168.10.10 logged into UPS [ups]

                                  When the UPS is on-battery I get notifications that it is on battery from both pfsense and my Synology NAS (upsmon.conf issue was fixed by Synology already), so all good. But when the either charge.low (50) or runtime.low (300) is reached, I'm not seeing the pfsense box and Synology shutdown gracefully.

                                  1. Why am I getting these logs?

                                  upsmon parent process died
                                  Communications with UPS ups lost
                                  Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
                                  Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused

                                  1. In the past, you mentioned that the override.battery.charge.low and override.battery.runtime.low parameters are added in the Extra Arguments to driver section and that's what I've been doing since the very start. But in the NUT documentation, it says there to put it in the Additional configuration for ups.conf section. So which is which and what is the difference?
                                  dennypageD 1 Reply Last reply Reply Quote 0
                                  • dennypageD
                                    dennypage @kevindd992002
                                    last edited by

                                    @kevindd992002 First thing to do for diagnosis is to simplify.

                                    • Disable NUT on the Synology for now.
                                    • Remove anything and everything you have in the advanced section of the NUT configuration on pfSense.
                                    • Do a clean startup with mains power and battery at 100%.
                                    • Look at the "UPS Detail" section in Services -> UPS. What does it say the runtime is?

                                    When you post logs, you need to include any USB messages as well so that any USB connectivity issues can be seen in addition to NUT messages.

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

                                      @dennypage said in NUT package:

                                      @kevindd992002 First thing to do for diagnosis is to simplify.

                                      • Disable NUT on the Synology for now.
                                      • Remove anything and everything you have in the advanced section of the NUT configuration on pfSense.
                                      • Do a clean startup with mains power and battery at 100%.
                                      • Look at the "UPS Detail" section in Services -> UPS. What does it say the runtime is?

                                      When you post logs, you need to include any USB messages as well so that any USB connectivity issues can be seen in addition to NUT messages.

                                      Let's remove the NAS from the equation for now. I may know what caused it not to shutdown. I recently introduced an extension box to the main Synology NAS and when I timed the whole shutdown process, it took around 3 minutes for it to completely shutdown. So I changed the charge.low to 60, runtime.low to 480, and HOSTSYNC to 300 for now. That should do it. If the NAS shuts down before the 300 seconds are up though, will NUT wait for the whole 300 seconds to end before it shuts down itself?

                                      When the batt is at 100%, runtime is 660 (11 minutes).

                                      Here are the last 1000 "ups" logs:

                                      Nov 19 17:09:16 	upsd 	92762 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 17:09:14 	upsd 	92509 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 17:08:39 	upsd 	49563 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 17:08:37 	upsd 	49426 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 14:25:35 	upsd 	89641 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 14:25:33 	upsd 	89456 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 13:40:56 	upsd 	73569 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 13:40:54 	upsd 	73436 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 13:40:51 	upsd 	56996 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 13:40:44 	upsd 	42481 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 13:40:42 	upsd 	41304 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 13:40:41 	upsd 	68618 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 13:40:39 	upsd 	68564 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 12:00:29 	upsd 	59323 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 12:00:27 	upsd 	59041 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 12:00:24 	upsd 	34806 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 11:59:10 	kernel 		uhub2: <vendor 0x0438 product 0x7900, class 9/0, rev 2.00/0.18, addr 2> on usbus1
Nov 19 11:59:10 	kernel 		ugen1.2: <vendor 0x0438 product 0x7900> at usbus1
Nov 19 11:59:10 	kernel 		ugen0.2: <American Power Conversion Smart-UPS 750 FW651.13.I USB FW7.3> at usbus0
Nov 19 11:59:10 	kernel 		uhub1: <AMD EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
Nov 19 11:59:10 	kernel 		uhub0: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Nov 19 11:59:10 	kernel 		ugen1.1: <AMD EHCI root HUB> at usbus1
Nov 19 11:59:10 	kernel 		ugen0.1: <0x1022 XHCI root HUB> at usbus0
Nov 19 11:59:10 	kernel 		usbus1: 480Mbps High Speed USB v2.0
Nov 19 11:59:10 	kernel 		usbus1 on ehci0
Nov 19 11:59:10 	kernel 		usbus1: EHCI version 1.0
Nov 19 11:59:10 	kernel 		ehci0: <AMD FCH USB 2.0 controller> mem 0xf7fa6000-0xf7fa60ff irq 18 at device 19.0 on pci0
Nov 19 11:59:10 	kernel 		usbus0: 5.0Gbps Super Speed USB v3.0
Nov 19 11:59:10 	kernel 		usbus0 on xhci0
Nov 19 11:59:10 	kernel 		xhci0: <AMD FCH USB 3.0 controller> mem 0xf7fa2000-0xf7fa3fff irq 18 at device 16.0 on pci0
Nov 19 09:11:18 	upsd 	84968 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 09:11:16 	upsd 	84626 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 09:11:12 	upsd 	64189 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 09:11:11 	upsd 	8513 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 09:11:09 	upsd 	8296 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 09:11:05 	upsd 	32999 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 09:11:03 	upsd 	32630 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 09:11:00 	upsd 	8779 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 09:10:44 	upsd 	19226 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 09:10:42 	upsd 	17802 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 09:10:41 	upsd 	14108 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 09:10:40 	upsd 	11447 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 09:10:16 	kernel 		uhub2: <vendor 0x0438 product 0x7900, class 9/0, rev 2.00/0.18, addr 2> on usbus1
Nov 19 09:10:16 	kernel 		ugen1.2: <vendor 0x0438 product 0x7900> at usbus1
Nov 19 09:10:16 	kernel 		ugen0.2: <American Power Conversion Smart-UPS 750 FW651.13.I USB FW7.3> at usbus0
Nov 19 09:10:16 	kernel 		uhub1: <AMD EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
Nov 19 09:10:16 	kernel 		uhub0: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Nov 19 09:10:16 	kernel 		ugen1.1: <AMD EHCI root HUB> at usbus1
Nov 19 09:10:16 	kernel 		ugen0.1: <0x1022 XHCI root HUB> at usbus0
Nov 19 09:10:16 	kernel 		usbus1: 480Mbps High Speed USB v2.0
Nov 19 09:10:16 	kernel 		usbus1 on ehci0
Nov 19 09:10:16 	kernel 		usbus1: EHCI version 1.0
Nov 19 09:10:16 	kernel 		ehci0: <AMD FCH USB 2.0 controller> mem 0xf7fa6000-0xf7fa60ff irq 18 at device 19.0 on pci0
Nov 19 09:10:16 	kernel 		usbus0: 5.0Gbps Super Speed USB v3.0
Nov 19 09:10:16 	kernel 		usbus0 on xhci0
Nov 19 09:10:16 	kernel 		xhci0: <AMD FCH USB 3.0 controller> mem 0xf7fa2000-0xf7fa3fff irq 18 at device 16.0 on pci0
Nov 19 08:23:32 	upsd 	97751 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 08:23:30 	upsd 	97587 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 08:23:27 	upsd 	80805 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 08:23:25 	upsd 	74409 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 08:23:22 	upsd 	49642 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 08:23:21 	upsd 	10431 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 08:23:21 	upsd 	9372 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 08:23:18 	upsd 	50913 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 08:23:17 	upsd 	6319 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 08:23:14 	upsd 	26073 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 08:22:56 	upsd 	44338 	Connected to UPS [ups]: usbhid-ups-ups
Nov 19 08:22:54 	upsd 	41880 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 19 08:22:51 	upsd 	90116 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 19 08:22:28 	kernel 		uhub2: <vendor 0x0438 product 0x7900, class 9/0, rev 2.00/0.18, addr 2> on usbus1
Nov 19 08:22:28 	kernel 		ugen1.2: <vendor 0x0438 product 0x7900> at usbus1
Nov 19 08:22:28 	kernel 		ugen0.2: <American Power Conversion Smart-UPS 750 FW651.13.I USB FW7.3> at usbus0
Nov 19 08:22:28 	kernel 		uhub1: <AMD EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
Nov 19 08:22:28 	kernel 		uhub0: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Nov 19 08:22:28 	kernel 		ugen1.1: <AMD EHCI root HUB> at usbus1
Nov 19 08:22:28 	kernel 		ugen0.1: <0x1022 XHCI root HUB> at usbus0
Nov 19 08:22:28 	kernel 		usbus1: 480Mbps High Speed USB v2.0
Nov 19 08:22:28 	kernel 		usbus1 on ehci0
Nov 19 08:22:28 	kernel 		usbus1: EHCI version 1.0
Nov 19 08:22:28 	kernel 		ehci0: <AMD FCH USB 2.0 controller> mem 0xf7fa6000-0xf7fa60ff irq 18 at device 19.0 on pci0
Nov 19 08:22:28 	kernel 		usbus0: 5.0Gbps Super Speed USB v3.0
Nov 19 08:22:28 	kernel 		usbus0 on xhci0
Nov 19 08:22:28 	kernel 		xhci0: <AMD FCH USB 3.0 controller> mem 0xf7fa2000-0xf7fa3fff irq 18 at device 16.0 on pci0
Nov 18 18:48:45 	upsd 	68594 	Connected to UPS [ups]: usbhid-ups-ups
Nov 18 18:48:43 	upsd 	68475 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 18 17:56:24 	upsd 	85326 	Connected to UPS [ups]: usbhid-ups-ups
Nov 18 17:56:22 	upsd 	85178 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 18 17:56:18 	upsd 	68555 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 18 17:56:15 	upsd 	46596 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 18 17:56:12 	upsd 	36536 	Connected to UPS [ups]: usbhid-ups-ups
Nov 18 17:56:10 	upsd 	35747 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 18 17:56:09 	upsd 	41504 	Connected to UPS [ups]: usbhid-ups-ups
Nov 18 17:56:07 	upsd 	40389 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 18 17:55:51 	upsd 	47292 	Connected to UPS [ups]: usbhid-ups-ups
Nov 18 17:55:49 	upsd 	45686 	Can't connect to UPS [ups] (usbhid-ups-ups): Connection refused
Nov 18 17:55:46 	upsd 	68133 	Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
Nov 18 17:55:23 	kernel 		uhub2: <vendor 0x0438 product 0x7900, class 9/0, rev 2.00/0.18, addr 2> on usbus1
Nov 18 17:55:23 	kernel 		ugen1.2: <vendor 0x0438 product 0x7900> at usbus1
Nov 18 17:55:23 	kernel 		ugen0.2: <American Power Conversion Smart-UPS 750 FW651.13.I USB FW7.3> at usbus0
Nov 18 17:55:23 	kernel 		uhub1: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Nov 18 17:55:23 	kernel 		uhub0: <AMD EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
Nov 18 17:55:23 	kernel 		ugen0.1: <0x1022 XHCI root HUB> at usbus0
Nov 18 17:55:23 	kernel 		ugen1.1: <AMD EHCI root HUB> at usbus1
Nov 18 17:55:23 	kernel 		usbus1: 480Mbps High Speed USB v2.0
Nov 18 17:55:23 	kernel 		usbus1 on ehci0
Nov 18 17:55:23 	kernel 		usbus1: EHCI version 1.0
Nov 18 17:55:23 	kernel 		ehci0: <AMD FCH USB 2.0 controller> mem 0xf7fa6000-0xf7fa60ff irq 18 at device 19.0 on pci0
Nov 18 17:55:23 	kernel 		usbus0: 5.0Gbps Super Speed USB v3.0
Nov 18 17:55:23 	kernel 		usbus0 on xhci0
Nov 18 17:55:23 	kernel 		xhci0: <AMD FCH USB 3.0 controller> mem 0xf7fa2000-0xf7fa3fff irq 18 at device 16.0 on pci0
Nov 17 23:35:49 	kernel 		ugen0.2: <American Power Conversion Back-UPS RS 1500G FW878.L4 .I USB FWL4> at usbus0 (disconnected)

                                      FYI, I reversed the display order based on timestamp (latest log is on top now). You can see how I changed from using a Back-UPS RS 1500G to a Smart-UPS 750 in those logs. If it helps, here's the output of usbconfig dump_device_desc:

                                      ugen0.1: <0x1022 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0300
  bDeviceClass = 0x0009  <HUB>
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0003
  bMaxPacketSize0 = 0x0009
  idVendor = 0x0000
  idProduct = 0x0000
  bcdDevice = 0x0100
  iManufacturer = 0x0001  <0x1022>
  iProduct = 0x0002  <XHCI root HUB>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001

ugen1.1: <AMD EHCI root HUB> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x0009  <HUB>
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0001
  bMaxPacketSize0 = 0x0040
  idVendor = 0x0000
  idProduct = 0x0000
  bcdDevice = 0x0100
  iManufacturer = 0x0001  <AMD>
  iProduct = 0x0002  <EHCI root HUB>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001

ugen0.2: <American Power Conversion Smart-UPS 750 FW651.13.I USB FW7.3> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (30mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0110
  bDeviceClass = 0x0000  <Probed by interface class>
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0000
  bMaxPacketSize0 = 0x0008
  idVendor = 0x051d
  idProduct = 0x0002
  bcdDevice = 0x0006
  iManufacturer = 0x0003  <American Power Conversion>
  iProduct = 0x0001  <Smart-UPS 750 FW:651.13.I USB FW:7.3>
  iSerialNumber = 0x0002  <AS0817241894>
  bNumConfigurations = 0x0001

ugen1.2: <vendor 0x0438 product 0x7900> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0200
  bDeviceClass = 0x0009  <HUB>
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0001
  bMaxPacketSize0 = 0x0040
  idVendor = 0x0438
  idProduct = 0x7900
  bcdDevice = 0x0018
  iManufacturer = 0x0000  <no string>
  iProduct = 0x0000  <no string>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001

                                      Also, in case you've missed my other questions above:

                                      In the past, you mentioned that the override.battery.charge.low and override.battery.runtime.low parameters are added in the Extra Arguments to driver section and that's what I've been doing since the very start. But in the NUT documentation, it says there to put it in the Additional configuration for ups.conf section. So which is which and what is the difference?

                                      dennypageD 1 Reply Last reply Reply Quote 0
                                      • dennypageD
                                        dennypage @kevindd992002
                                        last edited by

                                        @kevindd992002 said in NUT package:

                                        In the past, you mentioned that the override.battery.charge.low and override.battery.runtime.low parameters are added in the Extra Arguments to driver section and that's what I've been doing since the very start. But in the NUT documentation, it says there to put it in the Additional configuration for ups.conf section. So which is which and what is the difference?

                                        From the ups.conf man page: “The file begins with global directives, and then each UPS has a section which contains a number of directives that set parameters for that UPS.”

                                        The battery variable overrides are not global directives. They are fields in a ups definition.

                                        K 1 Reply Last reply Reply Quote 0
                                        • K
                                          kevindd992002 @dennypage
                                          last edited by

                                          @dennypage said in NUT package:

                                          @kevindd992002 said in NUT package:

                                          In the past, you mentioned that the override.battery.charge.low and override.battery.runtime.low parameters are added in the Extra Arguments to driver section and that's what I've been doing since the very start. But in the NUT documentation, it says there to put it in the Additional configuration for ups.conf section. So which is which and what is the difference?

                                          From the ups.conf man page: “The file begins with global directives, and then each UPS has a section which contains a number of directives that set parameters for that UPS.”

                                          The battery variable overrides are not global directives. They are fields in a ups definition.

                                          Right. But then those fields in a ups definition are still located in the ups.conf file, right? I'm still confused. In the ups.conf file, the override variable is listed under UPS fields which are under ups.conf.

                                          dennypageD 1 Reply Last reply Reply Quote 0
                                          • dennypageD
                                            dennypage @kevindd992002
                                            last edited by

                                            @kevindd992002 Yes, they are in the same file. ups.conf looks like this:

                                            Global directive 1
                                            Global directive 2
                                            [ups1]
                                            Field 1 = X
                                            Field 2 = X
                                            [ups2]
                                            Field 1 = X
                                            Field 2 = X

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