similar to: What happens if I turn the DC off?

Yes, PC's wil notice it. I suggest. Powerdown the DC, replug the power to outlet and boot the DC. If the DC is only DC, then this should be done within a few min. Now switch the UPS Battery. Test the UPS. Users stay authenticated but yes, the will notice slow down. But its only a few min. I really advice the above, because if the UPS is old, the battery might blown up, resulting

On Wed, 18 Jul 2018 10:26:31 +0200 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > I assume I know it ... but I think this is worth being discussed and > clarified. > > At a customer we have 1 samba DC and 1 samba DM = fileserver. > > The DC is supported by a small UPS and the battery in that UPS is > getting old and tells me to

Am 2018-07-18 um 10:45 schrieb Rowland Penny via samba: > Have you ever heard of laptops ? you know those things that wander away > from the domain ;-) laptops? hm I'm gonna look that up on altavista asap. >> I understand that logins might fail, sure, but maybe the >> authenticated connections to the DM could be maintained by the DM >> itself for a short period of

Thank you for your response. The point is that I have configured my system to shut down at the event "upsc Inform@localhost ups.status"!="OL", not at "LB". So there will be no /etc/killpower file created. At an ups.status != "OL" event, the following script named "notifyme" is run: echo `date` >> /root/upsLog echo " No power, shutting

This patch introduces a handful of new options, I mentioned earlier in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02088.html See the large commit message in the follow-up for the details and rationale. I realize it's a bit larger diff - so if it's required I can split it into few smaller ones. Michal Soltys (1): APC smart driver update and new features.

This is 2nd version of the earlier patch featuring a few new features and fixes to the apcsmart driver, following the remarks in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02294.html Major changes from v1: - handle battery.charge and battery.runtime checks at main.c level - handle "immutable but writable" conflict gracefully at driver level -

Hi, I've been experiencing intermittent filesystem corruption on a Compaq Armada M700 laptop w/ IBM Travelstar 30GB drives (both the 40GN and 30GN models). This happens mostly under RH 7.2, w/ ext3 filesystems, but I think it's also happened under win98. All seems fine until power-down, power-up, and boot, where the corruption is discovered. Searching these archives, I found that there

Hello, Control HP R1500 G2 with nut via USB. Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-72-generic x86_64) nut V2.7.1 installed from repository /etc/nut/ups.conf [HPR1500] driver=usbhid-ups port=auto After dealing hours with this, hope this will help some : rename udev rule to higher priority and move it to its right location, reload udev rules mv /lib/udev/rules.d/52-nut-usbups.rules

Hi, I have several Linux machines at home and I'm considering buying a UPS for them. I see that many models are supported by NUT (great!) but since I'm new to the UPS world I have some questions about UPS features and NUT support of them I couldn't find an answer for: 1/ are there UPS models who report/meter power usage through USB? per UPS socket or globally? 2/ are there UPS models

My new MGE Ellipse Premium 1200 is now working fine. I've tested pulling the plug and the computer shuts down properly and comes back up when I replug. The only strange behaviour is that when I put the power back on the battery shows as being at 86%. If it was at 86% it should have lasted longer. Is there any calibration step I can do? The only commands the ups seems to support are: $ upscmd

Sorry for a bit longer delay than I anticipated, I was stuffed with the work. This is the next iteration of the patch adding some functionality to apcsmart driver, and relying on 'ignorelb' recently added. Follow up from previous thread: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02331.html Main differences is that V3 is split into many small patches, so the

Try ALL:ALL in /etc/hosts.allow temporarily. If that still doesn't work, it's likely something else. If it does, only then screw with creating narrow rules . . . - Tim On November 25, 2016 6:37:02 AM CST, Roger Price <roger at rogerprice.org> wrote: >On Fri, 25 Nov 2016, Jonah Naylor wrote: > >> upsd : ipaddressofclientgoeshere > >If it were me I would write >

hello i think i found a bug i wanted nut to suspend to ram instead of powering off so i made a script that runs the commands but i ran into a problem i changed the shutdown command in upsmon.conf to my suspend script and i tested with upsmon -c fsd everything worked fine system went into suspend and i woke it backup by pressing the power button, now here is where i noticed some problems first one

Hello, I find in shutdown.txt file that before system boot after a power failure, it's better to check powerdown flag to be sure and pausing in the startup script to let the batteries recharge with filesystem. So i want to know which startup script is concerned? For the system or for nut? Thanks to explanation. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi centos 6.3 uses traditional SysV script ( not systemctl) here is the /etc/init.d/ups ( script) assuming it similar to nutshutdown # more /etc/init.d/ups #! /bin/bash # # ups: Starts the Network UPS Tools # # chkconfig: - 26 74 # description: Network UPS Tools is a collection of programs which provide a common \ # interface for monitoring and administering UPS hardware. # processname: upsd #

Hello! After I type "upsmon", in syslog the following message appears: Aug 16 14:11:09 marto upsmon[7731]: Master privileges unavailable on UPS [Inform@localhost] Aug 16 14:11:09 marto upsmon[7731]: Reason: Access denied Can you tell me where my error is, my configuration files are: ups.conf: [Inform] driver = powercom port = /dev/ttyS0 desc = "inform guard" linevoltage = 220

I've just set up a CyberPower Value 2200E-GP on a system running Lucid AMD64, with the current NUT package via apt-get, and it seems to be working fine for me with the usbhid-ups driver, so I guess it can go in the HCL? I'm using the system to host several virtual servers under KVM, and to make things simple I set it up to hibernate rather than shutdown, that way all the guest OS

Dears, I finally resolve my problem, I just make symbolic link: [test at box var/run/]# ln -s -T /var/state/ups/ nut Now I finally got services online: # /sbin/service ups start Starting UPS driver controller: [ OK ] Starting upsd: [ OK ] Starting UPS monitor (master): [ OK ] BUT, on upsc I

Gentlemen, I have done some experiments with an APC Back-UPS ES 650, to identify the currently specified items that are not available with this device, and to find out what non-standard items the device provides. Of the currently specified items, the following are not available: UPS.Battery.Temperature UPS.Output.PercentLoad UPS.PowerSummary.DelayBeforeShutdown UPS.Battery.Test

Am 2017-07-11 um 11:43 schrieb Rowland Penny: > On Tue, 11 Jul 2017 10:21:37 +0200 > "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > >> Am 2017-07-11 um 09:34 schrieb Stefan G. Weichinger via samba: >> >>> [2017/07/11 09:31:17.790046, 2] >>> ../source4/dns_server/dns_query.c:1019(dns_server_process_query_send)