[systemd-devel] moved from systemd 195 to 225, unable to start custom services.

[Zbigniew Jędrzejewski-Szmek]

On Fri, Nov 17, 2017 at 05:11:26PM +0530, Shekhar arya wrote:
> Hi
> 
> I have upgraded my systemd from older version v195 (used in poky 1.6) to
> v225 to resolve some of the memory leak issues. I have resolved all the
> dependencies while compilation and now system boots fine. However, after
> the boot is complete, systemd is not able to start services present in
> /lib/systemd/system folder. These services where perfectly working fine
> with previous version of systemd. Journalctl logs report /var/ and /tmp/
> directories as read-only but in mount I can see them as read-write fs.
> Below is the log which I referred. Am I missing something or does newer
> version of systemd required certain more configurations to run the custom
> services?

Hi,
ancient versions of systemd are not supported upstream, in general.
It sounds like you are using a split-/usr scenario. You might need to
tweak the configuration options to adjust rootprefix.

Zbyszek