Good morning Holger,
Have you updated the backend (unpacking the fs-update-3.0.1.tar.gz via the FirstSpirit installation directory)?
If so, did you then start the FirstSpirit server via the fs-server start script?
Yes, I did.
The fs5 start script is outdated and cannot be used with 2022.9.
A start as a service configured with the old version could also cause the effect.
Have a look at the fs-wrapper.log - maybe you will find a hint there.
-> Yes I tried fs5 start. fs-warapper.log show like this:
INFO | jvm 1 | 2022/09/12 08:49:49 | [0.214s][info][class,load] java.text.MessageFormat$Field source: jrt:/java.base
INFO | jvm 1 | 2022/09/12 08:49:49 | Error: Could not find or load main class de.espirit.firstspirit.server.CMSServer
INFO | jvm 1 | 2022/09/12 08:49:49 | Caused by: java.lang.ClassNotFoundException: de.espirit.firstspirit.server.CMSServer
INFO | jvm 1 | 2022/09/12 08:49:49 | [0.214s][info][class,load] java.lang.Shutdown source: jrt:/java.base
INFO | jvm 1 | 2022/09/12 08:49:49 | [0.214s][info][class,load] java.lang.Shutdown$Lock source: jrt:/java.base
DEBUG | wrapper | 2022/09/12 08:49:49 | Preparing to restart with mode 2.
DEBUG | wrapper | 2022/09/12 08:49:49 | JVM was only running for 0 seconds leading to a failed restart count of 1.
DEBUG | wrapper | 2022/09/12 08:49:49 | Enqueue Event 'jvm_failed_invocation'
FATAL | wrapper | 2022/09/12 08:49:49 | There were 1 failed launches in a row, each lasting less than 35 seconds. Giving up.
FATAL | wrapper | 2022/09/12 08:49:49 | There may be a configuration problem: please check the logs.
DEBUG | wrapper | 2022/09/12 08:49:49 | Enqueue Event 'jvm_max_failed_invocations'
DEBUG | wrapper | 2022/09/12 08:49:49 | Enqueue Event 'wrapper_stop'
DEBUG | wrapperp | 2022/09/12 08:49:50 | closing backend server.
If these hints do not help, please contact our Tech Support so that the problem can be analysed.
-> Yes please send an technical to support. Thank you
Regards,
Tuan Anh
