similar to: MGE Pulsar M 3000 communication problems

I'm running nut 2.0.1 with an MGE pulsar evolution 3000 with the mge-utalk (serial) driver on NetBSD 3.1 . I had a very strange occurance in my basement datacenter this early AM. the following was logged by upslog: 20080219 023452 100.0 123.0 049.0 [OL CHRG] NA 60.00 20080219 023522 100.0 122.8 049.0 [OL CHRG] NA 60.00 20080219 023552 098.0 123.0 049.0 [OL DISCHRG] NA 60.00 20080219 023622

Greetings Experts! Sorry for my poor english, but I?m inside of a terrible nightmare!!! I?m using Samba+LDAP has about 2 months ago without problems, but in the last 4 hours, the system is absolutelly unstable. I couldn?t upgrade or patched anything. The problem simply has appeared. Principally system characteristics: - Sun Fire V880 running Solaris 9 - openldap-2.2.23 - nss_ldap-232 -

Hello all, I'm running samba 2.2.4 on Sun Solaris version Sunos 5.8 generic_108528-17, Samba version 2.2.4 I'm getting this error in my /var/adm/messages and don't know what it means, I suspect it is also responsible for causing the delays in the application running from the shares. Jun 8 14:53:53 krypton nmbd[3096]: [ID 702911 daemon.error] query_name_response: Multiple (2)

Hi I've compiled and installed 2.2.5 on a Solaris 2.8 box. When attempting to browse the workgroup, a popup messages is displayed: Simple is not accessible. A device attached to the system is not functioning If I check the log file, the following error messages show up: ............ Jul 3 10:08:26 serv03 smbd[1544]: [ID 702911 daemon.error] [2002/07/03 10:08:26, 0]

What does this mean? >Feb 19 07:58:11 apophis upsmon[533]: [ID 702911 daemon.alert] Master privileges unavailable on UPS [ups@apophis] >Feb 19 07:58:11 apophis upsmon[533]: [ID 702911 daemon.alert] Reason: Access denied And is it normal for my UPS (APC SmartUPS 620) to drop into battery mode for a few seconds every day or so? Or is this a main supply glitch? Nothing else in the house

Good day oh technical ones . I was running Samba 4 (client only, not using it as a DC so effectively running Samba 3 code from the Samba 4 tree) and, other than a little "Gotcha!" regarding decoding Kerberos PACs, it was all working perfectly. Then recently I had to upgrade, to "4.2.0pre1-GIT-b505111" (I had to upgrade the OS on the server

I recently upgraded from Samba v3.6.25 to v4.3.3. After the upgrade, I realized I should change my smb.conf because the syslog parameters are deprecated. My old parameters were: log level = 1 syslog = 6 syslog only = yes Also, I built Samba with --with-syslog-facility=LOG_LOCAL7. I'm having trouble replicating the same configuration with v4.3.3. The syslog

Hi all, I have an error message that pops up every time someone connects to my Samba server. All day long I get these messages from smbd: Dec 28 07:27:24 srv-pvcs smbd[638]: [ID 702911 daemon.error] [2004/12/28 07:27:24, 0] smbd/service.c:(252) Dec 28 07:27:24 srv-pvcs smbd[638]: [ID 702911 daemon.error] rhunt1-pc (162.18.178.237) couldn't find service o The last part, "couldn't

Hello, Rsync is working great for me right now, using version 2.6.5 on two Solaris 9 V100 servers. Box A is the source and box B is the destination, and also box B is my rsync server box. Box A is a rsync client. Yesterdar from Box B I pulled 250 meg just fine from box A with rsync. Today from the client I want to just copy over to the server what files have changed today. So my command

Hello, My MGE Pulsar Evolution 800 had some hardware troubles (it may be the batteries according to the manual). The fault was not detected so the power was cut to the load and nothing appears in the log files. Arnaud: do you know if the UPS have some way to report this kind of troubles to the PC so that NUT can handle it with a shutdown sequence ? Philippe

Hello, I'm trying to communicate with a MGE Pulsar STS 16 using nut under Linux, but I've had no luck so far. I haven't saw it supported in the doc, so if there's anything I can try... Thanks, Arnaud. -- Perso: http://launay.org/blog/ H?bergement: http://www.nocworld.com/

I have an MGE Pulsar Evolution 1100 connected to a Debian box, with nut-2.0.1 (the standard "sarge" packages). I have it connected through USB, and I'm using newhidups. However, about once a day the driver looses contact with the UPS and I have to restart NUT to get it to drop the "data stale" nonsense (it happens more often than this, but most times it recovers without

(Sorry, I accidentally discarded the wrong message in the moderation queue - please subscribe to the list to avoid this in the future.) > From: <onyx at netfusion.fr> > Subject: [HCL] MGE Pulsar Evolution 1100 - not recognized by USB driver > Date: December 22, 2011 12:15:16 AM EST > To: <nut-upsuser at lists.alioth.debian.org> > > > Hi everybody, > > It

Hi all, Have been using Nut on Linux for over ten years now and find it brilliant. Thanks. Just upgraded to 2.4.2 and have the 5 or 6 models of UPS's that we use (apcsmart, megatec, mge-shut, surgemax, digitus) all working including the MGE Pulsar Evolution 1100 on a USB connection using the usbhid-ups driver. Running on SLES9. Old but we still have a few servers out there running

On 9/28/06, Ingo Schaefer <ingo@ingo-schaefer.de> wrote: > Hallo, > > I installed nut 2.0.4 on a Solaris 8 and tried two things: > > First I wanted the ups to connect via usb, but I could not compile the > usb drivers. Make usb told me: no target named usb found Do you have libusb installed? (I was not aware that there was a port of libusb for versions of Solaris before

Hi, My UPS is MGE Pulsar Ellipse Premium 1200VA, connected on USB port, usbhid-ups driver. Using simply KNotify about UPS connection states I noticed that sometimes unpredictably a notification appears that the USB connection to the UPS is lost and a few seconds later another notification appears that the connection is restored. And this repeats to infinity. The only way to get out of it is to

Hello all, I wonder if the improvements to a driver called "newmge-shut" which have been mentioned in October 06 got it to the 2.0.5 release? I tried my setup again with this release and still get this "communication lost -> established -> lost -> established" cycle. USB was not working because of the Solaris 8 installation. Regards, Ingo -------------- next part

Hi, I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the mge-shut driver but I'm having some problems. It appears to init OK but I can't, say, turn the outlets off, eg.. harrow:~>upsc mge@localhost battery.charge: 78 battery.charge.low: 20 battery.runtime: 05760 driver.name: mge-shut driver.parameter.port: /dev/cuad1 driver.version: 2.0.3 driver.version.internal: 0.65

hello, I tested all config with my ups and psp all seems to be OK now, I had change ups name and user name in ups.conf, upsd.users, upsmon.conf etc etc ... but I have quickly these events in my syslog without doing anyting what can I do ? Nov 15 11:09:22 mezenc upsmon[3865]: Poll UPS [pm2200 at localhost] failed - Data stale thanks a lot for your help Sabine GOUDARD Ecole Nationale

I am running NUT 2.2.0 compiled from the FreeBSD ports tree. [inchoate 14:50] ~ >upsc ups1 at localhost battery.charge: 59 battery.charge.low: 20 battery.charge.restart: 0 battery.runtime: 6350 battery.type: PbAc battery.voltage: 43.0 driver.name: usbhid-ups driver.parameter.offdelay: 120 driver.parameter.ondelay: 13 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: