Thomas,
The return from ACCT_STAT and ENTRIES where size is NULL is the empty set.
Here is the additional stack:
(gdb) where
#0 0x00007f218c4e18e5 in raise () from /lib64/libc.so.6
#1 0x00007f218c4e30c5 in abort () from /lib64/libc.so.6
#2 0x00007f218c51f7f7 in __libc_message () from /lib64/libc.so.6
#3 0x00007f218c525126 in malloc_printerr () from /lib64/libc.so.6
#4 0x00007f218c528ba4 in _int_malloc () from /lib64/libc.so.6
#5 0x00007f218c529951 in malloc () from /lib64/libc.so.6
#6 0x00007f218d39b772 in my_malloc (size=30924, my_flags=30924) at
/export/home/pb2/build/sb_0-10188268-1378800052.79/rpm/BUILD/mysql-5.6.14/mysql-5.6.14/mysys/my_malloc.c:38
#7 0x00007f218d399cce in alloc_root (mem_root=0x23207d0, length=<value
optimized out>) at
/export/home/pb2/build/sb_0-10188268-1378800052.79/rpm/BUILD/mysql-5.6.14/mysql-5.6.14/mysys/my_alloc.c:224
#8 0x00007f218d3712ee in cli_read_rows (mysql=0x65d200, mysql_fields=0x0,
fields=7) at
/export/home/pb2/build/sb_0-10188268-1378800052.79/rpm/BUILD/mysql-5.6.14/mysql-5.6.14/sql-common/client.c:1530
#9 0x00007f218d373979 in cli_read_query_result (mysql=0x65d200) at
/export/home/pb2/build/sb_0-10188268-1378800052.79/rpm/BUILD/mysql-5.6.14/mysql-5.6.14/sql-common/client.c:4120
#10 0x00007f218d36fbd6 in mysql_real_query (mysql=0x65d200, query=<value
optimized out>, length=<value optimized out>)
at
/export/home/pb2/build/sb_0-10188268-1378800052.79/rpm/BUILD/mysql-5.6.14/mysql-5.6.14/sql-common/client.c:4157
#11 0x00000000004348d9 in _db_exec_sql ()
#12 0x0000000000434649 in ListMgr_GetVar ()
#13 0x000000000041c263 in ChgLogRdr_StoreStats ()
#14 0x00000000004033c1 in dump_stats.clone.1 ()
#15 0x00000000004039fd in stats_thr ()
#16 0x000000000040492a in main ()
Thank you for your assistance,
Dan Milroy
From: LEIBOVICI Thomas [mailto:[email protected]]
Sent: Tuesday, January 7, 2014 3:24 AM
To: Daniel Milroy
Cc: [email protected]; Peter A Ruprecht
Subject: Re: [robinhood-support] Segfault and error in updating database entries
1) Regarding the DB update errors, I think there is a wrong 'size' value
somewhere in the DB
that creates troubles to build the accounting table.
This might be a 'NULL' value for the size of an entry.
First, you can check that there is no such records in ACCT_STAT:
select * from ACCT_STAT where size is NULL;
And in ENTRIES too (much more longer request...):
select * from ENTRIES where size is NULL;
2) Regarding the segfault, I need more stack
(for example, this can be obtained by typing 'where' in gdb.)
regards,
On 12/31/13 19:10, Daniel Milroy wrote:
Hello,
After completing an initial scan to populate the robinhood database, I've run
into some problems running the application as a daemon. The robinhood host is
running robinhood 2.4.3, and Lustre client 2.4.2 on RHEL 6.4. Robinhood will
segfault and dump core after running for between 1 and 3 days. Nothing is
written to /var/log/messages or dmesg. The core files vary in size from
22MB-17GB and contain the following information:
[New Thread 30924]
[New Thread 30931]
[New Thread 30929]
[New Thread 30932]
[New Thread 30934]
[New Thread 30930]
[New Thread 30926]
[New Thread 30928]
[New Thread 30937]
[New Thread 30935]
[New Thread 30933]
Reading symbols from /usr/lib64/libmysqlclient.so.18...done.
Loaded symbols for /usr/lib64/libmysqlclient.so.18
Reading symbols from /lib64/libpthread.so.0...(no debugging symbols
found)...done.
[Thread debugging using libthread_db enabled]
Loaded symbols for /lib64/libpthread.so.0
Reading symbols from /lib64/libm.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib64/libm.so.6
Reading symbols from /lib64/librt.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib64/librt.so.1
Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib64/libdl.so.2
Reading symbols from /usr/lib64/liblustreapi.so...done.
Loaded symbols for /usr/lib64/liblustreapi.so
Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib64/libc.so.6
Reading symbols from /usr/lib64/libstdc++.so.6...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib64/libstdc++.so.6
Reading symbols from /lib64/libgcc_s.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib64/libgcc_s.so.1
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /lib64/libnss_files.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libnss_files.so.2
Reading symbols from /lib64/libnss_sss.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libnss_sss.so.2
Core was generated by `/usr/sbin/robinhood -d -f
/etc/robinhood.d/tmpfs/robinhood_janus.conf -p /var/r'.
Program terminated with signal 6, Aborted.
#0 0x00007f218c4e18e5 in raise () from /lib64/libc.so.6
On a possibly related note, there are thousands of the following entries in
robinhood.log:
2013/12/31 10:53:37 robinhood@jana[2716/8]: ListMgr | Error 1 executing query
'UPDATE ENTRIES SET
owner='user12',gr_name='user12grp',size=9026,blocks=24,last_access=1388512416,last_mod=1388512416,type='file',md_update=1388512417,whitelisted=0,release_class='@default@',rel_cl_update=1388512417
WHERE id='0x210a18513:0x19e15:0x0'': Out of range value for column 'sz1K' at
row 1
2013/12/31 10:53:37 robinhood@jana[2716/8]: ListMgr | Unhandled error 1264:
default conversion to DB_REQUEST_FAILED
2013/12/31 10:53:37 robinhood@jana[2716/8]: EntryProc | Error 7 performing
database operation.
2013/12/31 10:53:37 robinhood@jana[2716/7]: ListMgr | Unhandled error 1264:
default conversion to DB_REQUEST_FAILED
I followed the instructions in "Re: [robinhood-devel] RBH DB Fail - Out of
range value for column 'sz1k'" and dropped the ACCT_STAT table. After
rebuilding the table the errors continue, and now include several other
columns. Would upgrading to robinhood 2.5.0 be advisable?
Please let me know if I can provide additional information that may be helpful
to the diagnosis of these problems.
Thank you in advance,
Dan Milroy
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
robinhood-support mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/robinhood-support
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support
