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

    UPS shutdown

    pfSense Packages
    12
    67
    29.9k
    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.
    • R
      rsw686
      last edited by

      @trendchiller:

      How can I check, why the service won't start ?
      any idea ?

      Configure nut via the webgui. Then go to the console and run

      /usr/local/libexec/nut/upsdrvctl start

      You should see something like

      Detected SMART-UPS 700 [serialnum] on /dev/ttyd0

      Otherwise it will give you an error message. The config files are stored in /usr/local/etc/nut/ If you get it working let me know what you changed to make it work.

      After you get that far then you run the following commands. Be sure to replace myups with the name you gave your ups in the nut config.

      /usr/local/sbin/upsd
      /usr/local/sbin/upsmon myups@localhost

      Both the above commands should tell you they were successfully executed.

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

        so… the error was some "spaces" in the UPS name...

        just use [a-z],[A-Z],[0-9]

        sometime later there will be some update by @rsw686

        ;D now it works !!!  ;D

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

          @trendchiller:

          so… the error was some "spaces" in the UPS name...

          just use [a-z],[A-Z],[0-9]

          sometime later there will be some update by @rsw686

          ;D now it works !!!  ;D

          I put the necessary checks in place so this shouldn't happen to anybody else. :) I also improved the status page. To get the latest reinstall the package via the webgui.

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

            jepp… looks nice now :-)
            alpha status should be changed to beta soon, I think ;-)

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

              Has anyone else tried to get NUT going on a Nokia IP330?  I have the package installed but it will not recognize any cable I throw at it.  I have an APC Back-UPS Pro 650, which connects fine to my pc via the 2 different cables I have.

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

                @Sifter:

                Has anyone else tried to get NUT going on a Nokia IP330?  I have the package installed but it will not recognize any cable I throw at it.  I have an APC Back-UPS Pro 650, which connects fine to my pc via the 2 different cables I have.

                How many serial ports on your IP330. The bottom one is always the console port. If that is all you have you will have to add a second serial port above it. All IP330s have the hole in the metal, just the sticker on the front is different. Find or buy one of the below serial port adapters. On the board there is a jumper to move from the modem to the serial port. Then you just plug the ribbon cable in and screw it in the front of the IP330.

                Here is a pic from a website I found showing the jumper. I did this mod on mine as it originally had the modem exposed. I have not tested out NUT on it, but will try it in the next day or so and let you know.

                http://criggie.dyndns.org/tech/ip330/images/jumper1.jpg

                My IP330 is shown below. The pic is before I rearranged the rack. I painted it black as the sticker on the front was peeling off and it matches everything else I have. As you can see the modem is on the far right.

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

                  thanks for your response, I didnt even notice the cutout was already there, but will def. try this.

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

                    @Sifter:

                    thanks for your response, I didnt even notice the cutout was already there, but will def. try this.

                    Hmm I just hooked up a ups to my ip330 on com2, and I couldn't get it to work. I have an embedded install on there so that might be part of the issue. When I try and start the driver control I get the error

                    Can't uu_lock ttyd1: creat error: No such file or directory

                    I'll have to look into this some more and see if I can get it to work. The IP330 is my main box and I don't really plan on switching to the full install to test this. Let me know if you find out anything different.

                    EDIT:

                    I'm making progress, I had to mkdir /var/spool/lock and set the permissions as this was missing on the embedded installs. There might be something missing from the embedded install to get this to work. I would be interested in seeing how it works out for you since you have a full install.

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

                      I noticed that the NUT service will NOT start after a firmware upgrade…

                      after hitting "change" button in NUT settings it runs again...

                      perhaps that should be fixed...  ;)

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

                        @trendchiller:

                        I noticed that the NUT service will NOT start after a firmware upgrade…

                        after hitting "change" button in NUT settings it runs again...

                        perhaps that should be fixed...  ;)

                        I don't have the slightest clue why that is happening. Any errors in the logs? Do any packages start? Feel free to submit a fix.

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

                          As far as getting my APC UPS to work with the ip330 I have only gotten it to work in simple signaling mode, meaning I'm using APC Back-UPS as the UPS type. Either my serial ribbon cable going to the board is bad or the IP330 has some issue with serial communication.

                          1 Reply Last reply Reply Quote 0
                          • P
                            patord
                            last edited by

                            @rsw686:

                            Hmm I just hooked up a ups to my ip330 on com2, and I couldn't get it to work. I have an embedded install on there so that might be part of the issue. When I try and start the driver control I get the error

                            Can't uu_lock ttyd1: creat error: No such file or directory

                            I installed the NUT package on a fresh hard drive based SNAPSHOT-02-14-2007 and get a similar error (for ttyd0) on a box that worked fine under win32 (com1) for an APC BackUPS Pro with the 95B cable in full signal mode.  I tried all the various permutations from the webgui with no go. Went to the shell and hand ran the various nut binaries to see what I could figure out.  At first I thought it had to do with settings in /etc/ttys for the various ttydX, especially ttyd0 due to the console definitions.  But after eliminating that and a few other things, I'm still at a loss.

                            I'll try hand editing the ups.conf and try setting it to simple signaling like you did to see what happens.

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

                              @patord:

                              @rsw686:

                              Hmm I just hooked up a ups to my ip330 on com2, and I couldn't get it to work. I have an embedded install on there so that might be part of the issue. When I try and start the driver control I get the error

                              Can't uu_lock ttyd1: creat error: No such file or directory

                              I installed the NUT package on a fresh hard drive based SNAPSHOT-02-14-2007 and get a similar error (for ttyd0) on a box that worked fine under win32 (com1) for an APC BackUPS Pro with the 95B cable in full signal mode.  I tried all the various permutations from the webgui with no go. Went to the shell and hand ran the various nut binaries to see what I could figure out.  At first I thought it had to do with settings in /etc/ttys for the various ttydX, especially ttyd0 due to the console definitions.  But after eliminating that and a few other things, I'm still at a loss.

                              I'll try hand editing the ups.conf and try setting it to simple signaling like you did to see what happens.

                              Does the /var/spool/lock directory exist? If you create that directory and run chown uucp:dialer /var/spool/lock does it work? If so I will put a check to make sure that directory exists and if not create it. All the full installs I've seen have already had it, but something might have changed.

                              From your post you have the console running on ttyd0. The only thing I can think of is that there is some conflict when the console is being directed to a serial port and using other serial ports.

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

                                Does this package work with a USB type interface…..I can't seem to get it to work. I have a APC Back-UPS 1500 XS/RS.

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

                                  I commited a fix that will ensure that /var/spool/lock is present and create the directory if it is not. Please reinstall the package and try again. If it still does not work run

                                  /usr/local/libexec/nut/upsdrvctl start

                                  from the console and let me know the error message. Also do you have the console redirected to the serial port or no?

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

                                    @ColdFusion:

                                    Does this package work with a USB type interface…..I can't seem to get it to work. I have a APC Back-UPS 1500 XS/RS.

                                    Supposedly it does, but I have no USB UPS's to test with. On the settings page select APC Back-UPS LS USB. Configure the port as auto. If you still can't get it to work run

                                    /usr/local/libexec/nut/upsdrvctl start

                                    from the console and let me know the error message.

                                    The LS and RS use the same driver. I will add the RS to the drop down list.

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

                                      I get this in my logs…......Feb 19 12:10:27 last message repeated 7 times
                                      Feb 19 12:10:27 last message repeated 7 times
                                      Feb 19 12:09:52 upsmon[20333]: Poll UPS [apc1500@localhost] failed - Driver not connected
                                      Feb 19 12:09:52 upsmon[20333]: Poll UPS [apc1500@localhost] failed - Driver not connected
                                      Feb 19 12:09:47 upsmon[20333]: UPS apc1500@localhost is unavailable
                                      Feb 19 12:09:47 upsmon[20333]: Poll UPS [apc1500@localhost] failed - Driver not connected
                                      Feb 19 12:09:47 upsmon[20333]: UPS apc1500@localhost is unavailable
                                      Feb 19 12:09:47 upsmon[20333]: Poll UPS [apc1500@localhost] failed - Driver not connected
                                      Feb 19 12:09:42 upsmon[20333]: Poll UPS [apc1500@localhost] failed - Driver not connected
                                      Feb 19 12:09:42 upsmon[20333]: Poll UPS [apc1500@localhost] failed - Driver not connected
                                      Feb 19 12:09:41 upsd[20329]: Can't connect to UPS [apc1500] (apc1500): Permission denied
                                      Feb 19 12:09:37 last message repeated 6 times
                                      Feb 19 12:09:41 upsd[20329]: Can't connect to UPS [apc1500] (apc1500): Permission denied
                                      Feb 19 12:09:37 last message repeated 5 times
                                      Feb 19 12:09:12 last message repeated 24 times
                                      Feb 19 12:09:07 upsmon[20333]: Poll UPS [apc1500@localhost] failed - Driver not connected

                                      And this is what this says….....$ /usr/local/libexec/nut/upsdrvctl start
                                      Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5)

                                      Network UPS Tools - UPS driver controller 2.0.5

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

                                        I might be able to get access to a USB UPS to test here this week. In the meantime I added some checks and echo statements to the rc file.

                                        If you could reinstall the package, verify the settings and click change on the nut settings page. Then execute this script on the console and copy/paste the results here. This will identify exactly where the problem occurs and I can check the permissions since USB permissions are different the serial port permissions.

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

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

                                          $ /usr/local/etc/rc.d/nut.sh start
                                          stopping upsmon
                                          stopping upsd
                                          stopping newhidups
                                          Network UPS Tools - UPS driver controller 2.0.5
                                          forcing newhidups termination
                                          starting newhidups
                                          Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5)

                                          Network UPS Tools - UPS driver controller 2.0.5
                                          starting upsd
                                          starting upsmon

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

                                            Here's my log info also…..........
                                            Feb 19 15:21:51 last message repeated 25 times
                                            Feb 19 15:21:21 last message repeated 24 times
                                            Feb 19 15:19:46 last message repeated 7 times
                                            Feb 19 15:19:21 last message repeated 7 times
                                            Feb 19 15:19:11 upsmon[6811]: Poll UPS [APC1500@localhost] failed - Driver not connected
                                            Feb 19 15:19:09 upsd[6808]: Client on 127.0.0.1 logged out
                                            Feb 19 15:19:09 upsd[6808]: Connection from 127.0.0.1
                                            Feb 19 15:19:06 last message repeated 4 times
                                            Feb 19 15:18:46 upsmon[6811]: Poll UPS [APC1500@localhost] failed - Driver not connected
                                            Feb 19 15:18:46 upsmon[6811]: Poll UPS [APC1500@localhost] failed - Driver not connected
                                            Feb 19 15:18:41 upsmon[6811]: UPS APC1500@localhost is unavailable
                                            Feb 19 15:18:41 upsmon[6811]: UPS APC1500@localhost is unavailable
                                            Feb 19 15:18:41 upsmon[6811]: Poll UPS [APC1500@localhost] failed - Driver not connected
                                            Feb 19 15:18:41 upsmon[6811]: Poll UPS [APC1500@localhost] failed - Driver not connected
                                            Feb 19 15:18:36 upsmon[6811]: Communications with UPS APC1500@localhost lost
                                            Feb 19 15:18:36 upsmon[6811]: Communications with UPS APC1500@localhost lost
                                            Feb 19 15:18:36 upsmon[6811]: Poll UPS [APC1500@localhost] failed - Driver not connected
                                            Feb 19 15:18:36 upsmon[6811]: Poll UPS [APC1500@localhost] failed - Driver not connected
                                            Feb 19 15:18:36 upsd[6808]: Client monuser@127.0.0.1 logged into UPS [APC1500]
                                            Feb 19 15:18:36 upsd[6808]: Connection from 127.0.0.1
                                            Feb 19 15:18:36 upsd[6808]: Startup successful
                                            Feb 19 15:18:36 upsmon[6810]: Startup successful
                                            Feb 19 15:18:36 upsd[6807]: Can't connect to UPS [APC1500] (APC1500): Permission denied
                                            Feb 19 15:18:36 upsd[6807]: Can't connect to UPS [APC1500] (APC1500): Permission denied
                                            Feb 19 15:18:33 last message repeated 2 times
                                            Feb 19 15:18:36 newhidups[6806]: Startup successful
                                            Feb 19 15:18:35 newhidups[6569]: Signal 15: exiting
                                            Feb 19 15:18:34 upsd[6571]: Signal 15: exiting
                                            Feb 19 15:18:34 upsd[6571]: Client monuser@127.0.0.1 logged out
                                            Feb 19 15:18:34 upsmon[6575]: Signal 15: exiting
                                            Feb 19 15:18:33 last message repeated 2 times
                                            Feb 19 15:18:23 last message repeated 6 times
                                            Feb 19 15:18:23 last message repeated 6 times
                                            Feb 19 15:17:53 upsmon[6575]: Poll UPS [APC1500@localhost] failed - Driver not connected
                                            Feb 19 15:17:53 upsmon[6575]: Poll UPS [APC1500@localhost] failed - Driver not connected
                                            Feb 19 15:17:48 upsmon[6575]: UPS APC1500@localhost is unavailable
                                            Feb 19 15:17:48 upsmon[6575]: UPS APC1500@localhost is unavailable
                                            Feb 19 15:17:48 upsmon[6575]: Poll UPS [APC1500@localhost] failed - Driver not connected
                                            Feb 19 15:17:48 upsmon[6575]: Poll UPS [APC1500@localhost] failed - Driver not connected
                                            Feb 19 15:17:43 upsd[6571]: Client on 127.0.0.1 logged out
                                            Feb 19 15:17:43 upsd[6571]: Connection from 127.0.0.1

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