Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dietpi-dashboard.service: Failed with result 'signal'. #763

Closed
CrueBrew opened this issue Mar 14, 2024 · 5 comments · May be fixed by #765
Closed

dietpi-dashboard.service: Failed with result 'signal'. #763

CrueBrew opened this issue Mar 14, 2024 · 5 comments · May be fixed by #765
Labels
bug Something isn't working

Comments

@CrueBrew
Copy link

When running the Stable release of DietPi-Dashboard, it fails to run.

root@DietPi5:~# systemctl status dietpi-dashboard
× dietpi-dashboard.service - Web Dashboard (DietPi)
     Loaded: loaded (/etc/systemd/system/dietpi-dashboard.service; enabled; preset: enabled)
     Active: failed (Result: signal) since Thu 2024-03-14 11:34:48 EDT; 15s ago
   Duration: 20ms
    Process: 15174 ExecStart=/opt/dietpi-dashboard/dietpi-dashboard (code=killed, signal=SEGV)
   Main PID: 15174 (code=killed, signal=SEGV)
        CPU: 1ms

Mar 14 11:34:48 DietPi5 systemd[1]: Started dietpi-dashboard.service - Web Dashboard (DietPi).
Mar 14 11:34:48 DietPi5 systemd[1]: dietpi-dashboard.service: Main process exited, code=killed, status=11/SEGV
Mar 14 11:34:48 DietPi5 systemd[1]: dietpi-dashboard.service: Failed with result 'signal'.

I am unable to try the Nightly release as it fails to install. It looks like the download link is broke.
Here is the results from that.

#### Details:
- Date           | Thu Mar 14 11:19:26 EDT 2024
- DietPi version | v9.1.1 (MichaIng/master)
- Image creator  |
- Pre-image      |
- Hardware       | RPi 5 Model B (aarch64) (ID=5)
- Kernel version | `Linux DietPi5 6.6.20+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64 GNU/Linux`
- Distro         | bookworm (ID=7,RASPBIAN=0)
- Command        | `curl -sSfL https://nightly.link/ravenclaw900/DietPi-Dashboard/workflows/push-build/main/dietpi-dashboard-aarch64.zip -o dietpi-dashboard-aarch64.zip`
- Exit code      | 22
- Software title | DietPi-Software

I saw you fixed a similar issue before and requested this information, so I'm going to go ahead and include it.

root@DietPi5:~# journalctl -u dietpi-dashboard
Mar 11 22:44:58 DietPi5 systemd[1]: Started dietpi-dashboard.service - Web Dashboard (DietPi).
Mar 11 22:44:58 DietPi5 systemd[1]: dietpi-dashboard.service: Main process exited, code=killed, status=11/SEGV
Mar 11 22:44:58 DietPi5 systemd[1]: dietpi-dashboard.service: Failed with result 'signal'.
Mar 14 10:49:10 DietPi5 systemd[1]: Started dietpi-dashboard.service - Web Dashboard (DietPi).
Mar 14 10:49:10 DietPi5 systemd[1]: dietpi-dashboard.service: Main process exited, code=killed, status=11/SEGV
Mar 14 10:49:10 DietPi5 systemd[1]: dietpi-dashboard.service: Failed with result 'signal'.
Mar 14 10:52:06 DietPi5 systemd[1]: Started dietpi-dashboard.service - Web Dashboard (DietPi).
Mar 14 10:52:06 DietPi5 systemd[1]: dietpi-dashboard.service: Main process exited, code=killed, status=11/SEGV
Mar 14 10:52:06 DietPi5 systemd[1]: dietpi-dashboard.service: Failed with result 'signal'.
Mar 14 10:53:00 DietPi5 systemd[1]: Started dietpi-dashboard.service - Web Dashboard (DietPi).
Mar 14 10:53:00 DietPi5 systemd[1]: dietpi-dashboard.service: Main process exited, code=killed, status=11/SEGV
Mar 14 10:53:00 DietPi5 systemd[1]: dietpi-dashboard.service: Failed with result 'signal'.
Mar 14 11:34:48 DietPi5 systemd[1]: Started dietpi-dashboard.service - Web Dashboard (DietPi).
Mar 14 11:34:48 DietPi5 systemd[1]: dietpi-dashboard.service: Main process exited, code=killed, status=11/SEGV
Mar 14 11:34:48 DietPi5 systemd[1]: dietpi-dashboard.service: Failed with result 'signal'.
root@DietPi5:~# cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=1
G_DIETPI_VERSION_RC=1
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
G_LIVE_PATCH_STATUS[0]='not applicable'
root@DietPi5:~# echo $G_DISTRO_NAME $G_RASPBIAN
bookworm 0
root@DietPi5:~# uname -a
Linux DietPi5 6.6.20+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64 GNU/Linux
root@DietPi5:~# dmesg -l emerg,alert,crit,err,warn
[    1.174751] F2FS not supported on PAGE_SIZE(16384) != 4096
[    3.888606] rpivid_hevc: module is from the staging directory, the quality is unknown, you have been warned.
[   18.100859] systemd[639]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
root@DietPi5:~# dmesg | grep segfault
root@DietPi5:~#

Hopefully this can't point you to the right direction.
Thank you!

