Retain (all versions)
When logging into the Retain Worker an error 500 error is thrown.:
Retain experienced an error, which has been logged. Please inform the administrator.
Error: com.thoughtworks.xstream.io.StreamException: : Error on line 1: Premature end of file.
There are a couple of possible solutions to this issue.
1. First clear the cache on your browser or try a different browser.
2. Re-create the Worker "bootstrap".
This error can occur when the RetainWorker2.cfg (bootstrap) file is empty or has missing information. With the missing configuration information, the Retain Worker does not know how to communicate to the Retain Server. It will then throw the error.
This is usually caused by running out of space on the root partition where the Retain Worker is installed. Every 10 minutes the Retain Server will poll and send information to the Retain Worker to update the RetainWorker2.cfg file. If there is not enough space, the information from the Retain Server will not be added to the file, as nothing can be written, and therefore it will end up as a 0 KB file.
To verify the problem:
Navigate to /opt/beginfinite/retain/RetainWorker/WEB-INF/cfg directory.
Check the size of the RetainWorker2.cfg file.
If it is at 0 Kb that indicates the issue. Please check the disk space. (df -h)
Note: At first glance there might be enough space on the root partition. However, if you have your data on the same root partition as your Retain applications, running a job will use up the space until the disk space is no more. Run a job on Retain and monitor the disk space.
It is required to recreate a new bootstrap:
To solve the problem, the disk space must be fixed. There are several ways to remedy the disk space:
1) Remove old Retain log files or other files that are not critical to the operation of Retain (/opt/beginfinite/retain/tomcat7/logs)
2) Remove old files that are no longer needed on the system, and are not critical to the operation of Retain
3) If you have the data on the same root partition as the Retain application, move the data, and/or the database to a new partition that is larger.
4) Migrate to a new server that has a larger root partition.