On Tue, Jul 1, 2008 at 10:04 AM, Ercan Istek [EMAIL PROTECTED] wrote:
Jul 1 11:56:46 ginning upsd[10590]: Can't connect to UPS [tuncmatik]
(megatec-tuncmatik): Connection refused
Jul 1 11:56:46 ginning upsd[10590]: Data for UPS [tuncmatik] is stale -
check driver
Jul 1 11:56:46 ginning
Asking for UPS status [Q1]...
Q1 = OK [(214.5 214.5 220.1 030 49.9 2.22 41.5 ]
Calculated battery charge: 100.0%
Asking for UPS status [Q1]...
Q1 = OK [(214.5 214.5 220.1 030 49.9 2.22 41.5 ]
Calculated battery charge: 100.0%
*** stack smashing detected ***: megatec
On Wed, Jul 02, 2008 at 11:35:27AM +0300, Ercan Istek wrote:
Asking for UPS status [Q1]...
Q1 = OK [(214.5 214.5 220.1 030 49.9 2.22 41.5 ]
Calculated battery charge: 100.0%
Asking for UPS status [Q1]...
Q1 = OK [(214.5 214.5 220.1 030 49.9 2.22 41.5 ]
Calculated
Asking for UPS status [Q1]...
Q1 = OK [(214.5 214.5 220.1 030 49.9 2.22 41.5 ]
Calculated battery charge: 100.0%
Asking for UPS status [Q1]...
Q1 = OK [(214.5 214.5 220.1 030 49.9 2.22 41.5 ]
Calculated battery charge: 100.0%
*** stack smashing detected ***: megatec
Title: megatec process die
Jul 1 11:56:46 ginning upsd[10590]: Can't connect to UPS [tuncmatik] (megatec-tuncmatik): Connection refused
Jul 1 11:56:46 ginning upsd[10590]: Data for UPS [tuncmatik] is stale - check driver
Jul 1 11:56:46 ginning kernel: megatec[21553]: segfault at 100 ip
On Tue, Jul 1, 2008 at 10:04 AM, Ercan Istek [EMAIL PROTECTED] wrote:
Jul 1 11:56:46 ginning upsd[10590]: Can't connect to UPS [tuncmatik]
(megatec-tuncmatik): Connection refused
Jul 1 11:56:46 ginning upsd[10590]: Data for UPS [tuncmatik] is stale -
check driver
Jul 1 11:56:46 ginning
On Tue, Jul 1, 2008 at 2:22 PM, Ercan Istek [EMAIL PROTECTED] wrote:
Hello Carlos,
nut-client-2.2.2-1.fc9.i386
nut-2.2.2-1.fc9.i386
I am using Fedora 9
Linux ginning 2.6.25.4-30.fc9.i686 #1 SMP Wed May 21 18:12:35 EDT 2008 i686
i686 i386 GNU/Linux
Is the problem reproducible? How to
On Tue, Jul 1, 2008 at 2:47 PM, Ercan Istek [EMAIL PROTECTED] wrote:
Hello Carlos,
it occur 7-8 hour after i start nut.
megatec binary dies.
Without more information (a stack trace or something), it's kind of
difficult to find the problem. It can be a megatec issue, or an issue
with the
Like I said, this may be a problem with megatec, or it may not, so
please CC: the NUT mailing-list when you reply.
Please run the driver with -DDD at least. Does it terminate in the
same place everytime? Rebuilding the driver with debugging symbols on
and run it through valgrind would be useful
9 matches
Mail list logo