@CrueBrew CrueBrew added the bug Something isn't working label Mar 14, 2024
@Joulinar
Copy link
Collaborator

yes, you would need to the nightly build. However, it seems something wrong with the build process.

@MichaIng @ravenclaw900 can you have a look?

@MichaIng
Copy link
Collaborator

MichaIng commented Mar 15, 2024

Hmm strange. There is a clippy warning that args.get(0) has been replaced with args.first(), but the builds succeed and the artifacts are uploaded: https://github.com/ravenclaw900/DietPi-Dashboard/actions/runs/8292617773

So I guess https://nightly.link/ stopped updating its links for some reason. Maybe it requires the whole workflow to succeed, including the lint. I'll open a PR to apply the suggested changes.

EDIT: If really the failing clippy test is the reason for the missing nightly link, this will fix it: #765

@MichaIng MichaIng linked a pull request Mar 15, 2024 that will close this issue
@CrueBrew
Copy link
Author

Any updates on getting the nightly build working again?
Thanks!

@m0nkeecodes
Copy link

Any updates on getting the nightly build working again? Thanks!

@CrueBrew : I have never commented on GitHub before but I feel obligated to share this with you and possibly others after finally getting dietpi-dashboard nightly build to run successfully on my Raspberry Pi 5 8gb.

Hardware: RPi 5 8gb
Kernel: 6.6.20+rpt-rpi-2712
Architecture: aarch64
OS & Version: DietPi - 9.2.1

First off, a big thank you to @MichaIng for this post just above.

Click here for the solution, a.k.a Tl;dr:

Working nightly links: https://nightly.link/ravenclaw900/DietPi-Dashboard/actions/runs/8302631750
When you encounter the error while installing the nightly build via dietpi-software, select the option to edit the command line that crashed and replace the url with the one for your architecture. This is the one for RPi5: https://nightly.link/ravenclaw900/DietPi-Dashboard/actions/runs/8302631750/dietpi-dashboard-aarch64.zip
Then run the command and it should successfully complete the installation. Then restart the dietpi-dashboard service and access the web interface via http://192.168.X.XX:5252.

Click here for the explanation incl. instructions:

This part is for those like me who are curious about the details or experience similar issues in the future.
I went to https://nightly.link/ and pasted https://github.com/ravenclaw900/DietPi-Dashboard/actions/runs/8302631750 from MichaIng's post to generate this nightly link: https://nightly.link/ravenclaw900/DietPi-Dashboard/actions/runs/8302631750
Then I uninstalled dietpi-dashboard and rebooted my Pi5 to be sure, even though executing "dietpi-software reinstall 200" to reinstall dietpi-dashboard and selecting nightly build probably would do just fine.

Regardless of the method, start the installation and choose nightly when asked. If you have the same problem I had, then this is where we encounter the error. DietPi will give you a few options where one is to edit the command that caused the error. Select that and replace the url with one of the nightly links. For Pi5 it is: https://nightly.link/ravenclaw900/DietPi-Dashboard/actions/runs/8302631750/dietpi-dashboard-aarch64.zip
Let the rest of the command line be as is. Then run the command and the install should succeed.
When finished, run "systemctl restart dietpi-dashboard.service" and you're done. You should now be able to access the web interface by going to http://192.168.X.XX:5252. If you can't log in due to incorrect password, continue reading below.

I don't know if this part will be the same for you but I will share it to safe:
When going to http://192.168.X.XX:5252 it will ask for a password that, according to the DietPi wiki, is "dietpi". This is probably my fault, but, it wouldn't accept the password. So I went into "cd /opt/dietpi-dashboard" and opened "config.toml" to set a new password. You do this by running the command "echo -n 'YOUR_PASSWORD' | sha512sum" in the terminal and replacing the long hash = "XXXXXXXX" string in the config.toml file with the one you generated. Then save the file and exit back to terminal. Once there, run "systemctl restart dietpi-dashboard.service" and you're done. Now the web interface should let you in with your new password.

I hope it can help someone. :)

Cheers!
/m0nkee

@CrueBrew
Copy link
Author

Any updates on getting the nightly build working again? Thanks!

@CrueBrew : I have never commented on GitHub before but I feel obligated to share this with you and possibly others after finally getting dietpi-dashboard nightly build to run successfully on my Raspberry Pi 5 8gb.

Hardware: RPi 5 8gb Kernel: 6.6.20+rpt-rpi-2712 Architecture: aarch64 OS & Version: DietPi - 9.2.1

First off, a big thank you to @MichaIng for this post just above.

Click here for the solution, a.k.a Tl;dr:
Working nightly links: https://nightly.link/ravenclaw900/DietPi-Dashboard/actions/runs/8302631750 When you encounter the error while installing the nightly build via dietpi-software, select the option to edit the command line that crashed and replace the url with the one for your architecture. This is the one for RPi5: https://nightly.link/ravenclaw900/DietPi-Dashboard/actions/runs/8302631750/dietpi-dashboard-aarch64.zip Then run the command and it should successfully complete the installation. Then restart the dietpi-dashboard service and access the web interface via http://192.168.X.XX:5252.

Click here for the explanation incl. instructions:
I hope it can help someone. :)

Cheers! /m0nkee

Great! That go it working. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants