[RESOLVED] Another kolibri server running

Support Kolibri
1

If you have a specific technical inquiry, construct your post with the following:

Summary

After upgrading to v. 0.16.2, Kolibri will not launch. Journal reports there is another Kolibri server running. I stop that (don’t know why there is anyway). Still the kolibri.service fails to start.

Technical details

  • 0.16.2
  • RPi 400
  • Any

Here are the details from the terminal session I was running:

**pi@kolibri-saaresalaam**:**~ $** systemctl status kolibri.service

**●** kolibri.service - LSB: kolibri daemon, an offline education platform

Loaded: loaded (/etc/init.d/kolibri; enabled; vendor preset: enabled)

Active: **failed** (Result: exit-code) since Thu 2024-07-11 17:21:28 WAT; 3min 14s ago

Process: 545 ExecStart=/etc/init.d/kolibri start **(code=exited, status=1/FAILURE)**

CPU: 13.633s

Jul 11 17:21:19 kolibri-saaresalaam kolibri[689]: INFO 2024-07-11 17:21:19,067 Running Kolibri with the following settings: kolibri.deployment.default.settings.base

Jul 11 17:21:19 kolibri-saaresalaam kolibri[689]: INFO 2024-07-11 17:21:19,111 Configuring Redis: maxmemory-policy allkeys-lru

Jul 11 17:21:19 kolibri-saaresalaam kolibri[689]: INFO 2024-07-11 17:21:19,115 Configuring Redis: maxmemory 397759693

Jul 11 17:21:21 kolibri-saaresalaam kolibri[689]: INFO 2024-07-11 17:21:21,681 Starting Kolibri 0.16.2

Jul 11 17:21:26 kolibri-saaresalaam kolibri[689]: ERROR 2024-07-11 17:21:26,740 There is another Kolibri server running. Please use `kolibri stop` and try again.

Jul 11 17:21:28 kolibri-saaresalaam runuser[669]: pam_unix(runuser:session): session closed for user pi

Jul 11 17:21:28 kolibri-saaresalaam systemd[1]: **kolibri.service: Control process exited, code=exited, status=1/FAILURE**

Jul 11 17:21:28 kolibri-saaresalaam systemd[1]: **kolibri.service: Failed with result 'exit-code'.**

Jul 11 17:21:28 kolibri-saaresalaam systemd[1]: **Failed to start LSB: kolibri daemon, an offline education platform.**

Jul 11 17:21:28 kolibri-saaresalaam systemd[1]: **kolibri.service: Consumed 13.633s CPU time.**

**pi@kolibri-saaresalaam**:**~ $** kolibrii stop

-bash: kolibrii: command not found

**pi@kolibri-saaresalaam**:**~ $** kolibri stop

INFO 2024-07-11 17:29:01,091 Option DEBUG in section [Server] being overridden by environment variable KOLIBRI_DEBUG

INFO 2024-07-11 17:29:01,097 Option DEBUG_LOG_DATABASE in section [Server] being overridden by environment variable KOLIBRI_DEBUG_LOG_DATABASE

INFO 2024-07-11 17:29:02,624 Kolibri server has successfully been stopped.

**pi@kolibri-saaresalaam**:**~ $** kolibri status

Stopped (1)

**pi@kolibri-saaresalaam**:**~ $** systemctl status kolibri.service

**●** kolibri.service - LSB: kolibri daemon, an offline education platform

Loaded: loaded (/etc/init.d/kolibri; enabled; vendor preset: enabled)

Active: **failed** (Result: exit-code) since Thu 2024-07-11 17:21:28 WAT; 7min ago

Process: 545 ExecStart=/etc/init.d/kolibri start **(code=exited, status=1/FAILURE)**

CPU: 13.633s

Jul 11 17:21:19 kolibri-saaresalaam kolibri[689]: INFO 2024-07-11 17:21:19,067 Running Kolibri with the following settings: kolibri.deployment.default.settings.base

Jul 11 17:21:19 kolibri-saaresalaam kolibri[689]: INFO 2024-07-11 17:21:19,111 Configuring Redis: maxmemory-policy allkeys-lru

Jul 11 17:21:19 kolibri-saaresalaam kolibri[689]: INFO 2024-07-11 17:21:19,115 Configuring Redis: maxmemory 397759693

Jul 11 17:21:21 kolibri-saaresalaam kolibri[689]: INFO 2024-07-11 17:21:21,681 Starting Kolibri 0.16.2

Jul 11 17:21:26 kolibri-saaresalaam kolibri[689]: ERROR 2024-07-11 17:21:26,740 There is another Kolibri server running. Please use `kolibri stop` and try again.

Jul 11 17:21:28 kolibri-saaresalaam runuser[669]: pam_unix(runuser:session): session closed for user pi

Jul 11 17:21:28 kolibri-saaresalaam systemd[1]: **kolibri.service: Control process exited, code=exited, status=1/FAILURE**

Jul 11 17:21:28 kolibri-saaresalaam systemd[1]: **kolibri.service: Failed with result 'exit-code'.**

