On Fri, Jan 2, 2015 at 7:59 PM, Chris Ridd via smartos-discuss <[email protected]> wrote: > > Hi, > > Every hour I'm getting email a warning from cron, e.g. > > logadm: Warning: /zones/5e45a3c6-50db-43ba-8a60-22856cfe0ac7/root/tmp/vm.log: > No such file or directory > logadm: Warning: /zones/584f4288-b76b-419f-92ca-9ab09b069737/root/tmp/vm.log: > No such file or directory > logadm: Warning: /zones/b8e40c76-7c66-4efe-8eac-77845b0818df/root/tmp/vm.log: > No such file or directory > logadm: Warning: /zones/380331e2-c950-491d-9496-7c97e97000f8/root/tmp/vm.log: > No such file or directory > logadm: Warning: /zones/5ea84500-1a2c-4bb6-aab9-be597f56c98d/root/tmp/vm.log: > No such file or directory > logadm: Warning: /zones/e4bee648-543f-42b9-8b1d-4ec844227ff3/root/tmp/vm.log: > No such file or directory > logadm: Warning: /zones/e36feed9-ce0b-4fa7-85cb-8017c2e083e9/root/tmp/vm.log: > No such file or directory > logadm: Warning: /zones/db5c9bc9-db3b-4418-9997-838ea928b1bf/root/tmp/vm.log: > No such file or directory > > These VMs do not exist on my server any more - they were probably ones that I > created and destroyed after briefly messing around with them. They *might* > all have been KVM-based VMs, but I can't be certain. > > Is this a known problem, and is there a fix? I'm not 100% sure how logadm is > choosing these log files. > > `uname -v` reports joyent_20141225T170427Z > > Thanks, > > Chris
You may use following: logadm -r /zones/<uuid>/root/tmp/vm.log to get rid of them (: Best, Filip ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
