similar to: unexpected shutdown, had to reinstall xorg.server

Displaying 20 results from an estimated 4000 matches similar to: "unexpected shutdown, had to reinstall xorg.server"

2016 Jun 27
0
unexpected shutdown, had to reinstall xorg.server
Greetings all; I expect that I may not have the shutdown properly configured, but my site was subjected to some bad weather related intermittent power losses a week+ back, and I have an automatic standby plant, a 20kw, that usuall fires up and has the lights back on in 7 or 8 seconds. So while the power folks were reclosing substation breakers to see where the next tree limb was shorting
2023 Jun 20
1
had to reinstall on new drive, lost all nut related .conf's
On 6/19/23 18:57, gene heskett wrote: > Greetings Jim & friends; > > Just installed nut 2.7.4 on a debian bullseye system.? ups is: > Bus 001 Device 006: ID 051d:0003 American Power Conversion UPS > Device Descriptor: > ? bLength??????????????? 18 > ? bDescriptorType???????? 1 > ? bcdUSB?????????????? 2.00 > ? bDeviceClass??????????? 0 > ?
2020 Jan 02
2
Delayed UPS shutdown
On Wed, 1 Jan 2020, Gene Heskett wrote: > But I should preface this with the fact that I have a 20kw nat gas fired > standby with a sub 10 second startup time in the back yard. > > The ups really should be smart enough to take a delayed shutdown command > and be able to do without further commanding from the monitoring nut > running machine, something I would think on the
2023 Jun 19
1
had to reinstall on new drive, lost all nut related .conf's
Greetings Jim & friends; Just installed nut 2.7.4 on a debian bullseye system. ups is: Bus 001 Device 006: ID 051d:0003 American Power Conversion UPS Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor
2020 Jan 02
1
Delayed UPS shutdown
On Thu, 2 Jan 2020, Harlan Stenn wrote: > On 1/2/2020 3:12 AM, Roger Price wrote: >> On Wed, 1 Jan 2020, Gene Heskett wrote: >>> But I should preface this with the fact that I have a 20kw nat gas >>> fired standby with a sub 10 second startup time in the back yard. >>> > My understanding is: > > If there is a power outage, there comes a point where
2023 Jun 20
1
had to reinstall on new drive, lost all nut related .conf's
On 6/19/23 20:29, gene heskett wrote: Some speeling korrections > On 6/19/23 18:57, gene heskett wrote: >> Greetings Jim & friends; >> >> Just installed nut 2.7.4 on a debian bullseye system.? ups is: >> Bus 001 Device 006: ID 051d:0003 American Power Conversion UPS >> Device Descriptor: >> ?? bLength??????????????? 18 >> ?? bDescriptorType????????
2023 May 22
3
got nut 2.8.1 but despite reinstall, shows 2.7.4
gene heskett <gheskett at shentel.net> writes: > Which file in the nut I pulled a month ago, should I start with to get > the new version actually running? I still get - -V=2.7.4 It is likely that you have built new nut but old nut is still on your system. I do a 'sudo make install' to write over the distribution nut (on NetBSD/pkgsrc, surely not what you are using).
2023 May 22
2
got nut 2.8.1 but despite reinstall, shows 2.7.4
On 5/22/23 07:13, Greg Troxel wrote: > gene heskett <gheskett at shentel.net> writes: > >> Which file in the nut I pulled a month ago, should I start with to get >> the new version actually running? I still get - -V=2.7.4 > > It is likely that you have built new nut but old nut is still on your > system. I do a 'sudo make install' to write over the
2016 Nov 27
3
SBC's and ssh's encryptions
On Sunday 27 November 2016 13:49:17 Peter Stuge wrote: > Gene Heskett wrote: > > > On pi, in same shell as above, start the GUI application > > > > So the monitor is plugged into the droid, but the keyboard & mouse > > are plugged into the pi? > > No; X11 is a remote windowing protocol. Monitor, keyboard and mouse > are connected where your X server
2023 May 22
2
got nut 2.8.1 but despite reinstall, shows 2.7.4
On Mon, 2023-05-22 at 15:54:51 +0200, Matus UHLAR - fantomas wrote: > > > gene heskett <gheskett at shentel.net> writes: > > > > Which file in the nut I pulled a month ago, should I start with to get > > > > the new version actually running? I still get - -V=2.7.4 > > > On 5/22/23 07:13, Greg Troxel wrote: > > > It is likely that you have
2023 May 22
2
got nut 2.8.1 but despite reinstall, shows 2.7.4
Which file in the nut I pulled a month ago, should I start with to get the new version actually running? I still get - -V=2.7.4 Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D.
2023 May 22
1
got nut 2.8.1 but despite reinstall, shows 2.7.4
On 5/22/23 03:10, gene heskett wrote: > Which file in the nut I pulled a month ago, should I start with to get > the new version actually running? I still get - -V=2.7.4 The UPGRADING file tsalks about a 2.8.1, but I have started with the autogen 3 times in the usual sequence, winding up with 2.7.4 twice, and while the third time is supposed yo be a charm, now it won't run at all.
2023 May 22
1
got nut 2.8.1 but despite reinstall, shows 2.7.4
>>gene heskett <gheskett at shentel.net> writes: >>>Which file in the nut I pulled a month ago, should I start with to get >>>the new version actually running? I still get - -V=2.7.4 >On 5/22/23 07:13, Greg Troxel wrote: >>It is likely that you have built new nut but old nut is still on your >>system. I do a 'sudo make install' to write over
2023 May 22
1
got nut 2.8.1 but despite reinstall, shows 2.7.4
I think you have just the libraries - also you'd need a *-dev package for headers. The docs/config-prereqs.txt has the dependencies in more detail. In quick practice, --with-all=auto can help better if you don't monitor a netxml device ;) HTH Jim On Mon, May 22, 2023, 15:24 gene heskett <gheskett at shentel.net> wrote: > On 5/22/23 03:10, gene heskett wrote: > > Which
2015 Dec 29
2
access to upsrw
Greetings Charles; I hope you had a nice Christmas, and will have a happy and prosperous new year in 2016. You mentioned upsrw in a message earlier, so I ran it, and found the shutdown timeout was only 20 seconds. gene at coyote:~$ upsrw myups [input.transfer.high] High voltage transfer point (V) Type: STRING Value: 140 [input.transfer.low] Low voltage transfer point (V) Type: STRING Value:
2015 Aug 18
2
Need the date included in nuts -wall msgs.
Greetings all; Is it possible to set a logging option in one of the config files so that when we have a 1 second power bump, the date is included, both in the log, and in the -wall broadcast? We apparently have a substation regulator in the process of failing, and the recycle isn't normally slow enough to reset the clocks, but it killing one of my computers w/o actually causing a reboot.
2020 Jan 02
0
Delayed UPS shutdown
On 1/2/2020 3:12 AM, Roger Price wrote: > On Wed, 1 Jan 2020, Gene Heskett wrote: >> But I should preface this with the fact that I have a 20kw nat gas >> fired standby with a sub 10 second startup time in the back yard. >> >> The ups really should be smart enough to take a delayed shutdown >> command and be able to do without further commanding from the >>
2020 Jan 08
1
unexpected UPS status
On Wed, 8 Jan 2020, Gene Heskett wrote: > On Wednesday 08 January 2020 06:44:03 Roger Price wrote: >> I am surprised that there is no ups.delay.start for this UPS. > My new APC Smart-UPS_1500 doesn't have it either. Hello Gene, The NUT 2.7.2 "device dump library" entry for the APC Smart-UPS 1500 at https://networkupstools.org/ddl/APC/Smart-UPS_1500.html shows an entry
2020 Jan 08
2
unexpected UPS status
On Tue, 7 Jan 2020, Eyal Lebedinsky wrote: > On 2020-01-07 23:01, Roger Price wrote: >> There is no report for variable "ups.delay.start" in your upsc output. >> What does command "upsc <ups> ups.delay.start" report? > > $ upsc eaton ups.delay.start > Init SSL without certificate database > Error: Variable not supported by UPS I am surprised
2020 Oct 30
2
Can't get CyberPower UPS to work with Raspberry Pi 4
On Thursday 29 October 2020 22:12:00 Charles Lepple wrote: > On Oct 28, 2020, at 9:56 PM, Gene Heskett <gheskett at shentel.net> wrote: > > Which looks very incomplete to me. OTOH, its not a very big UPS but > > neither is the pi. I have tested that, and it shuts off long before > > it outouts a LB signal. > > Which part looks incomplete, the variables or the