Skip site navigation (1) Skip section navigation (2)

Re: WARNING: dup(0) failed after 3195 successes: Bad file

From: "Mike Leahy" <mgleahy(at)fes(dot)uwaterloo(dot)ca>
To: <pgsql-cygwin(at)postgresql(dot)org>
Subject: Re: WARNING: dup(0) failed after 3195 successes: Bad file
Date: 2004-08-10 15:19:05
Message-ID: 000601c47eed$60404470$6b916181@mgltoshiba (view raw or flat)
Thread:
Lists: pgsql-cygwin
Mike,

Thanks for the suggestions...as you mentioned, the dup(0) error really had
nothing to do with the problem.  It was ZoneAlarm Security Suite causing the
problem.  I had suspected the firewall had been part of the issue to start
with, but shutting it down apparently isn't enough...just now I tried
uninstalling the whole ZA Security Suite, rebooted, and now I'm able to
create tables again (BTW, I was able to open template1 with psql, but the
CREATE DATABASE sql command just hung there as did the createdb executable).
I have two computers I'm testing stuff on - I went back to the other, and
couldn't figure out any settings that would get ZA to unlock whatever is
freezing the command.  I tried allowing the PG 5432 port, I tried turning
every feature off, and of course just turning the whole ZA system right off,
and still it wouldn't work without uninstalling completely.  I don't know if
anyone on this list has a clue what the problem would be, but I figure this
is one for the ZoneAlarm forums...

Thanks,
Mike

-----Original Message-----
From: pgsql-cygwin-owner(at)postgresql(dot)org
[mailto:pgsql-cygwin-owner(at)postgresql(dot)org] On Behalf Of mike g
Sent: August 6, 2004 12:58 AM
To: Mike Leahy
Cc: pgsql-cygwin(at)postgresql(dot)org
Subject: Re: [CYGWIN] WARNING: dup(0) failed after 3195 successes: Bad file

Ok,

If you can connect to the database you can issue the sql statements to
create another database.  Initdb creates the initial database named
template1.  Connect to that and you can issue other sql queries that you
need to.

You can use psql (command line) which is included with the postgres
install or download pgadminIII for a gui version.

I believe that the createdb command calls a psql script.

If you haven't already try creating a new blank database and some test
tables to see if you postgres install is really working properly before
restoring.

Mike

On Thu, 2004-08-05 at 12:11, Mike Leahy wrote:
> I'm just running createdb to create the database - and it hangs, and the
only 
> error message I can find anywhere are the dup(0) message in the postmaster

> log.  I have a bunch of scripts that create/import tables in that database

> once it's created - the dump file that I have I created using pg_dump, but

> I've never tried it...I'm guessing it would be executed using psql?
> 
> Is there an alternative method to the createdb command?
> 
> Thanks,
> Mike
> 
> Quoting Mike G <mike(at)thegodshalls(dot)com>:
> 
> > Hi,
> > 
> > How are you trying to create the database?  Through psql,pgadmin, or
> > something else?
> > 
> > How did you backup the database?  pg_dumpall, pg_dump or something else?
> > 
> > I believe I have seen that error in my logs as well but it has not
prevented
> > me from doing anything.
> > 
> > Mike
> >  Wed, Aug 04, 2004 at 02:47:33AM -0400, Mike Leahy wrote:
> > > Hello list,
> > > 
> > > I'm just reposting this question, that didn't get feedback a few weeks
ago.
> >  I 
> > > can't for the life of me guess why I'm getting this error in the logs
when
> > the 
> > > postmaster service starts.  I've got it running in cygwin on XP Pro
(SP2),
> > 
> > > originally with ipc-daemon, now with cygserver.  I've seen similar
postings
> > 
> > > about this answer, but I can't tell if anyone has actually resolved
it...
> > > 
> > > A better description of what I've done to try to fix this is below...
> > > 
> > > Any guesses/suggestions?
> > > 
> > > Thanks,
> > > Mike
> > > 
> > > 
> > > -----Original Message-----
> > > From: pgsql-cygwin-owner(at)postgresql(dot)org [mailto:pgsql-cygwin-
> > > owner(at)postgresql(dot)org] On Behalf Of Mike Leahy
> > > Sent: July 10, 2004 1:20 AM
> > > To: pgsql-cygwin(at)postgresql(dot)org
> > > Subject: Re: [CYGWIN] WARNING: dup(0) failed after 3195 successes: Bad
file
> > 
> > > descriptor
> > > 
> > > Hello list,
> > > 
> > > I'm getting this error as well.  I'm running XP Pro, with SP2 (RC2).
Until
> > 
> > > just now I had PostgreSQL 7.4.1.  As far as I could tell, everything
was 
> > > running fine...then as I was updating some tables I started getting
errors
> > 
> > > (sorry I didn't record them).  I had my whole database backed up, so I
> > tried 
> > > to delete the database using "dropdb" so I could reload the backup,
but the
> > 
> > > dropdb command just hung there and did nothing...
> > > 
> > > I tried cleaning out the whole PG data folder, and reinitializing.  It
> > seemed 
> > > okay...I could run "createuser", but it hung again with "createdb".
Next I
> > 
> > > installed PostgreSQL 7.4.3.  I got through the setup okay, and the
services
> > 
> > > appear to be running fine, db initialized okay, and I could create new
> > users 
> > > as before, but the postmaster.log still has the same "dup(0)" error,
and it
> > 
> > > still hangs if I try to create a database.
> > > 
> > > Earlier this week I installed the second release of XP SP2 - I suppose
that
> > 
> > > could have something to do with it.  Did the others with this error
find a
> > 
> > > solution?
> > > 
> > > Kind regards,
> > > Michael Leahy
> > > 
> > > -----Original Message-----
> > > From: pgsql-cygwin-owner(at)postgresql(dot)org [mailto:pgsql-cygwin-
> > > owner(at)postgresql(dot)org] On Behalf Of Jason Tishler
> > > Sent: June 14, 2004 12:07 PM
> > > To: David P. Lurie
> > > Cc: pgsql-cygwin(at)postgresql(dot)org
> > > Subject: Re: [CYGWIN] WARNING: dup(0) failed after 3195 successes: Bad
file
> > 
> > > descriptor
> > > 
> > > David,
> > > 
> > > On Sun, Jun 13, 2004 at 07:42:30PM -0400, David P. Lurie wrote:
> > > > The following warning occurs each time that postgresql 7.4.2 is
loaded:
> > > > 
> > > > WARNING:  dup(0) failed after 3195 successes: Bad file descriptor
> > > > [snip]
> > > > 
> > > > Is this a serious problem? Occurs on two different XP Pro systems.
> > > 
> > > AFAICT, no.
> > > 
> > > Jason
> > > 
> > > -- 
> > > PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
> > > Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6
> > > 
> > > ---------------------------(end of
broadcast)---------------------------
> > > TIP 6: Have you searched our list archives?
> > > 
> > >                http://archives.postgresql.org
> > > 
> > > 
> > > ----------------------------------------
> > > This mail sent through www.mywaterloo.ca
> > > 
> > > ---------------------------(end of
broadcast)---------------------------
> > > TIP 8: explain analyze is your friend
> > > 
> > > 
> > > ----------------------------------------
> > > This mail sent through www.mywaterloo.ca
> > > 
> > > ---------------------------(end of
broadcast)---------------------------
> > > TIP 3: if posting/reading through Usenet, please send an appropriate
> > >       subscribe-nomail command to majordomo(at)postgresql(dot)org so that
your
> > >       message can get through to the mailing list cleanly
> > 
> 
> 
> 
> 
> ----------------------------------------
> This mail sent through www.mywaterloo.ca

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

               http://archives.postgresql.org


In response to

pgsql-cygwin by date

Next:From: Mike GDate: 2004-08-11 03:56:53
Subject: Re: problem running ipc-daemon2
Previous:From: aviv huriDate: 2004-08-10 06:05:43
Subject: problem running ipc-daemon2

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group