CSV Import Jobs never starts

In general, when a job hangs at “Starting” it means that it failed to start, more or less immediately, before it was able to update its status. Getting logging or anything out of this kind of failure is tough, since it’s usually failing so early that none of our logging is set up. A common type of problem is having the wrong PHP-CLI path (Omeka S will try to guess it for you, but if there are multiple php binaries or the correct one isn’t called php, then we can’t guess correctly).

You can try to run the job manually on the command line to see if you get some more useful output. All you need is the Job ID from the leftmost column of the Jobs page. Running from the root of your S install:

php application/data/scripts/perform-job.php --job-id [insert job ID here] --base-path /