NUT package (2.8.0 and below)

Gertjan

If you are not seeing this in the logs, then the Synology is not successfully connecting.

@dennypage : thanks for your last (above) message.
I knew something was missing.
Could figure out what is was / didn't take the time for it.

Placed this on the NUT settings page :

because the file on my Syno said ( /usr/syno/etc/ups/upsmon.conf ) :

.....
MONITOR ups@192.168.1.1 1 monuser secret slave
....

Know I have :

192.168.1.15 is my Syno.

When I have some time, I'll check what happens when pfSense (the UPS master) is switched to battery.

kevindd992002

@dennypage said in NUT package:

upsd

Ok, that's not good then. When I checked the logs now, I didn't see any upsd entries. I only saw upsmon entries. I then restarted the pfsense UPS monitoring service and got this:


Aug 9 07:52:04 	upsmon 	17459 	UPS ups on battery
Aug 9 08:02:16 	upsmon 	17459 	UPS ups on line power
Aug 9 08:04:01 	upsmon 	17459 	UPS ups on battery
Aug 9 08:05:16 	upsmon 	17459 	UPS ups on line power
Aug 9 11:01:04 	upsmon 	17459 	Signal 15: exiting
Aug 9 11:01:04 	upsd 	19154 	User local-monitor@::1 logged out from UPS [ups]
Aug 9 11:01:04 	upsd 	19154 	mainloop: Interrupted system call
Aug 9 11:01:04 	upsd 	19154 	Signal 15: exiting
Aug 9 11:01:04 	usbhid-ups 	18838 	Signal 15: exiting
Aug 9 11:01:04 	upsmon 	37412 	Startup successful
Aug 9 11:01:05 	usbhid-ups 	38472 	Startup successful
Aug 9 11:01:05 	upsd 	38680 	listening on 192.168.55.1 port 3493
Aug 9 11:01:05 	upsd 	38680 	listening on 192.168.10.1 port 3493
Aug 9 11:01:05 	upsd 	38680 	listening on ::1 port 3493
Aug 9 11:01:05 	upsd 	38680 	listening on 127.0.0.1 port 3493
Aug 9 11:01:05 	upsd 	38680 	Connected to UPS [ups]: usbhid-ups-ups
Aug 9 11:01:05 	upsd 	38722 	Startup successful
Aug 9 11:01:07 	upsd 	38722 	User local-monitor@::1 logged into UPS [ups]

I don't see any logs in the past. Does pfsense do circular logging? I'm thinking past logs were deleted or something but the weird thing is that I still have August 2 logs from other services so that couldn't be it. I'm not really sure.

The most pressing matter though is why does the Synology GUI say that it is connected to the UPS but the pfsense system logs doesn't show that? What could be the issue here? I have a similar setup in two locations but this one has a Synology client and experiencing this issue.

EDIT1:

I did another test. Like I said, I have two locations and I have a site-to-site OpenVPN tunnel between them. I connected the Synology device to the UPS of the remote site and when I checked the pfsense system logs there, I also didn't see the monuser log that we're looking for. So this tells me that there is something wrong with the Synology device? I'm not really sure.

EDIT2:

I already tried reinstalling the NUT package to no avail. Here's what I see in Synology:

It does show the correct UPS statistics there so I know it's connecting.

Gertjan

@kevindd992002 said in NUT package:

Does pfsense do circular logging?

Yep (see manual - the clog stuff)

Did you looked up the user name of your UPS ? I had to access the files (found them using the Syno forums) to see that the user/password were.
I entered those into the UPS settings on pfSense (see above).

kevindd992002

monuser/secret is the default username/password for Synology devices. It's interesting though:

This means that my Synology's upsmon.conf file has nothing in it. @dennypage , do you know why? I also changed the password in the upsd.users settings of the pfsense master NUT service and my Synology slave still connected in the GUI and was able to obtain device information. It's as if that the Synology UPS does not use any authentication to connect to the pfsense slave.

