After latest update: cat: /proc/uptime: Transport endpoint is not connected

May 18, 2019
231
15
38
Varies
Code:
uptime=$(cat /proc/uptime | sed 's/\..*$//' | tr -d '[:blank:]')

is something i use on the host a lot for several cronjob scripts. after the latest update, it gives

Code:
cat: /proc/uptime: Transport endpoint is not connected

i can change the scripts to remove this, but there are a lot of them. currently I am unable to monitor a lot of things in the guests.
 
hi,

works here for me. what's your pveversion -v?
 
thanks for the quick reply, oguz


Code:
proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve)
pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
pve-kernel-helper: 6.1-7
pve-kernel-5.3: 6.1-5
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.18-1-pve: 5.3.18-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 2.0.1-1+pve7
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-15
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 4.0.0-pve1
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-21
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-6
pve-ha-manager: 3.0-8
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-7
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1
 
it works from the cli, but not in the script.
hmm okay.

how do you run the script? maybe a snippet will be helpful
 
I misspoke. I have the uptime check on both host and guest. it does not work on the guest

/usr/sbin/pct exec 110 -- bash -c "cat /proc/uptime | sed 's/\..*$//' | tr -d '[:blank:]'"

or simply

/usr/sbin/pct exec 110 -- bash -c "cat /proc/uptime"

it doesn't work from the cli either. sorry not enough coffee yet.
 
okay still works in my container with the command you sent.

what's in the CT? can you post the config? what's running in it?
 
it doesn't work on any of the 15 cts, exactly after the update last night.

Code:
# pct enter 107
root@one1:~/scripts# cat /proc/uptime
cat: /proc/uptime: Transport endpoint is not connected
root@one1:~/scripts# exit
exit
root@node2:~/scripts# cat /etc/pve/lxc/107.conf
arch: amd64
cores: 4
hostname: blah
memory: 2048
net0: name=eth0,bridge=vmbr1,gw=10.10.10.1,hwaddr=a:b:c:d:e,ip=10.10.10.107/24,type=veth
onboot: 1
ostype: ubuntu
protection: 1
rootfs: lvmt_containers1-nvme1:vm-107-disk-0,mountoptions=noatime,size=25G
swap: 1024
unprivileged: 1

CT configs have not changed.
 
did you reboot after the update?

i can't reproduce the issue unfortunately so i'm guessing something with your setup must be causing it.
 
the config on 20 containers did not change, only the update. it is mounted on 107:

Code:
mount | grep /proc
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
proc on /proc/sys/net type proc (rw,nosuid,nodev,noexec,relatime)
proc on /proc/sys type proc (ro,nosuid,nodev,noexec,relatime)
proc on /proc/sysrq-trigger type proc (ro,nosuid,nodev,noexec,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
lxcfs on /proc/cpuinfo type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/diskstats type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/loadavg type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/meminfo type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/stat type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/swaps type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
lxcfs on /proc/uptime type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
 
but cat /proc/version works

9xgRk5j.png


permissions for the mount point??

# chown nobody:nogroup /proc/uptime chown: cannot access '/proc/uptime': Transport endpoint is not connected
 

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 yours easily in our online shop.

Buy now!