Campaign Classic v7: Workflows “No space left on device error”
This article discusses what to do when there’s no more space left on a database server and workflows/deliveries result in a No space left on device error.
Description description
Environments
- Adobe Campaign (AC)
- Adobe Campaign Classic v7 (ACC v7)
Issue
Workflows and deliveries stop running.
The Audit logs show an error similar to:
PGS-220000 PostgreSQL error: ERROR: could not write to file “base/pgsql_tmp/pgsql_tmpXXXXX.XXX”: No space left on device.
Resolution resolution
Follow these steps to resolve the issue:
- Check if there are any paused workflows and stop them.
- Check if there are any workflows that have the option Keep the result of interim populations between two executions activated.
- If there are any, deactivate the option, save the workflow, and restart it so that the modification is taken into account.
- Check if there are any new workflows created recently that started running when the issue occurred.
- Make sure the cleanup workflow has been running in the last few days.
- If the instance is hosted by Adobe, use the Control panel to check if there are any long-running workflows. Otherwise, ask your DBA to check if there are any long-running queries.
- Check the runwf.log file, and see which workflows are generating errors. NOTE: In the runwf.log, there will be an error on the query that failed to execute, and you should be able to get the workflow ID from the temporary table name. The full directory address of the runwf.log file is:
<installation directory>/var/<instance>/log/runwf.log - Once the culprit workflows are identified, stop them to free space on the database server, and work to improve their execution.
Cause
This PostgreSQL error occurs when all the disk space on the database server has been exhausted.
It’s caused because there are one or multiple custom workflows that are consuming too much disk space.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f