You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use the EGA Fuse client for access to specific datasets for the Solve-RD project: works great :) This is inside a folder for this project on an HPC cluster. Now we want to do the same for other datasets for another project (Cineca). Obviously that has to be mounted in a different location and with different permissions, but it is on the same HPC cluster. Running a second instance of the EGA Fuse client fails, because port 8080 is already in use. Would it be possible to add another commanline option to specify the port number in addition to mountpoint and credentials, so we can run multiple instances of the EGA Fuse client?
The error we get is this:
$> sudo journalctl -u ega-fuse-client@cineca
-- Logs begin at Thu 2021-03-18 14:19:34 UTC, end at Mon 2021-08-02 15:20:59 UTC. --
Aug 02 12:19:39 gearshift systemd[1]: Started EGA Fuse Client for cineca mount..
Aug 02 12:19:40 gearshift systemd[1]: Stopping EGA Fuse Client for cineca mount....
Aug 02 12:19:40 gearshift systemd[1]: Stopped EGA Fuse Client for cineca mount..
Aug 02 12:19:40 gearshift systemd[1]: Started EGA Fuse Client for cineca mount..
Aug 02 12:19:44 gearshift env[19674]: ,------. ,----. ,---. ,------. ,--. ,--. ,---. ,------. ,-----. ,--. ,--. ,------. ,--. ,--. ,--------.
Aug 02 12:19:44 gearshift env[19674]: | .---' ' .-./ / O \ | .---' | | | | ' .-' | .---' ' .--./ | | | | | .---' | ,'.| | '--. .--'
Aug 02 12:19:44 gearshift env[19674]: | `--, | | .---. | .-. | | `--, | | | | `. `-. | `--, | | | | | | | `--, | |' ' | | |
Aug 02 12:19:44 gearshift env[19674]: | `---. ' '--' | | | | | | |` ' '-' ' .-' | | `---. ' '--'\ | '--. | | | `---. | | ` | | |
Aug 02 12:19:44 gearshift env[19674]: `------' `------' `--' `--' `--' `-----' `-----' `------' `-----' `-----' `--' `------' `--' `--' `--'
Aug 02 12:19:44 gearshift env[19674]: 2021-08-02 12:19:44.297 INFO 19674 --- [ main] u.ac.ebi.ega.egafuse.EgaFuseApplication : Starting EgaFuseApplication v2.0.0 on gearshift with PID 19674 (/usr/local/ega-fuse-client/ega-fuse-client-2.0.0.jar started by root in /)
Aug 02 12:19:44 gearshift env[19674]: 2021-08-02 12:19:44.302 INFO 19674 --- [ main] u.ac.ebi.ega.egafuse.EgaFuseApplication : No active profile set, falling back to default profiles: default
Aug 02 12:19:45 gearshift env[19674]: 2021-08-02 12:19:45.980 INFO 19674 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)
Aug 02 12:19:46 gearshift env[19674]: 2021-08-02 12:19:46.030 INFO 19674 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
Aug 02 12:19:46 gearshift env[19674]: 2021-08-02 12:19:46.031 INFO 19674 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.31]
Aug 02 12:19:46 gearshift env[19674]: 2021-08-02 12:19:46.323 INFO 19674 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
Aug 02 12:19:46 gearshift env[19674]: 2021-08-02 12:19:46.324 INFO 19674 --- [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 1856 ms
Aug 02 12:19:47 gearshift env[19674]: 2021-08-02 12:19:47.526 INFO 19674 --- [ main] o.s.s.concurrent.ThreadPoolTaskExecutor : Initializing ExecutorService 'applicationTaskExecutor'
Aug 02 12:19:47 gearshift env[19674]: 2021-08-02 12:19:47.735 INFO 19674 --- [ main] o.apache.catalina.core.StandardService : Stopping service [Tomcat]
Aug 02 12:19:47 gearshift env[19674]: 2021-08-02 12:19:47.755 INFO 19674 --- [ main] ConditionEvaluationReportLoggingListener :
Aug 02 12:19:47 gearshift env[19674]: Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
Aug 02 12:19:47 gearshift env[19674]: 2021-08-02 12:19:47.757 ERROR 19674 --- [ main] o.s.b.d.LoggingFailureAnalysisReporter :
Aug 02 12:19:47 gearshift env[19674]: ***************************
Aug 02 12:19:47 gearshift env[19674]: APPLICATION FAILED TO START
Aug 02 12:19:47 gearshift env[19674]: ***************************
Aug 02 12:19:47 gearshift env[19674]: Description:
Aug 02 12:19:47 gearshift env[19674]: Web server failed to start. Port 8080 was already in use.
Aug 02 12:19:47 gearshift env[19674]: Action:
Aug 02 12:19:47 gearshift env[19674]: Identify and stop the process that's listening on port 8080 or configure this application to listen on another port.
Aug 02 12:19:47 gearshift env[19674]: 2021-08-02 12:19:47.760 INFO 19674 --- [ main] o.s.s.concurrent.ThreadPoolTaskExecutor : Shutting down ExecutorService 'applicationTaskExecutor'
Aug 02 12:19:47 gearshift systemd[1]: ega-fuse-client@cineca.service: main process exited, code=exited, status=1/FAILURE
Aug 02 12:19:47 gearshift systemd[1]: Unit ega-fuse-client@cineca.service entered failed state.
Aug 02 12:19:47 gearshift systemd[1]: ega-fuse-client@cineca.service failed.
This is correct as we already have another instances of the EGA Fuse client running for Solve-RD:
Dear developers,
We use the EGA Fuse client for access to specific datasets for the Solve-RD project: works great :) This is inside a folder for this project on an HPC cluster. Now we want to do the same for other datasets for another project (Cineca). Obviously that has to be mounted in a different location and with different permissions, but it is on the same HPC cluster. Running a second instance of the EGA Fuse client fails, because port 8080 is already in use. Would it be possible to add another commanline option to specify the port number in addition to mountpoint and credentials, so we can run multiple instances of the EGA Fuse client?
The error we get is this:
This is correct as we already have another instances of the EGA Fuse client running for Solve-RD:
The text was updated successfully, but these errors were encountered: