public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Tume Römer" <Tume.Romer@optillion.com>
To: "Mel Hatzis" <hatzis@juniper.net>
Cc: help-gnats@gnu.org
Subject: RE: Failing to connect
Date: Fri, 14 Nov 2003 06:56:00 -0000	[thread overview]
Message-ID: <ED5C6BBC01A6524D919D9067AC85CDE240B7AC@exchsthlm.corp.optillion.com> (raw)

Thanks - I solved it by creating the default as suggested,
but now I understand _what_ is happening. This should
definitely be mentioned in the UPGRADING document.

I'll use the GNATSDB environment variable to get rid of
the unneeded default database (It confuses my users :-) )

/Tume

> -----Original Message-----
> From: Mel Hatzis [mailto:hatzis@juniper.net]
> Sent: den 13 november 2003 21:42
> To: Tume Römer
> Cc: help-gnats@gnu.org
> Subject: Re: Failing to connect
> 
> 
> On 11/13/2003 05:29 AM, Tume Römer submitted:
> > I've installed Gnats 4.0 (Upgrade from 3.113) on a Solaris 
> 2.7 machine.
> > 
> > I'm getting the following error on a telnet connect (and in 
> gnatsweb):
> > 
> > -----
> > telnet enterprise 1529
> > Trying <ipnumber here>
> > Connected to enterprise.
> > Escape character is '^]'.
> > 417 GNATS initialization of database failed: No such 
> database as default
> > Connection closed by foreign host.
> > ----
> > 
> > Gnats was configured with the following:
> > .//configure  --host=sparc-sun-solaris2.7 
> --with-gnats-server=enterprise --with-full-gnats --prefix
> > =/opt/gnats --with-gnats-default-db=/opt/gnats/share/gnats/FAR
> > 
> > And resides in /opt/gnats with all databases in 
> /opt/gnats/share/gnats (FAR is one of them).
> > 
> > databases file is in /opt/gnats/etc/gnats and looks like 
> this without the comments:
> > 
> > FAR:Field And Repair Database:/opt/gnats/share/gnats/FAR
> > Development:Development and RMA 
> Database:/opt/gnats/share/gnats/Development
> > QualitySystem:Quality System 
> Database:/opt/gnats/share/gnats/QualitySystem
> > Production:Production Database:/opt/gnats/share/gnats/Production
> > 
> 
> GNATS generally requires that you have a database named 'default'.
> This is because the gnats server automatically connects to the
> 'default' database when it receives a client connection.
> 
> You can circumvent this by setting the GNATSDB environment
> variable to one of the databases you've defined above
> (FAR, Development, QualitySystem or Production) in the
> environment under which gnatsd is run.
> 
> Good luck.
> 
> --
> Mel Hatzis
> 
> > and the gnatsd.host-access looks like this:
> > *:edit:
> > 
> > I really do not have a clue and would appreciate any input 
> on how to debug this.
> > 
> > Regards,
> > /Tume
> > 
> > 
> > 
> > _______________________________________________
> > Help-gnats mailing list
> > Help-gnats@gnu.org
> > http://mail.gnu.org/mailman/listinfo/help-gnats
> 
> 
> 


_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats

             reply	other threads:[~2003-11-14  6:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14  6:56 Tume Römer [this message]
2003-11-14  8:08 ` Yngve Svendsen
  -- strict thread matches above, loose matches on Subject: below --
2003-11-13 13:28 Tume Römer
2003-11-13 20:57 ` Mel Hatzis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ED5C6BBC01A6524D919D9067AC85CDE240B7AC@exchsthlm.corp.optillion.com \
    --to=tume.romer@optillion.com \
    --cc=hatzis@juniper.net \
    --cc=help-gnats@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).