Incident #12303
closed
The production Sharelatex instance is not using a permanent storage for the users documents
100%
Description
There was a mistake in the ansible task that launches the container instance: the syntax for the volume configuration was wrong but the command completed with success anyway, without setting up the storage volume.
Updated by Andrea Dell'Amico about 7 years ago
I'm going to stop the service, copy the user data outside the container, than restart the container with the external volume mounted correctly.
Updated by Andrea Dell'Amico about 7 years ago
- Status changed from New to In Progress
Updated by Andrea Dell'Amico about 7 years ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
There's no way to add a volume to an existing container. As we are running a specific version with lots of local customisations I chose to add a cron job that synchronizes the users data with a directory on the docker host.
That directory will be mounted as a container volume when will switch to a new image.
Updated by Luca Frosini about 7 years ago
I'm not able to use sharelatex.
At https://services.d4science.org/group/collabresearch/sharelatex I get:
No gCore resource named ShareLatex is present in the scope /d4science.research-infrastructures.eu/FARM/CollabResearch
Updated by Andrea Dell'Amico about 7 years ago
It also happens for /d4science.research-infrastructures.eu/FARM/D4STeam, but I don't know why. @roberto.cirillo@isti.cnr.it do you have any idea? I already restarted the tomcat instance once.
Updated by Roberto Cirillo about 7 years ago
There was a problem with the registry service of FARM VO during the restart from last night. Now the problem is solved but the gCore Endpoint is still not published. It will be published in 20 minutes otherwise we should restart the container.
Updated by Roberto Cirillo about 7 years ago
I see that now the resource is correctly published on FARM VO and the portlet works on CollabResearch VRE.
