Just trying to connect the Waveshare 10.1inch HDMI LCD display for my Google coral developer board. As i am not sure about this...
Weston service status:
weston.service - Weston Wayland Compositor (on tty7)
Loaded: loaded (/lib/systemd/system/weston.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-12-28 04:58:03 UTC; 48min ago
Docs: man:weston(1)
man:weston.ini(5)
http://wayland.freedesktop.org/
Process: 3873 ExecStart=/usr/bin/weston --log=${XDG_RUNTIME_DIR}/weston.log (code=exited, status=1/FAILURE)
Main PID: 3873 (code=exited, status=1/FAILURE)
Dec 28 04:58:02 zippy-orange systemd[1]: Starting Weston Wayland Compositor (on tty7)...
Dec 28 04:58:02 zippy-orange systemd[3873]: pam_unix(login:session): session opened for user mendel by mendel(ui
Dec 28 04:58:03 zippy-orange systemd[1]: weston.service: Main process exited, code=exited, status=1/FAILURE
Dec 28 04:58:03 zippy-orange systemd[1]: weston.service: Failed with result 'exit-code'.
Dec 28 04:58:03 zippy-orange systemd[1]: Failed to start Weston Wayland Compositor (on tty7).
and also I have searched for solutions, (but not helped me out)
https://gitlab.freedesktop.org/wayland/weston/-/issues/204
https://github.com/waveshare/LCD-show.git
Any suggestions or troubleshoot for this ?
The ix8M kernel is limited in the range of clock speeds that it supports, and small HDMI monitors generally don't work with it. You can see more about it here:
https://community.nxp.com/t5/i-MX-Processors/HDMI-DRM-custom-resolution-and-clock-frequency/m-p/1029696
Related
I am following the instructions here to install Telit asset gateway on my Raspberry Pi. This is a fresh install of 64-bit Pi OS running on a Pi 4.
Installation seems to go well and I get the message
Updating file permissions...
Running post-install commands...
systemd detected, installing deviceWISE services
Installation is complete.
I then check to see if the service is running using systemctl status devicewise.service and it returns this:
● devicewise.service - deviceWISE Asset Gateway
Loaded: loaded (/etc/systemd/system/devicewise.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-12-07 17:19:36 GMT; 19ms ago
Main PID: 2846
Tasks: 1 (limit: 4164)
CPU: 6ms
CGroup: /system.slice/devicewise.service
Dec 07 17:19:36 raspberrypi systemd[1]: Started deviceWISE Asset Gateway.
Dec 07 17:19:36 raspberrypi systemd[2846]: devicewise.service: Failed to execute /opt/dw/dwcore/dwcore: No such file or directory
Dec 07 17:19:36 raspberrypi systemd[2846]: devicewise.service: Failed at step EXEC spawning /opt/dw/dwcore/dwcore: No such file or di>
Dec 07 17:19:36 raspberrypi systemd[1]: devicewise.service: Main process exited, code=exited, status=203/EXEC
Dec 07 17:19:36 raspberrypi systemd[1]: devicewise.service: Failed with result 'exit-code'.
If I then try again it shows this:
● devicewise.service - deviceWISE Asset Gateway
Loaded: loaded (/etc/systemd/system/devicewise.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Wed 2022-12-07 17:19:55 GMT; 2s ago
Process: 2852 ExecStart=/opt/dw/dwcore/dwcore (code=exited, status=203/EXEC)
Main PID: 2852 (code=exited, status=203/EXEC)
CPU: 6ms
Telit requires the 32-bit version of Raspberry Pi OS to be running. Hopefully there will be a 64-bit version of DeviceWise for ARM in the near future.
ssh service is not getting started after upgrading debian 8 jessie to debian 9 strech
● ssh.service - OpenBSD Secure Shell server Loaded: loaded
(/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2021-05-28 13:36:30 UTC;
10min ago Process: 2155 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS
(code=exited, status=255) Process: 2152 ExecStartPre=/usr/sbin/sshd
-t (code=exited, status=0/SUCCESS) Main PID: 2155 (code=exited, status=255)
May 28 13:36:29 ip-172-31-43-40 systemd[1]: Starting OpenBSD Secure
Shell server... May 28 13:36:30 ip-172-31-43-40 systemd[1]:
ssh.service: Main process exited, code=exited, status=255/n/a May 28
13:36:30 ip-172-31-43-40 systemd[1]: Failed to start OpenBSD Secure
Shell server. May 28 13:36:30 ip-172-31-43-40 systemd[1]: ssh.service:
Unit entered failed state. May 28 13:36:30 ip-172-31-43-40 systemd[1]:
ssh.service: Failed with result 'exit-code'.
kindly check the source list, in your source list might be something that disables the SSH
kindly use the different source list
Kindly change your /etc/apt/source.list to this Link it might work.
I'm trying to launch a simple bash script called script-startup.sh when my raspberry Pi boots, using systemd. This script only contains some basic actions on files (copying, moving, executing binaries) and calls make as well to compile bits of codes.
I created a new file with path /etc/systemd/system/baymabx.service :
[Unit]
Description=Baymabx
After=pm2-pi
[Service]
ExecStart=/home/pi/Desktop/baymabx/script-startup.sh
Launching /home/pi/Desktop/baymabx/script-startup.sh in the terminal works as it is intended to be. Also, pm2-pi.service is pm2 starting my backend server, that I need before using my script.
However, after doing systemctl start baymabx and systemctl status baymabx, I get :
● baymabx.service - Baymabx
Loaded: loaded (/etc/systemd/system/baymabx.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2020-12-11 01:34:06 CET; 3min 2s ago
Process: 359 ExecStart=/home/pi/Desktop/baymabx/script-startup.sh (code=exited, status=203/EXEC)
Main PID: 359 (code=exited, status=203/EXEC)
Dec 11 01:34:06 raspberrypi systemd[1]: Started Baymabx.
Dec 11 01:34:06 raspberrypi systemd[359]: baymabx.service: Failed to execute command: Exec format error
Dec 11 01:34:06 raspberrypi systemd[359]: baymabx.service: Failed at step EXEC spawning /home/pi/Desktop/baymabx/script-startup.sh: Exec format error
Dec 11 01:34:06 raspberrypi systemd[1]: baymabx.service: Main process exited, code=exited, status=203/EXEC
Dec 11 01:34:06 raspberrypi systemd[1]: baymabx.service: Failed with result 'exit-code'.
Anyone know how I can get it to work ?
I was editing /etc/crontab when things turned south. I have no idea why, and I rolled back my changes on the /etc/crontab file but apache is still messed up and I can't access local development websites hosted on this machine. When I run systemctl status apache2.service this is what I get:
apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2020-10-04 11:27:33 MDT; 6min ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 2413 ExecStart=/usr/sbin/apachectl start (code=exited, status=203/EXEC)
Oct 04 11:27:33 pidev.local systemd[1]: Starting The Apache HTTP Server...
Oct 04 11:27:33 pidev.local systemd[2413]: apache2.service: Failed to execute command: No such file or directory
Oct 04 11:27:33 pidev.local systemd[2413]: apache2.service: Failed at step EXEC spawning /usr/sbin/apachectl: No such file or directory
Oct 04 11:27:33 pidev.local systemd[1]: apache2.service: Control process exited, code=exited, status=203/EXEC
Oct 04 11:27:33 pidev.local systemd[1]: apache2.service: Failed with result 'exit-code'.
Oct 04 11:27:33 pidev.local systemd[1]: Failed to start The Apache HTTP Server.
Any ideas? I can't seem to trace what's wrong here.
I finished to install Openstack Magnum service on CentOS 7, using this guide: http://docs.openstack.org/developer/magnum/install-guide-from-source.html
Checking the magnum-api and magnum-conductor services after reboot shows that the services are active, but few seconds later they are in failed state. The selinux is disabled, and the services are enabled.
Restarting the magnum api service:
[root#controller01 magnum]# systemctl restart magnum-api
magnum-api status OK:
[root#controller01 magnum]# systemctl status magnum-api
● magnum-api.service - OpenStack Magnum API Service
Loaded: loaded (/etc/systemd/system/magnum-api.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2016-11-08 09:50:01 IST; 1s ago
Main PID: 21705 (magnum-api)
CGroup: /system.slice/magnum-api.service
└─21705 /var/lib/magnum/env/bin/python /var/lib/magnum/env/bin/magnum-api
Nov 08 09:50:01 controller01 systemd[1]: Started OpenStack Magnum API Service.
Nov 08 09:50:01 controller01 systemd[1]: Starting OpenStack Magnum API Service...
magnum-api service is failed after few seconds:
[root#controller01 magnum]# systemctl status magnum-api
● magnum-api.service - OpenStack Magnum API Service
Loaded: loaded (/etc/systemd/system/magnum-api.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Tue 2016-11-08 09:50:03 IST; 6s ago
Process: 21705 ExecStart=/var/lib/magnum/env/bin/magnum-api (code=exited, status=1/FAILURE)
Main PID: 21705 (code=exited, status=1/FAILURE)
Nov 08 09:50:02 controller01 systemd[1]: magnum-api.service: main process exited, code=exited, status=1/FAILURE
Nov 08 09:50:02 controller01 systemd[1]: Unit magnum-api.service entered failed state.
Nov 08 09:50:02 controller01 systemd[1]: magnum-api.service failed.
Nov 08 09:50:03 controller01 systemd[1]: magnum-api.service holdoff time over, scheduling restart.
Nov 08 09:50:03 controller01 systemd[1]: start request repeated too quickly for magnum-api.service
Nov 08 09:50:03 controller01 systemd[1]: Failed to start OpenStack Magnum API Service.
Nov 08 09:50:03 controller01 systemd[1]: Unit magnum-api.service entered failed state.
Nov 08 09:50:03 controller01 systemd[1]: magnum-api.service failed.
Happens the same for the magnum-conductor service.
How can I fix this?
Thanks,
Dedi
Thanks #Petesh. I just figure it out. The issue was because I set in the magnum.conf file:
host = controller.
Once I replaced the "controller" with the ip, it works. In other words, set:
host = <controller_IP>.