similar to: Autodetecting running drivers by the 'upsd' server

I am running tests on my system and UPS, making sure that it is reliably able to come up, detect power loss, shutdown safely, and then come back up when the power returns. It does that MOST of the time. However, a significant part of the time, the system comes up, and then doesn't respond to loss of power. Doing some checking, I find that the reason is because upsd never started. Capturing

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: This is a digitally signed message part. Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080812/04e0e065/attachment-0001.pgp

On Jul 7, 2015, at 4:12 PM, Rob Groner <rgroner at RTD.com> wrote: > It does that MOST of the time. However, a significant part of the time, the system comes up, and then doesn?t respond to loss of power. Doing some checking, I find that the reason is because upsd never started. Capturing its output, I see that it says : > > Fatal error: A previous upsd instance is already

This morning I finished building and configuring nut 2.6.0 on OpenBSD 4.8, and it is running fine. While I was in the config files, I noticed what looks like it may be a discrepancy between the config file commetns and the configure script default. uspd.conf has the following comment: # STATEPATH <path> # STATEPATH /var/run/nut # # Tell upsd to look for the driver state sockets in

I'm forwarding this to the list, as I'm not quite sure what's going on here. Never seen this on Linux, don't know if it is a FreeBSD thing or not. ---------- Forwarded message ---------- From: Herman J van der Merwe <herman@mercygate.com> Date: Feb 11, 2007 9:50 PM Subject: NUT on FreeBSD To: carlos.efr@mail.telepac.pt Hello Carlos Maybe you can assist me with NUT 2.0.5

I'm trying to see if we can make upsd autodetect the driver sockets from the STATEPATH. This works quite well and uses surprisingly little code (much less than parsing the 'ups.conf' file). However, since I can no longer read the name from the 'ups.conf' file, I need to extract this from the name of the socket. We might simply strip the drivername from the socket name again,

I noticed that many configuration options (configure.txt) have environment variable overrides. However, an important one does not. In the configuration.txt file, there is one section: Directories used by NUT at run-time ----------------------------------- --with-pidpath=PATH Changes the directory where pid files are stored. By default this is /var/run. Certain programs like upsmon will

the other day i was trying to create a new freebsd slice on the same disk i booted from (on a freshly updated RELENG_6) and both fdisk and sysinstall failed with some error (i think they could not write on the disk, or something similar). boot -s did not seem to help, either. I remember vaguely some time ago a bit of discussion on this topic, but cannot recall the outcome nor any keyword to

On Jul 30, 2013, at 10:39 AM, Pavel Potcheptsov (EKTOS) wrote: > Is this a trouble? Driver use path /var/state/ups/ but upsd use path /var/db/nut/upsd.pid Yes, the driver and upsd need to agree on the path to the socket. From the FreeBSD ports tree: /usr/ports/sysutils/nut/Makefile: STATEDIR?= /var/db/nut [...] CONFIGURE_ARGS= --sysconfdir=${PREFIX}/etc/nut \

Hi, I was experimenting with Logstash + elasticsearch on FreeBSD 9 - initially I downloaded it by hand (I forgot to check for a port) and it worked fine. I then tried the port and this forced me to use a different java version (was jdk-16.0.3p4_25 now openjdk6-b27) and it seems that the new one causes a panic. Unfortunately crashdumps aren't working properly, however I did get the panic

Hi all, I've been making a wrapper script for the backup tool 'duplicity', allowing me to create config files for each resource, wherein I define whether a snapshot should be made prior to backing up the resource or not. Now I find that my snapshots never change .... The script creates a snapshot, creates md device, mounts it, runs backup against the mounted snapshot,

Hi, I work for a small company that makes radar systems for research organisations and we use FreeBSD on the PCs for data acquisition and processing. We have recently shifted to FreeBSD6/amd64 and one machine in particular is exhibiting a strange problem. The acquisition process is a Tcl interpreter with a largish chunk of C code which talks to the hardware (via RS485 and a custom PCI card).

Hi all, A recent thread inspired me to try getting a proper serial console working on a Supermicro X9SCL motherboard with IPMI. However I find that while I see loader messages and the getty I enabled after boot I don't get any kernel messages which does somewhat limit the utility.. The BMC creates COM3 (/dev/cuau2) which works with getty. I modified /boot/loader.conf like so..

It seems a php-extensions bug. If you comment the mhash.so in /usr/local/etc/php/extensions.ini as: ;entension=mhash.so all works fine and you don't get anymore httpd crash (signal 11) if you use 'apachectl graceful'. Maybe will be a good idea to open PR for this? I hope it helps someone.... (I'm very surprised that this isn't a documented bug in 7.0 yet) -- Thanks, Jordi

Anyone know what is the problem for this? thanks Andrew freebsd 540$ /usr/local/etc/rc.d/nut restart nut not running? (check /var/db/nut/upsd.pid). Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - Generic UPS driver 1.32 (2.0.4) UPS type: APC Back-UPS (940-0023A cable) Unable to open /dev/cuad0: Device busy Current user id: uucp (66) Serial port owner: uucp (66) Serial

Hi Arjen, in server/upsd.c r731, you moved the call conf_load() from after check_perms() (~ l.1020) to before setupsignals() (~ l.989). The problem is that conf_load() needs to open the ups driver socket, and it assumes that STATEPATH is the current working directory. The directory is only set in l.1016. Therefore, the first attempt to open a socket will always fail. From the user's point of

I'm sure I'm missing something, but I can't seem to get NUT working on FreeBSD. bryce at tahiti[/usr/local/etc/nut]>cat ups.conf [belkin] driver = usbhid-ups port = auto vendorid = 050d #productid = 0751 bryce at tahiti[/usr/local/etc/nut]>s /usr/local/libexec/nut/usbhid-ups -DDDDD -a belkin Network UPS Tools - Generic HID driver 0.34 (2.4.1) USB communication driver 0.31

Since updating to 6.3-RELEASE on two machines I see this message a lot. It is printed whenever a kernel module is loaded. The modules load OK. Nothing special or different about them. It seems to be harmless, but any idea why it's started happening since the release? Cheers BMS

I am looking at the newhid driver for this Pulsar EXtreme here but it gives odd results, for example there is no status variable :) eg debug level is '2' Checking device (0463/FFFF) (/dev/usb0//dev/ugen0) - VendorID: 0463 - ProductID: ffff - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: /dev/usb0 Trying to match device Device matches HID descriptor retrieved

For those that may have run across the story on Slashdot about this NIC, here is our statement: Recently there were a few stories published, based on a blog post by an end-user, suggesting specific network packets may cause the Intel? 82574L Gigabit Ethernet Controller to become unresponsive until corrected by a full platform power cycle. Intel was made aware of this issue in September 2012 by