Re: Bind 9 (Was: bsdstats) - fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0)

2009-07-28 Thread Anton Shterenlikht
On Mon, Jul 27, 2009 at 07:37:26PM -0800, Mel Flynn wrote:
 On Monday 27 July 2009 18:35:17 Marc G. Fournier wrote:
  --On Monday, July 27, 2009 14:07:44 -0800 Mel Flynn
 
  mel.flynn+fbsd.questi...@mailing.thruhere.net wrote:
   On Monday 27 July 2009 13:17:51 Anton Shterenlikht wrote:
   On ia64 8.0-beta1 SMP, running bsdstats-5.4_2,
   I get this error:
  
   # /usr/local/etc/periodic/monthly/300.statistics
   /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1023: fatal
   error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0) ?
   0
  
   : 34) == 0) failed
  
   That error from bind,
  
   [:1: unexpected operator
  
   Is not handled gracefully in the bsdstats script.
 
  Is there something I can do to improve the script to handle it better?
 
 Well, if OP can provide sh -x /usr/local/etc/periodic/monthly/300.statistics 
 output, it's easier to see which variable is empty as a result of a resolver 
 error. Then fix the test expression and either exit or use a retry_x_times 
 mechanism.

# script zzz sh -x /usr/local/etc/periodic/monthly/300.statistics -nodelay

Script started on Tue Jul 28 11:14:53 2009
+ [ -r /etc/defaults/periodic.conf ]
+ . /etc/defaults/periodic.conf
+ periodic_conf_files='/etc/periodic.conf /etc/periodic.conf.local'
+ local_periodic=/usr/local/etc/periodic
+ daily_output=root
+ daily_show_success=YES
+ daily_show_info=YES
+ daily_show_badconfig=NO
+ daily_clean_disks_enable=NO
+ daily_clean_disks_files='[#,]* .#* a.out *.core *.CKP .emacs_[0-9]*'
+ daily_clean_disks_days=3
+ daily_clean_disks_verbose=YES
+ daily_clean_tmps_enable=NO
+ daily_clean_tmps_dirs=/tmp
+ daily_clean_tmps_days=3
+ daily_clean_tmps_ignore='.X*-lock .X11-unix .ICE-unix .font-unix .XIM-unix'
+ daily_clean_tmps_ignore='.X*-lock .X11-unix .ICE-unix .font-unix .XIM-unix 
quota.user quota.group'
+ daily_clean_tmps_verbose=YES
+ daily_clean_preserve_enable=YES
+ daily_clean_preserve_days=7
+ daily_clean_preserve_verbose=YES
+ daily_clean_msgs_enable=YES
+ daily_clean_msgs_days=''
+ daily_clean_rwho_enable=YES
+ daily_clean_rwho_days=7
+ daily_clean_rwho_verbose=YES
+ daily_clean_hoststat_enable=YES
+ daily_backup_passwd_enable=YES
+ daily_backup_aliases_enable=YES
+ daily_calendar_enable=NO
+ daily_accounting_enable=YES
+ daily_accounting_compress=NO
+ daily_accounting_flags=-q
+ daily_accounting_save=3
+ daily_news_expire_enable=YES
+ daily_status_disks_enable=YES
+ daily_status_disks_df_flags='-l -h'
+ daily_status_zfs_enable=NO
+ daily_status_ata_raid_enable=NO
+ daily_status_gmirror_enable=NO
+ daily_status_graid3_enable=NO
+ daily_status_gstripe_enable=NO
+ daily_status_gconcat_enable=NO
+ daily_status_network_enable=YES
+ daily_status_network_usedns=YES
+ daily_status_rwho_enable=YES
+ daily_status_mailq_enable=YES
+ daily_status_mailq_shorten=NO
+ daily_status_include_submit_mailq=YES
+ daily_status_security_enable=YES
+ daily_status_mail_rejects_enable=YES
+ daily_status_mail_rejects_logs=3
+ daily_status_mail_rejects_shorten=NO
+ daily_status_named_enable=YES
+ daily_status_named_usedns=YES
+ daily_status_ntpd_enable=NO
+ daily_queuerun_enable=YES
+ daily_submit_queuerun=YES
+ daily_local=/etc/daily.local
+ daily_status_security_inline=NO
+ daily_status_security_output=root
+ daily_status_security_noamd=NO
+ daily_status_security_logdir=/var/log
+ daily_status_security_diff_flags='-b -u'
+ daily_status_security_chksetuid_enable=YES
+ daily_status_security_chkmounts_enable=YES
+ daily_status_security_chkuid0_enable=YES
+ daily_status_security_passwdless_enable=YES
+ daily_status_security_logincheck_enable=YES
+ daily_status_security_ipfwdenied_enable=YES
+ daily_status_security_ipfdenied_enable=YES
+ daily_status_security_pfdenied_enable=YES
+ daily_status_security_ipfwlimit_enable=YES
+ daily_status_security_ipf6denied_enable=YES
+ daily_status_security_kernelmsg_enable=YES
+ daily_status_security_loginfail_enable=YES
+ daily_status_security_tcpwrap_enable=YES
+ weekly_output=root
+ weekly_show_success=YES
+ weekly_show_info=YES
+ weekly_show_badconfig=NO
+ weekly_locate_enable=YES
+ weekly_whatis_enable=YES
+ weekly_catman_enable=NO
+ weekly_noid_enable=NO
+ weekly_noid_dirs=/
+ weekly_status_pkg_enable=NO
+ pkg_version=pkg_version
+ pkg_version_index=/usr/ports/INDEX-8
+ weekly_local=/etc/weekly.local
+ monthly_output=root
+ monthly_show_success=YES
+ monthly_show_info=YES
+ monthly_show_badconfig=NO
+ monthly_accounting_enable=YES
+ monthly_local=/etc/monthly.local
+ [ -z '' ]
+ source_periodic_confs_defined=yes
+ source_periodic_confs
+ local i sourced_files
+ sourced_files=:/etc/periodic.conf:
+ [ -r /etc/periodic.conf ]
+ . /etc/periodic.conf
+ monthly_statistics_enable=YES
+ monthly_statistics_report_devices=YES
+ monthly_statistics_report_ports=YES
+ sourced_files=:/etc/periodic.conf::/etc/periodic.conf.local:
+ [ -r /etc/periodic.conf.local ]
+ periodic_conf=/etc/periodic.conf
+ umask
+ oldmask=0022
+ umask 066
+ version=5.4
+ checkin_server=rpt.bsdstats.org
+ 

Re: Bind 9 (Was: bsdstats) - fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0)