dennypage

@Gertjan and the UPS on the server must be named “ups”

dennypage

@kevindd992002 said in NUT package:

This means that my Synology's upsmon.conf file has nothing in it. @dennypage , do you know why? I also changed the password in the upsd.users settings of the pfsense master NUT service and my Synology slave still connected in the GUI and was able to obtain device information. It's as if that the Synology UPS does not use any authentication to connect to the pfsense slave.

The upsd.users file on pfSense will be overwritten whenever the service re-saves.

On the Syno you’re probably looking in the wrong place for the upsmon.conf file. They moved it a few releases back. Look to see what file gets modded.

kevindd992002

@dennypage said in NUT package:

@kevindd992002 said in NUT package:

This means that my Synology's upsmon.conf file has nothing in it. @dennypage , do you know why? I also changed the password in the upsd.users settings of the pfsense master NUT service and my Synology slave still connected in the GUI and was able to obtain device information. It's as if that the Synology UPS does not use any authentication to connect to the pfsense slave.

The upsd.users file on pfSense will be overwritten whenever the service re-saves.

On the Syno you’re probably looking in the wrong place for the upsmon.conf file. They moved it a few releases back. Look to see what file gets modded.

I meant I changed the password of the monuser user in the pfsense NUT GUI. So technically if I change that to some gibberish random string, the Syno won't be able to connect and get the ups device information, right? Or is that monuser account only used for monitoring alone?

That's weird. All documentation I see in the Internet say that's the correct place for the upsmon.conf in a Syno. And regardless, you won't be able to change the Syno monuser account anyway, right?

kevindd992002

@dennypage , do you still have any other ideas/clues as to why this is happening on my environment?

dennypage

@kevindd992002 said in NUT package:

monuser/secret is the default username/password for Synology devices. It's interesting though:

This means that my Synology's upsmon.conf file has nothing in it. @dennypage , do you know why? I also changed the password in the upsd.users settings of the pfsense master NUT service and my Synology slave still connected in the GUI and was able to obtain device information. It's as if that the Synology UPS does not use any authentication to connect to the pfsense slave.

Some of the previous information has to be incorrect.

An empty upsmon.conf file would not only would this mean that there is no authentication, it would also mean that the Synology was able to magically intuit the IP address of the remote NUT master.

I am running DSM 6.2.2-24922 Update 2.

There are these "ups.conf" and "upsmon.conf" files:

-rwxr-xr-x 1 root root 3935 May 9 15:51 /etc.defaults/ups/ups.conf
-rwxr-xr-x 1 root root 3924 May 10 2015 /etc/ups/ups.conf
-rw-r----- 1 root root 3935 May 9 15:51 /usr/syno/etc.defaults/ups/ups.conf
-rw-r----- 1 root root 3898 Aug 11 15:08 /usr/syno/etc/ups/ups.conf
-rw-r----- 1 root root 12150 May 9 15:51 /usr/syno/etc.defaults/ups/upsmon.conf
-rw-r--r-- 1 root root 12150 Aug 11 15:08 /usr/syno/etc/ups/upsmon.conf

The operational files currently appear in /usr/syno/etc/ups.

With ups monitoring enabled on the Synology, /usr/syno/etc/ups/upsmon.conf cannot not be empty, regardless of the ups being local or remote.

I would suggest you start from the ground up. Ignore pfSense for now. Update, reboot and reconfigure ups monitoring on the Synology. Confirm that it is updating /usr/syno/etc/ups/upsmon.conf as expected.

Gertjan

Also : login using 'root'.

dennypage

@Gertjan said in NUT package:

Also : login using 'root'.

Lol. I thought that might be a Synology issue as well. I did test however, and was able to see the correct content of upsmon.conf using sudu.

kevindd992002

@dennypage said in NUT package:

@kevindd992002 said in NUT package:

