Last week I upgraded PostgreSQL to 7.3.1 and PHP to 4.3 last week, and I fo=
und
that the CLI is giving me lots of headaches.
At first, a script that had to recieve mail form a pipe (an alias) and inse=
rt
data into my PostgreSQL database stopped working. Put PEAR::DB on the scrip=
t
and found that the connection didn't find that database (not the server, th=
e
database where it should be inserted the data). If I execute the script fro=
m
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 did=
n't
work, even though the same command works from the postgres bash. The postgr=
es
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 s=
uch
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.

--
Porqu=E9 usar una base de datos relacional cualquiera,
si pod=E9s usar PostgreSQL?
------------------------------------------------------------ -----
Mart=EDn Marqu=E9s | mmarques [at] unl.edu.ar
Programador, Administrador, DBA | Centro de Telematica
Universidad Nacional
del Litoral
------------------------------------------------------------ -----


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo [at] postgresql.org so that your
message can get through to the mailing list cleanly

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?


---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

On Lun 10 Feb 2003 13:03, Stephan Szabo wrote:
> >
> > 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 fr=
om
> > PostgreSQL, so I guess the problem is there.
>
> Are the environments different, maybe something like LD_LIBRARY_PATH or
> some such?

Fixed!
Just linked th libgcc_s.so.1 to /usr/lib.
This never happend with other versions off PostgreSQL, and I have been
building since 7.0.3. It's the first time this happens.

Thanks all!

--
Porqu=E9 usar una base de datos relacional cualquiera,
si pod=E9s usar PostgreSQL?
------------------------------------------------------------ -----
Mart=EDn Marqu=E9s | mmarques [at] unl.edu.ar
Programador, Administrador, DBA | Centro de Telematica
Universidad Nacional
del Litoral
------------------------------------------------------------ -----


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo [at] postgresql.org so that your
message can get through to the mailing list cleanly