From alexey@REDACTED Mon Dec 15 14:05:27 2003 From: alexey@REDACTED (Alexey Shchepin) Date: Mon, 15 Dec 2003 15:05:27 +0200 Subject: Mnesia crash Message-ID: <8765gigrjc.fsf@office.sevcom.net> Hi! Few days ago there was power failure on jabber.ru with working ejabberd. After system was started, ejabberd loaded without problems. But yesterday, after restarting using init:restart(), the following errors appears in log: =ERROR REPORT==== 2003-12-15 00:12:21 === ** dets: Bug was found when accessing table roster, ** dets: operation was {lookup_keys,[{"xxxxx", {"xxxxxxxxx","icq.jabber.ru",[]}}]} and reply was {1,'EXIT'}. =ERROR REPORT==== 2003-12-15 00:12:22 === Mnesia('ejabberd@REDACTED'): ** ERROR ** (core dumped to file: "/usr/home/ermine/server/ejabberd/src/MnesiaCore.ejabberd@REDACTED") ** FATAL ** mnesia_locker crashed: {badarg, [{erlang, '++', [{badarith, [{dets_v9,slot_position,1}, {dets_v9,eval_work_list,2}, {dets,update_cache,2}, {dets,stream_end,5}, {dets,do_apply_op,4}, {proc_lib,init_p,5}]}, [{roster, {"xxxxx", {"xxxxxxxx", "icq.jabber.ru", []}}, "xxxxx", ... {lists,append,2}, {mnesia_locker, set_read_lock_on_all_keys, 6}, {mnesia_locker,loop,1}, {mnesia_sp,init_proc,4}, {proc_lib,init_p,5}]} state: [<0.85.0>] Is this is because of previous crash, or this is bug in dets or mnesia? Information that probably needed: Erlang version: R9C OS: FreeBSD 4.9 Result of mnesia:schema(roster): -- Properties for roster table --- access_mode -> read_write active_replicas -> ['ejabberd@REDACTED'] arity -> 10 attributes -> [uj,user,jid,name,subscription,ask,groups,xattrs,xs] checkpoints -> [] commit_work -> [{index,set,[{3,{dets,{roster,index,3}}}]}] cookie -> {{1067,256640,401479},'ejabberd@REDACTED'} disc_copies -> [] disc_only_copies -> ['ejabberd@REDACTED'] frag_properties -> [] index -> [3] load_by_force -> false load_node -> 'ejabberd@REDACTED' load_order -> 0 load_reason -> local_only local_content -> false master_nodes -> [] memory -> 30050014 ram_copies -> [] record_name -> roster record_validation -> {roster,10,set} setorbag -> set size -> 131139 snmp -> [] storage_type -> disc_only_copies subscribers -> [] user_properties -> [] version -> {{4,0},{'ejabberd@REDACTED',{1067,260145,62112}}} where_to_commit -> [{'ejabberd@REDACTED',disc_only_copies}] where_to_read -> 'ejabberd@REDACTED' where_to_write -> ['ejabberd@REDACTED'] wild_pattern -> {roster,'_','_','_','_','_','_','_','_','_'} {index,3} -> {roster,index,3} MnesiaCore contains some private info, so I not include it here (I can send it to one of Erlang developers). From eleberg@REDACTED Mon Dec 15 19:28:09 2003 From: eleberg@REDACTED (eleberg@REDACTED) Date: Mon, 15 Dec 2003 19:28:09 +0100 (MET) Subject: documentation-bug Message-ID: <200312151828.hBFIS9F01735@wsb017.uab.ericsson.se> greetings, MODULE calendar has 2 errors. 1 a typo in time_to_secnds(Time) -> Secs this should be time_to_seconds(Time) -> Secs 2 wrong return value in datetime_to_gregorian_seconds(DateTime) -> Days this should be datetime_to_gregorian_seconds(DateTime) -> Seconds please accept my apologies if this is my browser mangeling perfectly good text replies, if any, go to bengt.kleberg@REDACTED bengt From alexey@REDACTED Fri Dec 19 10:57:18 2003 From: alexey@REDACTED (Alexey Shchepin) Date: Fri, 19 Dec 2003 11:57:18 +0200 Subject: beam got SIGSEGV Message-ID: <87iskdjfk1.fsf@office.sevcom.net> Hi! Hour ago ejabberd on jabber.ru get SIGSEGV: This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... Core was generated by `beam'. Program terminated with signal 11, Segmentation fault. ... (gdb) bt #0 0x80ba22e in erts_deep_process_dump () #1 0x80b9a23 in erts_deep_process_dump () #2 0x80b97fd in erts_deep_process_dump () #3 0x80b2069 in erl_crash_dump () #4 0x807164f in erl_exit () #5 0x80818f4 in make_hash2 () #6 0x80a55e0 in db_get_hash () #7 0x809a5ce in ets_lookup_2 () #8 0x80be03b in process_main () #9 0x8071573 in erl_start () #10 0x806319c in main () #11 0x80630ee in _start () Also erl_crash.dump was created, which starts with following lines: =erl_crash_dump:0.1 Fri Dec 19 11:22:26 2003 Slogan: Invalid tag in make_hash2(0x0) System version: Erlang (BEAM) emulator version 5.3 [source] [hipe] I can send URLs to core dump and erl_crash.dump to one of Erlang developers. BEAM was started with "+Mea r10b" options. From alexey@REDACTED Mon Dec 22 12:16:18 2003 From: alexey@REDACTED (Alexey Shchepin) Date: Mon, 22 Dec 2003 13:16:18 +0200 Subject: beam got SIGSEGV In-Reply-To: <87iskdjfk1.fsf@office.sevcom.net> (Alexey Shchepin's message of "Fri, 19 Dec 2003 11:57:18 +0200") References: <87iskdjfk1.fsf@office.sevcom.net> Message-ID: <87r7yx897j.fsf@office.sevcom.net> Hi! AS> Hi! Hour ago ejabberd on jabber.ru get SIGSEGV: [...] AS> BEAM was started with "+Mea r10b" options. FYI: this bug is reproducible without this option. Now I have few erl_crash.dump files, which ends with something like this: =proc_heap:<0.8173.0> C675BF8:lHFFFFFFFF|HC2B0178 After dumping of this line, erlang process got SIGSEGV. All core dumps have same backtrace as in my previous message. From alexey@REDACTED Mon Dec 22 10:58:56 2003 From: alexey@REDACTED (Alexey Shchepin) Date: Mon, 22 Dec 2003 11:58:56 +0200 Subject: beam got SIGSEGV In-Reply-To: <87iskdjfk1.fsf@office.sevcom.net> (Alexey Shchepin's message of "Fri, 19 Dec 2003 11:57:18 +0200") References: <87iskdjfk1.fsf@office.sevcom.net> Message-ID: <87r7yx897j.fsf@office.sevcom.net> Hi! AS> Hi! Hour ago ejabberd on jabber.ru get SIGSEGV: [...] AS> BEAM was started with "+Mea r10b" options. FYI: this bug is reproducible without this option. Now I have few erl_crash.dump files, which ends with something like this: =proc_heap:<0.8173.0> C675BF8:lHFFFFFFFF|HC2B0178 After dumping of this line, erlang process got SIGSEGV. All core dumps have same backtrace as in my previous message.