similar to: Debian 10 nut 2.7.4-8 and APC Back UPS 600i on 940-0020B

I was check out that is the connection between driver-monitor-server-client is working or not. I was put my server directly on power cable, keep control cable connection and use command: $ watch upsc APC600 I was switch to battery, after 2-3 second it show that is on battery OB and after it shutdown because of low battery LO. I think that systemd scripts some what unsynchronized, but after it

On 28.08.19 12:54, tovis r-visor wrote: >I'm using nut for many years on my home "server" without problems running >on Debian 6.x nut version 2.4.3 >Now I have decided to move to Debian 10. I have started from zero and >install new system on a different disk. I have successfully installed new >nut version 2.7.4 >Aug 27 16:52:53 nusi upsd[506]: fopen

> On Sun, 8 Sep 2019, tovis r-visor wrote: > >> After long struggling, check every parts of UPS and cable, I have realized >> that is after boot I reload the driver the system work well: >> # systemctl restart nut-driver.service >> I was checked up to real "battery low" and shutdown, switch off the UPS every thing goes well. >> I was activated

> On Wed, 28 Aug 2019, tovis r-visor wrote: >> I was switch to battery, after 2-3 second it show that is on battery OB and after it shutdown because of low battery LO. > I wondered how old is your battery ? > Roger > I have change it 2019.03.08. 12V/10Ah YUASA. > I was checked not only battery voltage (13.6V without load), but charging > voltage and output voltage using

Hello, could nut clients have its settings file? It would be easier to configure UPSes for upsc, upsmon and nut-monitor with client config file. Maybe ups.conf ? -- Matus UHLAR - fantomas, uhlar at fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. My mind is like a steel

On 19.02.24 14:48, Dan Grostick via Nut-upsuser wrote: >Msmtp is not sending messages when invoked from upssched-cmd. >I can manually invoke it from the command line. where is its config file? >There is a 's' instead of an 'x' in the ls -l. Might this be some sort of >permission problem? Should not be the case. >upsmon.conf has run user as root. msmtp may use

Jan 19 05:50:13 mars nut-monitor[849]: Signal 15: exiting Jan 19 05:50:13 mars nut-monitor[849]: Network UPS Tools upsmon 2.8.0 Jan 19 05:50:13 mars systemd[1]: Stopping nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller... Jan 19 05:50:13 mars systemd[1]: nut-monitor.service: Deactivated successfully. Jan 19 05:50:13 mars systemd[1]: Stopped nut-monitor.service

On Sep 11, 2019, at 5:25 AM, tovis r-visor <tovis at r-visor.hu> wrote: > > I does not change any of them. Simple, after boot, using > $ watch upsc MYUPS > what is give me "LB OL" > from another terminal I restart: > # systemctl restart nut-driver.service > after some seconds the status is changed to simply "OL". Are there any systemd units that

On Jun 3, 2013, at 12:21 PM, Matus UHLAR - fantomas wrote: > It would be easier to configure UPSes for upsc, upsmon and nut-monitor with > client config file. > Maybe ups.conf ? If you are looking for a simpler way to set up NUT in general, there is the nut-scanner tool. I don't use it, but others on the list might be able to help. The separation between clients and server is to

On 19.01.24 16:20, Stefan Schumacher via Nut-upsuser wrote: >This morning at 9:50 the server stopped working unexpectedly - I was >still sleeping until 10:00, so no user intervention took place. > >Jan 19 05:50:17 mars nut-server[1303]: mainloop: Interrupted system call >Jan 19 05:50:17 mars nut-server[1303]: Signal 15: exiting >Jan 19 05:50:17 mars nut-server[1303]: Network UPS

On Wed, 28 Aug 2019, tovis r-visor wrote: > I was switch to battery, after 2-3 second it show that is on battery OB > and after it shutdown because of low battery LO. I wondered how old is your battery ? Roger

Hello and thanks for all the replies. This morning at 9:50 the server stopped working unexpectedly - I was still sleeping until 10:00, so no user intervention took place. Jan 19 05:50:17 mars nut-server[1303]: mainloop: Interrupted system call Jan 19 05:50:17 mars nut-server[1303]: Signal 15: exiting Jan 19 05:50:17 mars nut-server[1303]: Network UPS Tools upsd 2.8.0 Jan 19 05:50:17 mars

On 19.01.24 09:00, Jim Klimov via Nut-upsuser wrote: >Well, from your logs it seems that at 05:17:03 your nut-server (upsd) >restarted, so an upsmon reconnection attempt at 05:17:09 had an issue with >that (config not all applied? strange a bit) but since 05:17:14 it is okay. > >Maybe a few too many banners shown from upsmon, while its same uptime seems >to continue. Maybe

With recent NUT releases, driver disconnections should be contained in its own `nut-driver at eaton` instance (the `@upsname` part is derived from the `ups.conf` section name). One of the drivers failing and restarting is not a proper cause for the data server to recycle. Also, nowadays some (maybe not all) USB-capable drivers should try to reconnect without restarting. Note however, that in some

I have a quite old home server based on Debian 6.x packages using courier imap server (exim4, fetchmail, courier, apache2, squirrelmail) to keep my and my wife emails (about 25G). I want renew my server to Debian 10 (buster) and got a recommendation to use dovecot instead of courier. For this purpose I'm using a different PC as a sandbox. Debian 10 currently offer dovecot version 2.3.4.1

Msmtp is not sending messages when invoked from upssched-cmd. I can manually invoke it from the command line. There is a 's' instead of an 'x' in the ls -l. Might this be some sort of permission problem? upsmon.conf has run user as root. Dan -------------- next part -------------- An HTML attachment was scrubbed... URL:

> > On 30.9.2019 13.40, tovises wrote: >>> >>>> On 30 Sep 2019, at 13.13, tovises via dovecot <dovecot at dovecot.org> >>>> wrote: >>>> WOW! - amazing quickly, I'm really grateful. >>>> >>>> I was using: -u tovis imapc: nusi but still something wrong. >>>> Patstebin: https://pastebin.com/tH4wzJka

> > On 29.9.2019 23.38, tovises via dovecot wrote: >> I have a quite old home server based on Debian 6.x packages using >> courier >> imap server (exim4, fetchmail, courier, apache2, squirrelmail) to keep >> my >> and my wife emails (about 25G). >> I want renew my server to Debian 10 (buster) and got a recommendation to >> use dovecot instead of

> > On 30.9.2019 12.38, tovises wrote: >>> On 29.9.2019 23.38, tovises via dovecot wrote: >>>> I have a quite old home server based on Debian 6.x packages using >>>> courier >>>> imap server (exim4, fetchmail, courier, apache2, squirrelmail) to keep >>>> my >>>> and my wife emails (about 25G). >>>> I want renew

> > >> On 30 Sep 2019, at 13.13, tovises via dovecot <dovecot at dovecot.org> >> wrote: >>> >> WOW! - amazing quickly, I'm really grateful. >> >> I was using: -u tovis imapc: nusi but still something wrong. >> Patstebin: https://pastebin.com/tH4wzJka >> The most relevant part (I think) is: >>