Yes, you did OK. Yes, it means something. I see exactly where it is crashing, but cannot imagine exactly why.
Now, please do the following: - Open a bug report with http://bugs.bacula.org - Upload your traceback - Be sure to specify your OS, what version of Bacula you are using and what SQL database (SQLite, MySQL, or PostgreSQL). - Run the Director once more manually, and when it stops, instead of getting the trace back, enter the following commands and put the results in a bugnote: thread 5 print *field print field->name print i On Wednesday 22 June 2005 00:38, Gary Kopp wrote: > Here's the gdb output running bacula-dir under the debugger. The > bconsole command was "list pools". I hope it means something to > somebody :-) And I also hope I'm posting this reply correctly... > > Starting program: /usr/sbin/bacula-dir -s -f -c > /etc/bacula/bacula-dir.conf > [Thread debugging using libthread_db enabled] > [New Thread 16384 (LWP 7309)] > [New Thread 32769 (LWP 7319)] > [New Thread 16386 (LWP 7320)] > [New Thread 32771 (LWP 7321)] > [New Thread 49156 (LWP 7396)] > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 49156 (LWP 7396)] > 0x080715aa in list_result (jcr=0x8d03770, mdb=0x8d04280, > send=0x8064d5c <prtit(void*, char const*)>, ctx=0x8d04130, > type=HORZ_LIST) > at sql.c:445 > 445 col_len = strlen(field->name); > Current language: auto; currently c++ > > Thread 5 (Thread 49156 (LWP 7396)): > #0 0x080715aa in list_result (jcr=0x8d03770, mdb=0x8d04280, > send=0x8064d5c <prtit(void*, char const*)>, ctx=0x8d04130, > type=HORZ_LIST) > at sql.c:445 > #1 0x08076399 in db_list_pool_records (jcr=0x8d03770, mdb=0x8d04280, > sendit=0x8064d5c <prtit(void*, char const*)>, ctx=0x8d04130, > type=HORZ_LIST) at sql_list.c:97 > #2 0x08064403 in do_list_cmd (ua=0x8d04130, cmd=0x8cfe120 "list pools", > > llist=HORZ_LIST) at ua_output.c:329 > #3 0x08063c77 in list_cmd (ua=0x8d04130, cmd=0x8cfe120 "list pools") > at ua_output.c:235 > #4 0x0805d6df in do_a_command (ua=0x8d04130, cmd=0x8cfe120 "list > pools") > at ua_cmds.c:161 > #5 0x0806c4e7 in handle_UA_client_request (arg=0x8d04148) at > ua_server.c:140 > #6 0x0808daee in workq_server (arg=0x80b3b80) at workq.c:347 > #7 0x0083de21 in pthread_start_thread () from /lib/i686/libpthread.so.0 > #8 0x0083dfb5 in pthread_start_thread_event () from > /lib/i686/libpthread.so.0 > #9 0x00cf5b1a in clone () from /lib/i686/libc.so.6 > > Thread 4 (Thread 32771 (LWP 7321)): > #0 0x00843ac6 in nanosleep () from /lib/i686/libpthread.so.0 > #1 0x00000001 in ?? () > #2 0x0083fb88 in __pthread_timedsuspend_new () from > /lib/i686/libpthread.so.0 > #3 0x0083c459 in pthread_cond_timedwait_relative () > from /lib/i686/libpthread.so.0 > #4 0x0808d398 in watchdog_thread (arg=0x0) at watchdog.c:289 > #5 0x0083de21 in pthread_start_thread () from /lib/i686/libpthread.so.0 > #6 0x0083dfb5 in pthread_start_thread_event () from > /lib/i686/libpthread.so.0 > #7 0x00cf5b1a in clone () from /lib/i686/libc.so.6 > > Thread 3 (Thread 16386 (LWP 7320)): > #0 0x00ceeef1 in select () from /lib/i686/libc.so.6 > #1 0x0000000a in ?? () > #2 0x08d0197c in ?? () > #3 0x01975330 in ?? () > #4 0x00000000 in ?? () > > Thread 2 (Thread 32769 (LWP 7319)): > #0 0x00cecb7a in poll () from /lib/i686/libc.so.6 > #1 0x0083cd5e in __pthread_manager () from /lib/i686/libpthread.so.0 > #2 0x0083d02a in __pthread_manager_event () from > /lib/i686/libpthread.so.0 > #3 0x00cf5b1a in clone () from /lib/i686/libc.so.6 > > Thread 1 (Thread 16384 (LWP 7309)): > #0 0x00843ac6 in nanosleep () from /lib/i686/libpthread.so.0 > #1 0x00000000 in ?? () > > -----Original Message----- > From: Kern Sibbald [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 21, 2005 3:42 PM > To: bacula-users@lists.sourceforge.net > Cc: Gary Kopp > Subject: Re: [Bacula-users] Newbie: Dir seg faults in bconsole > > On Tuesday 21 June 2005 21:26, Gary Kopp wrote: > > Just built and configured bacula 1.36.3 on RHEL 3, using MySQL 4.1. > > Tape tests, including multi-fill, worked fine. After starting bacula, > > I'm executing bconsole. Some commands will work fine, but at > > relatively > > > unpredictable times, with relatively unpredictable commands, bconsole > > will exit to the shell and the log will show a director seg fault. > > The > > > traceback, which to me doesn't seem to show anything of interest, is > > as > > > follows: > > > > Using host libthread_db library "/lib/libthread_db.so.1". > > [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP > > 7548)] [New Thread 32769 (LWP 7549)] [New Thread 16386 (LWP 7550)] > > [New > > > Thread 32771 (LWP 7551)] [New Thread 49156 (LWP 7555)] > > 0x0011dac6 in nanosleep () from /lib/i686/libpthread.so.0 > > $1 = "localhost-dir", '\0' <repeats 16 times> > > $2 = 0x95d0230 "bacula-dir" > > $3 = 0x95d0790 "/usr/sbin/bacula-dir" > > $4 = "MySQL" > > $5 = 0x80a201c "1.36.3 (22 April 2005)" > > $6 = 0x809ade2 "i686-redhat-linux-gnu" > > $7 = 0x809addb "redhat" > > $8 = 0x809adc8 "Enterprise release" > > #0 0x0011dac6 in nanosleep () from /lib/i686/libpthread.so.0 > > #1 0x00000000 in ?? () > > > > Thread 5 (Thread 49156 (LWP 7555)): > > #0 0x0011e1bb in waitpid () from /lib/i686/libpthread.so.0 > > #1 0x00375ae0 in ?? () > > #2 0x00000000 in ?? () > > > > Thread 4 (Thread 32771 (LWP 7551)): > > #0 0x0011dac6 in nanosleep () from /lib/i686/libpthread.so.0 > > #1 0x00000001 in ?? () > > #2 0x00119b88 in __pthread_timedsuspend_new () from > > /lib/i686/libpthread.so.0 > > #3 0x00116459 in pthread_cond_timedwait_relative () > > from /lib/i686/libpthread.so.0 > > #4 0x0808d398 in watchdog_thread (arg=0x0) at watchdog.c:289 > > #5 0x00117e21 in pthread_start_thread () from > > /lib/i686/libpthread.so.0 > > > #6 0x00517b1a in clone () from /lib/i686/libc.so.6 > > > > Thread 3 (Thread 16386 (LWP 7550)): > > #0 0x00510ef1 in select () from /lib/i686/libc.so.6 > > #1 0x00000006 in ?? () > > #2 0x095d797c in ?? () > > #3 0x01925370 in ?? () > > #4 0x00000000 in ?? () > > > > Thread 2 (Thread 32769 (LWP 7549)): > > #0 0x0050eb7a in poll () from /lib/i686/libc.so.6 > > #1 0x00116d5e in __pthread_manager () from /lib/i686/libpthread.so.0 > > #2 0x00517b1a in clone () from /lib/i686/libc.so.6 > > > > Thread 1 (Thread 16384 (LWP 7548)): > > #0 0x0011dac6 in nanosleep () from /lib/i686/libpthread.so.0 > > #1 0x00000000 in ?? () > > #0 0x0011dac6 in nanosleep () from /lib/i686/libpthread.so.0 No > > symbol > > > table info available. > > #1 0x00000000 in ?? () > > No symbol table info available. > > #0 0x00000000 in ?? () > > No symbol table info available. > > #0 0x00000000 in ?? () > > No symbol table info available. > > #0 0x00000000 in ?? () > > No symbol table info available. > > #0 0x00000000 in ?? () > > No symbol table info available. > > #0 0x00000000 in ?? () > > No symbol table info available. > > #0 0x00000000 in ?? () > > No symbol table info available. > > > > > > Can anyone give me suggestions on my next debugging step?? > > Manually run the Director under the debugger as documented in the Kaboom > > chapter. This will almost surely produce a good traceback. -- Best regards, Kern ("> /\ V_V ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
