When using the top command, an error message appears after interruption: bad data in /proc/uptime
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
Host System:
Ubuntu 24.04.4 LTS
containerd://2.2.3-k3s1
v1.35.4+k3s1
Container Image:
nestybox-ubuntu-bionic-systemd-docker
top - 10:15:37 up 0 min, 0 users, load average: 1.43, 1.65, 1.90
Tasks: 92 total, 1 running, 91 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.7 us, 0.3 sy, 0.0 ni, 99.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 65822980 total, 4776340 free, 16178136 used, 44868504 buff/cache
top - 10:15:52 up 0 min, 0 users, load average: 1.12, 1.56, 1.87
Tasks: 92 total, 1 running, 91 sleeping, 0 stopped, 0 zombie
%Cpu(s): 3.8 us, 0.5 sy, 0.0 ni, 95.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 65822980 total, 4898452 free, 16055832 used, 44868696 buff/cache
KiB Swap: 8388604 total, 8378108 free, 10496 used. 48387136 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
586 root 20 0 4096124 60064 35712 S 600.0 0.1 1:10.89 containerd
2247 root 20 0 36772 3260 2636 R 100.0 0.0 0:00.02 top
1 root 20 0 77460 8672 6720 S 0.0 0.0 0:00.25 systemd
225 root 20 0 62628 5484 4976 S 0.0 0.0 0:00.02 systemd-journal
438 systemd+ 20 0 70500 5964 5428 S 0.0 0.0 0:00.02 systemd-resolve
581 message+ 20 0 47640 4248 3728 S 0.0 0.0 0:00.01 dbus-daemon
582 root 20 0 61888 5496 4956 S 0.0 0.0 0:00.02 systemd-logind
599 root 20 0 72308 6396 5648 S 0.0 0.0 0:00.00 sshd
660 root 20 0 6000268 88220 53000 S 0.0 0.1 0:23.96 dockerd
1090 root 20 0 4660 1712 1576 S 0.0 0.0 0:00.01 sh
1122 root 20 0 18672 3680 3056 S 0.0 0.0 0:00.00 bash
1127 root 20 0 4685752 53004 32312 S 0.0 0.1 0:03.01 docker
1707 root 20 0 1226672 5224 2992 S 0.0 0.0 0:00.00 docker-proxy
1714 root 20 0 1152940 4932 2876 S 0.0 0.0 0:00.00 docker-proxy
1735 root 20 0 712144 11128 8324 S 0.0 0.0 0:00.68 containerd-shim
1768 root 20 0 11468 8040 6772 S 0.0 0.0 0:00.09 nginx
1906 systemd+ 20 0 11948 3788 2080 S 0.0 0.0 0:00.00 nginx
1907 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1908 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1909 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1910 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1911 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1912 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1913 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1914 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1915 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1916 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1917 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1918 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1919 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1920 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1921 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1922 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1923 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1924 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1925 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1926 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1927 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1928 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1929 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1930 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1931 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
1932 systemd+ 20 0 11948 3376 1668 S 0.0 0.0 0:00.00 nginx
bad data in /proc/uptime
bad data in /proc/uptime
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the interruption of top in the reported Ubuntu, containerd/K3s, and Docker image environment, focusing on the /proc/uptime entry point. Trace how the runtime exposes or updates /proc/uptime and identify why top reads invalid data; done means interruption no longer produces the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes, ubuntu
- Domain
- devops, infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 40/100