seb-server process restarting repeatedly

[takuya-chan]

I pulled the anhefti/seb-server:v2.0-stable image from GitHub and started the container using docker compose up -d. However, when I run the docker compose ps command, I get the following output:

NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS
seb-server anhefti/seb-server:v2.0-stable "/__cacert_entrypoin..." seb-server About a minute ago Restarting (1) 10 seconds ago

It seems the container is repeatedly restarting approximately every 60 seconds.
I checked the logs using docker logs seb-server, but all I see is the Spring Boot startup banner looping endlessly—there’s no clear indication of why the container keeps restarting.

The docker-compose.yml I used is based on the sample provided in the official documentation, with only the server name and image name modified.

Does anyone know what might be causing seb-server to continuously restart like this?

Thank you.

[anhefti]

Hi

Then the container is not starting up correctly and has error in the log. What is your exact setup?
Please follow the instructions in the SEB Server installation documentation: https://seb-server-setup.readthedocs.io/en/latest/overview.html
and if the issue remains please use docker logs seb-server to get the logs from container to get more information about why it is not starting up correctly.

[takuya-chan]

Thanks for your reply.
When I run docker logs seb-server, the log output keeps repeating the following content(Spring Boot Logo and DEBUG messages) endlessly, and there’s no information at all about what might be causing the container to restart.

00:52:43.064 [main] DEBUG org.apache.ibatis.logging.LogFactory - Logging initialized using 'class org.apache.ibatis.logging.slf4j.Slf4jImpl' adapter.
00:52:43.068 [main] DEBUG org.apache.ibatis.logging.LogFactory - Logging initialized using 'class org.apache.ibatis.logging.slf4j.Slf4jImpl' adapter.

. ____ _ __ _ _
/\ / ' __ _ () __ __ _ \ \ \
( ( )__ | '_ | '| | ' / ` | \ \ \
\/ )| |)| | | | | || (| | ) ) ) )
' || .__|| ||| |_, | / / / /
=========||==============|/=////
:: Spring Boot :: (v2.6.15)

00:53:47.642 [main] DEBUG org.apache.ibatis.logging.LogFactory - Logging initialized using 'class org.apache.ibatis.logging.slf4j.Slf4jImpl' adapter.
00:53:47.646 [main] DEBUG org.apache.ibatis.logging.LogFactory - Logging initialized using 'class org.apache.ibatis.logging.slf4j.Slf4jImpl' adapter.

. ____ _ __ _ _
/\ / ' __ _ () __ __ _ \ \ \
( ( )__ | '_ | '| | ' / ` | \ \ \
\/ )| |)| | | | | || (| | ) ) ) )
' || .__|| ||| |_, | / / / /
=========||==============|/=////
:: Spring Boot :: (v2.6.15)

---

For the SEB Server installation, I used the following docker-compose.yml file:

---

services:
mariadb:
image: "mariadb:10.5"
container_name: seb-server-mariadb
environment:
- MYSQL_ROOT_PASSWORD=${SEBSERVER_PWD}
volumes:
- seb-server-mariadb:/var/lib/mysql
networks:
- seb-server-network
restart: unless-stopped

seb-server:
image: "anhefti/seb-server:v2.0-stable"
container_name: seb-server
environment:
- JAVA_HEAP_MIN=1G
- JAVA_HEAP_MAX=6G
- spring_profiles_active=gui,ws,prod-ws,prod-gui,prod
- datastore_mariadb_server_address=seb-server-mariadb
- datastore_mariadb_server_port=3306
- sebserver_password=${SEBSERVER_PWD}
- sebserver_mariadb_password=${SEBSERVER_PWD}
- sebserver_init_adminaccount_init_pwd=${USER_PWD}

    # Set the below URL component settings from where the the web-service is externally available
    # NOTE: This must be the address from that the service is externally available (not network internal address)
    - sebserver_webservice_http_external_scheme=http
    - sebserver_webservice_http_external_servername=####.#######.ac.jp
    - sebserver_webservice_http_external_port=8080
  ports:
      - 8080:8080
  networks:
      - seb-server-network
  depends_on:
      - "mariadb"
  restart: unless-stopped

networks:
seb-server-network:
name: seb-server-network

volumes:
seb-server-mariadb:
name: seb-server-db

In the project directory where this file is located, I ran docker compose pull, and after it completed successfully, I started the container with docker compose up -d.

At my university, we are currently in the early stages of testing Safe Exam Browser. During this process, I thought that SEB Server might help solve some of the issues we've encountered. However, it's difficult to fully understand what it can do without actually running it. We're also at the stage where we’d like to try it out to see, for example, how much load features like taking screen snapshots would place on the server and network when enabled.

[anhefti]

Hi

This docker compose seems to be a very old one without screen proctoring at all. Again, please follow the installation guide: https://seb-server-setup.readthedocs.io/en/latest/general_installation.html and use the latest stable installation templates from the SEB Server setup repository: https://github.com/SafeExamBrowser/seb-server-setup

We recommend installing the "prod/bundled" setup and make your TLS termination on external proxy. This is described here: https://seb-server-setup.readthedocs.io/en/latest/install-production.html#bundled-setup-with-or-without-tls-termination

Please also read the SEB Server user guide to get a overview of SEB Server and its features: https://seb-server.readthedocs.io/en/latest/#

[anhefti]

I also tried with the docker-compose.yml from the Docker Hub Page, that seems to be the one you have. If you follow the instructions correctly and fill in the missing env-variables or create a .env file within the installation directory, it seems still to work correctly.

But if you want to also test with screen proctoring, you will need the whole setup like described above.