similar to: UPS Socomec is unavailable appears in the logs

Hello, I have tried to use the blazer_ser driver to interface with my UPS. nut is not able to detect the UPS. I have not been able to find much info regarding Socomec UPS support in nut. Socomec does publish a description of the serial protocol for these UPS's, which can be found here: http://www.socomec.com/download-jbus-modbus.html(select UPS OTHER for device model, 1-5KVA for device power

Hi, I am considering purchasing a UPS and want one that I can query from bash scripts. I would assume nut to be the best tool to allow this. I have been directed to a Socomec RT 3000VA UPS. I have previously had MGE Pulsars and interfaced to them with nut's mge-utalk and mge-shut drivers with reasonable success, apart from the odd data stale error. These Socomec units have RS-232

Hello We have an Socomec Sicon Netys PR3000 UPS equipped with NetVision Web/SNMP adaptor. I try to monitor the ups using snmp-ups driver and netvision mibs set. The snmp-ups driver starts correctly and connects to the UPS, upsd confirms it, but upsmon constantly shows "No communication" error I think the cause is the SNMP adapter reports the UPS status as "ECO mode"

Hi Saulius, The spec you sent me is simply a Megatec excerpt: http://www.networkupstools.org/protocols/megatec.html So Socomec is simply a megatec rebranding (selling by simply putting its name on). As per the NUT compatibility list (http://www.networkupstools.org/compat/stable.html), Sicon are supported by the powercom driver. But since it's a megatec unit, you should preferably try the

Hi Henning, note that I've cc'ed the NUT users list for info. 2015-02-04 13:47 GMT+01:00 Henning Fehrmann <henning.fehrmann at aei.mpg.de>: > Hi Arnaud, > > > the best to process the value would be to have the MIB definition for > > upsAlarmOnBattery, as for example: > > [1] >

2011/11/5 Arnaud Quette <aquette.dev at gmail.com> > Hi Greg, > > 2011/11/4 Charles Lepple <clepple at gmail.com> > >> On Thu, Nov 3, 2011 at 12:23 AM, Greg Trounson <gregt at maths.otago.ac.nz> >> wrote: >> > These Socomec units have RS-232 connectors and claim to support JBUS. >> > On the nut compatibility page I only see one Socomec

hello, I have a few UPSes (NETYS PR 3000, 2000, 1000), with no SNMP-adapter installed. There are serial ports only. I tried to use megatec and powercom drivers. They don't work. Which driver to use? Thanks. -- wbr

On Oct 2, 2014, at 1:53 AM, Tarvo Tiits <Tarvo.Tiits at automaatika.ee> wrote: > On 02.10.2014 03:42, Charles Lepple wrote: >> On Oct 1, 2014, at 5:07 AM, Tarvo.Tiits at automaatika.ee wrote: >> >>> Why is ups.status empty? >> If I understand the commit log for SVN r3590, then that revision was supposed to set the status to OL if the numeric state was 9 for

Hi, I have UPS Socomec ITYS 3000 with Netvision card. OS is Centos 6.5 64-bit. NUT installed with yum,. nut-2.6.5-2.el6.x86_64 nut-client-2.6.5-2.el6.x86_64 Why is ups.status empty? Here is upsc output: upsc myups at localhost battery.charge: 97.00 battery.runtime: -60.00 battery.voltage: -0.10 device.mfr: Net Vision v6.01 (SN 0101414290) device.model: ITYS 3 kVA device.serial: 3I14450043

On 02.10.2014 03:42, Charles Lepple wrote: > On Oct 1, 2014, at 5:07 AM, Tarvo.Tiits at automaatika.ee wrote: > >> Why is ups.status empty? > If I understand the commit log for SVN r3590, then that revision was supposed to set the status to OL if the numeric state was 9 for ECO mode. It does not appear to do that: > >

