Hello!
The minus sign prefix in ExecStartPre should avoid failing start when error
is encountered.
I don't understand why it does in your specific case. Perhaps you should
ask Red Hat. Or wait for 2.6 release where this command is amended.
Regards,
--
Ilya Kasnacheev
2018-07-11 19:07
Hi,
/etc/systemd/system/apache-ignite@.service:
[Unit]
Description=Apache Ignite In-Memory Computing Platform Service
After=syslog.target network.target
[Service]
Type=forking
User=ignite
WorkingDirectory=/usr/share/apache-ignite/work
PermissionsStartOnly=true
ExecStartPre=-/usr/bin/mkdir
Hello!
Can you please share your /etc/systemd/system/apache-ignite@.service file?
And also the result of dpkg -S /etc/systemd/system/apache-ignite@.service
command execution?
Regards,
--
Ilya Kasnacheev
2018-07-11 18:29 GMT+03:00 ApacheUser :
> Hi ilya,
>
> I am using Ignite 2.5, The
That’s normal output of running service.
> On 11 Jul 2018, at 18:29, ApacheUser wrote:
>
> Hi ilya,
>
> I am using Ignite 2.5, The message pasted from "systemctl status
> apache-ign...@default-config.xml "command. I did nt run any command.
>
> full message:
>
> ]# systemctl status
Hi ilya,
I am using Ignite 2.5, The message pasted from "systemctl status
apache-ign...@default-config.xml "command. I did nt run any command.
full message:
]# systemctl status apache-ign...@default-config.xml
● apache-ign...@default-config.xml.service - Apache Ignite In-Memory
Computing
Hello!
What version of package are you using? Since 2.4 there should be a minus
sign before mkdir, which will make it non-essential. Also, I don't
understand why chown is ran before mkdir. Petr, can you chime in by chance?
Regards,
--
Sent from:
the service is running but cant access, full message below
[]# systemctl status apache-ign...@default-config.xml
● apache-ign...@default-config.xml.service - Apache Ignite In-Memory
Computing Platform Service
Loaded: loaded (/etc/systemd/system/apache-ignite@.service; enabled;
vendor preset:
