A file /tmp/1784895643 showed up on my system. It was hogging resources and bogging the system down, an dshowing up under this name as a kernel process.
File info shows:
root@NODE250:/home/pi# file 1784895643
1784895643: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, no section header
And I was seeing this in the logs:
root@NODE250:/# journalctl -b|grep 1784895
Jun 21 11:22:32 NODE250 kernel: mempolicy: Request by '1784895643' to set policy to 5 ignored
Jun 21 11:22:32 NODE250 kernel: mempolicy: Request by '1784895643' to set policy to 5 ignored
Jun 21 11:22:32 NODE250 kernel: mempolicy: Request by '1784895643' to set policy to 5 ignored
Jun 21 11:22:32 NODE250 kernel: mempolicy: Request by '1784895643' to set policy to 5 ignored
Jun 22 01:41:09 NODE250 kernel: mempolicy: Request by '1784895643' to set policy to 5 ignored
I seem to have fixed it (???) by removing this file from /tmp. I am wondering if this is some sort of virus I picked up on an update. My system is on a local network with no ports forwarded, but I have been keeping up2date with rpi-update and apt-get update/upgrade.
Any ideas?
File info shows:
root@NODE250:/home/pi# file 1784895643
1784895643: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, no section header
And I was seeing this in the logs:
root@NODE250:/# journalctl -b|grep 1784895
Jun 21 11:22:32 NODE250 kernel: mempolicy: Request by '1784895643' to set policy to 5 ignored
Jun 21 11:22:32 NODE250 kernel: mempolicy: Request by '1784895643' to set policy to 5 ignored
Jun 21 11:22:32 NODE250 kernel: mempolicy: Request by '1784895643' to set policy to 5 ignored
Jun 21 11:22:32 NODE250 kernel: mempolicy: Request by '1784895643' to set policy to 5 ignored
Jun 22 01:41:09 NODE250 kernel: mempolicy: Request by '1784895643' to set policy to 5 ignored
I seem to have fixed it (???) by removing this file from /tmp. I am wondering if this is some sort of virus I picked up on an update. My system is on a local network with no ports forwarded, but I have been keeping up2date with rpi-update and apt-get update/upgrade.
Any ideas?
Statistics: Posted by rboudrie — Mon Jun 22, 2026 5:58 am








