Background SEDNA version 3.4.66 on Ubuntu 10.10 >From time to time, after an Amazon instances has been shutdown, SEDNA fails to start properly.
I use a modified init.d script provided by Charles Foster to start and stop SEDNA. Command line Starting database recovery or hot-backup restoration... Database recovery in progress... SEDNA Message: FATAL ERROR in process [720] /home/ubuntu/sedna/bin/se_sm qbDb System error. This error means system malfunction. Cannot create data directory for soft fault logs Cannot create soft fault log ...... Log file INFO 11/11/2011 15:29:20 (GOV pid=536) [gov_functions.cpp:log_out_system_information:87]: SEDNA version is 3.4.66 (64bit Release) INFO 11/11/2011 15:29:20 (GOV pid=536) [gov_functions.cpp:log_out_system_information:95]: System: Linux 2.6.35-22-virtual x86_64 LOG 11/11/2011 15:29:20 (GOV pid=536) [gov.cpp:main:239]: Process ping server is ready LOG 11/11/2011 15:29:20 (GOV pid=536) [listener.cpp:client_listener:70]: GOVERNOR is ready LOG 11/11/2011 15:29:21 (SM qbDb pid=548) [sm.cpp:main:493]: Event log is ready LOG 11/11/2011 15:29:21 (SM qbDb pid=548) [sm.cpp:main:506]: Ping client has been started SYS 11/11/2011 15:29:21 (SM qbDb pid=548) [uprocess.c:uGetEnvironmentVariable:101]: getenv (code = 0): Success SYS 11/11/2011 15:29:21 (SM qbDb pid=548) [uprocess.c:uGetEnvironmentVariable:101]: getenv (code = 0): Success LOG 11/11/2011 15:29:21 (SM qbDb pid=548) [sm.cpp:recover_database_by_physical_and_logical_log:753]: Event log in recovery procedure is ready LOG 11/11/2011 15:29:21 (SM qbDb pid=548) [sm.cpp:recover_database_by_physical_and_logical_log:763]: Starting database recovery or hot-backup restoration... SYS 11/11/2011 15:29:21 (SM qbDb pid=548) [ummap.c:uMemLock:200]: mlock (code = 12): Cannot allocate memory WARN 11/11/2011 15:29:21 (SM qbDb pid=548) [bm_functions.cpp:_bm_init_buffer_pool:98]: Can't lock memory. It is not supported without root, RLIMIT_MEMLOCK exceeded or there are not enough system resources. LOG 11/11/2011 15:29:21 (SM qbDb pid=548) [sm.cpp:recover_database_by_physical_and_logical_log:803]: Buffer manager is started LOG 11/11/2011 15:30:10 (SM qbDb pid=548) [sm.cpp:recover_database_by_physical_and_logical_log:810]: Database has been recovered by physical log successfully LOG 11/11/2011 15:30:10 (SM qbDb pid=548) [blk_mngmt.cpp:extend_tmp_file:629]: Temp file has been extended, size: 6400000 LOG 11/11/2011 15:30:10 (SM qbDb pid=548) [sm.cpp:recover_database_by_physical_and_logical_log:822]: Checkpoints are disabled LOG 11/11/2011 15:30:10 (SM qbDb pid=548) [sm.cpp:recover_database_by_physical_and_logical_log:845]: Wu is initialized LOG 11/11/2011 15:30:10 (RCV qbDb pid=594) [tr.cpp:TRmain:182]: Session is ready ERROR 11/11/2011 15:30:13 (RCV qbDb pid=594) [vmm.cpp:vmm_remap:104]: (SE1035) Memory mapping error. INFO 11/11/2011 15:30:13 (SM qbDb pid=548) [bm_core.cpp:bm_log_out_io_statistics:521]: IO block reads:34, writes:0 LOG 11/11/2011 15:30:13 (RCV qbDb pid=594) [tr.cpp:TRmain:514]: Session is closed SYS 11/11/2011 15:30:14 (GOV pid=536) [uprocess.c:uWaitForChildProcess:495]: waitpid (code = 10): No child processes FATAL 11/11/2011 15:30:14 (GOV pid=536) [gov_table.cpp:wait_erase_session:133]: Error, WaitForProcess failed Questions Is there something I can do to recover from the failure? Is there a standard start and stop practice that should be utilized? Is this problem resolved in the newest SEDNA RC? Thanks, Malcolm ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Sedna-discussion mailing list Sedna-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sedna-discussion
