similar to: Nut not working remotely

OK, can someone tell me what utterly moronic thing I am doing wrong? I have two roughly identical Linux system running NUT, and one works properly. The other almost does. The second system works well once everything is up, but after booting, the system does not have connectivity to the UPS. I have to manually run `upsdrvctl start backup`, `/etc/init.d/nut start`, and `upsd` to get NUT

Leslie, This message is most appropriate for the NUT user list. I kept Rik Faith's and Nicholas Kain's copyright information because the tripplite_usb driver borrows heavily from the tripplite (serial) driver, but they are not responsible for the mess that I made in the USB driver. See below. On Dec 28, 2008, at 5:28 PM, Lelsie Rhorer wrote: > Gentlemen, > >

Hello. I need some help. I was running uw-imap on my IMAP server (so I am using mbox email files), but I was having trouble with Outlook 2013, so I decided to move to dovecot. At first things were looking much better, except that most of my folders, other than the Inbox, were not showing up. I started changing both the dovecot configuration and the folder structure of my mail files,

On 9/6/2014 12:47 PM, Charles Lepple wrote: > On Sep 6, 2014, at 12:39 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > >> I made a number of hardware and software changes, including an upgrade to the latest software versions for that distro (Debian Wheezy), > > Can you be more specific about the changes? Well, I did an automated upgrade (apt-get upgrade), I changed

Hello. I have had NUT working for several years on my servers. Recently I made changes to the main server, where the UPS is local, and now upsd won't properly load there, which essentially disables the entire UPS shutdown system. I made a number of hardware and software changes, including an upgrade to the latest software versions for that distro (Debian Wheezy), although I did not

On Sep 6, 2014, at 12:39 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > I made a number of hardware and software changes, including an upgrade to the latest software versions for that distro (Debian Wheezy), Can you be more specific about the changes? Key variables: * USB controller information (old and new hardware) * Kernel versions, for both working and non-working setups

I just did a fresh installation of Debian Jessie on one of my servers, but NUT won't configure and install. When I try to install, I get the following: Setting up nut-client (2.7.2-1+b2) ... Job for nut-monitor.service failed. See 'systemctl status nut-monitor.service' and 'journalctl -xn' for details. invoke-rc.d: initscript nut-client, action "start" failed.

Hi Leslie, 2014-09-29 17:14 GMT+02:00 Leslie Rhorer <lrhorer at mygrande.net>: > > I just did a fresh installation of Debian Jessie on one of my > servers, but NUT won't configure and install. When I try to install, I get > the following: > > Setting up nut-client (2.7.2-1+b2) ... > Job for nut-monitor.service failed. See 'systemctl status >

On Sep 6, 2014, at 4:16 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > Oh, hey! That seems to have worked. I'm sure the UPS got plugged into a different port one of the (many) times the server was removed from the relay rack, and it was on a USB 3.0 port. I moved it to a 1.0 port and everything seems to be working just fine. The specifics of the motherboard and its USB

Hello I recently bought a small UPS by Eaton (Ellipse ECO 800) in order to prevent my btrfs-fileserver (running Debian 12 Bookworm 12.4 from shutting down abruptly while writing something important during a power loss. I am using the version 2.8.0.7 provided by Debian. I have found very gooddocumentation on how to set up the UPS and the services on the server connected to it. Unfortunately

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 someone should check on that, seems like a good and easy newcomer issue to learn

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

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 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

    I just set up a UPS on a Debian Stretch system for my sister-in-law.  Obviously, I want NUT to properly shut down the unit when the battery gets low.  This means upsmon must be running and healthy.  When I run 'systemctl status nut-monitor`, I see the following in the journal: nut-monitor.service: Supervising process 778 which is not our child. We'll most likely not notice when

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

Up until a few days ago, I had SAMBA running just fine on several different systems, but very recently on of the server has quit announcing itself to the newtwork. Smbd, nmbd, and winbindd are all running on the server, and the machines on the network can all still reach the shares on the system, but an attempt to browse for the server and its available shares from a client PC does not produce a

On Wed, Apr 1, 2009 at 10:54 PM, Lelsie Rhorer <lrhorer at satx.rr.com> wrote: > > Gentlemen, > > I am running a Tripp Lite OMNISV1500XL under NUT using the > tripplite_usb driver on a Debian "Lenny" Linux system. The platform is an > AMD Athlon 64 x 2 processor running kernel 2.6.26. The driver is up and > running, but there are several issues.

I have a Symmetra LX 16000 UPS with a Network Management Card (Schneider Electric, I think).?? Can NUT be configured to report from this unit and shutdown hosts based upon messages from this unit?