Jul 11 17:21:28 kolibri-saaresalaam systemd[1]: **Failed to start LSB: kolibri daemon, an offline education platform.**

Jul 11 17:21:28 kolibri-saaresalaam systemd[1]: **kolibri.service: Consumed 13.633s CPU time.**

**pi@kolibri-saaresalaam**:**~ $** sudo systemctl start kollibri.service

Failed to start kollibri.service: Unit kollibri.service not found.

**pi@kolibri-saaresalaam**:**~ $** sudo systemctl start kolibri.service

Job for kolibri.service failed because the control process exited with error code.

See "systemctl status kolibri.service" and "journalctl -xe" for details.

**pi@kolibri-saaresalaam**:**~ $** journalctl -xe

░░ A start job for unit kolibri.service has begun execution.

░░

░░ The job identifier is 2387.

Jul 11 17:30:03 kolibri-saaresalaam runuser[2452]: pam_unix(runuser:session): session opened for user pi(uid=1000) by (uid=0)

Jul 11 17:30:08 kolibri-saaresalaam kolibri[2453]: INFO 2024-07-11 17:30:08,756 Option DEBUG in section [Server] being overridden by environment variable KOLIBRI_DEB>

Jul 11 17:30:08 kolibri-saaresalaam kolibri[2453]: INFO 2024-07-11 17:30:08,759 Option DEBUG_LOG_DATABASE in section [Server] being overridden by environment variabl>

Jul 11 17:30:09 kolibri-saaresalaam kolibri[2453]: /usr/lib/python3/dist-packages/kolibri/dist/rest_framework/utils/serializer_helpers.py:107: SyntaxWarning: "is" with a>

Jul 11 17:30:09 kolibri-saaresalaam kolibri[2453]: if value is None or value is '':

Jul 11 17:30:10 kolibri-saaresalaam kolibri[2453]: INFO 2024-07-11 17:30:10,717 Running Kolibri with the following settings: kolibri.deployment.default.settings.base

Jul 11 17:30:11 kolibri-saaresalaam kolibri[2453]: INFO 2024-07-11 17:30:11,783 Starting Kolibri 0.16.2

Jul 11 17:30:16 kolibri-saaresalaam kolibri[2453]: ERROR 2024-07-11 17:30:16,826 There is another Kolibri server running. Please use `kolibri stop` and try again.

Jul 11 17:30:17 kolibri-saaresalaam runuser[2452]: pam_unix(runuser:session): session closed for user pi

Jul 11 17:30:17 kolibri-saaresalaam systemd[1]: **kolibri.service: Control process exited, code=exited, status=1/FAILURE**

░░ Subject: Unit process exited

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ An ExecStart= process belonging to unit kolibri.service has exited.

░░

░░ The process' exit code is 'exited' and its exit status is 1.

Jul 11 17:30:17 kolibri-saaresalaam systemd[1]: **kolibri.service: Failed with result 'exit-code'.**

░░ Subject: Unit failed

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ The unit kolibri.service has entered the 'failed' state with result 'exit-code'.

Jul 11 17:30:17 kolibri-saaresalaam systemd[1]: **Failed to start LSB: kolibri daemon, an offline education platform.**

░░ Subject: A start job for unit kolibri.service has failed

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ A start job for unit kolibri.service has finished with a failure.

░░

░░ The job identifier is 2387 and the job result is failed.

Jul 11 17:30:17 kolibri-saaresalaam systemd[1]: **kolibri.service: Consumed 8.466s CPU time.**

░░ Subject: Resources consumed by unit runtime

░░ Defined-By: systemd

░░ Support: https://www.debian.org/support

░░

░░ The unit kolibri.service completed and consumed the indicated resources.

Jul 11 17:30:17 kolibri-saaresalaam sudo[2437]: pam_unix(sudo:session): session closed for user root
2

Hi @cjackson , we’re sorry you are experiencing these issues.

I slightly retouched your post to apply the code formatting, to make it easier to review. Hoping @jredrejo will have a moment to look at this terminal output.

3

Thank you @RadinaMatic!

How do you do the code formatting?

4

hi @cjackson could it be you were running kolibri-server on this machine too?
If that’s the case, it would explain your problem, don’t do

systemctl start kolibri

just do
systemctl restart kolibri-server

If this is not the case, did you try restarting the server? a lock file might be remaining from a previous run and cheating the system to believe it’s still running. Rebooting is the easiest way to delete it.

Regards
José

5

Hello, Chris!

After you paste the code output in the post, you can manually type three backtics (```) above and below it, or select the full output and use the Preformatted text button (looks like </>) from the post toolbar. Shortcut for this feature is Ctrl+e.

6

@jredrejo : I should post this so that you and everyone knows that this was not a problem caused by the upgrade. It was an oversight by me. I discovered that my browser was automatically adding “HTTPS” rather than “HTTP” the the URL I have set up on our network here. That was the cause of not being able to access Kolibri.

Problem sovled.

7

@RadinaMatic : Thank you for that explanation.

1 Like