Forum OpenACS Development: Re: Error on OS X using install-ns.sh

Collapse
5: Re: Error on OS X using install-ns.sh (response to 4)
Posted by Dave Bauer on 09/11/15 02:47 AM
I found a few more issues.

1) You can't run naviserver without setting path if you have another version of postgresql installed. I use the homebrew installed postgresql.

Is the server running locally and accepting
connections on Unix domain socket "/var/pgsql_socket/.s.PGSQL.5432"?

It is running but the socket file is in /tmp/.s.PGSQL.5432
Some answers suggest creating a symlink. That is one option. It seems to solve the problem.

sudo mkdir /var/pgsql_socket
sudo ln -s /tmp/.s.PGSQL.5432 /var/pgsql_socket/

I am not sure if this will survive a restart of postgresql.

After this I found a bug in tdom pkgIndex.tcl, a missing space.

error reading package index file /usr/local/ns/lib/tdom0.8.3/pkgIndex.tcl: expected version number but got "0.8.3"load"

Collapse
6: Re: Error on OS X using install-ns.sh (response to 5)
Posted by Gustaf Neumann on 09/11/15 09:11 AM
The first one seems to be a problem of homebrew. If you use the preconfigured versions from MacPorts, everything is fine. Are you using the postgres client and server from homebrew? if yes, this is a homebrew problem and should be reported to the homebrew maintainers.

The problem with tDOM is an old one, and was fixed 7 years ago [1]. Unfortunately, the release strategy of tDOM is very slow. So far, i was reluctant to use the tip verison from github in the script, but that gives unreliable results when new commits are added. The git repo seems outdated, but fossil archive is not better in this regard.

Maybe i'll find some time to work on a portfile for mac ports for OpenACS and its needed components.

[1] https://github.com/tDOM/tdom/commit/c652019092165ac1eb67dfb10992a86c69385c26

Collapse
7: Re: Error on OS X using install-ns.sh (response to 6)
Posted by Gustaf Neumann on 09/11/15 09:47 AM
To address the tdom problem, i've changed the install script to use a date-based git release (due to lack of a proper tag in the tdom repos).
Collapse
8: Re: Error on OS X using install-ns.sh (response to 6)
Posted by Dave Bauer on 09/11/15 01:07 PM
Gustaf, do you know how Naviserver gets the path to the PostgreSQL socket? I use the home brew version of PostgreSQL every day and it seems to work fine with other applications, so somewhere there is a difference in how it connects.

I'll see if I can look into this further myself as well, but I thought you might know this type of thing.

Thanks for updating the tdom install. I found it simple enough to change but if there is a good way to automate it, that works, even better.

Collapse
9: Re: Error on OS X using install-ns.sh (response to 8)
Posted by Gustaf Neumann on 09/11/15 01:39 PM
NaviServer does not do anything for specifying the socket, it just uses the defaults from the postgres client library.
Collapse
10: Re: Error on OS X using install-ns.sh (response to 9)
Posted by Dave Bauer on 09/11/15 02:35 PM
Thanks for confirming that. I'll have to figure out where it gets that information.

I don't seem to be able to find more than one version of psql. I did

sudo su -
cd /
find . -type f -name "psql"

and only the home brew install of psql was found.

Is there another way I can look for another postgresql install? I am running OS X 10.9.5 Mavericks.

next I looked at the postgresql install script that builds postgresql https://github.com/Homebrew/homebrew/blob/master/Library/Formula/postgresql.rb

I don't see any configuration that changes the default socket directory. Presumably the Naviserver database driver is connecting to a misconfigured library? The socket is definitely in /tmp/.s.PGSQL.5432 and that is the default setting for Postgresql, from what I can find.

Any other ideas where to look? I'd like to be able to consistenly install it correctly, and if possible find the home brew postgresql install script, but I don't see where this is changed when postgresql is compiled.

Collapse
11: Re: Error on OS X using install-ns.sh (response to 10)
Posted by Michael Aram on 09/11/15 03:11 PM
Hello Dave,

IIRC, when compiling PG manually the default location of the socket is in /tmp/.s.PGSQL.5432. When using PG from the distribution, it is somewhere else.

Anyhow, when I install OpenACS, I typically use a wrapper script for starting NaviServer, which includes the PATH to PG. To be honest, I dont know if this is (still) really needed, but maybe it helps?


function install_nsd_pg {
# Add wrapper script
local NSD_PREFIX=$1
local PG_VERSION=$2
local PG_PREFIX=$3

cat <<EOF > ${NSD_PREFIX}/bin/nsd-pg${PG_VERSION}
#!/bin/bash
export PATH=\$PATH:${PG_PREFIX}/bin
export LD_LIBRARY_PATH=\$LD_LIBRARY_PATH:${PG_PREFIX}/lib:${NSD_PREFIX}/lib
ulimit -c unlimited
exec ${NSD_PREFIX}/bin/nsd \$*
EOF
chmod 755 ${NSD_PREFIX}/bin/nsd-pg${PG_VERSION}
}
# Set vars as needed....
install_nsd_pg $PREFIX_NS $POSTGRES_VERSION $PREFIX_POSTGRES