2009-07-27 Thread Mel Flynn
On Monday 27 July 2009 13:17:51 Anton Shterenlikht wrote:
 On ia64 8.0-beta1 SMP, running bsdstats-5.4_2,
 I get this error:

 # /usr/local/etc/periodic/monthly/300.statistics
 /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1023: fatal
 error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0) ? 0
 : 34) == 0) failed

That error from bind,

 [:1: unexpected operator

Is not handled gracefully in the bsdstats script.

The annoyance is that ISC Bind finds it not useful to print errno, which is 
what you'd need to figure out why this lock can't be destroyed. It is however 
a programming error in bind, or a rare case of stack corruption by the kernel.

If you see this error a lot or can reliably reproduce it, I'd file a PR.
-- 
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Bind 9 (Was: bsdstats) - fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0)

2009-07-27 Thread Marc G. Fournier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



- --On Monday, July 27, 2009 14:07:44 -0800 Mel Flynn 
mel.flynn+fbsd.questi...@mailing.thruhere.net wrote:

 On Monday 27 July 2009 13:17:51 Anton Shterenlikht wrote:
 On ia64 8.0-beta1 SMP, running bsdstats-5.4_2,
 I get this error:

 # /usr/local/etc/periodic/monthly/300.statistics
 /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1023: fatal
 error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0) ? 0
 : 34) == 0) failed

 That error from bind,

 [:1: unexpected operator

 Is not handled gracefully in the bsdstats script.

Is there something I can do to improve the script to handle it better?



- -- 
Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org)
Email . scra...@hub.org  MSN . scra...@hub.org
Yahoo . yscrappy   Skype: hub.orgICQ . 7615664
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (FreeBSD)

iEYEARECAAYFAkpuY+UACgkQ4QvfyHIvDvOquwCdGpyNjkbx2e/jt9TB48RX6JrD
mJEAoL+l0a5UI3xCX/2/F+MJB5hPgIR/
=uH7U
-END PGP SIGNATURE-

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Bind 9 (Was: bsdstats) - fatal error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0)

2009-07-27 Thread Mel Flynn
On Monday 27 July 2009 18:35:17 Marc G. Fournier wrote:
 --On Monday, July 27, 2009 14:07:44 -0800 Mel Flynn

 mel.flynn+fbsd.questi...@mailing.thruhere.net wrote:
  On Monday 27 July 2009 13:17:51 Anton Shterenlikht wrote:
  On ia64 8.0-beta1 SMP, running bsdstats-5.4_2,
  I get this error:
 
  # /usr/local/etc/periodic/monthly/300.statistics
  /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/task.c:1023: fatal
  error: RUNTIME_CHECK(((pthread_mutex_destroy(((manager-lock))) == 0) ?
  0
 
  : 34) == 0) failed
 
  That error from bind,
 
  [:1: unexpected operator
 
  Is not handled gracefully in the bsdstats script.

 Is there something I can do to improve the script to handle it better?

Well, if OP can provide sh -x /usr/local/etc/periodic/monthly/300.statistics 
output, it's easier to see which variable is empty as a result of a resolver 
error. Then fix the test expression and either exit or use a retry_x_times 
mechanism.
-- 
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org