Heimdall Update script

[bussio]

When I run your update script for Heimdall to update from v2.4.8 to v2.4.9, the script runs without problems in LXC. If I call afterwards in the browser "Heimdall Dashboard Interface - IP:7990", then I got this message:

Safari cannot open the page "192.168.178.106:7990" because the server has terminated the connection
unexpectedly terminated the connection. This sometimes happens when a server is overloaded. Wait
a few minutes and then try again.

[tteck]

What does systemctl status heimdall.service show?

[bussio]

This is the console output:
root0heimdalldashboard:~# systemctl status heimdall. service

• heimdall.serviceHeimdall
  Loaded: loaded (/etc/systemd/system/heimdall. service; enabled; vendor preset: enabled)
  Active: activating (auto-restart) (Result: exit-code) since Sat 2022-04-02 11:59:08 UTC; 1s ago
  Process: 6355 ExecStart=/usr/bin/php artisan serve--port 7990--host 0.0.0.0 (code=exited, status=1/FAILURE)
  Main PID: 6355 (code=exited, status=1/FAILURE)
  CPU: 130ms
  Apr 02 11:59:08 heimdalldashboard systemd[1]: heimdall. service: Main process exited, code=exited, status=1/FAILURE
  Apr 02 11:59:08 heimdalldashboard systemd[1]: heimdall.service: Failed with result exit-code'

[tteck]

output from cat /etc/systemd/system/heimdall.service

[bussio]

root@heimdalldashboard:#cat/etc/systemd/system/heimdall.service
[Unit]
Description=Heimdall
After=network.target
[Service]
Restart=always
RestartSec=5
Type=simple
User=root
WorkingDirectory=/opt/Heimdall
ExecStart=/usr/bin/php artisan serve-port 7990-host 0.0.0.0
TimeoutStopSec=30
[Install]
WantedBy=multi-user.target
root@heimdalldashboard:#

[tteck]

why the line through?

[bussio]

Soory, in the original all this is not crossed out ...

[tteck]

output from ls /opt

[bussio]

root@heimdalldashboard:~# ls /opt
Heimdall

[tteck]

Everything looks correct. Have you rebooted the LXC?

[bussio]

I just did it again ... the error message of the browser remains.

[tteck]

I have no idea then. Everything looks correct
things to try:

1. raise cores from 1 to 2 then systemctl start heimdall.service
2. re-run the update script
   🤷🏻‍♂️

[bussio]

I did ... unfortunately no change?!

[tteck]

If you create another Heimdall LXC, will it start?

[bussio]

I delete the LXC once and recreate it. Then I will get back to you ...

[tteck]

You don't have to delete the original yet

[bussio]

OK.

[bussio]

Yes, the newly created LXC starts normally

[tteck]

Have you updated the original host lately apt update?

[bussio]

Yes. All packages are up to date.

[tteck]

I have no idea what could have happened.
Looks like starting over then. Hate that, sorry

[bussio]

Does it do anything if I run the update script again in the newly created LXC with Heimdall 2.4.9?

[tteck]

Just re-updates. I just did mine to see

[bussio]

I ran the script again in the new LXC.
After that the LXC was still executable ...

[tteck]

Something corrupted the original, somehow 🤷🏻‍♂️

[bussio]

Ok, I will continue to use the new LXC for now ... maybe you will find something until the next version.
Thanks first ...

[tteck]

v2.4.10 is now out