Page 1 of 1

Running script at startup fails in LM 20, worked in 19.3

Posted: Tue Jan 12, 2021 2:45 pm
by dpbe
In LM 19.3 during boot an SH script was executed by systemd and it working fine. In LM this is no longer working. I set the loglevel of systemd to debug and this are the results. Does someone know what's going wrong?

Code: Select all

Jan 12 19:32:25 I7-Linux systemd[1]: startup.service: Failed to set 'blkio.weight' attribute on '/system.slice/startup.service' to '500': No such file or dire>
Jan 12 19:32:25 I7-Linux systemd[1]: startup.service: Passing 0 fds to service
Jan 12 19:32:25 I7-Linux systemd[1]: startup.service: About to execute: /bin/bash /usr/bin/logoff_add.sh
Jan 12 19:32:25 I7-Linux systemd[1]: startup.service: Forked /bin/bash as 994
Jan 12 19:32:25 I7-Linux systemd[1]: startup.service: Changed dead -> running
Jan 12 19:32:25 I7-Linux systemd[1]: startup.service: Job 145 startup.service/start finished, result=done
Jan 12 19:32:25 I7-Linux systemd[1]: Started Clear Cache.
Jan 12 19:32:25 I7-Linux systemd[994]: startup.service: Executing: /bin/bash /usr/bin/logoff_add.sh
Jan 12 19:32:25 I7-Linux systemd[1]: startup.service: Failed to read oom_kill field of memory.events cgroup attribute: No such file or directory
Jan 12 19:32:25 I7-Linux systemd[1]: startup.service: Child 994 belongs to startup.service.
Jan 12 19:32:25 I7-Linux systemd[1]: startup.service: Main process exited, code=exited, status=0/SUCCESS
Jan 12 19:32:25 I7-Linux systemd[1]: startup.service: Succeeded.
Jan 12 19:32:25 I7-Linux systemd[1]: startup.service: Service will not restart (restart setting)
Jan 12 19:32:25 I7-Linux systemd[1]: startup.service: Changed running -> dead
Jan 12 19:32:25 I7-Linux systemd[1]: startup.service: Control group is empty.
The content of the Startup.service is:

Code: Select all

[Unit]
Description=Clear Cache

[Service]
ExecStart=/bin/bash /usr/bin/logoff_add.sh

[Install]
WantedBy=multi-user.target

Re: Running script at startup fails in LM 20, worked in 19.3

Posted: Sat Jan 30, 2021 11:05 am
by 4VPPsaPBhrzaSfRoI2
did you find a solution? i'm having the same issue to run a script in that the unit.service fails and outputs that oom_kill message.