Home > mailing lists

Thread: ipc-daemon2 failure

ipc-daemon2 failure

From

"Marvin"

Date:

23 July 2003, 22:36:06

I have just installed (at last) the CygWin on my XP Machine

I have followed every step, but when I try to start the ipc-daemon2:

$ ipc-daemon2 --install-as-service

as a NT Service I get the following error box:

"The procedure entry point __getreent could not be located in the dynamic link library cygwin1.dll"

I have a headache at this point.

Please help me.

I'm about to drop all this stuff.

Thank you for ANY ideas and comments.

MAGO

_________________________________________________________________

IncrediMail - El E-mail ha evolucionado finalmente - Haga clic aquí

Attachment

IMSTP.gif

Re: ipc-daemon2 failure

From

Jason Tishler

Date:

24 July 2003, 01:31:58

Marvin,

On Wed, Jul 23, 2003 at 04:35:00PM -0600, Marvin wrote:
> I have followed every step, but when I try to start the ipc-daemon2:

Do *not* use cygipc 2.00 with the official Cygwin PostgreSQL until I
release a version built against it.

Thanks,
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

Re: ipc-daemon2 failure

From

"Roger Ackroyd"

Date:

24 July 2003, 10:43:56

Marvin

Note the earlier post by Jason re: using cygwin 2.

With reference to cygwin1 -

Check the version on your cygwin1.dll in .../cygwin/bin. I had similar problems and found I was running something like 1.3.10. Upgrading to cygwin1.dll version 1.5.1. from http://cygwin.com/snapshots cleared the problems. Unzip it with bunzip2.

(Jason: I thought I had posted my solution last week as you requested. Probably never received due to my ineptitude at posting to lists. The above is essentially what I did in order to solve the issue on this XP Home machine. On the readme, under requirements, it recommends cygwin 1.3.16-1. At footnote [16] ref step 10, it states 'For cygwin 1.3.22-1 and below, a bug prevents this from working...'. Is this problem something related to this without perhaps being the direct cause?)

Roger

----- Original Message -----
From: Marvin
To: pgsql-cygwin@postgresql.org
Sent: Wednesday, July 23, 2003 11:35 PM
Subject: [CYGWIN] ipc-daemon2 failure

I have just installed (at last) the CygWin on my XP Machine
I have followed every step, but when I try to start the ipc-daemon2:

$ ipc-daemon2 --install-as-service

as a NT Service I get the following error box:

"The procedure entry point __getreent could not be located in the dynamic link library cygwin1.dll"

I have a headache at this point.
Please help me.
I'm about to drop all this stuff.

Thank you for ANY ideas and comments.

MAGO

_________________________________________________________________
IncrediMail - El E-mail ha evolucionado finalmente - Haga clic aquí

Attachment

IMSTP.gif

Re: ipc-daemon2 failure

From

Jason Tishler

Date:

24 July 2003, 14:45:27

Roger,

On Thu, Jul 24, 2003 at 11:43:04AM +0100, Roger Ackroyd wrote:
> (Jason: I thought I had posted my solution last week as you requested.
> Probably never received due to my ineptitude at posting to lists.

I did, but you sent it *only* to me which enabled me to procrastinate
responding.  Besides, I was tied up with the impending Python 2.3
release.

> The above is essentially what I did in order to solve the issue on
> this XP Home machine.

IIRC, you had other problems besides the AF_UNIX socket problem.  I was
hoping that you could clearly articulate them so I can *easily* update
the README as necessary.  I will go with Seth changes unless I hear
otherwise.

> On the readme, under requirements, it recommends cygwin 1.3.16-1. At
> footnote [16] ref step 10, it states 'For cygwin 1.3.22-1 and below, a
> bug prevents this from working...'. Is this problem something related
> to this without perhaps being the direct cause?)

Huh?  The above is very hard to understand.

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

Re: ipc-daemon2 failure

From

"Roger Ackroyd"

Date:

24 July 2003, 16:39:03

----- Original Message -----

From: "Jason Tishler" <jason@tishler.net>

To: "Roger Ackroyd" <postgresql@ackroyd.freeserve.co.uk>

Cc: <pgsql-cygwin@postgresql.org>

Sent: Thursday, July 24, 2003 3:19 PM

Subject: Re: [CYGWIN] ipc-daemon2 failure

> Roger,
>
> On Thu, Jul 24, 2003 at 11:43:04AM +0100, Roger Ackroyd wrote:
> > (Jason: I thought I had posted my solution last week as you requested.
> > Probably never received due to my ineptitude at posting to lists.
>
> I did, but you sent it *only* to me which enabled me to procrastinate
> responding. Besides, I was tied up with the impending Python 2.3
> release.
>

I must remember to change the from and to address each time I reply using Outlook Express. If I forget it posts it direct to mail I am replying to. My apologies(again).
> > The above is essentially what I did in order to solve the issue on
> > this XP Home machine.
>
> IIRC, you had other problems besides the AF_UNIX socket problem. I was
> hoping that you could clearly articulate them so I can *easily* update
> the README as necessary. I will go with Seth changes unless I hear
> otherwise.
>

It was only when I upgraded cygwin1.dll that everything finally worked. I may have been dealing with more than one problem.

The difficulty with this platform is that each time it fails it leaves folders and files around with altered permissions/user rights, with all the user switching, logging in and out, altering permissions, deleting folders, re-installing services, one never can be sure that later attempts are not being screwed by stuff left from before. It does not allow switching accounts from the cywin command line. Wouldnt allow me anyway.

The problem is frankly a bloody nightmare to engineer on windows, really makes you want to download linux and chuck windows up the street.

> > On the readme, under requirements, it recommends cygwin 1.3.16-1. At
> > footnote [16] ref step 10, it states 'For cygwin 1.3.22-1 and below, a
> > bug prevents this from working...'. Is this problem something related
> > to this without perhaps being the direct cause?)
>
> Huh? The above is very hard to understand.

