Hi Toni,
There's not a lot of information here to go on, but when we've seen this message before, it's usually about not being able to connect to Elasticsearch - and that has sometimes been due to not enough memory. How much RAM does your AtoM installation have available?
That said, I can't think why a connection to Elasticsearh would be important for a CSV export job, so it might also be about connecting to the MySQL database. Is there any chance you've tried a unique installation pattern - for example, installing the job scheduler on a different server?
Is this an archival description CSV export? How many rows, approximately, were you expecting (i.e. is this a big export, or just a small one)?
Let's see if we can get a more detailed error message. The first place to check would be the atom-worker logs. Can you see if there's anything relevant in the worker logs, with the following command?
- sudo journalctl -f -u atom-worker
There may not be anything more in there than is shown in the Job output in the user interface but it's worth checking.
Otherwise, do you have access to the command-line? If yes, I would suggest trying to run a command-line CSV export. That way the console should provide more information on any errors encountered. See:
Hopefully with more information we can recommend some next steps.
Cheers,