From tkiller@net-box.com  Mon Apr  6 21:44:44 1998
Received: from net-box.com (home.net-box.com [206.24.105.141])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17056
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 6 Apr 1998 21:44:44 -0700 (PDT)
          (envelope-from tkiller@net-box.com)
Received: (from root@localhost)
	by net-box.com (8.8.8/8.8.5) id VAA09886;
	Mon, 6 Apr 1998 21:44:35 -0700 (PDT)
Message-Id: <199804070444.VAA09886@net-box.com>
Date: Mon, 6 Apr 1998 21:44:35 -0700 (PDT)
From: tkiller@netbox.com
Reply-To: tkiller@netbox.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: Velocis/RDS Fails to start after OS Upgrade 2.1.6 -> 2.2.6
X-Send-Pr-Version: 3.2

>Number:         6233
>Category:       bin
>Synopsis:       Velocis/RDS Fails to start after OS Upgrade 2.1.6 -> 2.2.6
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Apr  6 21:50:00 PDT 1998
>Closed-Date:    Tue Apr 7 17:09:50 PDT 1998
>Last-Modified:  Tue Apr  7 17:10:37 PDT 1998
>Originator:     T Killer
>Release:        FreeBSD 2.2.6-RELEASE i386
>Organization:
NetBox Inc.
>Environment:
>Description:

	After updating our server from version 2.1.6 to 2.2.6 the Raima Velocis Database Server version 1.4.1 no longer starts.  It will load a couple of it's modules, but then stops loading and dumps a core record.  When viewed with gdb, the basic information is as follows [sorry, I don't know enough about core analysis to do much more]:

>How-To-Repeat:

	Try to restart the Database server.

>Fix:
	
	That's what I'm looking for...

>Release-Note:
>Audit-Trail:

From: Peter Wemm <peter@netplex.com.au>
To: tkiller@netbox.com
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: bin/6233: Velocis/RDS Fails to start after OS Upgrade 2.1.6 -> 2.2.6 
Date: Tue, 07 Apr 1998 13:01:22 +0800

 tkiller@netbox.com wrote:
 [..]
 > >>Core was generated by `rds'.
 > >>Program terminated with signal 12, Bad system call.
 > >>Cannot access memory at address 0x20019080.
 > >>#0  0x200e9ad5 in ?? ()
 > 
 > 	I have notified the vendor of the problem, but they do not have a serve
     r running 2.2.  The server ran fine under 2.1.6.  This is a very important 
     component of a major project we are working one.
 
 Just a hunch.. Have you got the SYSV IPC options enabled in your kernel?
 
 If not, you may need to build a custom kernel with the following options:
 options         SYSVSHM
 options         SYSVSEM
 options         SYSVMSG
 
 Under 2.2.x, the generic kernel has only got SYSVSHM, you might need the
 others.  I think they were all enabled by default in 2.1.x, but I have not
 checked.
 
 Cheers,
 -Peter
 
 

From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
To: tkiller@netbox.com
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: bin/6233: Velocis/RDS Fails to start after OS Upgrade 2.1.6 -> 2.2.6 
Date: Mon, 06 Apr 1998 22:34:59 -0700

 > 	After updating our server from version 2.1.6 to 2.2.6 the Raima Velocis
  Database Server version 1.4.1 no longer starts.  It will load a couple of it's
  modules, but then stops loading and dumps a core record.  When viewed with gdb
 , the basic information is as follows [sorry, I don't know enough about core an
 alysis to do much more]:
 
 This is something I think we'd have to work on in conjuncion with
 Raima since your PR information, regrettably, tells us very little of
 we'd need to know in actually getting to the bottom of this.  Is there
 any way you know of facilitating this?  Thanks.

From: "Tom Killilea" <tkiller@netbox.com>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: "FreeBSD-gnats-submit@FreeBSD.ORG" <FreeBSD-gnats-submit@FreeBSD.ORG>
Subject: Re: bin/6233: Velocis/RDS Fails to start after OS Upgrade 2.1.6 -> 2.2.6
Date: Mon, 06 Apr 1998 21:53:11 -0800

 Thanks for the quick response.  Another helpful person [Peter Wemm] has
 suggested a possible fix that we are going to try - an option to the
 kernel we my be missing.  If this fails, I will press Raima to see if
 they would cooperate to get workable code for 2.2 - I have already
 raised this as a possibility with their tech support.  I'll let you
 know if this is needed after we try the kernel modification.
 
 	Thanks - Tom K.
 
 On Mon, 06 Apr 1998 22:34:59 -0700, Jordan K. Hubbard wrote:
 
 >> 	After updating our server from version 2.1.6 to 2.2.6 the Raima Velocis
 > Database Server version 1.4.1 no longer starts.  It will load a couple of it's
 > modules, but then stops loading and dumps a core record.  When viewed with gdb
 >, the basic information is as follows [sorry, I don't know enough about core an
 >alysis to do much more]:
 >
 >This is something I think we'd have to work on in conjuncion with
 >Raima since your PR information, regrettably, tells us very little of
 >we'd need to know in actually getting to the bottom of this.  Is there
 >any way you know of facilitating this?  Thanks.
 >
 
 

From: "Tom Killilea" <tkiller@netbox.com>
To: "Peter Wemm" <peter@netplex.com.au>
Cc: "FreeBSD-gnats-submit@FreeBSD.ORG" <FreeBSD-gnats-submit@FreeBSD.ORG>
Subject: Re: bin/6233: Velocis/RDS Fails to start after OS Upgrade 2.1.6 -> 2.2.6
Date: Tue, 07 Apr 1998 12:27:10 -0800

 Peter -
 
 	Thank you VERY much for the suggestion - it worked perfectly. 
 We are now happily up and running the Raima database again.  Pretty
 impressive service for FreeBSD...  Guess we can consider this action
 item closed.
 
 	Best Regards - Tom K.
 
 On Tue, 07 Apr 1998 13:01:22 +0800, Peter Wemm wrote:
 
 >tkiller@netbox.com wrote:
 >[..]
 >> >>Core was generated by `rds'.
 >> >>Program terminated with signal 12, Bad system call.
 >> >>Cannot access memory at address 0x20019080.
 >> >>#0  0x200e9ad5 in ?? ()
 >> 
 >> 	I have notified the vendor of the problem, but they do not have a serve
 >    r running 2.2.  The server ran fine under 2.1.6.  This is a very important 
 >    component of a major project we are working one.
 >
 >Just a hunch.. Have you got the SYSV IPC options enabled in your kernel?
 >
 >If not, you may need to build a custom kernel with the following options:
 >options         SYSVSHM
 >options         SYSVSEM
 >options         SYSVMSG
 >
 >Under 2.2.x, the generic kernel has only got SYSVSHM, you might need the
 >others.  I think they were all enabled by default in 2.1.x, but I have not
 >checked.
 >
 >Cheers,
 >-Peter
 >
 >
 >
 
 
