similar to: A problem with power outages

I have a CentOS-5.6 remote server in a house in Italy, where there are occasional thunder-storms. There was one yesterday, when the electricity went off 3 times, for a second or so on each occasion. My server, an HP MicroServer, came back (re-booted) on 2 of the 3 occasions, but not on the third. I assume that the problem arises because the machine does not close down properly. (Although it is

Hi everyone. I'm currently looking for a monitoring program for a HP PowerTrust UPS (A2998A) for Linux. It seems that nut supported these UPSs until version 1.4.3. What was the reason for the driver being removed from nut? Are there plans to reintegrate it? I was playing around with the UPS and put the results here: http://www.project-athlon.org/wiki/index.php/HP_PowerTrust_A2998A They

Hi all, We've just had a power outage and the pc's can now no longer connect to the server. The server had power backup and did not go down which seems strange. Now when I try to connect the error message in smbd.log is smbd/connection.c:yield_connection(62) yield_connection: tdb_delete failed with error Record does not exist. and on the workstation it denies access citing security

Hi all! As I'm currently porting the HP PowerTrust driver from nut-1.4.3, I have a question regarding ups.delay.*. The PTs can delay the Shutdown/Restart and Kill commands by an arbitrary number of seconds, i.e. they wait for n seconds and then shutdown or kill. The delay for the restart after the shutdown can't be changed. Which of the ups.delay.* variables correspond to these values?

Hi all! As I'm currently porting the HP PowerTrust driver from nut-1.4.3, I have a question regarding ups.delay.*. The PTs can delay the Shutdown/Restart and Kill commands by an arbitrary number of seconds, i.e. they wait for n seconds and then shutdown or kill. The delay for the restart after the shutdown can't be changed. Which of the ups.delay.* variables correspond to these values?

Cyber Power Systems CP1000PFCLCD = upsc output = attached = Shutdown results = I experienced a genuine power outage shortly after setup. The 1 master system and the 1 slave system both shutdown successfully. The master shutdown before the slave (*not* a bug report; I may not have this configured correctly yet). The UPS was not powered off by the master. I don't know if the UPS

when I ran "sudo yum update" on my CentOS-7.2.1511 today, ddclient was updated to ddclient-3.8.3-1.el7.noarch (from 3.7.3), and ddclient.conf was moved to ddclient.conf.rpmsave . When I move it back, "sudo systemctl restart ddclient" fails with the error (in "sudo journalctl -xe | grep ddclient") Apr 21 13:05:39 alfred.gayleard.eu.localdomain touch[8590]:

Dear LLVMers, There was a campus wide power outage today at the University of Illinois. It took down most (if not all) computing services, including the LLVM web/subversion server and the mailing list server. Power has since been restored, and it appears that our IT department has gotten the LLVM web and SVN server operating again (I went in earlier this evening to see if the LLVM server

Maarten makes some poses some valid questions: > Did you check the Linux machines for system and/or update logs at the > given time? I'm afraid I don't know all the places to look for logs that might tell me something. My script that keeps MPG123 running keeps a log of all reboots and outages. A reconnect that lasts less than one minute is counted as continuous outage.

On Mar 8, 2009, at 10:55 PM, John Criswell wrote: > Dear LLVMers, > > There was a campus wide power outage today at the University of > Illinois. It took down most (if not all) computing services, > including > the LLVM web/subversion server and the mailing list server. > > Power has since been restored, and it appears that our IT department > has > gotten the

I would like to setup a small system based on CentOS6 "power outage"-save as possible. The hardware will be switch off by pulling the plug. To accomplishing this goal, I would mounting some fs parts readonly (e.g. /usr) and thinking about tmpfs for volatile parts (e.g. lock, run under var). Additionally "optimize" some vm.dirty_* kernel- and fs/ext4 parameters.

I have a TE205P that has been working fine for 2 years. power outage yesterday took out my everything for over an hour. Everything has come back up except the PRI. My provider has checked it to the box and says everything looks good on their end. I get this message: [Jul 9 12:40:32] WARNING[13709] chan_dahdi.c: No D-channels available! Using Primary channel 24 as D-channel anyway! ztcfg

Dan Langille via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > I have an idea for my shutdown process at home. My goal: maximize the network run-time. At present, the UPS has a run-time of about 57 minutes. > > This is my idea: > > * shutdown the servers after 15 minutes of downtime (for me, that's when battery.runtime hits 40) > * leave the network

Dear All, The Siebel Center (the building in which the llvm.org server is housed) is undergoing some significant work on its cooling system this weekend. Air conditioning will not be available, so we have been advised to shut down systems until the cooling work is done. This outage affects the following LLVM services: 1) The LLVM web server and SVN server will be unavailable starting noon

Hi, I'm struggling with a peculiar issue with my UPS. After a power outage, the devices powered by it properly shut down via nut. Eventually, the UPS also goes down. Power is still out, however, roughly 40 seconds after the UPS shut down, it turns back on and it starts supplying power to the load, thus turning back on the devices attached to it. This is obviously not something I want. In

Hey folks, Due to continuing problems with our datacenter, we''re moving some infrastructure this evening. During this period, both Redmine (https://projects.puppetlabs.com/) and the Forge (http://forge.puppetlabs.com) will be unavailable. Sorry about the short notice of this, and the outage earlier too [1]. If you have any issues in a couple of hours once it''s all back up,

On 7/4/2015 1:07 PM, John R Pierce wrote: > On 7/4/2015 12:28 AM, Jatin Davey wrote: >>> >> My server supports ACPI 4.0 standard , Will that be helpful ? > > does `init 0` as a root command cause it to gracefully shut down and > power off ? thats all the ACPI support you need. [Jatin] Yes, init 0 does gracefully shutdown the server and power off. > > >

Hi, On Tues Jul 17th, we had a full GitLab outage from 14:00 to 18:00 UTC, whilst attempting to upgrade the underlying storage. This was a semi-planned outage, which we'd hoped would last for approximately 30min. During the outage, the GitLab web UI and API, as well as HTTPS git clones through https://gitlab.freedesktop.org, were completely unavailable, giving connection timeout errors.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 == What happened == On Wednesday February 24th, at 6pm UTC time, the DC hosting some of the CentOS equipments used for various roles had suffered from multiple electricity power outages. The facility was completely dark for just under 2 hrs, and we were able to start recovering services by 8pm UTC. By midnight we had most services restored, by

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 == What happened == On Wednesday February 24th, at 6pm UTC time, the DC hosting some of the CentOS equipments used for various roles had suffered from multiple electricity power outages. The facility was completely dark for just under 2 hrs, and we were able to start recovering services by 8pm UTC. By midnight we had most services restored, by