thr3ads.net - Nut upsuser - [Nut-upsuser] MGE Pulsar M 3000 communication problems [Sep 2006]

If this information is useful, please help other people find it:
Share via:

Ingo Schaefer

2006-Sep-28 07:12 UTC

[Nut-upsuser] MGE Pulsar M 3000 communication problems

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

Second, because both ups and host have serial ports I tried to get it
working with serial.

The driver starts very fine, but takes a long time to detect the ups.

Upsd starts too, but while get in contact with the ups I am told:

Connected to UPS [mge3000-1]: mge-shut-ttyb
Synchronizing........ giving up

Starting upsmon is working as well, but I get strange communication
events from then.

suncore:root> Broadcast Message from nut (???) on suncore Wed Sep 27
15:47:42...Communications with UPS mge3000-1@localhost lost
Broadcast Message from nut (???) on suncore Wed Sep 27 15:47:52...
Communications with UPS mge3000-1@localhost established
Broadcast Message from nut (???) on suncore Wed Sep 27 15:48:12...
Communications with UPS mge3000-1@localhost lost
Broadcast Message from nut (???) on suncore Wed Sep 27 15:48:22...
Communications with UPS mge3000-1@localhost established
Broadcast Message from nut (???) on suncore Wed Sep 27 15:48:57...
Communications with UPS mge3000-1@localhost lost
Broadcast Message from nut (???) on suncore Wed Sep 27 15:49:12...
Communications with UPS mge3000-1@localhost established

Syslog shows:

Sep 27 15:32:08 suncore mge-shut[957]: [ID 702911 daemon.info] Startup
successful
Sep 27 15:32:08 suncore upsd[958]: [ID 702911 daemon.info] Connected to
UPS [mge3000-1]: mge-shut-ttyb
Sep 27 15:32:13 suncore upsd[959]: [ID 702911 daemon.info] Startup
successful
Sep 27 15:34:12 suncore upsd[959]: [ID 702911 daemon.notice] Data for
UPS [mge3000-1] is stale - check driver
Sep 27 15:34:26 suncore upsd[959]: [ID 702911 daemon.notice] UPS
[mge3000-1] data is no longer stale
Sep 27 15:34:38 suncore upsd[959]: [ID 702911 daemon.notice] Data for
UPS [mge3000-1] is stale - check driver
Sep 27 15:34:53 suncore upsd[959]: [ID 702911 daemon.notice] UPS
[mge3000-1] data is no longer stale
Sep 27 15:36:27 suncore upsd[959]: [ID 702911 daemon.notice] Data for
UPS [mge3000-1] is stale - check driver

Sep 27 15:48:07 suncore upsd[1504]: [ID 702911 daemon.notice] Data for
UPS [mge3000-1] is stale - check driver
Sep 27 15:48:12 suncore upsmon[1511]: [ID 702911 daemon.error] Poll UPS
[mge3000-1@localhost] failed - Data stale
Sep 27 15:48:12 suncore upsmon[1511]: [ID 702911 daemon.notice]
Communications with UPS mge3000-1@localhost lost
Sep 27 15:48:12 suncore wall: [ID 254490 auth.crit] dtlocal in utmpx is
not a tty
Sep 27 15:48:17 suncore upsmon[1511]: [ID 702911 daemon.error] Poll UPS
[mge3000-1@localhost] failed - Data stale
Sep 27 15:48:21 suncore upsd[1504]: [ID 702911 daemon.notice] UPS
[mge3000-1] data is no longer stale
Sep 27 15:48:22 suncore upsmon[1511]: [ID 702911 daemon.notice]
Communications with UPS mge3000-1@localhost established
Sep 27 15:48:22 suncore wall: [ID 254490 auth.crit] dtlocal in utmpx is
not a tty
Sep 27 15:48:57 suncore upsd[1504]: [ID 702911 daemon.notice] Data for
UPS [mge3000-1] is stale - check driver
Sep 27 15:48:57 suncore upsmon[1511]: [ID 702911 daemon.error] Poll UPS
[mge3000-1@localhost] failed - Data stale
Sep 27 15:48:57 suncore upsmon[1511]: [ID 702911 daemon.notice]
Communications with UPS mge3000-1@localhost lost
Sep 27 15:48:57 suncore wall: [ID 254490 auth.crit] dtlocal in utmpx is
not a tty
Sep 27 15:49:02 suncore upsmon[1511]: [ID 702911 daemon.error] Poll UPS
[mge3000-1@localhost] failed - Data stale
Sep 27 15:49:07 suncore upsmon[1511]: [ID 702911 daemon.error] Poll UPS
[mge3000-1@localhost] failed - Data stale
Sep 27 15:49:11 suncore upsd[1504]: [ID 702911 daemon.notice] UPS
[mge3000-1] data is no longer stale
Sep 27 15:49:12 suncore upsmon[1511]: [ID 702911 daemon.notice]
Communications with UPS mge3000-1@localhost established
Sep 27 15:49:12 suncore wall: [ID 254490 auth.crit] dtlocal in utmpx is
not a tty
Sep 27 15:49:23 suncore upsd[1504]: [ID 702911 daemon.notice] Data for
UPS [mge3000-1] is stale - check driver
Sep 27 15:49:24 suncore upsmon[1511]: [ID 702911 daemon.info] Signal 15:
exiting
Sep 27 15:49:24 suncore upsmon[1509]: [ID 702911 daemon.error] upsmon
parent: read: Bad file number
Sep 27 15:49:24 suncore upsd[1504]: [ID 702911 daemon.info] Client
monitor@127.0.0.1 logged out
Sep 27 15:49:26 suncore upsd[1504]: [ID 702911 daemon.info] Signal 15:
exiting
Sep 27 15:49:26 suncore mge-shut[1502]: [ID 702911 daemon.info] Signal
15: exiting

