The disk system can fill up over time. Eventually, Flow will fail when the disk fills up.
After days of ElectricFlow running uninterrupted, one of the following occurs:
- Users cannot login to the system.
When restarting Flow, Flow cannot connect to the database and reports in the GUI:
Server not running: Waiting for a valid database configuration - go to the Database Configuration page
Server not running: Can't connect to the database: No suitable driver - go to the Database Configuration page
- The commander.log file is no longer growing.
- Flow stopped writing to the log file when the disk became full.
- last error can be: “org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update”
- Steps fail with “AGENT_INTERNAL_ERROR”
- If you are using MySQL, stop and start MySQL - if MySQL is out of space, it will not restart.
- Check the Flow server’s disk space. The Flow server log files have filled up the disk - look at the size in the “logs” Flow directory.
- Check the database server’s disk space. When using local MySQL, do the following:
- Look at the size of the files in the MySQL data directory.
- Search the MySQL error log, found in mysql/data/.err by default, for any recent errors.
- Stop Flow.
- If using MySQL, stop MySQL.
- Recover disk space by compressing or deleting Flow log files.
- Check the contents of file database.properties found in the Flow conf directory.
- This file can be left corrupted, for example, it has only two lines instead of the twelve normally in the file.
- Restore this file from backup.
- If using MySQL, restart MySQL.
- Restart Flow.