journalctl does not contain messages it should; dmesg is not permitted

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: journalctl does not contain messages it should; dmesg is not permitted  (Read 87 times)

0 Members and 1 Guest are viewing this topic.

Gamliel Fishkin

  • Newbie
  • *
  • Offline Offline
  • Gender: Male
  • Posts: 2
    • Gamliel Fishkin's personal website

I have a free VPS with Debian10.0-64bit-minimal here. It works, thank you.

But messages which are supposed to appear in journalctl, do not appear in it. And when I try to use dmesg (N.B.: as root), I see it is not permitted to me.

Code: [Select]
$ sudo nft list chain inet filter input | grep Invalid
counter packets 81 bytes 6687 log prefix "Invalid-Input: " level debug
$ journalctl | grep -c Invalid
0
$ journalctl | wc -l
2862
$ sudo dmesg | grep -c Invalid
dmesg: read kernel buffer failed: Operation not permitted
0
$ sudo dmesg | wc -l
dmesg: read kernel buffer failed: Operation not permitted
0

On a KVM VPS at another company and at my home computer (both with Debian 10 "Buster" 64bit) all of it works fine.

Is the described problem a limitation of OpenVZ?
« Last Edit: May 17, 2020, 05:03:23 PM by Gamliel Fishkin »
Logged


Forum-Support2

  • Administrator
  • Jr. Member
  • *****
  • Offline Offline
  • Posts: 69

Hello,

we do not use OpenVZ for VS2/VS2free. It is a modified LXC/LXD System.

dmesg and other stuff may restricted inside a container. However, systctl should work.

KVM is full virtualized. This means you have full control at Kernel etc. since you do not use a shared kernel. We are currently develop KVM. May this is an option for you to test this later.
Logged
Pages: [1]   Go Up
 

Page created in 0.102 seconds with 22 queries.