Re: [Nut-upsuser] upsd crashes with a broken pipe error
On 02/15/2011 03:48 PM, Zach La Celle wrote:
On 02/15/2011 03:27 PM, Arjen de Korte wrote:
Citeren Zach La Celle lace...@roboticresearch.com:
You can see where the problem happens in parseconf.c, on line 125
with the code:
/* resize the lists */
ctx-arglist = realloc(ctx-arglist,
sizeof(char *) * ctx-numargs);
With the given arguments, this boils down to
ctx-arglist = realloc(NULL, sizeof(char *));
This is all normal. Upon the first invocation of add_arg_word,
ctx-arglist will be a NULL pointer (since there is nothing in the
list yet). This should then allocate a one element array of a pointer
to char (to store the
If ptr is a null pointer, realloc() shall be equivalent to malloc()
for the specified size.
After that, all hell breaks loose, but that's out of our control.
There is a slight problem in lines 131-132
ctx-argsize = realloc(ctx-argsize, sizeof(int *) * ctx-numargs);
which should really read
ctx-argsize = realloc(ctx-argsize, sizeof(size_t) * ctx-numargs);
but I doubt that sizeof(size_t) will be smaller that sizeof(int *),
so this just wastes a few bytes of memory.
This also might help:
(gdb) p *ctx
$4 = {f = 0x0, state = 5, ch = 9, arglist = 0x0, argsize = 0x0,
numargs = 1, maxargs = 1, wordbuf = 0x61f2e0 Z, wordptr = 0x61f2fd
, wordbufsize = 16, linenum = 0, error = 0, errmsg = '\000'
repeats 255 times, errhandler = 0, magic = 7497264, arg_limit =
32, wordlen_limit = 512}
None of these values is suspect.
If I go up in GDB to the pconf_char function, here is the
character which is killing it:
(gdb) p ch
$6 = 9 '\t'
This is expected. Any whitespace character ends the collection of
characters for the current argument and will start a new one. Nothing
out of the ordinary. If it was, 100% of the NUT installations would
suffer the same problems as you're seeing 100% of the time they start
the upsd server. This is not the case and even in your case, the
problem seems to occur intermittently, which is more an indication
you're either running out of memory or the system is suffering from
bad memory. Did you run a memory check lately?
Best regards, Arjen
I will run memtest86 tonight when I can garner some time to bring the
server down. It has 4GB of memory and is currently utilizing only
500MB, so I doubt it runs out. Nothing else is crashing. It only
runs email and apache.
Thank you for your help,
-Zach
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
On the Dell server, the MpMemory testing all passed. It doesn't seem to
be a physical problem with the memory on the machine. I also ran some
other basic diagnostics on the disk drives, cache, and the rest of the
system, and it all passed as well.
Any further ideas?
Thanks,
-Zach
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
Citeren Zach La Celle lace...@roboticresearch.com: On the Dell server, the MpMemory testing all passed. It doesn't seem to be a physical problem with the memory on the machine. I also ran some other basic diagnostics on the disk drives, cache, and the rest of the system, and it all passed as well. Any further ideas? As a last resort, running the upsd server in 'valgrind' could be useful, but only if the error occurs shortly after startup. You'll have to run it with -D though, to prevent it from backgrounding. What remains weird is that you seem to be the only one that has this problem. I've run upsd in valgrind for days on end and have not seen any memory problems after that. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
On 02/16/2011 10:16 AM, Arjen de Korte wrote: Citeren Zach La Celle lace...@roboticresearch.com: On the Dell server, the MpMemory testing all passed. It doesn't seem to be a physical problem with the memory on the machine. I also ran some other basic diagnostics on the disk drives, cache, and the rest of the system, and it all passed as well. Any further ideas? As a last resort, running the upsd server in 'valgrind' could be useful, but only if the error occurs shortly after startup. You'll have to run it with -D though, to prevent it from backgrounding. What remains weird is that you seem to be the only one that has this problem. I've run upsd in valgrind for days on end and have not seen any memory problems after that. Best regards, Arjen Unfortunately, errors usually take days to occur. They also don't occur on a regular interval. I'm wondering if the serial port to the APC is giving weird values...although I'm not sure why that would cause a malloc error. -Zach ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
Resurrecting this problem, because I finally caught it in the debugger... Here's the trace, with some GDB prints. Please excuse the length. - ... 545815.397326 mainloop: polling 4 filedescriptors *** glibc detected *** /sbin/upsd: malloc(): memory corruption: 0x0061f300 *** === Backtrace: = /lib/libc.so.6(+0x775b6)[0x776ac5b6] /lib/libc.so.6(+0x7b6d8)[0x776b06d8] /lib/libc.so.6(__libc_malloc+0x6e)[0x776b158e] /sbin/upsd[0x408e91] /sbin/upsd[0x4091d9] /sbin/upsd[0x409431] /sbin/upsd[0x4097e2] /sbin/upsd[0x409bdb] /sbin/upsd[0x402a26] /sbin/upsd[0x403789] /lib/libc.so.6(__libc_start_main+0xfd)[0x77653c4d] /sbin/upsd[0x402079] === Memory map: 0040-0040e000 r-xp fb:00 8806463 /sbin/upsd 0060d000-0060e000 r--p d000 fb:00 8806463 /sbin/upsd 0060e000-0060f000 rw-p e000 fb:00 8806463 /sbin/upsd 0060f000-0063 rw-p 00:00 0 [heap] 7000-70021000 rw-p 00:00 0 70021000-7400 ---p 00:00 0 76dfd000-76e13000 r-xp fb:00 9093248 /lib/libgcc_s.so.1 76e13000-77012000 ---p 00016000 fb:00 9093248 /lib/libgcc_s.so.1 77012000-77013000 r--p 00015000 fb:00 9093248 /lib/libgcc_s.so.1 77013000-77014000 rw-p 00016000 fb:00 9093248 /lib/libgcc_s.so.1 77014000-7702 r-xp fb:00 5104002 /lib/libnss_files-2.11.1.so 7702-7721f000 ---p c000 fb:00 5104002 /lib/libnss_files-2.11.1.so 7721f000-7722 r--p b000 fb:00 5104002 /lib/libnss_files-2.11.1.so 7722-77221000 rw-p c000 fb:00 5104002 /lib/libnss_files-2.11.1.so 77221000-7722b000 r-xp fb:00 5104004 /lib/libnss_nis-2.11.1.so 7722b000-7742a000 ---p a000 fb:00 5104004 /lib/libnss_nis-2.11.1.so 7742a000-7742b000 r--p 9000 fb:00 5104004 /lib/libnss_nis-2.11.1.so 7742b000-7742c000 rw-p a000 fb:00 5104004 /lib/libnss_nis-2.11.1.so 7742c000-77434000 r-xp fb:00 5104000 /lib/libnss_compat-2.11.1.so 77434000-77633000 ---p 8000 fb:00 5104000 /lib/libnss_compat-2.11.1.so 77633000-77634000 r--p 7000 fb:00 5104000 /lib/libnss_compat-2.11.1.so 77634000-77635000 rw-p 8000 fb:00 5104000 /lib/libnss_compat-2.11.1.so 77635000-777af000 r-xp fb:00 5103992 /lib/libc-2.11.1.so 777af000-779ae000 ---p 0017a000 fb:00 5103992 /lib/libc-2.11.1.so 779ae000-779b2000 r--p 00179000 fb:00 5103992 /lib/libc-2.11.1.so 779b2000-779b3000 rw-p 0017d000 fb:00 5103992 /lib/libc-2.11.1.so 779b3000-779b8000 rw-p 00:00 0 779b8000-779c1000 r-xp fb:00 9093205 /lib/libwrap.so.0.7.6 779c1000-77bc ---p 9000 fb:00 9093205 /lib/libwrap.so.0.7.6 77bc-77bc1000 r--p 8000 fb:00 9093205 /lib/libwrap.so.0.7.6 77bc1000-77bc2000 rw-p 9000 fb:00 9093205 /lib/libwrap.so.0.7.6 77bc2000-77bc3000 rw-p 00:00 0 77bc3000-77bda000 r-xp fb:00 5103999 /lib/libnsl-2.11.1.so 77bda000-77dd9000 ---p 00017000 fb:00 5103999 /lib/libnsl-2.11.1.so 77dd9000-77dda000 r--p 00016000 fb:00 5103999 /lib/libnsl-2.11.1.so 77dda000-77ddb000 rw-p 00017000 fb:00 5103999 /lib/libnsl-2.11.1.so 77ddb000-77ddd000 rw-p 00:00 0 77ddd000-77dfd000 r-xp fb:00 9093254 /lib/ld-2.11.1.so 77fee000-77ff1000 rw-p 00:00 0 77ff8000-77ffb000 rw-p 00:00 0 77ffb000-77ffc000 r-xp 00:00 0 [vdso] 77ffc000-77ffd000 r--p 0001f000 fb:00 9093254 /lib/ld-2.11.1.so 77ffd000-77ffe000 rw-p 0002 fb:00 9093254 /lib/ld-2.11.1.so 77ffe000-77fff000 rw-p 00:00 0 7ffea000-7000 rw-p 00:00 0 [stack] ff60-ff601000 r-xp 00:00 0 [vsyscall] Program received signal SIGABRT, Aborted. 0x77668a75 in raise () from /lib/libc.so.6 (gdb) up #1 0x7766c5c0 in abort () from /lib/libc.so.6 (gdb) #2 0x776a24fb in ?? () from /lib/libc.so.6 (gdb) #3 0x776ac5b6 in ?? () from
Re: [Nut-upsuser] upsd crashes with a broken pipe error
Citeren Zach La Celle lace...@roboticresearch.com:
You can see where the problem happens in parseconf.c, on line 125
with the code:
/* resize the lists */
ctx-arglist = realloc(ctx-arglist,
sizeof(char *) * ctx-numargs);
With the given arguments, this boils down to
ctx-arglist = realloc(NULL, sizeof(char *));
This is all normal. Upon the first invocation of add_arg_word,
ctx-arglist will be a NULL pointer (since there is nothing in the
list yet). This should then allocate a one element array of a pointer
to char (to store the
If ptr is a null pointer, realloc() shall be equivalent to malloc()
for the specified size.
After that, all hell breaks loose, but that's out of our control.
There is a slight problem in lines 131-132
ctx-argsize = realloc(ctx-argsize, sizeof(int *) * ctx-numargs);
which should really read
ctx-argsize = realloc(ctx-argsize, sizeof(size_t) * ctx-numargs);
but I doubt that sizeof(size_t) will be smaller that sizeof(int *), so
this just wastes a few bytes of memory.
This also might help:
(gdb) p *ctx
$4 = {f = 0x0, state = 5, ch = 9, arglist = 0x0, argsize = 0x0,
numargs = 1, maxargs = 1, wordbuf = 0x61f2e0 Z, wordptr = 0x61f2fd
, wordbufsize = 16, linenum = 0, error = 0, errmsg = '\000'
repeats 255 times, errhandler = 0, magic = 7497264, arg_limit =
32, wordlen_limit = 512}
None of these values is suspect.
If I go up in GDB to the pconf_char function, here is the
character which is killing it:
(gdb) p ch
$6 = 9 '\t'
This is expected. Any whitespace character ends the collection of
characters for the current argument and will start a new one. Nothing
out of the ordinary. If it was, 100% of the NUT installations would
suffer the same problems as you're seeing 100% of the time they start
the upsd server. This is not the case and even in your case, the
problem seems to occur intermittently, which is more an indication
you're either running out of memory or the system is suffering from
bad memory. Did you run a memory check lately?
Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
2011/1/16 Zach La Celle lace...@roboticresearch.com
On 01/11/2011 03:38 AM, Arnaud Quette wrote:
Hi Zach,
2011/1/10 Zach La Celle lace...@roboticresearch.com
On 01/06/2011 08:06 AM, Arnaud Quette wrote:
2011/1/5 Zach La Celle lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
root@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0 port 3493
0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups
2.550554 User upsmon@127.0.0.1 logged into UPS [rack1ups]
*** glibc detected *** upsd: free(): invalid next size (fast):
0x012c9870 ***
Can you give us some background information about this system? What
OS
and version, who built the package, etc.
Just to be sure, are you running the Ubuntu-provided package, or
something from another package repository? Which version of Ubuntu?
Running valgrind might produce similarly opaque results without debug
symbols (which you can enable if you build from source).
debug syms are available as separate debs.
As an example, for Ubuntu, look here:
https://wiki.kubuntu.org/DebuggingProgramCrash
then look for installing {nut,libupsclient}-dbgsym and others if needed
otherwise...
That is a bit
more involved, though (especially if you want to keep the installed
files in the same place) so I'd try that after Arjen's suggestion with
-DDD.
seconded for a first run.
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/
The only extra package I could find is the dev package. I'm not
sure if that contains debugging symbols.
I'm running with the -DDD option now. It hasn't crashed over the
weekend, so we'll see how long it takes to crash now. I'm getting source to
try and rebuild it so that I can walk through in GDB if necessary.
have you looked at the pointer I've sent, *and* applied the various
mentioned actions (adding key and repository, refresh apt cache, ...)?
otherwise, you won't see these packages!
I still fail to see what is your exact system (Ubuntu? which version?)
apart from the arch which is x86_64...
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/
I'm having trouble finding the upsd source code, or maybe I just don't
understand how to run it properly. The source I have for ubuntu/lucid seems
to either be for a different UPSD project, or to run very differently than
the version off of the Ubuntu repositories. Can you point me to the correct
source for upsd?
to get the one for your binary, check that you have a deb-src line for
main in your /etc/apt/sources.list
then apt-get source nut
or get the source here: http://packages.ubuntu.com/maverick/nut
note that upsd package is a completely different project.
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/
I now have the upsd source package installed and built for debug, but when
I run upsd I get errors connecting to my UPS. I copied all of the
configuration files from my normal config directory (/etc/nut) into the new
directory (/usr/local/ups/etc/), but I get an Error; cannot find rack1ups;
no such file or directory or something along those lines. I've tried to
fix this myself but it just doesn't seem to be working. Any idea?
in order to have a source compilation working in a Debian / derivative env.,
you need to configure using the following flags:
./configure --prefix=/usr \
--exec-prefix=/ \
--sysconfdir=/etc/nut \
--mandir=/usr/share/man \
--libdir=/lib \
--includedir=/usr/include \
--without-ssl \
--with-hal \
--with-cgi \
--with-dev \
--enable-static \
--with-statepath=/var/run/nut \
--with-altpidpath=/var/run/nut \
--with-drvpath=/lib/nut \
--with-cgipath=/usr/lib/cgi-bin/nut \
--with-htmlpath=/usr/share/nut/www \
--with-pidpath=/var/run/nut \
--datadir=/usr/share/nut \
Re: [Nut-upsuser] upsd crashes with a broken pipe error
On 01/11/2011 03:38 AM, Arnaud Quette wrote:
Hi Zach,
2011/1/10 Zach La Celle lace...@roboticresearch.com
mailto:lace...@roboticresearch.com
On 01/06/2011 08:06 AM, Arnaud Quette wrote:
2011/1/5 Zach La Celle lace...@roboticresearch.com
mailto:lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
mailto:clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com
mailto:lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
root@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0 port 3493
0.000354 Connected to UPS [rack1ups]:
apcsmart-rack1ups
2.550554 User upsmon@127.0.0.1
mailto:upsmon@127.0.0.1 logged into UPS [rack1ups]
*** glibc detected *** upsd: free(): invalid next
size (fast):
0x012c9870 ***
Can you give us some background information about
this system? What OS
and version, who built the package, etc.
Just to be sure, are you running the Ubuntu-provided
package, or
something from another package repository? Which version
of Ubuntu?
Running valgrind might produce similarly opaque results
without debug
symbols (which you can enable if you build from source).
debug syms are available as separate debs.
As an example, for Ubuntu, look here:
https://wiki.kubuntu.org/DebuggingProgramCrash
then look for installing {nut,libupsclient}-dbgsym and
others if needed otherwise...
That is a bit
more involved, though (especially if you want to keep
the installed
files in the same place) so I'd try that after Arjen's
suggestion with
-DDD.
seconded for a first run.
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/
The only extra package I could find is the dev package.
I'm not sure if that contains debugging symbols.
I'm running with the -DDD option now. It hasn't crashed
over the weekend, so we'll see how long it takes to crash
now. I'm getting source to try and rebuild it so that I can
walk through in GDB if necessary.
have you looked at the pointer I've sent, *and* applied the
various mentioned actions (adding key and repository, refresh apt
cache, ...)?
otherwise, you won't see these packages!
I still fail to see what is your exact system (Ubuntu? which
version?) apart from the arch which is x86_64...
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/
I'm having trouble finding the upsd source code, or maybe I just
don't understand how to run it properly. The source I have for
ubuntu/lucid seems to either be for a different UPSD project, or
to run very differently than the version off of the Ubuntu
repositories. Can you point me to the correct source for upsd?
to get the one for your binary, check that you have a deb-src line
for main in your /etc/apt/sources.list
then apt-get source nut
or get the source here: http://packages.ubuntu.com/maverick/nut
note that upsd package is a completely different project.
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/
I now have the upsd source package installed and built for debug, but
when I run upsd I get errors connecting to my UPS. I copied all of the
configuration files from my normal config directory (/etc/nut) into the
new directory (/usr/local/ups/etc/), but I get an Error; cannot find
rack1ups; no such file or directory or something along those lines.
I've tried to fix this myself but it just doesn't seem to be working.
Any idea?
Re: [Nut-upsuser] upsd crashes with a broken pipe error
Hi Zach,
2011/1/10 Zach La Celle lace...@roboticresearch.com
On 01/06/2011 08:06 AM, Arnaud Quette wrote:
2011/1/5 Zach La Celle lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
r...@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0 port 3493
0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups
2.550554 User ups...@127.0.0.1 logged into UPS [rack1ups]
*** glibc detected *** upsd: free(): invalid next size (fast):
0x012c9870 ***
Can you give us some background information about this system? What
OS
and version, who built the package, etc.
Just to be sure, are you running the Ubuntu-provided package, or
something from another package repository? Which version of Ubuntu?
Running valgrind might produce similarly opaque results without debug
symbols (which you can enable if you build from source).
debug syms are available as separate debs.
As an example, for Ubuntu, look here:
https://wiki.kubuntu.org/DebuggingProgramCrash
then look for installing {nut,libupsclient}-dbgsym and others if needed
otherwise...
That is a bit
more involved, though (especially if you want to keep the installed
files in the same place) so I'd try that after Arjen's suggestion with
-DDD.
seconded for a first run.
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/
The only extra package I could find is the dev package. I'm not sure
if that contains debugging symbols.
I'm running with the -DDD option now. It hasn't crashed over the
weekend, so we'll see how long it takes to crash now. I'm getting source to
try and rebuild it so that I can walk through in GDB if necessary.
have you looked at the pointer I've sent, *and* applied the various
mentioned actions (adding key and repository, refresh apt cache, ...)?
otherwise, you won't see these packages!
I still fail to see what is your exact system (Ubuntu? which version?)
apart from the arch which is x86_64...
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/
I'm having trouble finding the upsd source code, or maybe I just don't
understand how to run it properly. The source I have for ubuntu/lucid seems
to either be for a different UPSD project, or to run very differently than
the version off of the Ubuntu repositories. Can you point me to the correct
source for upsd?
to get the one for your binary, check that you have a deb-src line for
main in your /etc/apt/sources.list
then apt-get source nut
or get the source here: http://packages.ubuntu.com/maverick/nut
note that upsd package is a completely different project.
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/
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
2011/1/5 Zach La Celle lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
r...@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0 port 3493
0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups
2.550554 User ups...@127.0.0.1 logged into UPS [rack1ups]
*** glibc detected *** upsd: free(): invalid next size (fast):
0x012c9870 ***
Can you give us some background information about this system? What
OS
and version, who built the package, etc.
Just to be sure, are you running the Ubuntu-provided package, or
something from another package repository? Which version of Ubuntu?
Running valgrind might produce similarly opaque results without debug
symbols (which you can enable if you build from source).
debug syms are available as separate debs.
As an example, for Ubuntu, look here:
https://wiki.kubuntu.org/DebuggingProgramCrash
then look for installing {nut,libupsclient}-dbgsym and others if needed
otherwise...
That is a bit
more involved, though (especially if you want to keep the installed
files in the same place) so I'd try that after Arjen's suggestion with
-DDD.
seconded for a first run.
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/
The only extra package I could find is the dev package. I'm not sure
if
that contains debugging symbols.
I'm running with the -DDD option now. It hasn't crashed over the
weekend, so we'll see how long it takes to crash now. I'm getting
source to
try and rebuild it so that I can walk through in GDB if necessary.
have you looked at the pointer I've sent, *and* applied the various
mentioned actions (adding key and repository, refresh apt cache, ...)?
otherwise, you won't see these packages!
I still fail to see what is your exact system (Ubuntu? which version?)
apart
from the arch which is x86_64...
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/
I'm sorry, I'll be more specific. I'm running Ubuntu Server, 10.04.
The problem has reoccurred with a little more information. It seems like
a particular query fails, which causes the crash.
I'm sorry to paste the entire printout, but I think it might help. I'm
not sure what mailing list etiquette is for attaching files.
264490.001405 write: [destfd=6] [len=34] [VAR rack1ups ups.status TRIM
OL]
264490.001440 mainloop: polling 3 filedescriptors
264490.338233 mainloop: polling 3 filedescriptors
264492.340332 mainloop: no data available
264492.340379 mainloop: polling 3 filedescriptors
264494.342463 mainloop: no data available
264494.342503 mainloop: polling 3 filedescriptors
264495.001776 write: [destfd=6] [len=34] [VAR rack1ups ups.status TRIM
OL]
264495.001817 mainloop: polling 3 filedescriptors
264497.003930 mainloop: no data available
264497.003984 mainloop: polling 3 filedescriptors
264497.148206 mainloop: polling 3 filedescriptors
264499.150306 mainloop: no data available
264499.150356 mainloop: polling 3 filedescriptors
264500.002191 write: [destfd=6] [len=34] [VAR rack1ups ups.status TRIM
OL]
264500.002228 mainloop: polling 3 filedescriptors
264502.004317 mainloop: no data available
264502.004371 mainloop: polling 3 filedescriptors
264502.348230 mainloop: polling 3 filedescriptors
264502.407564 Connect from **.**.**.**
264502.407607 mainloop: polling 4 filedescriptors
264502.407654 write: [destfd=7] [len=21] [ERR INVALID-ARGUMENT]
264502.407675 write: [destfd=7] [len=20] [ERR UNKNOWN-COMMAND]
264502.407690 mainloop: polling 4 filedescriptors
264503.118172 mainloop: polling 4 filedescriptors
264504.409126 Disconnect **.**.**.** (no data available)
264504.409170 Disconnect from **.**.**.**
264504.409209 mainloop: polling 3 filedescriptors
264505.002641 write: [destfd=6] [len=34] [VAR rack1ups ups.status TRIM
OL]
264505.002672 mainloop: polling 3 filedescriptors
264505.168211 mainloop: polling 3 filedescriptors
264506.218088 mainloop: polling 3 filedescriptors
264508.208199 mainloop: polling 3 filedescriptors
264509.148184 mainloop: polling 3 filedescriptors
264510.003107 write: [destfd=6] [len=34] [VAR rack1ups ups.status TRIM
OL]
264510.003153 mainloop: polling
Re: [Nut-upsuser] upsd crashes with a broken pipe error
On 01/06/2011 08:06 AM, Arnaud Quette wrote:
2011/1/5 Zach La Celle lace...@roboticresearch.com
mailto:lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
mailto:clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com
mailto:lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
r...@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0 port 3493
0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups
2.550554 User ups...@127.0.0.1
mailto:ups...@127.0.0.1 logged into UPS [rack1ups]
*** glibc detected *** upsd: free(): invalid next size
(fast):
0x012c9870 ***
Can you give us some background information about this
system? What OS
and version, who built the package, etc.
Just to be sure, are you running the Ubuntu-provided package, or
something from another package repository? Which version of
Ubuntu?
Running valgrind might produce similarly opaque results
without debug
symbols (which you can enable if you build from source).
debug syms are available as separate debs.
As an example, for Ubuntu, look here:
https://wiki.kubuntu.org/DebuggingProgramCrash
then look for installing {nut,libupsclient}-dbgsym and others if
needed otherwise...
That is a bit
more involved, though (especially if you want to keep the
installed
files in the same place) so I'd try that after Arjen's
suggestion with
-DDD.
seconded for a first run.
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/
The only extra package I could find is the dev package. I'm not
sure if that contains debugging symbols.
I'm running with the -DDD option now. It hasn't crashed over
the weekend, so we'll see how long it takes to crash now. I'm
getting source to try and rebuild it so that I can walk through in
GDB if necessary.
have you looked at the pointer I've sent, *and* applied the various
mentioned actions (adding key and repository, refresh apt cache, ...)?
otherwise, you won't see these packages!
I still fail to see what is your exact system (Ubuntu? which version?)
apart from the arch which is x86_64...
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/
I'm having trouble finding the upsd source code, or maybe I just don't
understand how to run it properly. The source I have for ubuntu/lucid
seems to either be for a different UPSD project, or to run very
differently than the version off of the Ubuntu repositories. Can you
point me to the correct source for upsd?
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
2011/1/5 Zach La Celle lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
r...@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0 port 3493
0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups
2.550554 User ups...@127.0.0.1 logged into UPS [rack1ups]
*** glibc detected *** upsd: free(): invalid next size (fast):
0x012c9870 ***
Can you give us some background information about this system? What OS
and version, who built the package, etc.
Just to be sure, are you running the Ubuntu-provided package, or
something from another package repository? Which version of Ubuntu?
Running valgrind might produce similarly opaque results without debug
symbols (which you can enable if you build from source).
debug syms are available as separate debs.
As an example, for Ubuntu, look here:
https://wiki.kubuntu.org/DebuggingProgramCrash
then look for installing {nut,libupsclient}-dbgsym and others if needed
otherwise...
That is a bit
more involved, though (especially if you want to keep the installed
files in the same place) so I'd try that after Arjen's suggestion with
-DDD.
seconded for a first run.
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/
The only extra package I could find is the dev package. I'm not sure if
that contains debugging symbols.
I'm running with the -DDD option now. It hasn't crashed over the
weekend, so we'll see how long it takes to crash now. I'm getting source to
try and rebuild it so that I can walk through in GDB if necessary.
have you looked at the pointer I've sent, *and* applied the various
mentioned actions (adding key and repository, refresh apt cache, ...)?
otherwise, you won't see these packages!
I still fail to see what is your exact system (Ubuntu? which version?) apart
from the arch which is x86_64...
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/
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
2011/1/4 Charles Lepple clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
r...@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0 port 3493
0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups
2.550554 User ups...@127.0.0.1 logged into UPS [rack1ups]
*** glibc detected *** upsd: free(): invalid next size (fast):
0x012c9870 ***
Can you give us some background information about this system? What OS
and version, who built the package, etc.
Just to be sure, are you running the Ubuntu-provided package, or
something from another package repository? Which version of Ubuntu?
Running valgrind might produce similarly opaque results without debug
symbols (which you can enable if you build from source).
debug syms are available as separate debs.
As an example, for Ubuntu, look here:
https://wiki.kubuntu.org/DebuggingProgramCrash
then look for installing {nut,libupsclient}-dbgsym and others if needed
otherwise...
That is a bit
more involved, though (especially if you want to keep the installed
files in the same place) so I'd try that after Arjen's suggestion with
-DDD.
seconded for a first run.
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/
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
On 12/29/2010 10:00 AM, Zach La Celle wrote: On 12/29/2010 08:34 AM, Charles Lepple wrote: On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote: I ran this in debug mode and captures the backtrace. r...@*:/etc/nut# upsd -D Network UPS Tools upsd 2.4.3 0.00 listening on 0.0.0.0 port 3493 0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups 2.550554 User ups...@127.0.0.1 logged into UPS [rack1ups] *** glibc detected *** upsd: free(): invalid next size (fast): 0x012c9870 *** Can you give us some background information about this system? What OS and version, who built the package, etc. Do you have valgrind available? Your version of glibc probably has some more thorough memory corruption detection algorithms than the default - man malloc on one of my systems suggests that setting the MALLOC_CHECK_ environment variable to either 1 or 2 will print some additional diagnostics. Output of uname -a: Linux www 2.6.32-27-server #49-Ubuntu SMP Thu Dec 2 02:05:21 UTC 2010 x86_64 GNU/Linux Information about glibc: GNU C Library (Ubuntu EGLIBC 2.11.1-0ubuntu7.6) stable release version 2.11.1, by Roland McGrath et al. Compiled by GNU CC version 4.4.3. Compiled on a Linux 2.6.24-28-server system on 2010-11-17. I didn't know about that MALLOC_CHECK_ variable: I've set it and am running the software again to see if I get a better error. I can install valgrind if necessary. Let me see what happens this time. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser After setting the variable, the only further information I have is this: upsd: free(): invalid pointer: 0x0 1d20f30 *** Segmentation fault I'll install valgrind and see if I can catch any memory leaks that way: otherwise, I'm not sure exactly what else to do. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
Citeren Zach La Celle lace...@roboticresearch.com: After setting the variable, the only further information I have is this: upsd: free(): invalid pointer: 0x01d20f30 *** Segmentation fault Try again with debug level set to -DDD. This might provide a little more context of where this occurs. Best regards, Arjen PS You're not attempting to run a 32-bit version of the server here, are you? -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle lace...@roboticresearch.com wrote: On 12/29/2010 10:00 AM, Zach La Celle wrote: On 12/29/2010 08:34 AM, Charles Lepple wrote: On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote: I ran this in debug mode and captures the backtrace. r...@*:/etc/nut# upsd -D Network UPS Tools upsd 2.4.3 0.00 listening on 0.0.0.0 port 3493 0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups 2.550554 User ups...@127.0.0.1 logged into UPS [rack1ups] *** glibc detected *** upsd: free(): invalid next size (fast): 0x012c9870 *** Can you give us some background information about this system? What OS and version, who built the package, etc. Just to be sure, are you running the Ubuntu-provided package, or something from another package repository? Which version of Ubuntu? Running valgrind might produce similarly opaque results without debug symbols (which you can enable if you build from source). That is a bit more involved, though (especially if you want to keep the installed files in the same place) so I'd try that after Arjen's suggestion with -DDD. -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote: I ran this in debug mode and captures the backtrace. r...@*:/etc/nut# upsd -D Network UPS Tools upsd 2.4.3 0.00 listening on 0.0.0.0 port 3493 0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups 2.550554 User ups...@127.0.0.1 logged into UPS [rack1ups] *** glibc detected *** upsd: free(): invalid next size (fast): 0x012c9870 *** Can you give us some background information about this system? What OS and version, who built the package, etc. Do you have valgrind available? Your version of glibc probably has some more thorough memory corruption detection algorithms than the default - man malloc on one of my systems suggests that setting the MALLOC_CHECK_ environment variable to either 1 or 2 will print some additional diagnostics. -- Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
On 12/29/2010 08:34 AM, Charles Lepple wrote: On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote: I ran this in debug mode and captures the backtrace. r...@*:/etc/nut# upsd -D Network UPS Tools upsd 2.4.3 0.00 listening on 0.0.0.0 port 3493 0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups 2.550554 User ups...@127.0.0.1 logged into UPS [rack1ups] *** glibc detected *** upsd: free(): invalid next size (fast): 0x012c9870 *** Can you give us some background information about this system? What OS and version, who built the package, etc. Do you have valgrind available? Your version of glibc probably has some more thorough memory corruption detection algorithms than the default - man malloc on one of my systems suggests that setting the MALLOC_CHECK_ environment variable to either 1 or 2 will print some additional diagnostics. Output of uname -a: Linux www 2.6.32-27-server #49-Ubuntu SMP Thu Dec 2 02:05:21 UTC 2010 x86_64 GNU/Linux Information about glibc: GNU C Library (Ubuntu EGLIBC 2.11.1-0ubuntu7.6) stable release version 2.11.1, by Roland McGrath et al. Compiled by GNU CC version 4.4.3. Compiled on a Linux 2.6.24-28-server system on 2010-11-17. I didn't know about that MALLOC_CHECK_ variable: I've set it and am running the software again to see if I get a better error. I can install valgrind if necessary. Let me see what happens this time. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
I ran this in debug mode and captures the backtrace. r...@*:/etc/nut# upsd -D Network UPS Tools upsd 2.4.3 0.00 listening on 0.0.0.0 port 3493 0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups 2.550554 User ups...@127.0.0.1 logged into UPS [rack1ups] *** glibc detected *** upsd: free(): invalid next size (fast): 0x012c9870 *** === Backtrace: = /lib/libc.so.6(+0x775b6)[0x7f4b09d1c5b6] /lib/libc.so.6(cfree+0x73)[0x7f4b09d22e83] upsd[0x4094f8] upsd[0x40230d] upsd[0x402b9c] upsd[0x4036f9] /lib/libc.so.6(__libc_start_main+0xfd)[0x7f4b09cc3c4d] upsd[0x401fe9] === Memory map: 0040-0040d000 r-xp fb:00 8808105 /sbin/upsd 0060c000-0060d000 r--p c000 fb:00 8808105 /sbin/upsd 0060d000-0060e000 rw-p d000 fb:00 8808105 /sbin/upsd 012bc000-012dd000 rw-p 00:00 0 [heap] 7f4b0400-7f4b04021000 rw-p 00:00 0 7f4b04021000-7f4b0800 ---p 00:00 0 7f4b0946d000-7f4b09483000 r-xp fb:00 9093248 /lib/libgcc_s.so.1 7f4b09483000-7f4b09682000 ---p 00016000 fb:00 9093248 /lib/libgcc_s.so.1 7f4b09682000-7f4b09683000 r--p 00015000 fb:00 9093248 /lib/libgcc_s.so.1 7f4b09683000-7f4b09684000 rw-p 00016000 fb:00 9093248 /lib/libgcc_s.so.1 7f4b09684000-7f4b0969 r-xp fb:00 9093407 /lib/libnss_files-2.11.1.so 7f4b0969-7f4b0988f000 ---p c000 fb:00 9093407 /lib/libnss_files-2.11.1.so 7f4b0988f000-7f4b0989 r--p b000 fb:00 9093407 /lib/libnss_files-2.11.1.so 7f4b0989-7f4b09891000 rw-p c000 fb:00 9093407 /lib/libnss_files-2.11.1.so 7f4b09891000-7f4b0989b000 r-xp fb:00 9093362 /lib/libnss_nis-2.11.1.so 7f4b0989b000-7f4b09a9a000 ---p a000 fb:00 9093362 /lib/libnss_nis-2.11.1.so 7f4b09a9a000-7f4b09a9b000 r--p 9000 fb:00 9093362 /lib/libnss_nis-2.11.1.so 7f4b09a9b000-7f4b09a9c000 rw-p a000 fb:00 9093362 /lib/libnss_nis-2.11.1.so 7f4b09a9c000-7f4b09aa4000 r-xp fb:00 9093361 /lib/libnss_compat-2.11.1.so 7f4b09aa4000-7f4b09ca3000 ---p 8000 fb:00 9093361 /lib/libnss_compat-2.11.1.so 7f4b09ca3000-7f4b09ca4000 r--p 7000 fb:00 9093361 /lib/libnss_compat-2.11.1.so 7f4b09ca4000-7f4b09ca5000 rw-p 8000 fb:00 9093361 /lib/libnss_compat-2.11.1.so 7f4b09ca5000-7f4b09e1f000 r-xp fb:00 9093404 /lib/libc-2.11.1.so 7f4b09e1f000-7f4b0a01e000 ---p 0017a000 fb:00 9093404 /lib/libc-2.11.1.so 7f4b0a01e000-7f4b0a022000 r--p 00179000 fb:00 9093404 /lib/libc-2.11.1.so 7f4b0a022000-7f4b0a023000 rw-p 0017d000 fb:00 9093404 /lib/libc-2.11.1.so 7f4b0a023000-7f4b0a028000 rw-p 00:00 0 7f4b0a028000-7f4b0a031000 r-xp fb:00 9093205 /lib/libwrap.so.0.7.6 7f4b0a031000-7f4b0a23 ---p 9000 fb:00 9093205 /lib/libwrap.so.0.7.6 7f4b0a23-7f4b0a231000 r--p 8000 fb:00 9093205 /lib/libwrap.so.0.7.6 7f4b0a231000-7f4b0a232000 rw-p 9000 fb:00 9093205 /lib/libwrap.so.0.7.6 7f4b0a232000-7f4b0a233000 rw-p 00:00 0 7f4b0a028000-7f4b0a031000 r-xp fb:00 9093205 /lib/libwrap.so.0.7.6 7f4b0a031000-7f4b0a23 ---p 9000 fb:00 9093205 /lib/libwrap.so.0.7.6 7f4b0a23-7f4b0a231000 r--p 8000 fb:00 9093205 /lib/libwrap.so.0.7.6 7f4b0a231000-7f4b0a232000 rw-p 9000 fb:00 9093205 /lib/libwrap.so.0.7.6 7f4b0a232000-7f4b0a233000 rw-p 00:00 0 7f4b0a233000-7f4b0a24a000 r-xp fb:00 9093353 /lib/libnsl-2.11.1.so 7f4b0a24a000-7f4b0a449000 ---p 00017000 fb:00 9093353 /lib/libnsl-2.11.1.so 7f4b0a449000-7f4b0a44a000 r--p 00016000 fb:00 9093353 /lib/libnsl-2.11.1.so 7f4b0a44a000-7f4b0a44b000 rw-p 00017000 fb:00 9093353 /lib/libnsl-2.11.1.so 7f4b0a44b000-7f4b0a44d000 rw-p 00:00 0 7f4b0a44d000-7f4b0a46d000 r-xp fb:00 9093354 /lib/ld-2.11.1.so 7f4b0a66-7f4b0a663000 rw-p 00:00 0 7f4b0a669000-7f4b0a66c000 rw-p 00:00 0 7f4b0a66c000-7f4b0a66d000 r--p 0001f000 fb:00 9093354 /lib/ld-2.11.1.so 7f4b0a66d000-7f4b0a66e000 rw-p 0002 fb:00 9093354 /lib/ld-2.11.1.so 7f4b0a66e000-7f4b0a66f000 rw-p 00:00 0 7fffd1c8a000-7fffd1c9f000 rw-p 00:00 0 [stack] 7fffd1dff000-7fffd1e0 r-xp 00:00 0 [vdso]