Anyone has an idea?

Regards,
Ingo
-- 
"Milchreis schmeckt hervorragend, wenn man ihn kurz vor dem Verzehr
durch ein saftiges Steak ersetzt."
                                         gefunden bei frag-mutti.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url :
http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20060928/b173d36c/attachment.pgp

Peter Selinger

2006-Sep-28 17:18 UTC

head link

[Nut-upsuser] MGE Pulsar M 3000 communication problems

Ingo Schaefer 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
Strange. Doesn't your Makefile contain a line "usb: build-usb"? 
Make
sure to do "make usb" in the main NUT directory, not in one of the
subdirectories such as drivers/. -- Peter
 > Second, because both ups and host have serial ports I tried to get it
> working with serial.
> 
> The driver starts very fine, but takes a long time to detect the ups.
> 
> Upsd starts too, but while get in contact with the ups I am told:
> 
> Connected to UPS [mge3000-1]: mge-shut-ttyb
> Synchronizing........ giving up
> 
> Starting upsmon is working as well, but I get strange communication
> events from then.
> 
> suncore:root> Broadcast Message from nut (???) on suncore Wed Sep 27
> 15:47:42...Communications with UPS mge3000-1@localhost lost
> Broadcast Message from nut (???) on suncore Wed Sep 27 15:47:52...
> Communications with UPS mge3000-1@localhost established
> Broadcast Message from nut (???) on suncore Wed Sep 27 15:48:12...
> Communications with UPS mge3000-1@localhost lost
> Broadcast Message from nut (???) on suncore Wed Sep 27 15:48:22...
> Communications with UPS mge3000-1@localhost established
> Broadcast Message from nut (???) on suncore Wed Sep 27 15:48:57...
> Communications with UPS mge3000-1@localhost lost
> Broadcast Message from nut (???) on suncore Wed Sep 27 15:49:12...
> Communications with UPS mge3000-1@localhost established
> 
> Syslog shows:
> 
> Sep 27 15:32:08 suncore mge-shut[957]: [ID 702911 daemon.info] Startup
> successful
> Sep 27 15:32:08 suncore upsd[958]: [ID 702911 daemon.info] Connected to
> UPS [mge3000-1]: mge-shut-ttyb
> Sep 27 15:32:13 suncore upsd[959]: [ID 702911 daemon.info] Startup
> successful
> Sep 27 15:34:12 suncore upsd[959]: [ID 702911 daemon.notice] Data for
> UPS [mge3000-1] is stale - check driver
> Sep 27 15:34:26 suncore upsd[959]: [ID 702911 daemon.notice] UPS
> [mge3000-1] data is no longer stale
> Sep 27 15:34:38 suncore upsd[959]: [ID 702911 daemon.notice] Data for
> UPS [mge3000-1] is stale - check driver
> Sep 27 15:34:53 suncore upsd[959]: [ID 702911 daemon.notice] UPS
> [mge3000-1] data is no longer stale
> Sep 27 15:36:27 suncore upsd[959]: [ID 702911 daemon.notice] Data for
> UPS [mge3000-1] is stale - check driver
> 
> Sep 27 15:48:07 suncore upsd[1504]: [ID 702911 daemon.notice] Data for
> UPS [mge3000-1] is stale - check driver
> Sep 27 15:48:12 suncore upsmon[1511]: [ID 702911 daemon.error] Poll UPS
> [mge3000-1@localhost] failed - Data stale
> Sep 27 15:48:12 suncore upsmon[1511]: [ID 702911 daemon.notice]
> Communications with UPS mge3000-1@localhost lost
> Sep 27 15:48:12 suncore wall: [ID 254490 auth.crit] dtlocal in utmpx is
> not a tty
> Sep 27 15:48:17 suncore upsmon[1511]: [ID 702911 daemon.error] Poll UPS
> [mge3000-1@localhost] failed - Data stale
> Sep 27 15:48:21 suncore upsd[1504]: [ID 702911 daemon.notice] UPS
> [mge3000-1] data is no longer stale
> Sep 27 15:48:22 suncore upsmon[1511]: [ID 702911 daemon.notice]
> Communications with UPS mge3000-1@localhost established
> Sep 27 15:48:22 suncore wall: [ID 254490 auth.crit] dtlocal in utmpx is
> not a tty
> Sep 27 15:48:57 suncore upsd[1504]: [ID 702911 daemon.notice] Data for
> UPS [mge3000-1] is stale - check driver
> Sep 27 15:48:57 suncore upsmon[1511]: [ID 702911 daemon.error] Poll UPS
> [mge3000-1@localhost] failed - Data stale
> Sep 27 15:48:57 suncore upsmon[1511]: [ID 702911 daemon.notice]
> Communications with UPS mge3000-1@localhost lost
> Sep 27 15:48:57 suncore wall: [ID 254490 auth.crit] dtlocal in utmpx is
> not a tty
> Sep 27 15:49:02 suncore upsmon[1511]: [ID 702911 daemon.error] Poll UPS
> [mge3000-1@localhost] failed - Data stale
> Sep 27 15:49:07 suncore upsmon[1511]: [ID 702911 daemon.error] Poll UPS
> [mge3000-1@localhost] failed - Data stale
> Sep 27 15:49:11 suncore upsd[1504]: [ID 702911 daemon.notice] UPS
> [mge3000-1] data is no longer stale
> Sep 27 15:49:12 suncore upsmon[1511]: [ID 702911 daemon.notice]
> Communications with UPS mge3000-1@localhost established
> Sep 27 15:49:12 suncore wall: [ID 254490 auth.crit] dtlocal in utmpx is
> not a tty
> Sep 27 15:49:23 suncore upsd[1504]: [ID 702911 daemon.notice] Data for
> UPS [mge3000-1] is stale - check driver
> Sep 27 15:49:24 suncore upsmon[1511]: [ID 702911 daemon.info] Signal 15:
> exiting
> Sep 27 15:49:24 suncore upsmon[1509]: [ID 702911 daemon.error] upsmon
> parent: read: Bad file number
> Sep 27 15:49:24 suncore upsd[1504]: [ID 702911 daemon.info] Client
> monitor@127.0.0.1 logged out
> Sep 27 15:49:26 suncore upsd[1504]: [ID 702911 daemon.info] Signal 15:
> exiting
> Sep 27 15:49:26 suncore mge-shut[1502]: [ID 702911 daemon.info] Signal
> 15: exiting
> 
> Anyone has an idea?
> 
> Regards,
> Ingo