monuser/secret is the default username/password for Synology devices. It's interesting though:

This means that my Synology's upsmon.conf file has nothing in it. @dennypage , do you know why? I also changed the password in the upsd.users settings of the pfsense master NUT service and my Synology slave still connected in the GUI and was able to obtain device information. It's as if that the Synology UPS does not use any authentication to connect to the pfsense slave.

Some of the previous information has to be incorrect.

An empty upsmon.conf file would not only would this mean that there is no authentication, it would also mean that the Synology was able to magically intuit the IP address of the remote NUT master.

I am running DSM 6.2.2-24922 Update 2.

There are these "ups.conf" and "upsmon.conf" files:

-rwxr-xr-x 1 root root 3935 May 9 15:51 /etc.defaults/ups/ups.conf
-rwxr-xr-x 1 root root 3924 May 10 2015 /etc/ups/ups.conf
-rw-r----- 1 root root 3935 May 9 15:51 /usr/syno/etc.defaults/ups/ups.conf
-rw-r----- 1 root root 3898 Aug 11 15:08 /usr/syno/etc/ups/ups.conf
-rw-r----- 1 root root 12150 May 9 15:51 /usr/syno/etc.defaults/ups/upsmon.conf
-rw-r--r-- 1 root root 12150 Aug 11 15:08 /usr/syno/etc/ups/upsmon.conf

The operational files currently appear in /usr/syno/etc/ups.

With ups monitoring enabled on the Synology, /usr/syno/etc/ups/upsmon.conf cannot not be empty, regardless of the ups being local or remote.

I would suggest you start from the ground up. Ignore pfSense for now. Update, reboot and reconfigure ups monitoring on the Synology. Confirm that it is updating /usr/syno/etc/ups/upsmon.conf as expected.

I'm on that latest version too. I have auto-update enabled on this Synology box so it's always updated.

I udnerstand that a upsmon.conf is impossible but it is what I see and I don't have a clue as to why.

@Gertjan , running sudo is the same as running the command as root. Anyway, I went in as root (sudo -i) and see the same thing.

/usr/syno/etc.defaults/ups/upsmon.conf does have the contents that we expect but like mentioned this is not the operational file.

@dennypage , I already did try disabling and re-enabling ups monitoring on Synology to no avail. Is it a time for a Synology support ticket now?

dennypage

@kevindd992002 said in NUT package:

@dennypage , I already did try disabling and re-enabling ups monitoring on Synology to no avail. Is it a time for a Synology support ticket now?

Just for completeness, what does the command

ls -lc /usr/syno/etc/ups

show?

kevindd992002

@dennypage said in NUT package:

ls -lc /usr/syno/etc/ups

root@Synology:~# ls -lc /usr/syno/etc/ups
total 24
-rw-r----- 1 root root 5515 May 15 03:20 nutscan-usb.h
-rw-r----- 1 root root 3935 Aug  9 17:42 ups.conf
-rw-r----- 1 root root   15 May 15 03:20 upsd.conf
-rw-r----- 1 root root 2016 Aug  9 17:44 upsd.users
-rw-r--r-- 1 root root    0 Aug  9 17:42 upsmon.conf
-rw-r----- 1 root root 4020 Aug  9 17:42 upssched.conf

upsmon.conf has read rights for root, root (group), and others so I should be able to read the contents.

Gertjan

@kevindd992002 said in NUT package:

upsmon.conf has read rights for root, root (group), and others so I should be able to read the contents.

Your upsmon.conf is a zero bytes file.

Here mine for comparison :

root@DiskStation:~# ls -lc /usr/syno/etc/ups
total 36
-rw-r----- 1 root root  5515 May 15 06:19 nutscan-usb.h
-rw-r----- 1 root root  3935 Aug  7 17:12 ups.conf
-rw-r----- 1 root root    15 May 15 06:19 upsd.conf
-rw-r----- 1 root root  2016 May 15 06:19 upsd.users
-rw-r--r-- 1 root root 12151 Aug  7 17:12 upsmon.conf
-rw-r----- 1 root root  4051 Aug  7 17:12 upssched.conf