State-Changed-From-To: open->closed 
State-Changed-By: jkh 
State-Changed-When: Tue Apr 7 17:09:50 PDT 1998 
State-Changed-Why:  
Poster indicates that the problem occurred as a side-effect of not 
having needed SYSV kernel options enabled and that the problem has now 
gone away with the addition of those options. 
>Unformatted:
 >>gdb rds rds.core
 >>GDB is free software and you are welcome to distribute copies of it
 >> under certain conditions; type "show copying" to see the conditions.
 >>There is absolutely no warranty for GDB; type "show warranty" for details.
 >>GDB 4.16 (i386-unknown-freebsd), 
 >>Copyright 1996 Free Software Foundation, Inc.(no debugging symbols found)...
 >>Core was generated by `rds'.
 >>Program terminated with signal 12, Bad system call.
 >>Cannot access memory at address 0x20019080.
 >>#0  0x200e9ad5 in ?? ()
 
 	I have notified the vendor of the problem, but they do not have a server running 2.2.  The server ran fine under 2.1.6.  This is a very important component of a major project we are working one.
 
 >
 TERM=vt100
 PATH=/usr/local/ssl/bin:/home/tkiller/bin:/bin:/sbin:/usr/bin:/usr/games:/usr/sbin:/usr/local/bin:/usr/X11R6/bin:./:/usr/local/Hughes/bin:/usr/local/RDS/bin
 SHELL=/bin/csh
 HOME=/home/tkiller
 LOGNAME=tkiller
 USER=tkiller
 PWD=/home/tkiller
 EDITOR=emacs
 EXINIT=set autoindent
 PAGER=more
 SPELL=/usr/local/bin/ispell
 RDSHOME=/usr/local/RDS
 LD_LIBRARY_PATH=/usr/local/RDS/bin
 CATPATH=/usr/local/RDS/catalog
 
 
