You are not logged in.
Hello,
I have a little server (Core i7) at home for one year with ArchLinux running the gr-security kernel. It updates itself every night and reboots afterwards. I know it could be unsure to be too bleeding-edge, but Arch seems stable enough to work fine.
However I recently had a problem, twice, during the reboot process. Here is the journalctl output (sda1 is /, no swap):
[...]
Jan 12 02:00:52 my.server kernel: EXT4-fs (sda1): re-mounted. Opts: data=ordered
Jan 12 02:00:52 my.server kernel: grsec: denied bind() by /usr/lib/systemd/systemd[systemd:1] uid/euid:0/0 gid/egid:0/0, parent /[swapper/0:0] uid/euid:0/0 gid/egid:0/0
Jan 12 02:00:52 my.server systemd[1]: systemd-udevd-kernel.socket failed to listen on sockets: Permission denied
Jan 12 02:00:52 my.server systemd[1]: Failed to listen on udev Kernel Socket.
Jan 12 02:00:52 my.server systemd[1]: Unit systemd-udevd-kernel.socket entered failed state.
[...]The server is then unusable, but a simple manual reboot makes it work fine again.
So I wonder if:
this is a known bug,
I should not use the gr-security kernel on my server,
I should not update the server at all,
you have some advices about managing my server.
Thank you.
Offline