$ sudo systemctl start speech-dispatcherd.service
Job for speech-dispatcherd.service failed because the control process exited with error code.
See "systemctl status speech-dispatcherd.service" and "journalctl -xeu speech-dispatcherd.service" for details.
ov 10 21:42:32 wiley speech-dispatcher[3128]: [Wed Nov 10 21:42:32 2021 : 132158] speechd: Speech Dispatcher 0.10.2 starting
Nov 10 21:42:32 wiley systemd[1]: speech-dispatcherd.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ An ExecStart= process belonging to unit speech-dispatcherd.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 10 21:42:32 wiley systemd[1]: speech-dispatcherd.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ The unit speech-dispatcherd.service has entered the 'failed' state with result 'exit-code'.
Nov 10 21:42:32 wiley systemd[1]: Failed to start Speech-Dispatcher an high-level device independent layer for speech synthesis..
░░ Subject: A start job for unit speech-dispatcherd.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ A start job for unit speech-dispatcherd.service has finished with a failure.
░░
░░ The job identifier is 1578 and the job result is failed.
I'm trying to get speech api to work in firefox. If I type the command to speak from the cli it works fine, but voices array is empty in firefox.
I think speech-dispatcher needs to be running but it won't start on manjaro
Related
In Ubuntu 22.04
I have two service units that I have written.
One is terminated without problem by the ExecStop=/bin/kill -1 $MAINPID in the service file.
However, the other does not terminate normally in the same way as above.
$ sudo systemctl stop foo
$ systemctl status foo
× foo.service - foo server
Loaded: loaded (/etc/systemd/system/foo.service; disabled; vendor preset: enabled)
Active: failed (Result: timeout) since Thu 2023-02-16 19:28:31 KST; 2min 24s ago
Process: 141572 ExecStart=/opt/foo/sbin/foo_daemon/foo.py (code=killed, signal=HUP)
Process: 142097 ExecStop=/bin/kill -1 $MAINPID (code=exited, status=0/SUCCESS)
Main PID: 141572 (code=killed, signal=HUP)
CPU: 685ms
Feb 16 19:28:31 esm-op systemd[1]: foo.service: Failed with result 'timeout'.
Feb 16 19:28:31 esm-op systemd[1]: foo.service: Unit process 141605 (foo.py) remains running after unit stopped.
Feb 16 19:28:31 esm-op systemd[1]: foo.service: Unit process 141606 (foo.py) remains running after unit stopped.
Feb 16 19:28:31 esm-op systemd[1]: foo.service: Unit process 141607 (foo.py) remains running after unit stopped.
Feb 16 19:28:31 esm-op systemd[1]: foo.service: Unit process 141608 (foo.py) remains running after unit stopped.
Feb 16 19:28:31 esm-op systemd[1]: foo.service: Unit process 141609 (foo.py) remains running after unit stopped.
Below is my foo.service file.
[Unit]
Description=foo server
StartLimitIntervalSec=60
StartLimitBurst=3
[Service]
Environment="LD_LIBRARY_PATH=/opt/foo/lib"
ExecStart=/opt/foo/sbin/foo_daemon/foo.py
RestartSec=10
SuccessExitStatus=1 143 11
ExecStop=/bin/kill -1 $MAINPID
[Install]
WantedBy=graphical.target
Can someone help me?
When you make start of squid proxy server:
this massage appears (Job for squid.service failed because the control process exited with error code. See "systemctl status squid.service" and "journalctl -xe" for details.)
How to solve it?
the output:
-- Logs begin at Mon 2022-10-10 14:56:31 +03. –
Oct 13 19:36:40 toj-mgt-uv-fp01..com.sa systemd[1]: Starting Squid Web Proxy Server...
-- Subject: A start job for unit squid.service has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- A start job for unit squid.service has begun execution.
-- The job identifier is 62883.
Oct 13 19:36:40 toj-mgt-uv-fp01..com.sa squid[1051704]: 2022/10/13 19:36:40| ACL not found: fac
Oct 13 19:36:40 toj-mgt-uv-fp01..com.sa squid[1051704]: 2022/10/13 19:36:40| FATAL: Bungled /etc/squid/squid.conf line 6174: http_access allow fac
Oct 13 19:36:40 toj-mgt-uv-fp01..com.sa squid[1051704]: 2022/10/13 19:36:40| Squid Cache (Version 4.10): Terminated abnormally.
Oct 13 19:36:40 toj-mgt-uv-fp01..com.sa squid[1051704]: CPU Usage: 0.010 seconds = 0.000 user + 0.010 sys
Oct 13 19:36:40 toj-mgt-uv-fp01..com.sa squid[1051704]: Maximum Resident Size: 57888 KB
Oct 13 19:36:40 toj-mgt-uv-fp01..com.sa squid[1051704]: Page faults with physical i/o: 0
Oct 13 19:36:40 toj-mgt-uv-fp01..com.sa squid[1051704]: FATAL: Bungled /etc/squid/squid.conf line 6174: http_access allow fac
Oct 13 19:36:40 toj-mgt-uv-fp01..com.sa systemd[1]: squid.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- An ExecStartPre= process belonging to unit squid.service has exited.
-- The process' exit code is 'exited' and its exit status is 1.
Oct 13 19:36:40 toj-mgt-uv-fp01..com.sa systemd[1]: squid.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- The unit squid.service has entered the 'failed' state with result 'exit-code'.
Oct 13 19:36:40 toj-mgt-uv-fp01.****.com.sa systemd[1]: Failed to start Squid Web Proxy Server.
-- Subject: A start job for unit squid.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- A start job for unit squid.service has finished with a failure.
-- The job identifier is 62883 and the job result is failed.
thanks and regards.
So i tried to start elasticsearch with this command:
systemctl start elasticsearch.service
and i got this error :
Job for elasticsearch.service failed because a fatal signal was delivered to the control process.
See "systemctl status elasticsearch.service" and "journalctl -xe" for details.
this is "journalctl -xe" output :
mai 10 10:18:49 ouss kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/system.slice/elasticsearch.service,task=java,pid=24534,uid=122
mai 10 10:18:49 ouss kernel: Out of memory: Killed process 24534 (java) total-vm:1564676kB, anon-rss:550924kB, file-rss:0kB, shmem-rss:0kB
mai 10 10:18:49 ouss kernel: oom_reaper: reaped process 24534 (java), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
mai 10 10:18:40 ouss systemd[1]: elasticsearch.service: Main process exited, code=killed, status=9/KILL
mai 10 10:18:49 ouss /usr/lib/gdm3/gdm-x-session[1336]: (EE) client bug: timer event4 debounce: offset negative (-1094ms)
mai 10 10:18:49 ouss /usr/lib/gdm3/gdm-x-session[1336]: (EE) client bug: timer event4 debounce short: offset negative (-1249ms)
mai 10 10:18:49 ouss /usr/lib/gdm3/gdm-x-session[1336]: (II) event6 - VirtualBox mouse integration: SYN_DROPPED event - some input events have been lost.
mai 10 10:18:40 ouss systemd[1]: elasticsearch.service: Failed with result 'signal'.
mai 10 10:18:40 ouss systemd[1]: Failed to start Elasticsearch.
-- Subject: Unit elasticsearch.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit elasticsearch.service has failed.
--
-- The result is RESULT.
My java version :
openjdk version "1.8.0_252"
OpenJDK Runtime Environment (build 1.8.0_252-8u252-b09-1~18.04-b09)
OpenJDK 64-Bit Server VM (build 25.252-b09, mixed mode)
The issue was resolved by using the tarball installation by following the official https://www.elastic.co/guide/en/elasticsearch/reference/current/targz.html installation instructions.
Please make sure the user which you are using to run the elasticsearch process has write access to the filesystem where the elasticsearch process is writing. Please see the comments in the question section for more info and error related to this.
Please use https://askubuntu.com/questions/6723/change-folder-permissions-and-ownership for instructions on how to assign the ownership in ubuntu.
I have a problem with automatic running of service. I would like to run a script after user login. Once I have succeeded, however when I tried to automatize it, I'm getting an error and I can't find a mistake.
Service:
Description=Service desc
[Service]
Type=oneshot
Environment=DISPLAY=:0.0
Environment=XAUTHORITY=/home/albert/.Xauthority
Environment=HOME=/home/albert/
User=albert
Group=albert
RemainAfterExit=true
StandardOutput=journal
ExecStart=/home/albert/.startup-script.sh
[Install]
WantedBy=default.target
location:
/home/albert/.config/systemd/user/startup-service.service
permissions: -rw-r--r-- 1 albert albert 306 Jan 2 14:49 startup-service.service
Script
Permissions: -rwxr-x-r-x 1 albert albert 86 Jan 2 13:30 /home/albert/.startup-script.sh
Log
Jan 02 17:03:27 irpi-epsilon systemd[734]: Service desc
-- Subject: Unit UNIT has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit UNIT has begun starting up.
Jan 02 17:03:27 irpi-epsilon systemd[1025]: startup-script.service: Failed at step GROUP spawning /home/albert/.startup-script.sh: Operation not permitted
-- Subject: Process /home/albert/.startup-script.sh could not be executed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The process /home/albert/.startup-script.sh could not be executed and failed.
--
-- The error number returned by this process is 1.
Jan 02 17:03:27 irpi-epsilon systemd[734]: startup-script.service: Main process exited, code=exited, status=216/GROUP
Jan 02 17:03:27 irpi-epsilon systemd[734]: Service desc
-- Subject: Unit UNIT has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit UNIT has failed.
--
-- The result is failed.
Jan 02 17:03:27 irpi-epsilon systemd[734]: startup-script.service: Unit entered failed state.
Jan 02 17:03:27 irpi-epsilon systemd[734]: startup-script.service: Failed with result 'exit-code'.
I have called:
systemctl --user daemon-reload
systemctl --user enable startup-script.service
systemctl --user start startup-script
And I'm trying to do it on Raspberry Pi 3.
Thanks a lot for pointing me at any direction.
If somebody has similar problem then just remove
User and Group from service file. I don't know why, but without them it works pretty well. So the final working service description is:
Description=Service desc
[Service]
Type=oneshot
Environment=DISPLAY=:0.0
Environment=XAUTHORITY=/home/albert/.Xauthority
Environment=HOME=/home/albert/
RemainAfterExit=true
StandardOutput=journal
ExecStart=/home/albert/.startup-script.sh
[Install]
WantedBy=default.target
I am behind a proxy server and following the "Kubernetes Installation with Vagrant & CoreOS" steps listed here: https://coreos.com/kubernetes/docs/latest/kubernetes-on-vagrant.html
After finalizing the install, when I run
$ kubectl get nodes
I get the error.
Unable to connect to the server: Service Unavailable
e1, c1, and w1 are up and I can issue $vagrant ssh each of them.
when I check the w1, I have seen docker service was not running with the error listed below.
----------------------------------------------------------------------------
-- Unit docker.service has failed.
--
-- The result is dependency.
Aug 19 04:09:25 w1 systemd[1]: docker.service: Job docker.service/start failed with result 'dependency'.
Aug 19 04:09:25 w1 systemd[1]: flanneld.service: Unit entered failed state.
Aug 19 04:09:25 w1 systemd[1]: flanneld.service: Failed with result 'exit-code'.
Aug 19 04:09:30 w1 systemd[1]: flanneld.service: Service hold-off time over, scheduling restart.
Aug 19 04:09:30 w1 systemd[1]: Stopped Network fabric for containers.
-- Subject: Unit flanneld.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit flanneld.service has finished shutting down.
Aug 19 04:09:30 w1 systemd[1]: Starting Network fabric for containers...
-- Subject: Unit flanneld.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit flanneld.service has begun starting up.
Aug 19 04:09:30 w1 rkt[6888]: image: using image from file /usr/lib/rkt/stage1-images/stage1-fly.aci
Aug 19 04:09:31 w1 rkt[6888]: image: searching for app image quay.io/coreos/flannel
Aug 19 04:09:31 w1 rkt[6888]: run: discovery failed
Aug 19 04:09:31 w1 systemd[1]: flanneld.service: Main process exited, code=exited, status=1/FAILURE
Aug 19 04:09:31 w1 systemd[1]: Failed to start Network fabric for containers.
-- Subject: Unit flanneld.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit flanneld.service has failed.
--
-- The result is failed.
Aug 19 04:09:31 w1 systemd[1]: flanneld.service: Unit entered failed state.
Aug 19 04:09:31 w1 systemd[1]: flanneld.service: Failed with result 'exit-code'.
----------------------------------------------------------------------------
I am guessing that problem is because of I am behind the proxy. Before running the install steps I issue the commands
$export "HTTP_PROXY=http://http-proxy.xxxxxx.com:8080"
$export "HTTPS_PROXY=http://http-proxy.xxxxxx.com:8080"
$export "http_proxy=http://http-proxy.xxxxxx.com:8080"
$export "https_proxy=http://http-proxy.xxxxxx.com:8080"
Do you know if this is enough for the installation behind proxy or do I need to add proxy settings to somewhere else.
Thank you in advance,
turgos
The variables you're exporting are valid only in your current shell session, they are not available to your flannel systemd unit.
Create the following drop-in inside the systemd unit directory, and then reload the daemon with systemctl daemon-reload, it should fix your issue with flannel:
/etc/systemd/system/flannel.service.d/proxy.conf:
[Service]
Environment="HTTP_PROXY=http://http-proxy.xxx:8080"
Environment="...
A similar example is available in the CoreOS documentation: Customizing Docker