Skip to main content

My .fsconfig file is relatively large - around 3GB - and whenever I try to restore this to my new installation of FME Server, the process fails with an error.

The FME Server Web UI reports:

Error uploading "fmeserver_backup.fsconfig". Reason: Could not write FME Server request message. Connection may have been lost. An existing connection was forcibly closed by the remote host

And in the fmeconfiguration.log file, the following errors appear:

Thu-20-Oct-2016 07:16:57 PM   ERROR    RequestHandler-Thread   Could not read FME Server response message. Connection may have been lost.There is not enough space on the disk
Thu-20-Oct-2016 07:16:57 PM   ERROR    RequestHandler-Thread   401835 : IOException reading client request. Connection may have been closed. Request read so far: 

There might not be enough disk space available to restore the FME Server configuration file. FME Server currently needs ~3x the size of the .fsconfig file in available disk space. For this example, with a 3GB .fsconfig file, you will need ~9GB of available disk space.

This is a known issue and we are investigating how we can improve the resource usage for FME Server migrations.

There has been an improvement in FME Server 2017 and this is now down to 2x the size of the .fsconfig file.

Please see the answer in this article on how you may reduce the size of your backup file (.fsconfig).

Related Article: 15GB FME Server Backup

Community Stats

32,056
Posts
121,718
Replies
39,684
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.