Hello i tried to connect my netys 2000 pr ups to ubuntu 11.10 and i have a problem connecting it. After readin a few post i realized to dianosse the connection. I need help resolving the connextion issue So here is the response to??/lib/nut/usbhid-ups -u root -DDDDD -a netys: Network UPS Tools - Generic HID driver 0.35 (2.6.1) USB communication driver 0.31 ? ?0.000000 ? ? send_to_all: SETINFO

Hi All, About a month ago APC announced they were including MODBUS protocol support in their new APC UPSes. The technical note on this is here: http://www.apcmedia.com/salestools/MPAO-98KJ7F/MPAO-98KJ7F_R0_EN.pdf "Application Note #176 Modbus Implementation in APC Smart-UPS" The APC "announcement" appeared on their site in their user blogs by an APC employee, here:

On Oct 1, 2014, at 5:07 AM, Tarvo.Tiits at automaatika.ee wrote: > Why is ups.status empty? If I understand the commit log for SVN r3590, then that revision was supposed to set the status to OL if the numeric state was 9 for ECO mode. It does not appear to do that: https://github.com/networkupstools/nut/commit/9cb2de3d9568aa382cc118b4385d97d5664c457b Is your UPS set to ECO mode? Can you do

Hello Ted, 2013/9/11 Ted Mittelstaedt <tedm at mittelstaedt.us> > Hi All, > > About a month ago APC announced they were including MODBUS protocol > support in their new APC UPSes. The technical note on this is here: > > http://www.apcmedia.com/**salestools/MPAO-98KJ7F/MPAO-**98KJ7F_R0_EN.pdf<http://www.apcmedia.com/salestools/MPAO-98KJ7F/MPAO-98KJ7F_R0_EN.pdf>

On a Friday in 2020, Marcel Juffermans wrote: >Hi there, > >Since upgrading to openSUSE 15.2 (which includes libvirt 6.0.0) the >virtual guests don't get their RBD disks made available to them. On >openSUSE 15.1 (which includes libvirt 5.1.0) that worked fine. The XML >is as follows: > [...] >I tried to strace libvirtd. The results are as follows: > >On

It's QEMU 4.2.1-lp152.9.6.1. I've tried updating it from the Open Build Service repos but there's too many version conflicts. Marcel On 26/10/20 9:02 pm, Ján Tomko wrote: > On a Friday in 2020, Marcel Juffermans wrote: >> Hi there, >> >> Since upgrading to openSUSE 15.2 (which includes libvirt 6.0.0) the >> virtual guests don't get their RBD disks

I got more information ,after enable log_level to 10: ``` push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 3 push_conn_ctx(0) : conn_ctx_stack_ndx = 2 setting sec ctx (0, 0) - sec_ctx_stack_ndx = 3 Security token: (NULL) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups Adding cache entry with key=[ACCT_POL/password history] and timeout=[Thu Jan 1 03:00:00 AM 1970 MSK]

Hi there, Since upgrading to openSUSE 15.2 (which includes libvirt 6.0.0) the virtual guests don't get their RBD disks made available to them. On openSUSE 15.1 (which includes libvirt 5.1.0) that worked fine. The XML is as follows: <domain type='xen' id='7'>   <name>mytwotel-a</name>   <uuid>a56daa5d-c095-49d5-ae1b-00b38353614e</uuid>  

http://www.core-sdi.com/advisories/ssh1_sessionkey_recovery.htm includes the line of code: kill(SIGALRM, getppid()); This is contained within what is listed as an "unsupported and untested patch" developed by SSH.com. The problem is that the arguments to "kill" are in the wrong order. In other words, to obtain the effect that was apparently intended, the line of code

Sure. ``` [global] workgroup = EXAMPLE server string = dns proxy = no interfaces = eth0 bind interfaces only = yes log file = /var/log/samba/log.%m max log size = 1000 # new options log level = 5 netbios name = FILES #panic action = /usr/share/samba/panic-action %d server role = STANDALONE SERVER local master = no security = user encrypt passwords =