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

[Lennart Poettering]

On Fr, 17.11.17 17:11, Shekhar arya (shadowcat.arya at gmail.com) 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?
> 
> # Journalctl –no-pager
> 
> Jan 01 00:00:11 localhost systemd-journal[93]: Journal started
> 
> Jan 01 00:00:11 localhost systemd-sysctl[94]: Couldn't write 'fq_codel' to
> 'net/core/default_qdisc', ignoring: No such file or directory
> 
> Jan 01 00:00:11 localhost systemd-sysctl[94]: Couldn't write '16' to
> 'kernel/sysrq', ignoring: No such file or directory
> 
> Jan 01 00:00:11 localhost systemd-sysusers[113]: Failed to take lock:
> Read-only file system
> 
> Jan 01 00:00:12 localhost systemd-tmpfiles[118]: Failed to create directory
> or subvolume "/var/volatile/log": No such file or directory
> 
> Jan 01 00:00:12 localhost systemd-tmpfiles[118]: Failed to create directory
> or subvolume "/var/volatile/tmp": No such file or directory
> 
> Jan 01 00:00:12 localhost systemd-tmpfiles[118]: /tmp/volatile does not
> exist and cannot be created as the file system is read-only.
> 
> Jan 01 00:00:12 localhost systemd-tmpfiles[118]: Failed to create directory
> or subvolume "/tmp/volatile/tmp": No such file or directory
> 
> Jan 01 00:00:12 localhost systemd-tmpfiles[118]: Failed to create directory
> or subvolume "/tmp/volatile/cache": No such file or directory
> 
> Jan 01 00:00:12 localhost systemd-tmpfiles[118]:
> symlink(../proc/self/mounts, /etc/mtab) failed: Read-only file system
> 
> Jan 01 00:00:12 localhost systemd-tmpfiles[118]: chmod(/home) failed:
> Read-only file system
> 
> Jan 01 00:00:12 localhost systemd-tmpfiles[118]: /srv does not exist and
> cannot be created as the file system is read-only.
> 
> Jan 01 00:00:12 localhost systemd-tmpfiles[118]: Failed to create file
> /var/run/snmpd-env: No such file or directory

This suggests /var/run is not a symlink to /run as it should be. A
setup like that is seriously broken, and not supported. Please symlink
/var/run to /run.

Moreover, the other logs suggest that /tmp and /var is not writable on
your system. That's not really OK either. Both directories need to be
writable during runtime.

Lennart

-- 
Lennart Poettering, Red Hat