Hi Simon,
Can you reproduce this crash? If you are able to give us your data (full
event logs and source XML files) we'll be able to perform stress tedting on
our side. Of course, we guarantee that we'll not use this data except for
testing purposes.
I believe, this issue is fixed in the current development version of Sedna,
however there is no night builds with dtsearch support. I hope official
release will be soon.
Build 3.3.66dt fixes several critical bugs in dtsearch. Anyway, it's better
to use 3.3.66 than 3.3.58.
Ivan Shcheklein,
Sedna Team
On Wed, Jun 16, 2010 at 2:43 PM, Simon Kernthaler <[email protected]> wrote:
> We are running sedna with dtSearch functionality
> (sedna-3.3.58dt-bin-linux-i686.sh), and we had server crash.
>
> Contents of the fault directory are:
>
> fault-01-06-2010-14-06/
> ==================
> GOV1070.log
>
> SEDNA soft fault message:
> Failure in pping server (recv() call failed, one of the clients may be
> down).
>
> ==================
> SM1610.log
>
> SEDNA soft fault message:
> SEDNA GOVERNOR is down
>
> ==================
> TRN2797.log
>
> SEDNA soft fault message:
> SEDNA GOVERNOR is down
>
> (there are no error messages in the event log)
>
>
> Now I can't recover the database. I get the message:
>
> se...@symbols1:~$ se_sm sym
> Starting database recovery or hot-backup restoration...
> Database recovery in progress...
> SEDNA Message: ERROR SE4501
> Can't recover database by logical log
>
> SEDNA Message: ERROR SE4205
> Failed to run SM in the background mode (use '-background-mode off' for
> detailed diagnostics)
>
> There is a new fault directory with this file:
> GOV15761.log
>
> SEDNA soft fault message:
> Error, WaitForProcess failed
>
>
> The event log looks like:
>
> -- update insert
>
> (<instrument><id>I_DE000CG2TMB8</id><primary_symbol>EU^6401C</primary_symbol><isin>DE000CG2TMB8</isin><description>AEX
> 00317TLOPENC
>
> (NL0000000107)</description><type>5000</type><market_sector>279</market_sector><underlying>1Et,I:AEX</underlying><status>T</status><local_code>DE000CG2TMB8</local_code><exchange_symbol>6401C</exchange_symbol><market_code>XAM</market_code><lot_size>1.0,32</lot_size><quote
> currency='EUR'>EU^6401C</quote></instrument>) into
> index-scan("id","I_DE000CG2TMB8","EQ")/list
> LOG 01/06/2010 14:06:18 (TRN sym pid=2797 sid=49 trid=-1)
> [tr_common_funcs.cpp:on_transaction_end:356]: Transaction has been COMMITED
> LOG 01/06/2010 14:06:18 (TRN sym pid=2797 sid=49 trid=49)
> [tr_functions.cpp:on_user_statement_begin:101]: User query:
> --- index-scan ("id", "I_FR0117328445", "EQ")
> INFO 16/06/2010 09:25:21 (GOV pid=15761) [gov.cpp:main:237]: SEDNA
> version is 3.3.58
> INFO 16/06/2010 09:25:21 (GOV pid=15761)
> [gov_functions.cpp:log_out_system_information:81]: System: Linux
> 2.6.26-2-amd64 x86_64
> INFO 16/06/2010 09:25:21 (GOV pid=15761)
> [gmm.cpp:create_global_memory_mapping:126]: Layer address space start
> addr = 0x9a7b0000
> INFO 16/06/2010 09:25:21 (GOV pid=15761)
> [gmm.cpp:create_global_memory_mapping:127]: Layer address space
> boundary = 0xda7b0000
> LOG 16/06/2010 09:25:21 (GOV pid=15761) [gov.cpp:main:246]: Process
> ping server is ready
> LOG 16/06/2010 09:25:21 (GOV pid=15761)
> [listener.cpp:client_listener:68]: GOVERNOR is ready
> LOG 16/06/2010 09:25:34 (SM sym pid=15764) [sm.cpp:main:524]: Event
> log is ready
> LOG 16/06/2010 09:25:34 (SM sym pid=15764) [sm.cpp:main:537]: Ping
> client has been started
> LOG 16/06/2010 09:25:34 (SM sym pid=15764) [sm.cpp:main:543]: VMM
> region values determined
> SYS 16/06/2010 09:25:34 (SM sym pid=15764)
> [uprocess.c:uGetEnvironmentVariable:95]: getenv (code = 0): Success
> SYS 16/06/2010 09:25:34 (SM sym pid=15764)
> [uprocess.c:uGetEnvironmentVariable:95]: getenv (code = 0): Success
> LOG 16/06/2010 09:25:34 (SM sym pid=15764)
> [sm.cpp:recover_database_by_physical_and_logical_log:796]: Event log in
> recovery procedure is ready
> LOG 16/06/2010 09:25:34 (SM sym pid=15764)
> [sm.cpp:recover_database_by_physical_and_logical_log:800]:
> init_transaction_ids_table done
> LOG 16/06/2010 09:25:34 (SM sym pid=15764)
> [sm.cpp:recover_database_by_physical_and_logical_log:804]:
> init_checkpoint_sems done
> LOG 16/06/2010 09:25:34 (SM sym pid=15764)
> [sm.cpp:recover_database_by_physical_and_logical_log:806]: Starting
> database recovery or hot-backup restoration...
> LOG 16/06/2010 09:25:34 (SM sym pid=15764)
> [sm.cpp:recover_database_by_physical_and_logical_log:809]: logical log
> is started
> LOG 16/06/2010 09:25:34 (SM sym pid=15764)
> [sm.cpp:recover_database_by_physical_and_logical_log:824]:
> start_chekpoint_thread done
> SYS 16/06/2010 09:25:34 (SM sym pid=15764) [ummap.cpp:uMemLock:248]:
> mlock (code = 12): Cannot allocate memory
> WARN 16/06/2010 09:25:34 (SM sym pid=15764)
> [bm_functions.cpp:_bm_init_buffer_pool:138]: Can't lock memory. It is
> not supported without root, RLIMIT_MEMLOCK exceeded or there are not
> enough system resources.
> LOG 16/06/2010 09:25:35 (SM sym pid=15764)
> [sm.cpp:recover_database_by_physical_and_logical_log:846]: Buffer
> manager is started
> LOG 16/06/2010 09:25:36 (SM sym pid=15764)
> [sm.cpp:recover_database_by_physical_and_logical_log:853]: Database has
> been recovered by physical log successfully
> LOG 16/06/2010 09:25:36 (SM sym pid=15764)
> [blk_mngmt.cpp:extend_tmp_file:630]: Temp file has been extended, size:
> 6400000
> LOG 16/06/2010 09:25:36 (SM sym pid=15764)
> [sm.cpp:recover_database_by_physical_and_logical_log:862]: Checkpoints
> are disabled
> LOG 16/06/2010 09:25:36 (SM sym pid=15764)
> [sm.cpp:recover_database_by_physical_and_logical_log:866]:
> lm_table.init_lock_table done
> LOG 16/06/2010 09:25:36 (SM sym pid=15764)
> [sm.cpp:recover_database_by_physical_and_logical_log:888]: Wu is
> initialized
> LOG 16/06/2010 09:25:37 (RCV sym pid=15768) [tr.cpp:TRmain:248]:
> Session is ready
> ERROR 16/06/2010 09:33:28 (RCV sym pid=15768)
> [indexes.cpp:create_index:81]: (SE2033) Index with the same name already
> exists.
> INFO 16/06/2010 09:33:28 (SM sym pid=15764)
> [bm_core.cpp:bm_log_out_io_statistics:514]: IO block reads:4, writes:0
> LOG 16/06/2010 09:33:28 (RCV sym pid=15768) [tr.cpp:TRmain:602]:
> Session is closed
> ERROR 16/06/2010 09:33:37 (SM sym pid=15764)
> [trmgr.cpp:execute_recovery_by_logical_log_process:393]: (SE4501) Can't
> recover database by logical log
> ERROR 16/06/2010 09:33:37 (SM sym pid=15764)
> [sm.cpp:recover_database_by_physical_and_logical_log:940]: (SE4205)
> Failed to run SM in the background mode (use '-background-mode off' for
> detailed diagnostics)
>
> Any suggestions? It looks to me like there are two separate issues: the
> crash and the failure to recover from the logical log.
> Are either of these issues addressed in the newer 3.3.66 version? I am
> downloading it now.
>
> Thanks,
> Simon
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit. See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Sedna-discussion mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/sedna-discussion
>
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
lucky parental unit. See the prize list and enter to win:
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Sedna-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
