Re: [ADMIN] pg_dumpall in crontab doesn't work

Guthrie, John wrote: > keep in mind that cronjobs don't get your login environment, so things that > work in interactive mode often fail in cron unless you make sure to set up > the environment there too. > Thanks John, actually I didn't know that :-( In the meantime I added the "http://archiv

Re: [ADMIN] pg_dumpall in crontab doesn't work

Nils Höglund wrote: > >> 05 22 * * 1-5 postgres /usr/bin/pg_dumpall -D > >> /disks/postgres/db.pg_dumpall >> connected to template1... >> /usr/bin/pg_dumpall: 0: Bad file descriptor > > Filedescriptor 0 is STDIN. I would guess pg_dumpall want's to read something > from stdin, pherhaps ask y

[ADMIN] pg_dumpall in crontab doesn't work

I'm doing some backup action for my database using crontab. Unfortunately the following entry doesn't work and I can't figure out the problem: - /etc/crontab --- 05 22 * * 1-5 postgres /usr/bin/pg_dumpall -D > /disks/postgres/db.pg_dumpall --

[ADMIN] pg_dumpall fails in cronjob

Hi all, I have a stange problem when executing pg_dumpall as a cron job. The crontab entry looks like: 05 22 * * 1-5 postgres /usr/bin/pg_dumpall -D > /disks/postgres/db.pg_dumpall On stderr I get the message connected to template1... /usr/bin/pg_dumpall: 0: Bad file descriptor The createt

[ADMIN] pg_dumpall in crontab

ALC Computertechnik GmbH Kaiserstr. 100, D-52134 Herzogenrath, GERMANY Fon +49 2407 95810 Fax +49 2407 958139 http://www.alc.de - ------ Werner Modenbach [EMAIL PROTECTED] - --

[ADMIN] creating documentation about user functions etc.

t the message server1:[pgsql] >pg_dumpall > db.out failed sanity check, type with oid 155265 was not found pg_dump failed on volleyball, exiting server1:[pgsql] > How can I solve this? Any hints? -- ----

[ADMIN] pg_dumpall: Message "failed sanity check, type with oid 155265 not found"

ow can I solve this? Any hints? Thanks in advance. - Werner - -- ------- Werner Modenbach [EMAIL PROTECTED] ALC Computertechnik GmbH http://www.alc.de