It seems that only your upsmon.conf file is created correctly.
Mine has 12151 bytes, yours none.

edit : something in your (Syno GUI) settings makes the system complain, and it fails to create the config file ?

kevindd992002

@Gertjan said in NUT package:

@kevindd992002 said in NUT package:

upsmon.conf has read rights for root, root (group), and others so I should be able to read the contents.

Your upsmon.conf is a zero bytes file.

Here mine for comparison :
root@DiskStation:~# ls -lc /usr/syno/etc/ups
total 36
-rw-r----- 1 root root  5515 May 15 06:19 nutscan-usb.h
-rw-r----- 1 root root  3935 Aug  7 17:12 ups.conf
-rw-r----- 1 root root    15 May 15 06:19 upsd.conf
-rw-r----- 1 root root  2016 May 15 06:19 upsd.users
-rw-r--r-- 1 root root 12151 Aug  7 17:12 upsmon.conf
-rw-r----- 1 root root  4051 Aug  7 17:12 upssched.conf
It seems that only your upsmon.conf file is created correctly.
Mine has 12151 bytes, yours none.

edit : something in your (Syno GUI) settings makes the system complain, and it fails to create the config file ?

Right, I notice that. You mean my upsmon.conf is NOT created correctly.

Nothing complains in the Syno GUI but it doesn't follow any of the UPS master's (in pfsense) commands and there is no log in pfsense where the UPS is connecting to it using the monuser account.

Gertjan

@kevindd992002 said in NUT package:

is NOT created correctly

Yep, that right - sorry for the typo.

I taled the main messages 'syslog' - it does show up some UPS related messages.

Here I activate the UPs with the 192.168.1.1 == my pfSense.

2019-08-20T17:26:39+02:00 DiskStation synoscgi_SYNO.Core.ExternalDevice.UPS_1_set[8663]: webapi-UPS.cpp:238 Set Service from Disable to Enable
2019-08-20T17:26:41+02:00 DiskStation upsmon[8721]: Startup successful
2019-08-20T17:26:41+02:00 DiskStation upsmon[8723]: UPS [ups@192.168.1.1] connected

I used the command

tail -f /var/log/messages

Use also

grep 'ups' /var/log/messages

kevindd992002

@Gertjan said in NUT package:

grep 'ups' /var/log/messages

Thanks for the tip. Look at my /var/log/messages: https://pastebin.com/pGHXFzgp

It looks like the last time my UPS connection worked properly was on 6/4/2019 which was a long time ago! I don't know what happened but I see a lot of these now:

2019-06-04T17:58:02+08:00 Synology synoservice: synoservice.c:1559 pause gcpd du e to require service cupsd runkey is stop

You have any clue as to what's that?

Gertjan

Your Syno clock is ok ?
Or all messages from last month are missing ? Or did you only took a part of the log ?

A fact is : it all changed here for you :

2019-06-04T14:38:33+08:00 Synology synoups: [UPS] Check Boot Status.
2019-06-04T14:38:33+08:00 Synology synoups: [UPS] Server is going to Safe Mode. It will stop all services and umount all volumes.

I know you won't like the next advise : re-install de DSM ...... ;)

dennypage

@Gertjan said in NUT package:

A fact is : it all changed here for you :

2019-06-04T14:38:33+08:00 Synology synoups: [UPS] Check Boot Status.
2019-06-04T14:38:33+08:00 Synology synoups: [UPS] Server is going to Safe Mode. It will stop all services and umount all volumes.

This entry in the log indicates that the Synology is waiting to have the power removed and restored.

It's unlikely that the Synology has been sitting in safe mode (non functional) for 75 days. But if it hasn't been rebooted since then, I would certainly reboot it.