I was referring to Seths amendments to the original readme, that might have confued it. To try and clarify it states:-

In requirements

The following packages or later are required ...

...

cygwin 1.3.16-1

...

Then at footnote [16] with reference to Connect to PostgreSQL (psql) step 10

"[16] For cygwin 1.3.22-1 and below a bug prevents this from working ... ... "

Which of these is correct? If the second is correct, then surely end to end readme procedure cannot work.

I know it seems like a minor point but,

Did upgrading to cygwin1.dll 1.5.1 possibly cure [16] and one or more other problems with cygwin on this machine? That is what I cannot be sure of.

Is there a version later than 1.3.22-1 and equal to or earlier than 1.5.1, that is known to cure all or any of the observed similar problems?

In which case does cygwin version 1.3.16-1 in requirements need to be changed? Does footnote [16] then become redundant?

Also, I could have been doing something else wrong (and in parallel) all along before I (obviously) did it right!

Do'nt think I really dare say anything more concrete.

Roger
>
> 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 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
>

Re: ipc-daemon2 failure

From

Jason Tishler

Date:

25 July 2003, 13:06:16

Roger,

On Thu, Jul 24, 2003 at 05:38:11PM +0100, Roger Ackroyd wrote:
> ----- Original Message -----
> From: "Jason Tishler" <jason@tishler.net>
> To: "Roger Ackroyd" <postgresql@ackroyd.freeserve.co.uk>
> Cc: <pgsql-cygwin@postgresql.org>
> Sent: Thursday, July 24, 2003 3:19 PM
> Subject: Re: [CYGWIN] ipc-daemon2 failure
>
> > IIRC, you had other problems besides the AF_UNIX socket problem.  I
> > was hoping that you could clearly articulate them so I can *easily*
> > update the README as necessary.  I will go with Seth changes unless
> > I hear otherwise.
> >
> It was only when I upgraded cygwin1.dll that everything finally worked.

Yes.

> I may have been dealing with more than one problem.

It appears so.

> [snip]
>
> > > On the readme, under requirements, it recommends cygwin 1.3.16-1.
> > > At footnote [16] ref step 10, it states 'For cygwin 1.3.22-1 and
> > > below, a bug prevents this from working...'. Is this problem
> > > something related to this without perhaps being the direct cause?)
> >
> > Huh?  The above is very hard to understand.
>
> I was referring to Seths amendments to the original readme, that might
> have confued it. To try and clarify it states:-
> In requirements
> The following packages or later are required ...
                         ^^^^^^^^
> ...
> cygwin 1.3.16-1
> ...
>
> Then at footnote [16] with reference to Connect to PostgreSQL (psql)
> step 10
>
> "[16] For cygwin 1.3.22-1 and below a bug prevents this from working
> ... ... "
>
> Which of these is correct?  If the second is correct, then surely end
> to end readme procedure cannot work.

Both are not quite right anymore.  I don't know exactly when the AF_UNIX
problem was introduced.  IIRC, it was 1.3.20, but I don't have the
energy to track down this detail.

> I know it seems like a minor point but,

Yes.  It will become even more insignificant when I rebuild PostgreSQL
against 1.5.x and update the README accordingly.

> Did upgrading to cygwin1.dll 1.5.1 possibly cure [16] and one or more
> other problems with cygwin on this machine?  That is what I cannot be
> sure of.

AFAICT, only [16].

> Is there a version later than 1.3.22-1 and equal to or earlier than
> 1.5.1, that is known to cure all or any of the observed similar
> problems?

Yes, 1.5.0, but again it only fixes [16].

> In which case does cygwin version 1.3.16-1 in requirements need to be
> changed?

See above.

> Does footnote [16] then become redundant?

See above.

> Also, I could have been doing something else wrong (and in parallel)
> all along before I (obviously) did it right!

IIRC, yes.

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

Re: ipc-daemon2 failure

From

"Roger Ackroyd"

Date:

26 July 2003, 13:56:52

Jason
> > Subject: Re: [CYGWIN] ipc-daemon2 failure
> > > IIRC, you had other problems besides the AF_UNIX socket problem.  I
> > > was hoping that you could clearly articulate them so I can *easily*
> > > update the README as necessary.  I will go with Seth changes unless
> > > I hear otherwise.
> > It was only when I upgraded cygwin1.dll that everything finally worked.
> Yes.
> > I may have been dealing with more than one problem.
> It appears so.

> Did upgrading to cygwin1.dll 1.5.1 possibly cure [16] and one or more
> other problems with cygwin on this machine?  That is what I cannot be
> sure of.
> AFAICT, only [16].

Now know that this is so from my exchanges with Marvin.
> > Also, I could have been doing something else wrong (and in parallel)
> > all along before I (obviously) did it right!
Lets see what happens with Marvin. I should have a better idea what my
mistake was, if and when he gets running.
(Like a water wheel with a sticky bearing)
>
> IIRC, yes.
It Is Relatively Common?

Roger

Re: ipc-daemon2 failure

From

Jason Tishler

Date:

28 July 2003, 13:29:17

Roger,

On Sat, Jul 26, 2003 at 02:55:11PM +0100, Roger Ackroyd wrote:
> > IIRC, yes.
> It Is Relatively Common?

See the following:

    http://www.acronymfinder.com/af-query.asp?String=exact&Acronym=iirc

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