Arnaud Quette

2006-Oct-03 14:12 UTC

head link

[Nut-upsuser] MGE Pulsar M 3000 communication problems

I should have started by this mail ;-)

2006/9/28, Ingo Schaefer <ingo@ingo-schaefer.de>:> Hallo,
>
> I installed nut 2.0.4 on a Solaris 8 and tried two things:
>
> ...
> Sep 27 15:49:23 suncore upsd[1504]: [ID 702911 daemon.notice] Data for
> UPS [mge3000-1] is stale - check driver
> Sep 27 15:49:24 suncore upsmon[1511]: [ID 702911 daemon.info] Signal 15:
> exiting
> Sep 27 15:49:24 suncore upsmon[1509]: [ID 702911 daemon.error] upsmon
> parent: read: Bad file number
> Sep 27 15:49:24 suncore upsd[1504]: [ID 702911 daemon.info] Client
> monitor@127.0.0.1 logged out
> Sep 27 15:49:26 suncore upsd[1504]: [ID 702911 daemon.info] Signal 15:
> exiting
> Sep 27 15:49:26 suncore mge-shut[1502]: [ID 702911 daemon.info] Signal
> 15: exiting
>
> Anyone has an idea?
Have a look at the mge-shut manpage, "KNOWN ISSUES" section.

Arnaud
-- 
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/

ingo@ingo-schaefer.de

2006-Oct-03 15:15 UTC

head link

[Nut-upsuser] MGE Pulsar M 3000 communication problems

Hello Arnaud and others,>I should have started by this mail ;-)
maybe ...
>Have a look at the mge-shut manpage, "KNOWN ISSUES" section.
I've had already done so and set the MAXAGE value to 45, notification is set
to 3 as suggested.

Today I set MAXAGE to exactly 25, but the error persists. 
Okay, not exactly. Now the "Synchronizing" on startup seem to work,
but after several seconds I get the "communication lost" errors again.

Regards,
Ingo

Reasonably Related Threads

Search for more seemingly similar threads

Nut upsuser - Sep 2006 - MGE Pulsar M 3000 communication problems

[Nut-upsuser] MGE Pulsar M 3000 communication problems

[Nut-upsuser] MGE Pulsar M 3000 communication problems

[Nut-upsuser] MGE Pulsar M 3000 communication problems

[Nut-upsuser] MGE Pulsar M 3000 communication problems

Reasonably Related Threads