-------- Original Message --------
Subject: smbstatus getting a SIGBUS error
Date: Thu, 08 Jun 2000 13:52:13 +0700
From: Arnold Troeger <stssart@bkk.unocal.com>
To: samba-bugs@samba.org
CC: arnold.troeger@bkk.unocal.com
I'm running Samba 2.0.7 and have been having a few problems with it.
Just to keep things focused, I'll stick with smbstatus as this one has
been the longest lasting problem. The problem: smbstatus functions
normally for some small bit of time after the samba daemons are
started. At some point after a significant number of users have
connected to the Samba server, smbstatus starts crashing with a bus
error. In this state, it will report on the connections but fails when
looking at the locks. I had a go at running gdb on the program and have
located the point of failure in "locking_shm.c" in the
shm_share_forall
routine: line 636
(gdb) s
shm_offset2addr (offset=1096040751) at ../locking/shmem_sysv.c:154
154 if (offset == 0 )
(gdb) s
157 if (!shm_header_p)
(gdb) s
160 return (void *)((char *)shm_header_p + offset);
(gdb) s
161 }
(gdb) s
shm_share_forall (fn=0x136b4 <print_share_mode>)
at ../locking/locking_shm.c:634
634 while(entry_scanner_p != 0) {
(gdb) s
636 if
(process_exists(entry_scanner_p->e.pid)) {
(gdb) s
Program received signal SIGBUS, Bus error.
0x17b88 in shm_share_forall (fn=0x136b4 <print_share_mode>)
at ../locking/locking_shm.c:636
636 if
(process_exists(entry_scanner_p->e.pid)) {
(gdb)
My Samba server is an E4000 with 6 CPUs running Solaris 2.6 and set up
with 1.3 TeraBytes of disk.
Thanks in advance for your assistance.
Best regards,
Arnold
--
Arnold Troeger Unocal Thailand
Phone: 011-66-2-545-5456 5th Floor, Tower 3, SCB Park
Plaza
FAX: 011-66-2-545-5374 19 Ratchadapisek Road, Chatuchak
Email: Arnold.Troeger@bkk.unocal.com Bangkok 10900, Thailand
------------------------------------------------------------------------
"Microsoft Windows: for when your machine is just too fast"
