Couldn't write '4 4 1 7' to 'kernel/printk'

tony blue

Active Member
Dec 26, 2017
64
1
33
50
Hello,

I have installed a new Ubuntu 14.04 LTS LXC containter. After boot I got this messages in /var/log/syslog:

Jan 19 10:56:23 Ubuntu-14 systemd-sysctl[45]: Couldn't write '4 4 1 7' to 'kernel/printk', ignoring: Rea
d-only file system
Jan 19 10:56:23 Ubuntu-14 systemd-sysctl[45]: Couldn't write '1' to 'kernel/kptr_restrict', ignoring: Re
ad-only file system
Jan 19 10:56:23 Ubuntu-14 systemd-sysctl[45]: Couldn't write '1' to 'fs/protected_hardlinks', ignoring:
Read-only file system
Jan 19 10:56:23 Ubuntu-14 systemd-sysctl[45]: Couldn't write '1' to 'fs/protected_symlinks', ignoring: R
ead-only file system
Jan 19 10:56:23 Ubuntu-14 systemd-sysctl[45]: Couldn't write '176' to 'kernel/sysrq', ignoring: Read-onl
y file system
Jan 19 10:56:23 Ubuntu-14 systemd-sysctl[45]: Couldn't write '1' to 'kernel/yama/ptrace_scope', ignoring
: Read-only file system
Jan 19 10:56:23 Ubuntu-14 systemd-sysctl[45]: Couldn't write '65536' to 'vm/mmap_min_addr', ignoring: Re
ad-only file system
Jan 19 10:56:23 Ubuntu-14 systemd-sysctl[45]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ign
oring: No such file or directory
Jan 19 10:56:23 Ubuntu-14 systemd[1]: systemd-journal-flush.service: Failed to reset devices.list: Opera
tion not permitted

What does it mean?

How can I fix it?

Thank you!

Tony
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!