Unnecessary item create by default LLD

[Eddit]

Hello,
I got a new installed Zabbix 4.0.3, after I add host in it(through auto registration), I found some unnecessary item discoverd by default filesystem LLD( "Mounted filesystem discovery" in "Template OS Linux"), like photo1 below

but actually my partition is:

Filesystem Size Used Avail Use% Mounted on
/dev/vda1 40G 31G 7.0G 82% /
devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 12K 3.9G 1% /dev/shm
tmpfs 3.9G 364K 3.9G 1% /run
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs 783M 0 783M 0% /run/user/0
tmpfs 783M 0 783M 0% /run/user/1000

I didn't edit any setting of the default "Template OS Linux", it should only get "/", doesn't it?
I'd like to know how to solve this and why it happend.

Thanks.

[Eddit]

Can anyone help with this please.
Thanks

[Eddit]

Anyone ?????

[Atsushi]

Execute the command as follows to check the contents of the file, and check whether there is a line of /tmp and /var/tmp. If it exists, please show me the contents of that line.

# cat /proc/mounts

[Eddit]

Thanks for reply.

Yes, I've checked the mounts which is :

rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
devtmpfs /dev devtmpfs rw,nosuid,size=8124092k,nr_inodes=2031023,mode=755 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode= 000 0 0
tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agen t=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_prio,net_cls 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct,cpu 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
configfs /sys/kernel/config configfs rw,relatime 0 0
/dev/vda1 / ext4 rw,relatime,data=ordered 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=34,pgrp=1,timeout=0,minproto=5,maxp roto=5,direct,pipe_ino=1112161 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=1626720k,mode=700,ui d=1000,gid=1000 0 0

and no such thing like the directory before

[Atsushi]

Please use the zabbix_get command on the server running the Zabbix server and try to get the value of vfs.fs.discovery of the target host.

ex.
$ zabbix_get -s ip-address -k vfs.fs.discovery

[Eddit]

It shows up:

{
"data": [{
"{#FSNAME}": "/",
"{#FSTYPE}": "rootfs"
}, {
"{#FSNAME}": "/",
"{#FSTYPE}": "ext4"
}, {
"{#FSNAME}": "/dev",
"{#FSTYPE}": "devtmpfs"
}, {
"{#FSNAME}": "/dev/shm",
"{#FSTYPE}": "tmpfs"
}, {
"{#FSNAME}": "/dev/pts",
"{#FSTYPE}": "devpts"
}, {
"{#FSNAME}": "/dev/mqueue",
"{#FSTYPE}": "mqueue"
}, {
"{#FSNAME}": "/dev/hugepages",
"{#FSTYPE}": "hugetlbfs"
}, {
"{#FSNAME}": "/proc",
"{#FSTYPE}": "proc"
}, {
"{#FSNAME}": "/proc/sys/fs/binfmt_misc",
"{#FSTYPE}": "autofs"
}, {
"{#FSNAME}": "/sys",
"{#FSTYPE}": "sysfs"
}, {
"{#FSNAME}": "/sys/kernel/security",
"{#FSTYPE}": "securityfs"
}, {
"{#FSNAME}": "/sys/fs/cgroup",
"{#FSTYPE}": "tmpfs"
}, {
"{#FSNAME}": "/sys/fs/cgroup/systemd",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/cpu,cpuacct",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/pids",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/perf_event",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/blkio",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/freezer",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/devices",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/net_cls,net_prio",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/cpuset",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/memory",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/hugetlb",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/pstore",
"{#FSTYPE}": "pstore"
}, {
"{#FSNAME}": "/sys/kernel/config",
"{#FSTYPE}": "configfs"
}, {
"{#FSNAME}": "/sys/kernel/debug",
"{#FSTYPE}": "debugfs"
}, {
"{#FSNAME}": "/run",
"{#FSTYPE}": "tmpfs"
}, {
"{#FSNAME}": "/run/user/0",
"{#FSTYPE}": "tmpfs"
}, {
"{#FSNAME}": "/run/user/1001",
"{#FSTYPE}": "tmpfs"
}, {
"{#FSNAME}": "/tmp",
"{#FSTYPE}": "ext4"
}, {
"{#FSNAME}": "/var/tmp",
"{#FSTYPE}": "ext4"
}]
}

but how does zabbix get these?

[Atsushi]

For Linux, the value of vfs.fs.discovery is obtained from /proc/mounts.

src/libs/zbxsysinfo/linux/diskspace.c
int VFS_FS_DISCOVERY(AGENT_REQUEST *request, AGENT_RESULT *result)

[Eddit]

Thank you, I understand. However there aren't /tmp nor /var/tmp from "/proc/mounts", how does the server still get these value?
And, sorry, I don't know much about C.

[Eddit]

Can anyone help with this please.
Thanks

[Atsushi]

Please double check whether you are using another server or container.

only in /proc/mounts

/run/user/1000

only in vfs.fs.discovery

/run/user/0
/run/user/1001
/tmp
/var/tmp

[Eddit]

Thanks for reply.
I don't have anyother Zabbix server, and if you mean docker etc. as container, no, I'm not using container.

I've noticed that /run/user/1000 exist, that's just my running process directory, managed by system, does that relevant to this issue?

[Eddit]

Is this a bug or something?

[Atsushi]

On the Linux server I am monitoring, there is no server whose content of /proc/mounts does not match the value of vfs.fs.discovery. Even when looking at the source, since the contents of /proc/mounts are processed line by line, the order of the mount points does not change.

I doubt that you compare it with information on another server because the result you presented suggests that the number and order of the mounted file systems do not match.

[zux]

Are you sure, that the discovery rule is run on the correct server?

[Eddit]

This one below is from the same server:

rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
devtmpfs /dev devtmpfs rw,nosuid,size=3995840k,nr_inodes=998960,mode=755 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode= 000 0 0
tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agen t=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct,cpu 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_prio,net_cls 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
configfs /sys/kernel/config configfs rw,relatime 0 0
/dev/vda1 / ext4 rw,relatime,data=ordered 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxp roto=5,direct 0 0
tmpfs /run/user/1001 tmpfs rw,nosuid,nodev,relatime,size=801044k,mode=700,uid =1001,gid=1001 0 0

{
"data": [{
"{#FSNAME}": "/",
"{#FSTYPE}": "rootfs"
}, {
"{#FSNAME}": "/",
"{#FSTYPE}": "ext4"
}, {
"{#FSNAME}": "/dev",
"{#FSTYPE}": "devtmpfs"
}, {
"{#FSNAME}": "/dev/shm",
"{#FSTYPE}": "tmpfs"
}, {
"{#FSNAME}": "/dev/pts",
"{#FSTYPE}": "devpts"
}, {
"{#FSNAME}": "/dev/mqueue",
"{#FSTYPE}": "mqueue"
}, {
"{#FSNAME}": "/dev/hugepages",
"{#FSTYPE}": "hugetlbfs"
}, {
"{#FSNAME}": "/proc",
"{#FSTYPE}": "proc"
}, {
"{#FSNAME}": "/proc/sys/fs/binfmt_misc",
"{#FSTYPE}": "autofs"
}, {
"{#FSNAME}": "/sys",
"{#FSTYPE}": "sysfs"
}, {
"{#FSNAME}": "/sys/kernel/security",
"{#FSTYPE}": "securityfs"
}, {
"{#FSNAME}": "/sys/fs/cgroup",
"{#FSTYPE}": "tmpfs"
}, {
"{#FSNAME}": "/sys/fs/cgroup/systemd",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/cpu,cpuacct",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/devices",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/hugetlb",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/blkio",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/perf_event",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/pids",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/net_cls,net_prio",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/memory",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/freezer",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/cgroup/cpuset",
"{#FSTYPE}": "cgroup"
}, {
"{#FSNAME}": "/sys/fs/pstore",
"{#FSTYPE}": "pstore"
}, {
"{#FSNAME}": "/sys/kernel/config",
"{#FSTYPE}": "configfs"
}, {
"{#FSNAME}": "/sys/kernel/debug",
"{#FSTYPE}": "debugfs"
}, {
"{#FSNAME}": "/run",
"{#FSTYPE}": "tmpfs"
}, {
"{#FSNAME}": "/run/user/1001",
"{#FSTYPE}": "tmpfs"
}, {
"{#FSNAME}": "/tmp",
"{#FSTYPE}": "ext4"
}, {
"{#FSNAME}": "/var/tmp",
"{#FSTYPE}": "ext4"
}]
}

I do have several server that monitored by zabbix, but /var/tmp and /tmp appear as usual.


And, @zux
You said discovery rule is not run on the correct server, the discovery rule on all these server is the same, I didn't edit them, or you mean something else?

[zux]

What I meant was, that maybe the IP address or DNS name, configured on the host in Zabbix is incorrect? Or maybe this discovery is configured as active agent? Not sure where to look for problems, but i'm pretty sure this is a configuration issue, so just carefully check everything again.

[Eddit]

The agent was added by auto registration, also I've checked the ip and they're correspond.
Is this an "active agent" for what you meant?