similar to: Live Recording on the NAS?

So I finally got a test in after I changed my RPi to the master and everything else (including my Synology) to slaves.  Before I did that though, I timed the shutdown of my Synology since it is the slowest slave to shutdown.  It took 40 seconds to shutdown, so I changed HOSTSYNC in upsmon.conf on the master (“Proton”) to 60.  I then did a test ("sudo upsmon -c fsd”). The slaves shutdown, then

Larry, I have not edited a single file, including anything to do with NUT, on the Synology via ssh.... ever. How is yours configured in the UI? Do you have it set to go into safe mode after a certain number minutes? Earlier, I was just copying and pasting the contents of some files to Roger but did not change anything. -- Todd Benivegna // todd at benivegna.com On Aug 14, 2020, 8:16 AM -0400,

On Fri, 14 Aug 2020, Todd Benivegna wrote: > https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave  > > I have the latest version of the Windows port of NUT (A UPS management package) installed on my Windows 7 machine. The UPS I am using is a > very old APC BK650M which is controlled and sends its status via a special serial cable to the Windows

Hello, I am wondering has anyone used Live Recording (monitor or mixmonitor) on to Storage Server via network 1 Gigabit connection? Does it perform well, let say about 50 live recordings at the same time. I am planning to make some system changes at work. I would like to put Asterisk VM on a ESXi host and the datastore will be hosted on Storage Server. On a ESXi host, there will be a few

On Mon, 10 Aug 2020, Todd Benivegna wrote: > synoups: https://hastebin.com/xexafofiha.bash Wow! What a mess. It looks as if Synology wanted to write their own "NUT", but decided it would be easier to put their ideas in a script when they saw they could use upssched.conf to call it. NUT intends such a script for timer management. Synology use it for general system management.

Thanks Larry, no problem. I appreciate the input. Whenever you get a chance I’d really like to compare notes with someone who has NUT and a Synology to see why the heck mine doesn’t work! ;). I’m also using my Pi as the master like you. Thanks. Todd -- Todd Benivegna // todd at benivegna.com On Aug 14, 2020, 11:55 AM -0400, Larry Fahnoe <fahnoe at fahnoetech.com>, wrote: > On Fri, Aug

Hi! I tried these two Dockers on Synology nas: https://github.com/JensErat/docker-tinc/ https://github.com/bys-control/docker-tinc For testing i set up a master Windows machine and a client one with also Windows. Connection between of them Works. So no i try to add a Synology NAS, so i can do remote backup. But i cannot set up any connection between the Docker container and master Windows

Roger, I just ran a manual test, killing power and see what happens.  I set the Synology “Time before DiskStation goes into Safe mode” to 5 minutes so I didn’t have to wait like an hour until it powered down.  Here is the log: https://hastebin.com/ovuwilufeb.sql Everything appeared to be normal; the servers powered off and the Synology went into safe mode.  Power was then cut to the Synology

On Fri, 7 Aug 2020, Todd Benivegna wrote: > APC Back-UPS NS 650M1 UPS ---USB---> Synology NAS (DS416 - Master?) > ---Ethernet---> Netgear Managed Switch w/ uplink to router <---Ethernet--- > Servers (Ubuntu 20.04 - Plex, Pulsar, Proton - All three set as slaves) I'm guessing that the UPS supplies only the NAS, not the 3 Ubuntu machines. Do they have their own UPS's?

How would I capture with Wireshark when it seemingly happens at random?  Whenever I test, everything appears to work normally.  I wish I could somehow replicate it.  Maybe I need to test manually and see if it’ll happen in front of me; I’ve never actually seen it happen… always happens when I’m away. -- Todd Benivegna // todd at benivegna.com On Aug 2, 2020, 12:12 PM -0400, Manuel Wolfshant

> Since it's NUT in the NAS which is deciding to order the shutdown, it would be > useful to see upsmon.conf, upssched.conf and upssched-cmd (or whatever Synology > use if anything) from the NAS to see what criteria they use. upsmon.conf (on Synology): RUN_AS_USER root MONITOR ups at localhost 1 monuser secret master MINSUPPLIES 1 SHUTDOWNCMD "" NOTIFYCMD /usr/sbin/upssched

Manuel, You are absolutely right.  I think this is all the Synology just being very dumb.  I guess those are my only two options at this point. I have no idea on how to set up the NUT server though on one of my NUCs or my Pi.  Do you know any good guides out there?  I’m guessing it’s easy enough to edit upsmon.conf on the Synology in order to get that to become a slave; I think would be all

upsmon.conf on server:  https://pastebin.com/z4CrUTxb nut.conf on server:  https://pastebin.com/540ShZH7 Permissions for /etc/nut:  https://hastebin.com/qecolodapi.diff On the Synology (I didn’t edit any of these files): ups.conf:  https://hastebin.com/dedereqizi.shell upsd.conf:  https://hastebin.com/pupeseweda.css upsd.users:  https://hastebin.com/ocenamecex.cs I don’t think I am able to run

I'm hoping that someone can shed some light on this… I have a Synology NAS (DS416) that has a feature where you can enable a “Network UPS Server” which is a NUT server.  I have been trying to get the Synology to shut down three Ubuntu 20.04 servers that I have. While it does work when I test it out manually, sometimes when I am away and the power goes out briefly, the servers shut down when

On Thu, 6 Aug 2020, Todd Benivegna wrote: > ... I grep’d the syslog and here’s the results: Could you also grep for upsd and upsmon in the NAS log? Is this possible? > proton at proton:~$ sudo grep upsmon /var/log/syslog > Aug  6 19:19:09 proton upsmon[1552]: UPS ups at 192.168.1.70 on battery > Aug  6 19:19:14 proton upsmon[1552]: UPS ups at 192.168.1.70 on line

We have to Samba DCs and a couple of Synology NAS connected/bound to the Samba AD. On regular basis the Synology NAS (I believe Samba 4.4.16) looses its connection to the AD outputting the error message, that the domain cannot be found. In the logs of the NAS I can only find the error message ?synowin: domain_test_join.c:59 net ads test join fail?. In the logs of the DC I notice that from one

Hi everyone, Well, we lost power here again.  I was not at home, but I guess a dump truck smashed into some power poles and took out half the city; actually tripped most of the breakers in the panel.  Anyways, the power was out for just a few seconds and of course my servers shutdown on me after power being out for just a second or two.  Here is my syslog from two different machines.  I included

>I wonder how difficult it would be to rip off their modifications and revert to a.standard, functional nut. I think it should be preatty simple. just rename Synology files and replacewith what you think is the best there... it's just a banch of scripts nothing more...

On 8/12/20 3:42 AM, Manuel Wolfshant wrote: > On 8/12/20 3:20 AM, Todd Benivegna wrote: >> Hi everyone, >> >> Well, we lost power here again.  I was not at home, but I guess a >> dump truck smashed into some power poles and took out half the city; >> actually tripped most of the breakers in the panel.  Anyways, the >> power was out for just a few seconds

On both the synology (samba 4.1.20) and PDC (samba 3.6.25) testparm showed client schannel = Auto server schannel = Auto I don't know if the server even supports schannel. Maybe it doesn't any all the clients successfully negotiated not to use it. On the synology, I set client schannel = no This fixed my domain membership issue. Although