Thread: v814 + OSX10.4.6 builds OK, but fails launch ...
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 hi all, i've working built-from-source v813 installs on OSX 10.4.6. staring with a clean 814 src tree, a similarly-config'd build completes without error: % postmaster --version postmaster (PostgreSQL) 8.1.4 but, on executable launch, if fails w/ @ postgresql.log: LOG: 00000: could not read symbolic link "postmaster" LOCATION: resolve_symlinks, exec.c:338 FATAL: XX000: /usr/local/pgsql/bin/postmaster:could not locate my own executable path LOCATION: PostmasterMain, postmaster.c:435 known? suggestion? cheers, richard - -- /"\ \ / ASCII Ribbon CampaignX against HTML email, vCards / \ & micro$oft attachments [GPG] OpenMacNews at gmail dot com fingerprint: 50C9 1C46 2F8F DE42 2EDB D460 95F7 DDBD 3671 08C6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iEYEAREDAAYFAkR08fkACgkQlffdvTZxCMaukACcC29AL0JRtQwW1DjDlNVlWOko /zwAoKp96K9LSsYZSZmlWs+QIKWrH6PI =Wc17 -----END PGP SIGNATURE-----
Richard <openmacnews@gmail.com> writes:
> LOG: 00000: could not read symbolic link "postmaster"
> LOCATION: resolve_symlinks, exec.c:338
> FATAL: XX000: /usr/local/pgsql/bin/postmaster: could not locate my
> own executable path
> LOCATION: PostmasterMain, postmaster.c:435
> known?
Nope, and we do have OS X machines in the buildfarm, so I think we'd
have noticed if there were a generic problem. I don't recall any recent
changes in that area of the code, either. Have you built PG
successfully before on this same machine? If so, what was the last
version that worked for you? Is there anything out of the ordinary
about the filesystem or directory path you installed PG on?
regards, tom lane
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 hi tom, >> LOG: 00000: could not read symbolic link "postmaster" >> LOCATION: resolve_symlinks, exec.c:338 >> FATAL: XX000: /usr/local/pgsql/bin/postmaster: could not locate my >> own executable path >> LOCATION: PostmasterMain, postmaster.c:435 > >> known? > > Nope, and we do have OS X machines in the buildfarm, so I think we'd > have noticed if there were a generic problem. I don't recall any recent > changes in that area of the code, either. Have you built PG > successfully before on this same machine? repeatedly. on this machine, and a variety of others similarly configured ... > If so, what was the last version that worked for you? v8.1.3 on all boxes. i can currently successfully (re)build 813 on this box now, with no such problems ... > Is there anything out of the ordinary > about the filesystem or directory path you installed PG on? 'out of the ordinary' ... well, not from my perspective, or from that, apparently, of v813. cheers, richard - -- /"\ \ / ASCII Ribbon CampaignX against HTML email, vCards / \ & micro$oft attachments [GPG] OpenMacNews at gmail dot com fingerprint: 50C9 1C46 2F8F DE42 2EDB D460 95F7 DDBD 3671 08C6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iEYEAREDAAYFAkR0+BQACgkQlffdvTZxCMad1gCfXvnR8nG8lZumMHK0HLB3b6w4 VXgAoIa/dCW06WyavJMTgjd376h51Wyr =fbTC -----END PGP SIGNATURE-----
Richard <openmacnews@gmail.com> writes:
>> If so, what was the last version that worked for you?
> v8.1.3 on all boxes. i can currently successfully (re)build 813 on this
> box now, with no such problems ...
Curious. I just rebuilt/tested CVS HEAD successfully on my own 10.4.6
laptop ... I'll try REL8_1_STABLE next, but I'll be *really* surprised
if it fails. There's got to be something odd about your configuration.
Look at PATH and so forth. Look at the postmaster -> postgres symlink;
is it where it's supposed to be?
regards, tom lane
Richard wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > hi all, > > i've working built-from-source v813 installs on OSX 10.4.6. > > staring with a clean 814 src tree, a similarly-config'd build completes > without error: > > % postmaster --version > postmaster (PostgreSQL) 8.1.4 > > but, on executable launch, if fails w/ @ postgresql.log: > > LOG: 00000: could not read symbolic link "postmaster" > LOCATION: resolve_symlinks, exec.c:338 > FATAL: XX000: /usr/local/pgsql/bin/postmaster: could not locate my > own executable path > LOCATION: PostmasterMain, postmaster.c:435 > > known? suggestion? Well it looks like the symlink to /usr/local/pgsql/bin/postmaster is broken. Joshua D. Drake > > cheers, > > richard > > - -- > > /"\ > \ / ASCII Ribbon Campaign > X against HTML email, vCards > / \ & micro$oft attachments > > [GPG] OpenMacNews at gmail dot com > fingerprint: 50C9 1C46 2F8F DE42 2EDB D460 95F7 DDBD 3671 08C6 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.3 (Darwin) > > iEYEAREDAAYFAkR08fkACgkQlffdvTZxCMaukACcC29AL0JRtQwW1DjDlNVlWOko > /zwAoKp96K9LSsYZSZmlWs+QIKWrH6PI > =Wc17 > -----END PGP SIGNATURE----- > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutionssince 1997 http://www.commandprompt.com/
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 tom, >> v8.1.3 on all boxes. i can currently successfully (re)build 813 on this >> box now, with no such problems ... > > Curious. yup. I just rebuilt/tested CVS HEAD successfully on my own 10.4.6 > laptop ... good to know ... > I'll try REL8_1_STABLE next, but I'll be *really* surprised > if it fails. There's got to be something odd about your configuration. > Look at PATH and so forth. checking 'by the numbers' ... the problem exists on four different boxes admittedly, they're all similarly configured ... fwiw, v813 is OK on all boxes. > Look at the postmaster -> postgres symlink; > is it where it's supposed to be? seems to be: /usr/local/pgsql/bin > ls -al postmasterlrwxrwx--- 1 root wheel 8 2006-05-24 07:48 postmaster -> postgres i'll let you know if i find anything; please do the same ... richard - -- /"\ \ / ASCII Ribbon CampaignX against HTML email, vCards / \ & micro$oft attachments [GPG] OpenMacNews at gmail dot com fingerprint: 50C9 1C46 2F8F DE42 2EDB D460 95F7 DDBD 3671 08C6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iEYEAREDAAYFAkR0/kUACgkQlffdvTZxCMaQ3gCfYnxf5D8dSmiulGFjy7UnrvjB HPwAn3pHIE0wg2bZkxk1g54R9b7Kp9Y/ =6nYL -----END PGP SIGNATURE-----
Richard <openmacnews@gmail.com> writes:
>> Look at the postmaster -> postgres symlink;
>> is it where it's supposed to be?
> seems to be:
> /usr/local/pgsql/bin > ls -al postmaster
> lrwxrwx--- 1 root wheel 8 2006-05-24 07:48 postmaster -> postgres
Hm, is it significant that that symlink is set for no access by world?
I don't remember if Darwin enforces access bits on symlinks, but check
to see if your 8.1.3 installation has identical privileges for the
symlink.
regards, tom lane
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
>> /usr/local/pgsql/bin > ls -al postmaster
>> lrwxrwx--- 1 root wheel 8 2006-05-24 07:48 postmaster -> postgres
>
> Hm, is it significant that that symlink is set for no access by world?
hmmm, too.
> I don't remember if Darwin enforces access bits on symlinks, but check
> to see if your 8.1.3 installation has identical privileges for the
> symlink.
will do ... gonna rebuild clean. been monkeying around too much
tracking this down.
fwiw,
make check====================== All 98 tests passed.======================
grumble ...
- --
/"\
\ / ASCII Ribbon CampaignX against HTML email, vCards
/ \ & micro$oft attachments
[GPG] OpenMacNews at gmail dot com
fingerprint: 50C9 1C46 2F8F DE42 2EDB D460 95F7 DDBD 3671 08C6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
iEYEAREDAAYFAkR1AIAACgkQlffdvTZxCMa6QwCgsqUv4qTWncirjZ1JmJlcx2Eu
IdEAn2R9jFMj4yD+PVegf4bCOuu2zcuJ
=kRQS
-----END PGP SIGNATURE-----
On Wed, May 24, 2006 at 05:45:57PM -0700, Richard wrote: > /usr/local/pgsql/bin > ls -al postmaster > lrwxrwx--- 1 root wheel 8 2006-05-24 07:48 postmaster -> postgres How did that happen. I was always under the impression that permission bits on symbolic links were ignored, and chmod on my machine (linux) won't let me change them anyway, it changes the bits on the underlying file. Is OSX different here? Have a nice day, -- Martijn van Oosterhout <kleptog@svana.org> http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to litigate.