similar to: Centos 5 not shutting down

Not much in the way of configuration…. I’m pretty sure I’ve got it correct. -- Todd Benivegna // todd at benivegna.com On Aug 13, 2020, 8:54 PM -0400, Manuel Wolfshant <wolfy at nobugconsulting.ro>, wrote: > On August 14, 2020 3:46:05 AM GMT+03:00, Todd Benivegna <todd at benivegna.com> wrote: > > So I finally got a test in after I changed my RPi to the master and > >

My notebook has a habit of getting hot, and Centos just shuts down. Just did it again: Jul 15 01:35:12 nc4010 kernel: ACPI: Critical trip point Jul 15 01:35:12 nc4010 kernel: Critical temperature reached (113 C), shutting down. Jul 15 01:35:12 nc4010 kernel: Critical temperature reached (55 C), shutting down. Jul 15 01:35:13 nc4010 shutdown[9847]: shutting down for system halt Jul 15 01:35:13

Hello All, I'm trying to establish a MASTER SLAVE configuration of UPS using NUT Driver. I'm able to shutdown the master after UPS is on BATTERY ( POWER BLACKOUT) .However I'm trying to shutdown the other SLAVE MACHINES BEFORE MASTER. But at the remote side ( Slaves ) shutdown after UPS blackout does not happen. My configuration in Master are /usr/etc/upsd.users

Pardon me for a long detailed post but this looks pretty serious. The bottom line is that, when I attempt to shut down or reboot my simple xen-2.0.7 server running FC3 with two domUs, shutting down xendomains appears to send python into an infinite loop. This may be due to a serious misconfiguration on my part but it is certainly a big problem. If we shutdown the domUs manually first, the

Hi all, my main xen test system is a pizza box, simply standard. The kernel of stable debian sarge can shut it down/restart it correctly. My own xen kernel (based on debians inofficial xen kernel) cannot. I do not know much of kernels and hardware yet, so please help me to understand: Is shutting down (as opposed to writing "power down" to the screen) or restarting based on APM or

So I have learned that Postfix should delay until Chronyd has moved the system time from 0 to current. What other services need to be delayed? Apache? Bind? Of course if this is a nameserver, Chronyd will probably not be able to resolve the NTP server addresses until Bind is running! thanks

'Father' of the IMAP protocol. Died Dec 28. http://en.wikipedia.org/wiki/Mark_Crispin Had a TOPS-20 in his basement that did a great job of keeping the house warm in the cool months (I remember one BAR bof where he extoled the benefits of this form of home heating).

Well FWbuilder is NOT easy. The documentation does not match the current GUI. Now the box is locked up. I will have to pull it again, hook it up to a kybd/VGA and reset iptables.... Maybe Shoreline with webmin.... Problem is I want a REAL router/firewall with little work. Both public and private nets have routable addresses. No NATing for me! I just help write the RFC ;) And all the

Hello all, I was asked about a proper way to ensure powerfail shutdown of a blade server fed off an APC SmartUPS, which is monitored by all hosts over SNMP. In particular, they'd like to avoid the "untimely" return of utility power - when the OSes are already shutting down, and would stay down because the UPS is well-fed now and thus won't power off and later power on to boot

On December 2, 2018 7:29:38 PM GMT+02:00, raul <raulvior.bcn at gmail.com> wrote: >I have restored original configuration and enabled the ignorelb flag. I > >didn't point out in the original e-mail that after every poweroff the >battery percentage is reported at 40% instead of 100% and charges >slowly again to 100%. Maybe the UPS sends a LB event and shuts down

I am running CentOS 5.3 and have just the two accounts "root" and "buz". I would like to be able to issue "shutdown" from the account "buz", and thus created /etc/shutdown.allow with the single entry "buz" (without any quotes). I still get the error message "only root can do this" (or something similar) even if I include the

OpenSUSE 12.3 has fully embraced systemd, but to get NUT working correctly now requires some further systemd engineering in addition to the usual NUT configuration files. A new systemd service unit is needed to power off the UPS. The service unit consists of a new file /etc/systemd/system/ups-delayed-shutdown.service [Unit] Description=Initiate delayed UPS shutdown

I am making some progress on my Centos 5 notebook build. So I am looking at Firefox and Thunderbird 2.0. Should I install them? Or is Redhat correct that there is nothing improved here and wait for 3.0? (well I have not even had a chance to look at Thunderbird 2.0, that is new)? I have the install steps we covered here back on 2/2/07; but are there rpms? I did not find anything over at

> > The documentation isn't explicit about this, but 'upsdrvctl shutdown' is > meant to be run after all of the other processes on the system have been > killed, real filesystems have been unmounted, and the kernel shutdown > syscall is about to be called. Usually the init scripts will take care of this, > although I don't know how CentOS handles that

Hi, we have a problem in oVirt that highly available VMs don't restart after host poweroff because Vdsm identifies the case as a user initiated shutdown (https://bugzilla.redhat.com/1800966). When poweroff is run on the host, libvirt-guests service takes an action. `virsh shutdown' is run on the VM, the guest OS is shut down cleanly and libvirt reports a shutdown event with

On 03/27/2017 03:24 PM, Mike wrote: > I recently converted my employer's firewall from pure iptabes to > firewalld and looked for something similar, more along the lines of > webmin, etc. > I didn't find anything close to a match. > In the end, it all came down to getting comfortable with > "firewall-cmd" in the shell. I have been digging and found that Fedora

> If there is no message to NUT, I would consider opening a trouble > ticket with Eaton. It is possible that there is a known issue and/or > a firmware upgrade. What kind of message to NUT? In the log (syslog) there is no other message registered. In nut.log only this appears: > Dec 1 08:10:54 openmediavault upsd[5284]: Data for UPS [ellipsemax] > is stale - check driver >

Hello, just a simple question, my router has CentOS 6 with the apcupsd running, in the log of apcupsd I see this: 2018-02-01 19:05:54 +0100 apcupsd 3.14.12 (29 March 2014) redhat startup succeeded 2018-02-04 15:52:43 +0100 Power failure. 2018-02-04 15:52:49 +0100 Running on UPS batteries. 2018-02-04 15:53:00 +0100 Reached remaining time percentage limit on batteries. 2018-02-04 15:53:00

"Daniel P. Berrange" <dan@berrange.com> writes: > On Wed, Aug 26, 2020 at 10:35:22PM +0200, Milan Zamazal wrote: >> Hi, >> > >> we have a problem in oVirt that highly available VMs don't restart after >> host poweroff because Vdsm identifies the case as a user initiated >> shutdown (https://bugzilla.redhat.com/1800966). >> >>

Michal wrote: > -----Original Message----- > From: Michal Privoznik [mailto:mprivozn@redhat.com] > Sent: Wednesday, July 10, 2013 12:45 PM > To: Lentes, Bernd > Cc: libvirt-ML (libvirt-users@redhat.com) > Subject: Re: [libvirt-users] guests not shutting down when > host shuts down > > On 10.07.2013 11:37, Lentes, Bernd wrote: > > Hi, > > > > i have a