tia® Content Server cannot access existing archived documents

Owned by Simone Conrad
Last updated: Jul 19, 2023

Symptoms

 

Existing archived documents are no more accessible via kgs Content Server

 

Error popup message in SAP when accessing archived document:

HTTP-Fehler 500     internal error in <Content Server>

Java.nio.FileSystemException:

<directory>

 

Web application server log file (e.g. catalina.out for Apache Tomcat) contains following exception:

        java.nio.file.FileSystemException: <File>: Read-only file system

 

Cause

 

tia® Content Server is a web application and therefore depends on the web application server (in the following using exemplarily Apache Tomcat) to have write access to the file system respective the network file system.

On Linux systems, the tomcat service definition requires configuration for that.

 

Resolution

 

The name of the tomcat service on the specific system may vary. Below the service name is assumed to be:  tomcat9

 

  1. Navigate to the directory containing the service definitions:  

    • cd /etc/system/system

    • And identify the tomcat service definition file:    tomcat9.service

    • Note: kgs recommends to backup the service definition file before editing to allow quick restoration in case of failure.

  2. Edit the service definition file.

    • In the [Service] section use the ReadWritePaths parameter to configure a directory for read-write access:

    • ReadWritePaths=<directory>

  3. Stop the tomcat service

    • systemctl shutdown tomcat9

  4. Reload the service definition

    • systemctl daemon-reload tomcat9

  5.  Start the service again

    • systemctl start tomcat9   

  6. Test and verify