Drucken

Bitte loggen sie sich ein oder registrieren sie sich.
1 Stunde 1 Tag 1 Woche 1 Monat Immer
Einloggen mit Benutzername, Passwort und Sitzungslänge

[feiyang]

####CUSTOMERDATA####
Title: Herr
First name: Yang
Last name: Fei
Customer ID: 13222595
Email: feiyang991128@gmail.com
####END CUSTOMERDATA####

####CONTRACTDATA####
Order ID: 384646
Plan name: vServer VS2-free v2.1
Order datetime: 2021-10-11 00:33:04
Deployment datetime: 2021-10-13 09:43:20
Termination datetime: none
Final deletion date: none
####END CONTRACTDATA####

####DETAILED DESCRIPTION####
Hello,

I'm running Debian 12 (Bookworm) inside an LXC container.

I'm unable to install and run BT Panel correctly because the container cannot read /proc/cpuinfo or /proc/meminfo.

The installation script reports:

cat: /etc/redhat-release: No such file or directory
cat: /proc/cpuinfo: Permission denied

The first message is expected on Debian, but the second one is not.

Additional information:

- OS: Debian GNU/Linux 12 (Bookworm)
- Virtualization: LXC
- Kernel: 5.4.123-1.el7.elrepo.x86_64

The following commands all fail:

cat /proc/cpuinfo
cat /proc/meminfo

Both return:

Permission denied

As a result, BT Panel reports errors such as:

ps: Unable to get total memory

I have already tried:

mount -o remount,hidepid=0 /proc

and remounting /proc, but the issue remains.

Could you please check the LXC container configuration or the host node? It appears that access to /proc/cpuinfo and /proc/meminfo is restricted inside the container, which prevents BT Panel and other system utilities from working correctly.

Thank you.
####END DETAILED DESCRIPTION####

####ERRORMESSAGE####
# systemd-detect-virt
lxc

# cat /proc/cpuinfo
cat: /proc/cpuinfo: Permission denied

# cat /proc/meminfo
cat: /proc/meminfo: Permission denied

# ls -l /proc/cpuinfo
-r--r----- 1 nobody nogroup 0 Jun 29 03:45 /proc/cpuinfo

# mount | grep " on /proc "
proc on /proc type proc (rw,relatime)
####END ERRORMESSAGE####

[jj458]

Hi feyang,

i had as similar problem with my Rocky Linux system.
For me it seems, the problem has been fixed: https://forum.euserv.de/index.php/topic,16284.msg47403.html#msg47403

But: no info from support.