{"action":"created","issue":{"url":"https://api.github.com/repos/wckr/wocker/issues/19","labels_url":"https://api.github.com/repos/wckr/wocker/issues/19/labels{/name}","comments_url":"https://api.github.com/repos/wckr/wocker/issues/19/comments","events_url":"https://api.github.com/repos/wckr/wocker/issues/19/events","html_url":"https://github.com/wckr/wocker/issues/19","id":95649222,"number":19,"title":"Error after vagrant up, and old data export (vagrant upでのエラーと、旧データの抜き出し)","user":{"login":"junonet","id":4397631,"avatar_url":"https://avatars.githubusercontent.com/u/4397631?v=3","gravatar_id":"","url":"https://api.github.com/users/junonet","html_url":"https://github.com/junonet","followers_url":"https://api.github.com/users/junonet/followers","following_url":"https://api.github.com/users/junonet/following{/other_user}","gists_url":"https://api.github.com/users/junonet/gists{/gist_id}","starred_url":"https://api.github.com/users/junonet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/junonet/subscriptions","organizations_url":"https://api.github.com/users/junonet/orgs","repos_url":"https://api.github.com/users/junonet/repos","events_url":"https://api.github.com/users/junonet/events{/privacy}","received_events_url":"https://api.github.com/users/junonet/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-07-17T12:41:41Z","updated_at":"2015-07-22T08:02:59Z","closed_at":null,"body":"There's no problem before; however, I got this error when `vagrant up` last Sunday:\r\n\r\n```\r\n==> default: Setting hostname...\r\nThe following SSH command responded with a non-zero exit status.\r\nVagrant assumes that this means the command failed!\r\n\r\nsystemctl start system-cloudinit@-var-tmp-hostname.yml.service\r\n\r\nStdout from the command:\r\n\r\nStderr from the command:\r\n\r\nJob for system-cloudinit@-var-tmp-hostname.yml.service failed because a configured resource limit was exceeded. See \"systemctl status system-cloudinit@-var-tmp-hostname.yml.service\" and \"journalctl -xe\" for details.\r\n```\r\n\r\nThe wocker version was v0.5.0, and I reinstalled v0.6.0.\r\n\r\nSearched on google:\r\nhttps://github.com/coreos/bugs/issues/382\r\nI get to the source of this issue but don't know what to do.\r\n\r\nSome of my friends also got this error.\r\n\r\nIt worked well just after reinstalling vagrant and wocker but would have same error.\r\n\r\nhttp://stackoverflow.com/questions/30822566/job-for-system-cloudinit-var-tmp-hostname-yml-service-failed-because-a-configu\r\nThis is another source.\r\n\r\n$update_channel='stable'\r\n$ vagrant destroy\r\n$ vagrant up\r\n\r\nThis worked well.\r\nHowever, `vagrant up` shown the same error next day.\r\n\r\nPlease tell me what should I do?\r\n\r\nーーーーーーーーーーーーーーーーーーーーーーーーーーーーー\r\n\r\nIn addítion, when I reinstalled wocker, I moved the old one to wocker_old.\r\nMy old data is in wocker_old/data e.g. hoge.\r\nI haven't exported the database to a SQL file like wordpress.sql.\r\n\r\n$ vagrant up　# when this worked\r\n$ cd wocker_old\r\n$ vagrant up\r\n$ vagrant ssh\r\n$ wocker start hoge\r\n\r\nGot this error:\r\n```\r\nError response from daemon: No such container: hoge\r\nFATA[0000] Error: failed to start one or more containers\r\n```\r\n\r\nwocker_old/data is not synced but wocker/data is.\r\n\r\nIs there any way to export the old database.\r\n\r\n----\r\n\r\n日本語で失礼します。\r\n\r\n前日には問題なかったものが\r\n次の日\r\nvagrant upすると\r\n\r\n==> default: Setting hostname...\r\nThe following SSH command responded with a non-zero exit status.\r\nVagrant assumes that this means the command failed!\r\n\r\nsystemctl start system-cloudinit@-var-tmp-hostname.yml.service\r\n\r\nStdout from the command:\r\n\r\nStderr from the command:\r\n\r\nJob for system-cloudinit@-var-tmp-hostname.yml.service failed because a configured resource limit was exceeded. See \"systemctl status system-cloudinit@-var-tmp-hostname.yml.service\" and \"journalctl -xe\" for details.\r\n\r\nというエラーが出るようになりました。\r\n先週の日曜日です。\r\n\r\nwockerのバージョンは、v0.5.0で、入れなおしの際は、v0.6.0にしました。\r\n\r\ngoogleで調べていくと\r\nhttps://github.com/coreos/bugs/issues/382\r\nの記事にたどり着くのですが、どうしていいのかわかりません\r\n\r\nこの症状は、知人も数名、同様におきています。\r\n\r\nvagrantとwocker を入れなおしても、初めはうまくいきますが、また同じようになりました。\r\n\r\nhttp://stackoverflow.com/questions/30822566/job-for-system-cloudinit-var-tmp-hostname-yml-service-failed-because-a-configu\r\n記事もあり、\r\n\r\n$update_channel='stable'\r\n$ vagrant destroy\r\n$ vagrant up\r\n\r\nすると、うまく動くようになったのですが、\r\nこれも、次の日にvagrant upすると、またエラーがでました。\r\n\r\nどのように対処していいのか教えていただけたらと思います。\r\n\r\nーーーーーーーーーーーーーーーーーーーーーーーーーーーーー\r\n\r\nまた、wockerを入れなおす際、元のデータをwocker_oldとしておいています。\r\nwocker_old > data > の中に作業中のものがあるのですが、（仮にhoge）\r\nデータをwordpress.sqlのようにexportしていませんでした。\r\n\r\n$ vagrant up　がうまくいく時に\r\n$ cd wocker_old\r\n$ vagrant up\r\n$ vagrant ssh\r\n$ wocker start hoge\r\n\r\nとしても、\r\nError response from daemon: No such container: hoge\r\nFATA[0000] Error: failed to start one or more containers \r\n\r\nとなり、\r\nwocker_old > data 内を見てくれず、\r\n新しく作ったwocker > data > の中を見に行ってしまいます。\r\n\r\nexportしてないが、元のデータファイルはある場合、\r\nデータを取り出すことはできないのでしょうか？\r\n\r\n\r\n非常にわかり難い説明で\r\n2点の質問になりますが、よろしくお願いします。\r\n\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/wckr/wocker/issues/comments/123608473","html_url":"https://github.com/wckr/wocker/issues/19#issuecomment-123608473","issue_url":"https://api.github.com/repos/wckr/wocker/issues/19","id":123608473,"user":{"login":"ixkaito","id":5457539,"avatar_url":"https://avatars.githubusercontent.com/u/5457539?v=3","gravatar_id":"","url":"https://api.github.com/users/ixkaito","html_url":"https://github.com/ixkaito","followers_url":"https://api.github.com/users/ixkaito/followers","following_url":"https://api.github.com/users/ixkaito/following{/other_user}","gists_url":"https://api.github.com/users/ixkaito/gists{/gist_id}","starred_url":"https://api.github.com/users/ixkaito/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ixkaito/subscriptions","organizations_url":"https://api.github.com/users/ixkaito/orgs","repos_url":"https://api.github.com/users/ixkaito/repos","events_url":"https://api.github.com/users/ixkaito/events{/privacy}","received_events_url":"https://api.github.com/users/ixkaito/received_events","type":"User","site_admin":false},"created_at":"2015-07-22T08:02:59Z","updated_at":"2015-07-22T08:02:59Z","body":"\r\n# Q1.\r\n\r\nPlease try this in your Wocker directory:\r\n\r\n```\r\n$ vagrant box update\r\n```\r\n\r\n```\r\n$ vagrant up\r\n```\r\n\r\n# Q2.\r\n\r\nDid you `vagrant destroy` in your old Wocker?\r\nIf you did, you're not able to export the DB anymore.\r\nIf you didn't, you will have no problem to export after you solved the error.\r\n\r\n----\r\n\r\n# 質問1\r\n\r\nWocker ディレクトリでこちらを試してください。\r\n\r\n```\r\n$ vagrant box update\r\n```\r\n\r\n```\r\n$ vagrant up\r\n```\r\n\r\n# 質問2\r\n\r\n旧 Wocker で `vagrant destroy` はしてないですよね？\r\nもししている場合は、DB のエクスポートはもう不可能です。\r\nしていない場合は上記エラー解決後通常通りでできます。"}}