> Got this when stopping a SmartOS zone, vmadm list returns the same error. > > vmadm stop 9652418f-a059-eb30-9024-de07910b0fb0 > Uncaught Error: EIO, i/o error > > FROM > Function.startup.resolveArgv0 (node.js:811:23) > startup (node.js:58:13) > node.js:902:3 > Abort (core dumped) >
This happens when your working directory is a mount that has since been unmounted. If you try to run vmadm (or anything that uses node) in a directory that's been deleted you'll get a similar error but with ENOENT instead of EIO. The reason it will have worked when you created a second connection is that new connection will have had a valid working directory. Thanks, Josh ------------------------------------------- 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
