{"action":"created","issue":{"url":"https://api.github.com/repos/vmware/vic-product/issues/1124","repository_url":"https://api.github.com/repos/vmware/vic-product","labels_url":"https://api.github.com/repos/vmware/vic-product/issues/1124/labels{/name}","comments_url":"https://api.github.com/repos/vmware/vic-product/issues/1124/comments","events_url":"https://api.github.com/repos/vmware/vic-product/issues/1124/events","html_url":"https://github.com/vmware/vic-product/issues/1124","id":275954803,"number":1124,"title":"Admiral logs are not getting updated on OVA","user":{"login":"lgayatri","id":25006749,"avatar_url":"https://avatars3.githubusercontent.com/u/25006749?v=4","gravatar_id":"","url":"https://api.github.com/users/lgayatri","html_url":"https://github.com/lgayatri","followers_url":"https://api.github.com/users/lgayatri/followers","following_url":"https://api.github.com/users/lgayatri/following{/other_user}","gists_url":"https://api.github.com/users/lgayatri/gists{/gist_id}","starred_url":"https://api.github.com/users/lgayatri/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lgayatri/subscriptions","organizations_url":"https://api.github.com/users/lgayatri/orgs","repos_url":"https://api.github.com/users/lgayatri/repos","events_url":"https://api.github.com/users/lgayatri/events{/privacy}","received_events_url":"https://api.github.com/users/lgayatri/received_events","type":"User","site_admin":false},"labels":[{"id":460949432,"url":"https://api.github.com/repos/vmware/vic-product/labels/component/admiral","name":"component/admiral","color":"d4c5f9","default":false},{"id":625572464,"url":"https://api.github.com/repos/vmware/vic-product/labels/component/ova","name":"component/ova","color":"d4c5f9","default":false},{"id":659998228,"url":"https://api.github.com/repos/vmware/vic-product/labels/status/need-info","name":"status/need-info","color":"d93f0b","default":false},{"id":712440499,"url":"https://api.github.com/repos/vmware/vic-product/labels/team/lifecycle","name":"team/lifecycle","color":"c2e0c6","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2017-11-22T06:08:36Z","updated_at":"2017-11-23T14:03:35Z","closed_at":"2017-11-23T14:03:35Z","author_association":"NONE","body":"@andrewtchin @mhagen-vmware @stuclem @sergiosagu \r\n\r\nThere were few errors in Admiral and I wanted to check the logs. Checked  journalctl -u admiral.service , docker logs vic-admiral and docker logs <containerID of Admiral> and noticed that the logs did not get updated after Nov 16 10:27:39 .\r\n\r\nAs per https://vmware.github.io/vic-product/assets/files/html/1.2/vic_vsphere_admin/appliance_logs.html,  docker logs vic-admiral should provide the logs but that is not showing updated logs.\r\n\r\nHowever the journalctl output says:\r\n-- Logs begin at Tue 2017-11-14 00:30:25 UTC, end at Wed 2017-11-22 05:34:25 UTC. -- \r\nbut there is no latest logging.\r\n\r\nI found xenonHost.0.log in /storage/log/admiral which seems to record admiral activity. The file is 545MB.\r\n\r\nThree issues here:\r\n1. We should fix \"docker logs vic-admiral\" to get the latest admiral logs\r\n2. If user should refer to xenonHost log in /storage/log/admiral for admiral logs, then can we zip the log file and use log rotation as single file with 545 MB is huge\r\n3. Why does journalctl show partial logs\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/vmware/vic-product/issues/comments/346626539","html_url":"https://github.com/vmware/vic-product/issues/1124#issuecomment-346626539","issue_url":"https://api.github.com/repos/vmware/vic-product/issues/1124","id":346626539,"user":{"login":"sergiosagu","id":2034419,"avatar_url":"https://avatars2.githubusercontent.com/u/2034419?v=4","gravatar_id":"","url":"https://api.github.com/users/sergiosagu","html_url":"https://github.com/sergiosagu","followers_url":"https://api.github.com/users/sergiosagu/followers","following_url":"https://api.github.com/users/sergiosagu/following{/other_user}","gists_url":"https://api.github.com/users/sergiosagu/gists{/gist_id}","starred_url":"https://api.github.com/users/sergiosagu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sergiosagu/subscriptions","organizations_url":"https://api.github.com/users/sergiosagu/orgs","repos_url":"https://api.github.com/users/sergiosagu/repos","events_url":"https://api.github.com/users/sergiosagu/events{/privacy}","received_events_url":"https://api.github.com/users/sergiosagu/received_events","type":"User","site_admin":false},"created_at":"2017-11-23T14:03:35Z","updated_at":"2017-11-23T14:03:35Z","author_association":"NONE","body":"> I logged in and I believe this is functioning correctly. The logs in journalctl are for the service starting, while the application logs are in `/storage/log/admiral`\r\n\r\nThat's the expected behavior I'd say.\r\n\r\n> The `Content is not allowed in prolog.` seems to be a java error coming from Admiral.\r\n\r\nNot sure exactly why this is happening yet, but the same issue is reported in https://github.com/vmware/vic-product/issues/1110\r\nThus I'm closing this one.\r\n\r\n"}}
{"actor":{"display_login":"sergiosagu"}}