NUT package



  • 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 ...... ;)



  • @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.



  • @dennypage
    The DSM was rebooted a lot of times since then. It certainly is not in safe mode because it is being used everyday.

    @Gertjan
    I posted a snippet of the result of the grep but did not skip in between lines, the clock is fine. Reinstalling DSM is my last resort, yes, but I have an open case with Snyology. Let me know if you have more ideas though.



  • @kevindd992002 said in NUT package:

    more ideas

    Yep, a nasty one.
    I'll post tomorrow the file upsmon.conf your missing, the one refuses to generate.
    You should edit it with your own settings - put in place - make it read only .... and start / restart the 'ups' demon.

    Here it is : https://pastebin.com/L1mqCb1Y

    Without the comments, these are the settings :

    RUN_AS_USER root
    
    MONITOR ups@192.168.1.1 1 monuser secret slave
    
    MINSUPPLIES 1
    
    SHUTDOWNCMD ""
    
    NOTIFYCMD /usr/sbin/upssched
    
    POLLFREQ 5
    
    POLLFREQALERT 5
    
    HOSTSYNC 15
    
    DEADTIME 90
    
    POWERDOWNFLAG /etc/killpower
    
    NOTIFYFLAG ONLINE EXEC
    NOTIFYFLAG ONBATT EXEC
    NOTIFYFLAG LOWBATT EXEC
    NOTIFYFLAG NOCOMM EXEC
    NOTIFYFLAG COMMBAD IGNORE
    NOTIFYFLAG COMMOK IGNORE
    NOTIFYFLAG SHUTDOWN IGNORE
    NOTIFYFLAG FSD EXEC
    NOTIFYFLAG NOPARENT SYSLOG
    
    RBWARNTIME 43200
    
    NOCOMMWARNTIME 300
    
    FINALDELAY 5
    

    My settings :

    51a65a27-05bc-469a-807f-25f1568a3587-image.png



  • @Gertjan

    Will Synology write the defaults in the file after restarting the ups daemon? I do have the correct upsmon.conf in etc.defaults/ so I can also use that (if it's the same as yours).



  • @kevindd992002 Given that the Synology isn’t writing the upsmon.conf file correctly, I wouldn’t count on it starting the upsmon service correctly either.



  • @Gertjan said in NUT package:

    grep 'ups' /var/log/messages

    Right. I'm at a loss here. I'm checking the syslog and messages log again and I do see the last successful connection of the Syno to my UPS NUT master was last 6/4/2019. Here's a more detailed view of the messages log file: https://pastebin.com/bXk7YEWf



  • @kevindd992002 Does "ps -elf" on the Synology show any ups processes running?



  • @dennypage said in NUT package:

    @kevindd992002 Does "ps -elf" on the Synology show any ups processes running?

    Looks like that's a no: https://pastebin.com/dKDHdg2w



  • @kevindd992002 Just for grins...

    Last ditch effort if I owned that Synology...

    Disable UPS support on the Synology, reboot the Synology, and then re-enable UPS support on the Synology.

    Btw out of curiosity, what model of Synology is it?



  • @dennypage said in NUT package:

    @kevindd992002 Just for grins...

    Last ditch effort if I owned that Synology...

    Disable UPS support on the Synology, reboot the Synology, and then re-enable UPS support on the Synology.

    Btw out of curiosity, what model of Synology is it?

    Ok, I just did that and checked upsmon.conf and /var/log/messages, same exact results :(

    I'm using a DS1817+, so it's a pretty recent model.



  • @kevindd992002 said in NUT package:

    Will Synology write the defaults in the file after restarting the ups daemon?

    I do not have the command for you how to start upsmon manually, but you'll find it on Google ^^ Like https://diktiosolutions.eu/en/synology/synology-ups-nut-en/
    This will not generate the config file : as pfSense, when you start (or activate) it using the GUI all the config files are build,
    I was curious : if only the config file building faulted, the process never gets started - but if that file is ok, and you start manually, then that's something that indicated that the GUI is at fault.

    @kevindd992002 said in NUT package:

    I do have the correct upsmon.conf in etc.defaults/ so I can also use that (if it's the same as yours).

    It should / could be somewhat different : like another master IP etc.
    Strange.
    I have nothing in this directory

    root@DiskStation:/etc/defaults# ll
    total 12
    drwxr-xr-x  2 root root 4096 Jul 10  2013 .
    drwxr-xr-x 51 root root 4096 Aug 20 20:47 ..
    -rw-r--r--  1 root root  459 Mar  4  2013 rc.conf
    


  • @Gertjan said in NUT package:

    @kevindd992002 said in NUT package:

    Will Synology write the defaults in the file after restarting the ups daemon?

    I do not have the command for you how to start upsmon manually, but you'll find it on Google ^^ Like https://diktiosolutions.eu/en/synology/synology-ups-nut-en/
    This will not generate the config file : as pfSense, when you start (or activate) it using the GUI all the config files are build,
    I was curious : if only the config file building faulted, the process never gets started - but if that file is ok, and you start manually, then that's something that indicated that the GUI is at fault.

    @kevindd992002 said in NUT package:

    I do have the correct upsmon.conf in etc.defaults/ so I can also use that (if it's the same as yours).

    It should / could be somewhat different : like another master IP etc.
    Strange.
    I have nothing in this directory

    root@DiskStation:/etc/defaults# ll
    total 12
    drwxr-xr-x  2 root root 4096 Jul 10  2013 .
    drwxr-xr-x 51 root root 4096 Aug 20 20:47 ..
    -rw-r--r--  1 root root  459 Mar  4  2013 rc.conf
    

    Yeah, that makes sense. I think the GUI is at fault here. It's just weird that when I change the UPS IP to an IP that I know is not used, the GUI also errors out, making it like it's connecting properly to the UPS.

    It's /usr/syno/etc.defaults/ups



  • @dennypage

    On another note, how do I "reset" the battery install date on my UPS for every time I install a new battery? Similar to how PowerChute does it?



  • @kevindd992002 said in NUT package:

    @dennypage

    On another note, how do I "reset" the battery install date on my UPS for every time I install a new battery? Similar to how PowerChute does it?

    Good question.
    I used Pan B : I'll hook them up to a PC with run PowerShute, and use that tool to reset the counter.
    (otherwise I have to reverse engineer a binary Windows app to see what communication goes over the USB wire .... or read the complete NUTS manual ....)



  • @Gertjan said in NUT package:

    @kevindd992002 said in NUT package:

    @dennypage

    On another note, how do I "reset" the battery install date on my UPS for every time I install a new battery? Similar to how PowerChute does it?

    Good question.
    I used Pan B : I'll hook them up to a PC with run PowerShute, and use that tool to reset the counter.
    (otherwise I have to reverse engineer a binary Windows app to see what communication goes over the USB wire .... or read the complete NUTS manual ....)

    Yeah, I mean I can always do that but I just want to know if there's a NUT command that can do the same action.

    As for my UPS issue, here's a some kind of useless reply from Synology (as I half expected):

    Dear Customer,

    Thank you for contacting Synology support.

    As the design, the configuration will be rewrite after you set up in DSM.

    And we checked the system seems like we can get contact to UPS properly.

    root@Synology:~# upsmon -D
    Network UPS Tools upsmon DSM6-2-2-24922-nano-1-C5-190604
    kill: No such process
    0.000000 UPS: ups@192.168.10.1 (slave) (power value 1)
    0.000344 Using power down flag file /etc/killpower
    0.000924 debug level is '1'
    0.006931 Trying to connect to UPS [ups@192.168.10.1]
    0.009822 Logged into UPS ups@192.168.10.1
    0.010296 UPS [ups@192.168.10.1] connected
    Executing command: online
    ^C 50.141267 Signal 2: exiting

    Would you like to tell us other finding, since the login log may need to refer to your configuration of NUT master.

    Looking forward to your messages.



  • Oh wait! They're not useless after all. It looks like they did something and now my upsmon.conf file is populated with the expected contents! And I can see the monuser account logged in in my pfsense ups logs :) I'll ask what they did, because they had remote access to my Syno. I see this in my /var/log/messages now:

    2019-08-26T10:17:51+08:00 Synology upsmon[25917]: Startup successful
    2019-08-26T10:17:51+08:00 Synology upsmon[25919]: UPS [ups@192.168.10.1] connected
    2019-08-26T10:55:26+08:00 Synology upsmon[25919]: Poll UPS [ups@192.168.10.1] failed - Server disconnected
    2019-08-26T10:55:55+08:00 Synology SystemInfo.cgi: ups_info_get.c:97 Can't get UPS status[0]
    2019-08-26T10:59:04+08:00 Synology upsmon[25919]: UPS [ups@192.168.10.1] connected
    2019-08-26T13:59:23+08:00 Synology upsmon[5713]: Startup successful
    2019-08-26T13:59:23+08:00 Synology upsmon[5715]: UPS [ups@192.168.10.1] connected
    
    


  • @kevindd992002 said in NUT package:

    @dennypage
    On another note, how do I "reset" the battery install date on my UPS for every time I install a new battery? Similar to how PowerChute does it?

    You can run upsrw and see what variables are exposed by the UPS. I believe the variable you are looking for is "battery.date". If it's there, you can update it via the "-s" option.



  • @kevindd992002 said in NUT package:

    Oh wait! They're not useless after all. It looks like they did something and now my upsmon.conf file is populated with the expected contents! And I can see the monuser account logged in in my pfsense ups logs :) I'll ask what they did, because they had remote access to my Syno.

    I'm also very interested to know what they changed.



  • @dennypage said in NUT package:

    @kevindd992002 said in NUT package:

    Oh wait! They're not useless after all. It looks like they did something and now my upsmon.conf file is populated with the expected contents! And I can see the monuser account logged in in my pfsense ups logs :) I'll ask what they did, because they had remote access to my Syno.

    I'm also very interested to know what they changed.

    Their reply, lol:

    Dear Customer,

    Thank you for contacting Synology support.

    Like the mail last time, we can't find the root cause from the log.

    We are still tracing this case, if you have more clues it will be helpful to let us know.

    The design of this configuration will be modify once you connect to other device.

    And we just copy it from the etc.default. Please check if there are any problem or not.

    Also just recommendation, if the upsmon.conf lose its content again please tell us, and let us check.

    Please don't copy it from etc.default by yourself because there might be some symptom to let us know the root cause.

    Thank you for your patience, and sorry for any inconvenience caused.


Log in to reply