SOLVED Ups Service does not start

[shant]

Hello everyone, we've been recently getting a lot of power cuts lately, my current ups has too much load on it so its not keeping up, i decided to get a new ups for my server (Eatons 3S) and use the auto shut down feature in case im not at home , but i wanted to try the ups service before i buy one, i realized that i couldn't make the service start, i did a bit of googling and found out that i have to chmod 777 /dev/ugenx.x (1.3 in my case), however it had no effect, i get the following error when i try to start the service

Sep 29 12:41:21 freenas notifier: Starting nut_upslog.
Sep 29 12:41:21 freenas notifier: Warning: initial connect failed: Connection failure: Connection refused
Sep 29 12:41:22 freenas notifier: Stopping nut_upslog.
Sep 29 12:41:22 freenas notifier: Waiting for PIDS: 13610.
Sep 29 12:41:22 freenas notifier: Stopping nut_upsmon.
Sep 29 12:41:46 freenas upsmon[13591]: upsmon parent: read
Sep 29 12:41:46 freenas notifier: Waiting for PIDS: 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592, 13592.
Sep 29 12:41:46 freenas notifier: nut not running? (check /var/db/nut/upsd.pid).

and this is what shell tells me when i run "upsc upshh@localhost"

# upsc upshh@localhost
Error: Connection failure: Connection refused

thanks!

 

[DrKK]

You should not have to chmod anything. I don't know where you got that from.

Almost certainly, the problem is that you either have the wrong port specified in the service->UPS->settings screen, or, the wrong driver type.

 

[shant]

Hello, thank you for your reply.
i was reading in this thread about the chmod thing, shouldn't have the ups service started regardless of what port or driver i set it to?
anyway, today i went on and purchased the Eaton 3S and tested it, it turned out just like you said, i have to choose correct driver for it to start and it worked, thank you.

 

[DrKK]

No.

The UPS service will only successfully start if the port, and the driver, selected are correct.