X-Original-To: pgsql-general@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 22CA44753A1; Mon, 10 Feb 2003 11:03:54 -0500 (EST) Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (Postfix) with ESMTP id 85BBA474E53; Mon, 10 Feb 2003 11:03:53 -0500 (EST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 21AF7D609; Mon, 10 Feb 2003 08:03:58 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 175645C02; Mon, 10 Feb 2003 08:03:58 -0800 (PST) Date: Mon, 10 Feb 2003 08:03:58 -0800 (PST) From: Stephan Szabo To: Martin Marques Cc: , Subject: Re: Not finding local variables and libs In-Reply-To: <200302100825.15158.martin@bugs.unl.edu.ar> Message-ID: <20030210080222.V97908-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/582 X-Sequence-Number: 37336 On Mon, 10 Feb 2003, Martin Marques wrote: > Last week I upgraded PostgreSQL to 7.3.1 and PHP to 4.3 last week, and I found > that the CLI is giving me lots of headaches. > At first, a script that had to recieve mail form a pipe (an alias) and insert > data into my PostgreSQL database stopped working. Put PEAR::DB on the script > and found that the connection didn't find that database (not the server, the > database where it should be inserted the data). If I execute the script from > the command line "cat some-mail | /usr/local/bin/php/arch.php" it works > great, but not if it's passed by the mail system. > Today I found out that the administration crons that run on sunday also didn't > work, even though the same command works from the postgres bash. The postgres > crontab looks like this: > > 0 23 * * 0 /usr/local/pgsql/bin/vacuumdb -z -v lismarch > 10 23 * * 0 /usr/local/pgsql/bin/vacuumdb -z -v horde > 30 23 * * 0 /usr/local/pgsql/bin/vacuumdb -z -v webunl > > I got error reports from mail that said this: > > Your "cron" job on bugs > /usr/local/pgsql/bin/vacuumdb -z -v lismarch > > produced the following output: > > ld.so.1: /usr/local/pgsql/bin/psql: fatal: libgcc_s.so.1: open failed: No such > file or directory > Killed > vacuumdb: vacuum lismarch failed > > > I thought it was a PHP problem, but these commands are especifically from > PostgreSQL, so I guess the problem is there. Are the environments different, maybe something like LD_LIBRARY_PATH or some such?