[systemd-devel] Job for skil.service failed because the control process exited with error code
Octavi Obiols Sales
octavi.obiols.s at gmail.com
Thu Apr 26 00:30:28 UTC 2018
Hello,
I am sending you this e-mail in order to get some help in starting the
software I installed. I installed it correctly, but when I started it, it
gave an error which said I should find support in this mailing list.
I properly installed SKIL (from Skymind) in my machine. However, when I
decided to start the software using the command
sudo systemctl start skil
the following message showed up:
Job for skil.service failed because the control process exited with error
code. See "systemctl status skil.service" and "journalctl -xe" for details.
The command "systemctl status skil.service" showed the following output:
skil.service - Skymind SKIL Service
Loaded: loaded (/etc/systemd/system/skil.service; disabled; vendor
preset: disabled)
Active: *failed* (Result: exit-code) since Wed 2018-04-25 17:20:18 PDT;
2min 30s ago
Process: 18788 ExecStart=/usr/bin/env bash
${SKIL_HOME}/sbin/start-skil-daemon --backend $SKIL_BACKEND *(code=exited,
status=1/FAILURE)*
Process: 18783 ExecStartPre=/bin/sh ${SKIL_HOME}/sbin/pre-start.sh
(code=exited, status=0/SUCCESS)
Apr 25 17:20:18 zelda.eng.uci.edu env[18788]: INFO: using SKIL_LOG_DIR
/var/log/skil
Apr 25 17:20:18 zelda.eng.uci.edu env[18788]: ERROR: error creating
lib/ext, please run start-skil-daemon.py as skil user and verify skil user
has permissions to write to SKIL_... (/opt/skil)
Apr 25 17:20:18 zelda.eng.uci.edu env[18788]: Traceback (most recent call
last):
Apr 25 17:20:18 zelda.eng.uci.edu env[18788]: File
"/opt/skil/sbin/start-skil-daemon.py", line 127, in <module>
Apr 25 17:20:18 zelda.eng.uci.edu env[18788]: os.mkdir(SKIL_HOME +
'/lib/ext')
Apr 25 17:20:18 zelda.eng.uci.edu env[18788]: OSError: [Errno 28] No space
left on device: '/opt/skil/lib/ext'
Apr 25 17:20:18 zelda.eng.uci.edu systemd[1]: *skil.service: control
process exited, code=exited status=1*
Apr 25 17:20:18 zelda.eng.uci.edu systemd[1]: *Failed to start Skymind SKIL
Service.*
Apr 25 17:20:18 zelda.eng.uci.edu systemd[1]: *Unit skil.service entered
failed state.*
Apr 25 17:20:18 zelda.eng.uci.edu systemd[1]: *skil.service failed.*
And the "journalctl -xe" command showed the following:
Unit session-12974.scope has begun starting up.
Apr 25 17:20:01 zelda.eng.uci.edu CROND[18770]: (root) CMD
(/usr/lib64/sa/sa1 1 1)
Apr 25 17:20:01 zelda.eng.uci.edu systemd[1]: Removed slice user-0.slice.
-- Subject: Unit user-0.slice has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-0.slice has finished shutting down.
Apr 25 17:20:01 zelda.eng.uci.edu systemd[1]: Stopping user-0.slice.
-- Subject: Unit user-0.slice has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
I would like to get some insights in this and see if I can figure out the
problem.
Thank you very much,
Octavi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20180425/9ec37f50/attachment-0001.html>
More information about the systemd-devel
mailing list