[Bug 535583] Re: Excessive logging by apcsmart program

2011-04-21 Thread Launchpad Bug Tracker
[Expired for nut (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nut (Ubuntu)
   Status: Incomplete = Expired

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/535583

Title:
  Excessive logging by apcsmart program

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 535583] Re: Excessive logging by apcsmart program

2011-02-15 Thread Lupe Christoph
On Monday, 2011-02-14 at 21:54:20 -, Arnaud Quette wrote:
 I definitely need more info!
 please reply to ALL:

 - what is the exact model and date of manufacturing?

SmartUPS 300I NET. I have the serial number (GS9809283199) but no date.

 - are you sure this unit is ok?

You can't prove the absence of faults.

 - have you really checked the cabling or made the whole (cable + UPS) work
 somehow (using APC's software or apcupsd)?

Well, as I said this is working OK for days or weeks. Then something
happens that triggers a bug in apcsmart.

 - what is the meantime between occurrences of these issues?

I don;t have enough data. It's in the range of weeks or months.

 - is the device reachable (using upsc for example) between issues?

Sure, everything works fine.

 A driver debug output is really needed!

I'm running it again, but no promises. Reboots are much more frequent
than this misbehaviour.

 Note that I'm not the developer of this driver, nor have any acquaintance
 with APC.

Same here. Though I will probably try to locate this bug if we don;t
make progress with the debugging output, either because it does not tell
us enough or because I don't manage to capture it.

I would have thought finding the place in the code where it is trying to
reset the UPS connection wouldn't be this hard.

Lupe Christoph
-- 
| It is a well-known fact in any organisation that, if you want a job|
| done, you should give it to someone who is already very busy.  |
| Terry Pratchett, Unseen Academicals  |

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
https://bugs.launchpad.net/bugs/535583

Title:
  Excessive logging by apcsmart program

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 535583] Re: Excessive logging by apcsmart program

2011-02-14 Thread Arnaud Quette
I definitely need more info!
please reply to ALL:

- what is the exact model and date of manufacturing?
- are you sure this unit is ok?
- have you really checked the cabling or made the whole (cable + UPS) work
somehow (using APC's software or apcupsd)?
- what is the meantime between occurrences of these issues?
- is the device reachable (using upsc for example) between issues?

A driver debug output is really needed!
Note that I'm not the developer of this driver, nor have any acquaintance
with APC.

cheers
Arnaud

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
https://bugs.launchpad.net/bugs/535583

Title:
  Excessive logging by apcsmart program

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 535583] Re: Excessive logging by apcsmart program

2011-02-12 Thread Lupe Christoph
Of course after a reboot, I forgot to stop nut and start apcsmart
with debugging. :-( So when the problem reoccurred, I didn't get the
debug output.

But I ran strace of the apcsmart process, you might be able to
use that instead.

write(4, Y, 1)= -1 EIO (Input/output error)
sendto(3, 27Feb 13 00:18:03 apcsmart[321..., 87, MSG_NOSIGNAL, NULL, 0) = 87
select(7, [4 5 6], NULL, NULL, {1, 999837}) = 1 (in [4], left {1, 999835})
write(4, Y, 1)= -1 EIO (Input/output error)
sendto(3, 27Feb 13 00:18:03 apcsmart[321..., 87, MSG_NOSIGNAL, NULL, 0) = 87
select(7, [4 5 6], NULL, NULL, {1, 999839}) = 1 (in [4], left {1, 999837})
write(4, Y, 1)= -1 EIO (Input/output error)
sendto(3, 27Feb 13 00:18:03 apcsmart[321..., 87, MSG_NOSIGNAL, NULL, 0) = 87
select(7, [4 5 6], NULL, NULL, {1, 999818}) = 1 (in [4], left {1, 999816})
write(4, Y, 1)= -1 EIO (Input/output error)
sendto(3, 27Feb 13 00:18:03 apcsmart[321..., 87, MSG_NOSIGNAL, NULL, 0) = 87
select(7, [4 5 6], NULL, NULL, {1, 999757}) = 1 (in [4], left {1, 999755})
write(4, Y, 1)= -1 EIO (Input/output error)
sendto(3, 27Feb 13 00:18:03 apcsmart[321..., 87, MSG_NOSIGNAL, NULL, 0) = 87
select(7, [4 5 6], NULL, NULL, {1, 999838}) = 1 (in [4], left {1, 999836})
write(4, Y, 1)= -1 EIO (Input/output error)
sendto(3, 27Feb 13 00:18:03 apcsmart[321..., 87, MSG_NOSIGNAL, NULL, 0) = 87
select(7, [4 5 6], NULL, NULL, {1, 999845}) = 1 (in [4], left {1, 999843})
write(4, Y, 1)= -1 EIO (Input/output error)
sendto(3, 27Feb 13 00:18:03 apcsmart[321..., 87, MSG_NOSIGNAL, NULL, 0) = 87
select(7, [4 5 6], NULL, NULL, {1, 999845}) = 1 (in [4], left {1, 999843})

I have no idea why there is an IO error on the serial port. When I
restart apcsmart, it works OK. But it does not seem to handle the
EIO, it just goes on and on looking for input on /dev/ttyS2 and
/var/run/nut/apcsmart-ups (on two FDs), but then ignores the input
available on /dev/ttyS2.

The 'Y' command tells the UPS to enter smart mode. I can imagine this
is the normal mode of operation, and apcsmart has been thrown off track
and tries to re-engage, but the code that is supposed to do this is
faulty. Or maybe the UPS has dropped the connection. When I unplug the
cable, the trace is similar but different:

write(4, C, 1)= 1
nanosleep({0, 0}, NULL) = 0
select(5, [4], NULL, NULL, {3, 0})  = 1 (in [4], left {2, 891541})
read(4, 045.9\r\n, 64)= 7
write(4, P, 1)= 1
nanosleep({0, 0}, NULL) = 0
select(5, [4], NULL, NULL, {3, 0})  = 1 (in [4], left {2, 892849})
read(4, 017.6\r\n, 64)= 7
write(4, X, 1)= 1
nanosleep({0, 0}, NULL) = 0
select(5, [4], NULL, NULL, {3, 0})  = 1 (in [4], left {2, 957850})
read(4, N, 64)= 1

Cable is now unplugged.

select(5, [4], NULL, NULL, {3, 0})  = 0 (Timeout)
sendto(3, 28Feb 13 00:42:05 apcsmart[249..., 73, MSG_NOSIGNAL, NULL, 0) = 73
write(6, DATASTALE\n, 10) = 10
select(7, [4 5 6], NULL, NULL, {0, 0})  = 1 (in [6], left {0, 0})
read(6, PING\n, 512)  = 5
write(6, PONG\n, 5)   = 5
write(4, Y, 1)= 1
nanosleep({0, 0}, NULL) = 0
select(5, [4], NULL, NULL, {3, 0})  = 0 (Timeout)
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGCHLD, NULL, {SIG_DFL, [], 0}, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
nanosleep({1, 0}, 0x7fff2890ea60)   = 0
write(4, \33, 1)  = 1
nanosleep({0, 0}, NULL) = 0
select(5, [4], NULL, NULL, {3, 0})  = 0 (Timeout)
write(4, Y, 1)= 1
nanosleep({0, 0}, NULL) = 0
select(5, [4], NULL, NULL, {3, 0})  = 0 (Timeout)
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGCHLD, NULL, {SIG_DFL, [], 0}, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
nanosleep({1, 0}, 0x7fff2890ea60)   = 0
write(4, \33, 1)  = 1
nanosleep({0, 0}, NULL) = 0
select(5, [4], NULL, NULL, {3, 0})  = 0 (Timeout)
write(4, Y, 1)= 1
nanosleep({0, 0}, NULL) = 0
select(5, [4], NULL, NULL, {3, 0})  = 0 (Timeout)
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGCHLD, NULL, {SIG_DFL, [], 0}, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
nanosleep({1, 0}, 0x7fff2890ea60)   = 0
write(4, \33, 1)  = 1
nanosleep({0, 0}, NULL) = 0
select(5, [4], NULL, NULL, {3, 0})  = 0 (Timeout)
write(4, Y, 1)= 1
nanosleep({0, 0}, NULL) = 0
select(5, [4], NULL, NULL, {3, 0})  = 0 (Timeout)
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGCHLD, NULL, {SIG_DFL, [], 0}, 8) = 0

[Bug 535583] Re: Excessive logging by apcsmart program

2011-02-10 Thread Lupe Christoph
Since the supposed fix, I have had several ne incidents of this bug.

I'm now running Maverick Meerkat, and the log shows this:

Feb 10 14:10:14 alanya apcsmart[3238]: Communications with UPS lost: 
Communications with UPS lost - check cabling
Feb 10 14:10:14 alanya apcsmart[3238]: smartmode: ser_send_char failed: 
Input/output error
Feb 10 14:10:14 alanya apcsmart[3238]: last message repeated 9 times

... and nauseam, or until the /var/log partition fills up. The nut
package is up to data (2.4.3-1ubuntu5). Please reopen this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
https://bugs.launchpad.net/bugs/535583

Title:
  Excessive logging by apcsmart program

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 535583] Re: Excessive logging by apcsmart program

2011-02-10 Thread Arnaud Quette
Hi Christoph,

2011/2/10 Lupe Christoph

 Since the supposed fix, I have had several ne incidents of this bug.

 I'm now running Maverick Meerkat, and the log shows this:

 Feb 10 14:10:14 alanya apcsmart[3238]: Communications with UPS lost:
 Communications with UPS lost - check cabling
 Feb 10 14:10:14 alanya apcsmart[3238]: smartmode: ser_send_char failed:
 Input/output error
 Feb 10 14:10:14 alanya apcsmart[3238]: last message repeated 9 times

 ... and nauseam, or until the /var/log partition fills up. The nut
 package is up to data (2.4.3-1ubuntu5). Please reopen this bug.


could you please send us a driver debug output for investigation purpose.
Ie, after having stopped the running NUT instance, launch:
$ sudo /lib/nut/apcsmart -D -a device-id-from-ups.conf

let it run for a few seconds / minutes (at least, have a couple of issue
reproduction), then break using Ctrl+C. Don't forget to relaunch NUT then...

cheers,
Arnaud
-- 
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
https://bugs.launchpad.net/bugs/535583

Title:
  Excessive logging by apcsmart program

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


Re: [Bug 535583] Re: Excessive logging by apcsmart program

2011-02-10 Thread Lupe Christoph
On Thursday, 2011-02-10 at 14:54:34 -, Arnaud Quette wrote:
 2011/2/10 Lupe Christoph

 could you please send us a driver debug output for investigation purpose.
 Ie, after having stopped the running NUT instance, launch:
 $ sudo /lib/nut/apcsmart -D -a device-id-from-ups.conf

 let it run for a few seconds / minutes (at least, have a couple of issue
 reproduction), then break using Ctrl+C. Don't forget to relaunch NUT then...

Will do, but this can take a few days or even weeks.

Lupe Christoph
-- 
| It is a well-known fact in any organisation that, if you want a job|
| done, you should give it to someone who is already very busy.  |
| Terry Pratchett, Unseen Academicals  |

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
https://bugs.launchpad.net/bugs/535583

Title:
  Excessive logging by apcsmart program

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 535583] Re: Excessive logging by apcsmart program

2011-02-10 Thread Laurent Bigonville
** Changed in: nut (Ubuntu)
   Status: Fix Released = Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.
https://bugs.launchpad.net/bugs/535583

Title:
  Excessive logging by apcsmart program

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 535583] Re: Excessive logging by apcsmart program

2010-04-15 Thread Chuck Short
This should be fixed for lucid. Thanks for the bug report.

Regards
chuck

** Changed in: nut (Ubuntu)
   Status: Confirmed = Fix Released

-- 
Excessive logging by apcsmart program
https://bugs.launchpad.net/bugs/535583
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 535583] Re: Excessive logging by apcsmart program

2010-03-10 Thread Thierry Carrez
** Changed in: nut (Ubuntu)
   Importance: Undecided = Medium

** Changed in: nut (Ubuntu)
   Status: New = Confirmed

-- 
Excessive logging by apcsmart program
https://bugs.launchpad.net/bugs/535583
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs