It is possible that under certain scenarios the coredumps detection mechanism will consider certain folders and files as coredumps even though they are not, because it will match the *core* regex.

From coredumps show command:

root@juniper> show system core-dumps no-forwarding

/var/tmp/*core*: No such file or directory
Host Crash Info:
--------------------------------------------------------------------------
lrwxrwxrwx  1 root  root          18 Feb 21 21:13 /var/crash/corefiles
lrwxrwxrwx  1 root  root          18 Feb 21 21:13 /var/crash/corefiles/corefiles

To resolve the issue and if necessary we can delete the files under the /var/tmp/ or host, if in doubt, consult with JTAC about the file to be deleted and whether or not it is a legitimate coredump.
 

• To remove the files from /var/tmp/:

Go to shell mode using >start shell

root@juniper% cd /var/tmp

root@juniper% ls >> to make sure you are under the right directory

root@juniper% rm <filename>

root@juniper% ls >> to make sure file is not longer in there

• To remove the file from Host Crash:

root@juniper> request app-engine host-shell
root@qfx5200-32C-node:~#
root@qfx5200-32C-node:~#
root@qfx5200-32C-node:~# cd /var/crash
root@qfx5200-32C-node:/var/crash# ls
corefiles
root@qfx5200-32C-node:/var/crash# rm corefiles
root@qfx5200-32C-node:/var/crash# exit
logout rlogin: connection closed
{master:0}
root@juniper> show system core-dumps

/var/tmp/*core*: No such file or directory
Host Crash Info:
------------------------------------------------------