Re: Watchers not watching

Hi Drew,

The following have worked for me on v1.1, but there's no guarantees I'm afraid. This should only be used as a last resort. Always remember to back your database up first!

WARNING: This almost certainly won't work on v1.5 (but I haven't tried it). Apple say that they've completely redesigned the database, so I would expect you to get SQL errors.

The first thing you need to do is to create symlinks so that the console installation of PostGres that comes with Final Cut Server actually works.
Log into your Final Cut Server machine, and in a Terminal window type:


cd "/Library/Application Support/Final Cut Server/Final Cut Server.bundle/Contents/PostgreSQL/lib" [this is all one line]
for x in `ls`; do ln -s $x /usr/lib; done


This will create symlinks (Unix-speak for Aliases, kind of) to all of the libraries that the Postgres commandline client uses.

Then type:


cd ..
bin/psql -h localhost -p 5433 -d px -U postgres


This runs the Postgres database client (psql) and connects you to the Final Cut Server database, which is called px. You will see a prompt which looks something like
px=#

Type in:

update pxeventresponse set eventstatusid=3;
\q


You should see a message saying something like "20000 rows affected".

The first line is the key one. This sets the column "eventstatusid" in the table "pxeventresponse" to 3 (which means "job complete"), for every entry.
The second line exits the Postgres commandline and brings you back to a Terminal prompt. Note the ; on the end of the line - you need this to make it run.

For me, this made the queues un-stick and things start running again. However, a few days later it jammed up again.... closer inspection showed that Final Cut Server hadn't flushed the rows from the table as I expected it to. If that happens, then what I did was:

cd "/Library/Application Support/Final Cut Server/Final Cut Server.bundle/Contents/PostgreSQL/" [all on one line]
bin/psql -h localhost -p 5433 -d px -U postgres
delete from pxeventresponse;
\q

This completely clears out the table pxeventresponse, and our installation has been running fine ever since.

Hope that's of some use.

Andy

-------------------------------

You want it when?