API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Jun 25th, 2018
4,111
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 47.79 KB | None | 0 0
raw download clone embed print report
  1. janderson@jUbuntu:~$ journalctl -xu snapd.service
  2. -- Logs begin at Mon 2018-06-18 11:05:02 EDT, end at Mon 2018-06-25 11:20:42 EDT. --
  3. Jun 18 11:05:03 jUbuntu systemd[1]: Starting Snappy daemon...
  4. -- Subject: Unit snapd.service has begun start-up
  5. -- Defined-By: systemd
  6. -- Support: http://www.ubuntu.com/support
  7. --
  8. -- Unit snapd.service has begun starting up.
  9. Jun 18 11:05:03 jUbuntu snapd[813]: AppArmor status: apparmor is enabled and all features are available
  10. Jun 18 11:05:03 jUbuntu snapd[813]: 2018/06/18 11:05:03.399132 helpers.go:115: error trying to compare the snap system key: system-key missing on disk
  11. Jun 18 11:05:03 jUbuntu snapd[813]: 2018/06/18 11:05:03.414730 daemon.go:323: started snapd/2.32.5+18.04 (series 16; classic) ubuntu/18.04 (amd64) linux/4.15.0-20-generic.
  12. Jun 18 11:05:03 jUbuntu systemd[1]: Started Snappy daemon.
  13. -- Subject: Unit snapd.service has finished start-up
  14. -- Defined-By: systemd
  15. -- Support: http://www.ubuntu.com/support
  16. --
  17. -- Unit snapd.service has finished starting up.
  18. --
  19. -- The start-up result is RESULT.
  20. Jun 18 11:05:03 jUbuntu snapd[813]: 2018/06/18 11:05:03.434702 stateengine.go:101: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial tcp: lookup api.snapc
  21. Jun 18 11:05:06 jUbuntu snapd[813]: 2018/06/18 11:05:06.880886 daemon.go:477: gracefully waiting for running hooks
  22. Jun 18 11:05:06 jUbuntu snapd[813]: 2018/06/18 11:05:06.880914 daemon.go:479: done waiting for running hooks
  23. Jun 18 11:05:07 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  24. Jun 18 11:05:07 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 1.
  25. lines 1-23...skipping...
  26. -- Logs begin at Mon 2018-06-18 11:05:02 EDT, end at Mon 2018-06-25 11:20:42 EDT. --
  27. Jun 18 11:05:03 jUbuntu systemd[1]: Starting Snappy daemon...
  28. -- Subject: Unit snapd.service has begun start-up
  29. -- Defined-By: systemd
  30. -- Support: http://www.ubuntu.com/support
  31. --
  32. -- Unit snapd.service has begun starting up.
  33. Jun 18 11:05:03 jUbuntu snapd[813]: AppArmor status: apparmor is enabled and all features are available
  34. Jun 18 11:05:03 jUbuntu snapd[813]: 2018/06/18 11:05:03.399132 helpers.go:115: error trying to compare the snap system key: system-key missing on disk
  35. Jun 18 11:05:03 jUbuntu snapd[813]: 2018/06/18 11:05:03.414730 daemon.go:323: started snapd/2.32.5+18.04 (series 16; classic) ubuntu/18.04 (amd64) linux/4.15.0-20-generic.
  36. Jun 18 11:05:03 jUbuntu systemd[1]: Started Snappy daemon.
  37. -- Subject: Unit snapd.service has finished start-up
  38. -- Defined-By: systemd
  39. -- Support: http://www.ubuntu.com/support
  40. --
  41. -- Unit snapd.service has finished starting up.
  42. --
  43. -- The start-up result is RESULT.
  44. Jun 18 11:05:03 jUbuntu snapd[813]: 2018/06/18 11:05:03.434702 stateengine.go:101: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial tcp: lookup api.snapcraft.io on 127.0.0.53:5
  45. Jun 18 11:05:06 jUbuntu snapd[813]: 2018/06/18 11:05:06.880886 daemon.go:477: gracefully waiting for running hooks
  46. Jun 18 11:05:06 jUbuntu snapd[813]: 2018/06/18 11:05:06.880914 daemon.go:479: done waiting for running hooks
  47. Jun 18 11:05:07 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  48. Jun 18 11:05:07 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 1.
  49. -- Subject: Automatic restarting of a unit has been scheduled
  50. -- Defined-By: systemd
  51. -- Support: http://www.ubuntu.com/support
  52. --
  53. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  54. -- the configured Restart= setting for the unit.
  55. Jun 18 11:05:07 jUbuntu systemd[1]: Stopped Snappy daemon.
  56. -- Subject: Unit snapd.service has finished shutting down
  57. -- Defined-By: systemd
  58. -- Support: http://www.ubuntu.com/support
  59. --
  60. -- Unit snapd.service has finished shutting down.
  61. Jun 18 11:05:07 jUbuntu systemd[1]: Starting Snappy daemon...
  62. -- Subject: Unit snapd.service has begun start-up
  63. -- Defined-By: systemd
  64. -- Support: http://www.ubuntu.com/support
  65. --
  66. -- Unit snapd.service has begun starting up.
  67. Jun 18 11:05:07 jUbuntu snapd[1628]: AppArmor status: apparmor is enabled and all features are available
  68. Jun 18 11:05:07 jUbuntu snapd[1628]: 2018/06/18 11:05:07.120297 daemon.go:323: started snapd/2.32.5+18.04 (series 16; classic) ubuntu/18.04 (amd64) linux/4.15.0-20-generic.
  69. Jun 18 11:05:07 jUbuntu systemd[1]: Started Snappy daemon.
  70. -- Subject: Unit snapd.service has finished start-up
  71. -- Defined-By: systemd
  72. -- Support: http://www.ubuntu.com/support
  73. --
  74. -- Unit snapd.service has finished starting up.
  75. --
  76. -- The start-up result is RESULT.
  77. Jun 18 11:05:07 jUbuntu snapd[1628]: 2018/06/18 11:05:07.121360 stateengine.go:101: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial tcp: lookup api.snapcraft.io on 127.0.0.53:
  78. Jun 18 15:08:13 jUbuntu systemd[1]: Stopping Snappy daemon...
  79. -- Subject: Unit snapd.service has begun shutting down
  80. -- Defined-By: systemd
  81. -- Support: http://www.ubuntu.com/support
  82. --
  83. -- Unit snapd.service has begun shutting down.
  84. Jun 18 15:08:13 jUbuntu snapd[1628]: 2018/06/18 15:08:13.049153 main.go:79: Exiting on terminated signal.
  85. Jun 18 15:08:13 jUbuntu systemd[1]: Stopped Snappy daemon.
  86. -- Subject: Unit snapd.service has finished shutting down
  87. -- Defined-By: systemd
  88. -- Support: http://www.ubuntu.com/support
  89. --
  90. -- Unit snapd.service has finished shutting down.
  91. Jun 18 15:08:38 jUbuntu systemd[1]: Starting Snappy daemon...
  92. -- Subject: Unit snapd.service has begun start-up
  93. -- Defined-By: systemd
  94. -- Support: http://www.ubuntu.com/support
  95. --
  96. -- Unit snapd.service has begun starting up.
  97. Jun 18 15:08:38 jUbuntu snapd[7135]: AppArmor status: apparmor is enabled and all features are available
  98. Jun 18 15:08:39 jUbuntu snapd[7135]: 2018/06/18 15:08:39.126794 daemon.go:323: started snapd/2.32.9+18.04 (series 16; classic) ubuntu/18.04 (amd64) linux/4.15.0-20-generic.
  99. Jun 18 15:08:39 jUbuntu systemd[1]: Started Snappy daemon.
  100. -- Subject: Unit snapd.service has finished start-up
  101. -- Defined-By: systemd
  102. -- Support: http://www.ubuntu.com/support
  103. --
  104. -- Unit snapd.service has finished starting up.
  105. --
  106. -- The start-up result is RESULT.
  107. Jun 18 15:09:24 jUbuntu snapd[7135]: 2018/06/18 15:09:24.160997 daemon.go:477: gracefully waiting for running hooks
  108. Jun 18 15:09:24 jUbuntu snapd[7135]: 2018/06/18 15:09:24.161020 daemon.go:479: done waiting for running hooks
  109. Jun 18 15:09:24 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  110. Jun 18 15:09:24 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 1.
  111. -- Subject: Automatic restarting of a unit has been scheduled
  112. -- Defined-By: systemd
  113. -- Support: http://www.ubuntu.com/support
  114. --
  115. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  116. -- the configured Restart= setting for the unit.
  117. Jun 18 15:09:24 jUbuntu systemd[1]: Stopped Snappy daemon.
  118. -- Subject: Unit snapd.service has finished shutting down
  119. -- Defined-By: systemd
  120. -- Support: http://www.ubuntu.com/support
  121. --
  122. -- Unit snapd.service has finished shutting down.
  123. Jun 18 15:09:24 jUbuntu systemd[1]: Starting Snappy daemon...
  124. -- Subject: Unit snapd.service has begun start-up
  125. -- Defined-By: systemd
  126. -- Support: http://www.ubuntu.com/support
  127. --
  128. -- Unit snapd.service has begun starting up.
  129. Jun 18 15:09:24 jUbuntu snapd[19804]: AppArmor status: apparmor is enabled and all features are available
  130. Jun 18 15:09:24 jUbuntu snapd[19804]: 2018/06/18 15:09:24.561520 daemon.go:323: started snapd/2.32.9+18.04 (series 16; classic) ubuntu/18.04 (amd64) linux/4.15.0-20-generic.
  131. Jun 18 15:09:24 jUbuntu systemd[1]: Started Snappy daemon.
  132. -- Subject: Unit snapd.service has finished start-up
  133. -- Defined-By: systemd
  134. -- Support: http://www.ubuntu.com/support
  135. --
  136. -- Unit snapd.service has finished starting up.
  137. --
  138. -- The start-up result is RESULT.
  139. Jun 18 15:09:49 jUbuntu snapd[19804]: 2018/06/18 15:09:49.801810 main.go:79: Exiting on terminated signal.
  140. Jun 18 15:09:49 jUbuntu systemd[1]: Stopping Snappy daemon...
  141. -- Subject: Unit snapd.service has begun shutting down
  142. -- Defined-By: systemd
  143. -- Support: http://www.ubuntu.com/support
  144. --
  145. -- Unit snapd.service has begun shutting down.
  146. Jun 18 15:09:49 jUbuntu systemd[1]: Stopped Snappy daemon.
  147. -- Subject: Unit snapd.service has finished shutting down
  148. -- Defined-By: systemd
  149. -- Support: http://www.ubuntu.com/support
  150. --
  151. -- Unit snapd.service has finished shutting down.
  152. -- Reboot --
  153. Jun 18 15:10:10 jUbuntu systemd[1]: Starting Snappy daemon...
  154. -- Subject: Unit snapd.service has begun start-up
  155. -- Defined-By: systemd
  156. -- Support: http://www.ubuntu.com/support
  157. --
  158. -- Unit snapd.service has begun starting up.
  159. Jun 18 15:10:11 jUbuntu snapd[845]: AppArmor status: apparmor is enabled and all features are available
  160. Jun 18 15:10:11 jUbuntu snapd[845]: 2018/06/18 15:10:11.131131 daemon.go:323: started snapd/2.32.9+18.04 (series 16; classic) ubuntu/18.04 (amd64) linux/4.15.0-23-generic.
  161. Jun 18 15:10:11 jUbuntu systemd[1]: Started Snappy daemon.
  162. -- Subject: Unit snapd.service has finished start-up
  163. -- Defined-By: systemd
  164. -- Support: http://www.ubuntu.com/support
  165. --
  166. -- Unit snapd.service has finished starting up.
  167. --
  168. -- The start-up result is RESULT.
  169. Jun 18 15:10:11 jUbuntu snapd[845]: 2018/06/18 15:10:11.152728 stateengine.go:101: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial tcp: lookup api.snapcraft.io on 127.0.0.53:5
  170. Jun 18 15:11:53 jUbuntu snapd[845]: 2018/06/18 15:11:53.517712 api.go:1004: Installing snap "phpstorm" revision unset
  171. Jun 18 15:45:59 jUbuntu snapd[845]: 2018/06/18 15:45:59.246211 main.go:79: Exiting on terminated signal.
  172. Jun 18 15:45:59 jUbuntu systemd[1]: Stopping Snappy daemon...
  173. -- Subject: Unit snapd.service has begun shutting down
  174. -- Defined-By: systemd
  175. -- Support: http://www.ubuntu.com/support
  176. --
  177. -- Unit snapd.service has begun shutting down.
  178. Jun 18 15:45:59 jUbuntu systemd[1]: Stopped Snappy daemon.
  179. -- Subject: Unit snapd.service has finished shutting down
  180. -- Defined-By: systemd
  181. -- Support: http://www.ubuntu.com/support
  182. --
  183. -- Unit snapd.service has finished shutting down.
  184. -- Reboot --
  185. Jun 18 15:48:33 jUbuntu systemd[1]: Starting Snappy daemon...
  186. -- Subject: Unit snapd.service has begun start-up
  187. -- Defined-By: systemd
  188. -- Support: http://www.ubuntu.com/support
  189. --
  190. -- Unit snapd.service has begun starting up.
  191. Jun 18 15:48:34 jUbuntu snapd[899]: AppArmor status: apparmor is enabled and all features are available
  192. Jun 18 15:48:34 jUbuntu snapd[899]: 2018/06/18 15:48:34.049754 daemon.go:323: started snapd/2.32.9+18.04 (series 16; classic) ubuntu/18.04 (amd64) linux/4.15.0-23-generic.
  193. Jun 18 15:48:34 jUbuntu systemd[1]: Started Snappy daemon.
  194. -- Subject: Unit snapd.service has finished start-up
  195. -- Defined-By: systemd
  196. -- Support: http://www.ubuntu.com/support
  197. --
  198. -- Unit snapd.service has finished starting up.
  199. --
  200. -- The start-up result is RESULT.
  201. Jun 18 15:48:34 jUbuntu snapd[899]: 2018/06/18 15:48:34.052686 stateengine.go:101: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial tcp: lookup api.snapcraft.io on 127.0.0.53:5
  202. Jun 18 16:27:20 jUbuntu snapd[899]: 2018/06/18 16:27:20 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-out\r\nCache-Control: no-cache\r\nConnection: close\r\nC
  203. Jun 18 16:57:12 jUbuntu snapd[899]: 2018/06/18 16:57:12 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-out\r\nCache-Control: no-cache\r\nConnection: close\r\nC
  204. Jun 18 16:58:54 jUbuntu snapd[899]: 2018/06/18 16:58:54.858726 main.go:79: Exiting on terminated signal.
  205. Jun 18 16:58:54 jUbuntu systemd[1]: Stopping Snappy daemon...
  206. -- Subject: Unit snapd.service has begun shutting down
  207. -- Defined-By: systemd
  208. -- Support: http://www.ubuntu.com/support
  209. --
  210. -- Unit snapd.service has begun shutting down.
  211. Jun 18 16:58:54 jUbuntu systemd[1]: Stopped Snappy daemon.
  212. -- Subject: Unit snapd.service has finished shutting down
  213. -- Defined-By: systemd
  214. -- Support: http://www.ubuntu.com/support
  215. --
  216. -- Unit snapd.service has finished shutting down.
  217. -- Reboot --
  218. Jun 18 16:59:22 jUbuntu systemd[1]: Starting Snappy daemon...
  219. -- Subject: Unit snapd.service has begun start-up
  220. -- Defined-By: systemd
  221. -- Support: http://www.ubuntu.com/support
  222. --
  223. -- Unit snapd.service has begun starting up.
  224. Jun 18 16:59:23 jUbuntu snapd[722]: AppArmor status: apparmor is enabled and all features are available
  225. Jun 18 16:59:23 jUbuntu snapd[722]: 2018/06/18 16:59:23.150089 daemon.go:323: started snapd/2.32.9+18.04 (series 16; classic) ubuntu/18.04 (amd64) linux/4.15.0-23-generic.
  226. Jun 18 16:59:23 jUbuntu systemd[1]: Started Snappy daemon.
  227. -- Subject: Unit snapd.service has finished start-up
  228. -- Defined-By: systemd
  229. -- Support: http://www.ubuntu.com/support
  230. --
  231. -- Unit snapd.service has finished starting up.
  232. --
  233. -- The start-up result is RESULT.
  234. Jun 18 16:59:23 jUbuntu snapd[722]: 2018/06/18 16:59:23.160370 stateengine.go:101: state ensure error: Get https://api.snapcraft.io/api/v1/snaps/sections: dial tcp: lookup api.snapcraft.io on 127.0.0.53:5
  235. Jun 18 17:02:18 jUbuntu snapd[722]: 2018/06/18 17:02:18 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-out\r\nCache-Control: no-cache\r\nConnection: close\r\nC
  236. Jun 18 17:11:51 jUbuntu snapd[722]: 2018/06/18 17:11:51.572180 api.go:1004: Installing snap "htop" revision unset
  237. Jun 18 17:55:09 jUbuntu snapd[722]: 2018/06/18 17:55:09.639172 api.go:1004: Installing snap "gimp" revision unset
  238. Jun 18 17:55:53 jUbuntu snapd[722]: 2018/06/18 17:55:53 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-out\r\nCache-Control: no-cache\r\nConnection: close\r\nC
  239. Jun 18 19:02:39 jUbuntu snapd[722]: 2018/06/18 19:02:39 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-out\r\nCache-Control: no-cache\r\nConnection: close\r\nC
  240. Jun 18 19:21:38 jUbuntu snapd[722]: 2018/06/18 19:21:38.641622 main.go:79: Exiting on terminated signal.
  241. Jun 18 19:21:38 jUbuntu systemd[1]: Stopping Snappy daemon...
  242. -- Subject: Unit snapd.service has begun shutting down
  243. -- Defined-By: systemd
  244. -- Support: http://www.ubuntu.com/support
  245. --
  246. -- Unit snapd.service has begun shutting down.
  247. Jun 18 19:21:38 jUbuntu systemd[1]: Stopped Snappy daemon.
  248. -- Subject: Unit snapd.service has finished shutting down
  249. -- Defined-By: systemd
  250. -- Support: http://www.ubuntu.com/support
  251. --
  252. -- Unit snapd.service has finished shutting down.
  253. -- Reboot --
  254. Jun 19 05:53:56 jUbuntu systemd[1]: Starting Snappy daemon...
  255. -- Subject: Unit snapd.service has begun start-up
  256. -- Defined-By: systemd
  257. -- Support: http://www.ubuntu.com/support
  258. --
  259. -- Unit snapd.service has begun starting up.
  260. Jun 19 05:53:56 jUbuntu snapd[800]: AppArmor status: apparmor is enabled and all features are available
  261. Jun 19 05:53:56 jUbuntu snapd[800]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  262. Jun 19 05:53:56 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  263. Jun 19 05:53:56 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  264. Jun 19 05:53:56 jUbuntu systemd[1]: Failed to start Snappy daemon.
  265. -- Subject: Unit snapd.service has failed
  266. -- Defined-By: systemd
  267. -- Support: http://www.ubuntu.com/support
  268. --
  269. -- Unit snapd.service has failed.
  270. --
  271. -- The result is RESULT.
  272. Jun 19 05:53:56 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  273. Jun 19 05:53:56 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 1.
  274. -- Subject: Automatic restarting of a unit has been scheduled
  275. -- Defined-By: systemd
  276. -- Support: http://www.ubuntu.com/support
  277. --
  278. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  279. -- the configured Restart= setting for the unit.
  280. Jun 19 05:53:56 jUbuntu systemd[1]: Stopped Snappy daemon.
  281. -- Subject: Unit snapd.service has finished shutting down
  282. -- Defined-By: systemd
  283. -- Support: http://www.ubuntu.com/support
  284. --
  285. -- Unit snapd.service has finished shutting down.
  286. Jun 19 05:53:57 jUbuntu systemd[1]: Starting Snappy daemon...
  287. -- Subject: Unit snapd.service has begun start-up
  288. -- Defined-By: systemd
  289. -- Support: http://www.ubuntu.com/support
  290. --
  291. -- Unit snapd.service has begun starting up.
  292. Jun 19 05:53:57 jUbuntu snapd[1092]: AppArmor status: apparmor is enabled and all features are available
  293. Jun 19 05:53:57 jUbuntu snapd[1092]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  294. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  295. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  296. Jun 19 05:53:57 jUbuntu systemd[1]: Failed to start Snappy daemon.
  297. -- Subject: Unit snapd.service has failed
  298. -- Defined-By: systemd
  299. -- Support: http://www.ubuntu.com/support
  300. --
  301. -- Unit snapd.service has failed.
  302. --
  303. -- The result is RESULT.
  304. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  305. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 2.
  306. -- Subject: Automatic restarting of a unit has been scheduled
  307. -- Defined-By: systemd
  308. -- Support: http://www.ubuntu.com/support
  309. --
  310. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  311. -- the configured Restart= setting for the unit.
  312. Jun 19 05:53:57 jUbuntu systemd[1]: Stopped Snappy daemon.
  313. -- Subject: Unit snapd.service has finished shutting down
  314. -- Defined-By: systemd
  315. -- Support: http://www.ubuntu.com/support
  316. --
  317. -- Unit snapd.service has finished shutting down.
  318. Jun 19 05:53:57 jUbuntu systemd[1]: Starting Snappy daemon...
  319. -- Subject: Unit snapd.service has begun start-up
  320. -- Defined-By: systemd
  321. -- Support: http://www.ubuntu.com/support
  322. --
  323. -- Unit snapd.service has begun starting up.
  324. Jun 19 05:53:57 jUbuntu snapd[1174]: AppArmor status: apparmor is enabled and all features are available
  325. Jun 19 05:53:57 jUbuntu snapd[1174]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  326. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  327. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  328. Jun 19 05:53:57 jUbuntu systemd[1]: Failed to start Snappy daemon.
  329. -- Subject: Unit snapd.service has failed
  330. -- Defined-By: systemd
  331. -- Support: http://www.ubuntu.com/support
  332. --
  333. -- Unit snapd.service has failed.
  334. --
  335. -- The result is RESULT.
  336. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  337. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 3.
  338. -- Subject: Automatic restarting of a unit has been scheduled
  339. -- Defined-By: systemd
  340. -- Support: http://www.ubuntu.com/support
  341. --
  342. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  343. -- the configured Restart= setting for the unit.
  344. Jun 19 05:53:57 jUbuntu systemd[1]: Stopped Snappy daemon.
  345. -- Subject: Unit snapd.service has finished shutting down
  346. -- Defined-By: systemd
  347. -- Support: http://www.ubuntu.com/support
  348. --
  349. -- Unit snapd.service has finished shutting down.
  350. Jun 19 05:53:57 jUbuntu systemd[1]: Starting Snappy daemon...
  351. -- Subject: Unit snapd.service has begun start-up
  352. -- Defined-By: systemd
  353. -- Support: http://www.ubuntu.com/support
  354. --
  355. -- Unit snapd.service has begun starting up.
  356. Jun 19 05:53:57 jUbuntu snapd[1221]: AppArmor status: apparmor is enabled and all features are available
  357. Jun 19 05:53:57 jUbuntu snapd[1221]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  358. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  359. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  360. Jun 19 05:53:57 jUbuntu systemd[1]: Failed to start Snappy daemon.
  361. -- Subject: Unit snapd.service has failed
  362. -- Defined-By: systemd
  363. -- Support: http://www.ubuntu.com/support
  364. --
  365. -- Unit snapd.service has failed.
  366. --
  367. -- The result is RESULT.
  368. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  369. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 4.
  370. -- Subject: Automatic restarting of a unit has been scheduled
  371. -- Defined-By: systemd
  372. -- Support: http://www.ubuntu.com/support
  373. --
  374. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  375. -- the configured Restart= setting for the unit.
  376. Jun 19 05:53:57 jUbuntu systemd[1]: Stopped Snappy daemon.
  377. -- Subject: Unit snapd.service has finished shutting down
  378. -- Defined-By: systemd
  379. -- Support: http://www.ubuntu.com/support
  380. --
  381. -- Unit snapd.service has finished shutting down.
  382. Jun 19 05:53:57 jUbuntu systemd[1]: Starting Snappy daemon...
  383. -- Subject: Unit snapd.service has begun start-up
  384. -- Defined-By: systemd
  385. -- Support: http://www.ubuntu.com/support
  386. --
  387. -- Unit snapd.service has begun starting up.
  388. Jun 19 05:53:57 jUbuntu snapd[1242]: AppArmor status: apparmor is enabled and all features are available
  389. Jun 19 05:53:57 jUbuntu snapd[1242]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  390. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  391. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  392. Jun 19 05:53:57 jUbuntu systemd[1]: Failed to start Snappy daemon.
  393. -- Subject: Unit snapd.service has failed
  394. -- Defined-By: systemd
  395. -- Support: http://www.ubuntu.com/support
  396. --
  397. -- Unit snapd.service has failed.
  398. --
  399. -- The result is RESULT.
  400. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  401. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
  402. -- Subject: Automatic restarting of a unit has been scheduled
  403. -- Defined-By: systemd
  404. -- Support: http://www.ubuntu.com/support
  405. --
  406. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  407. -- the configured Restart= setting for the unit.
  408. Jun 19 05:53:57 jUbuntu systemd[1]: Stopped Snappy daemon.
  409. -- Subject: Unit snapd.service has finished shutting down
  410. -- Defined-By: systemd
  411. -- Support: http://www.ubuntu.com/support
  412. --
  413. -- Unit snapd.service has finished shutting down.
  414. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Start request repeated too quickly.
  415. Jun 19 05:53:57 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  416. Jun 19 05:53:57 jUbuntu systemd[1]: Failed to start Snappy daemon.
  417. -- Subject: Unit snapd.service has failed
  418. -- Defined-By: systemd
  419. -- Support: http://www.ubuntu.com/support
  420. --
  421. -- Unit snapd.service has failed.
  422. --
  423. -- The result is RESULT.
  424. -- Reboot --
  425. Jun 19 06:23:06 jUbuntu systemd[1]: Starting Snappy daemon...
  426. -- Subject: Unit snapd.service has begun start-up
  427. -- Defined-By: systemd
  428. -- Support: http://www.ubuntu.com/support
  429. --
  430. -- Unit snapd.service has begun starting up.
  431. Jun 19 06:23:06 jUbuntu snapd[823]: AppArmor status: apparmor is enabled and all features are available
  432. Jun 19 06:23:06 jUbuntu snapd[823]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  433. Jun 19 06:23:06 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  434. Jun 19 06:23:06 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  435. Jun 19 06:23:06 jUbuntu systemd[1]: Failed to start Snappy daemon.
  436. -- Subject: Unit snapd.service has failed
  437. -- Defined-By: systemd
  438. -- Support: http://www.ubuntu.com/support
  439. --
  440. -- Unit snapd.service has failed.
  441. --
  442. -- The result is RESULT.
  443. Jun 19 06:23:06 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  444. Jun 19 06:23:06 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 1.
  445. -- Subject: Automatic restarting of a unit has been scheduled
  446. -- Defined-By: systemd
  447. -- Support: http://www.ubuntu.com/support
  448. --
  449. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  450. -- the configured Restart= setting for the unit.
  451. Jun 19 06:23:06 jUbuntu systemd[1]: Stopped Snappy daemon.
  452. -- Subject: Unit snapd.service has finished shutting down
  453. -- Defined-By: systemd
  454. -- Support: http://www.ubuntu.com/support
  455. --
  456. -- Unit snapd.service has finished shutting down.
  457. Jun 19 06:23:06 jUbuntu systemd[1]: Starting Snappy daemon...
  458. -- Subject: Unit snapd.service has begun start-up
  459. -- Defined-By: systemd
  460. -- Support: http://www.ubuntu.com/support
  461. --
  462. -- Unit snapd.service has begun starting up.
  463. Jun 19 06:23:06 jUbuntu snapd[973]: AppArmor status: apparmor is enabled and all features are available
  464. Jun 19 06:23:06 jUbuntu snapd[973]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  465. Jun 19 06:23:06 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  466. Jun 19 06:23:06 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  467. Jun 19 06:23:06 jUbuntu systemd[1]: Failed to start Snappy daemon.
  468. -- Subject: Unit snapd.service has failed
  469. -- Defined-By: systemd
  470. -- Support: http://www.ubuntu.com/support
  471. --
  472. -- Unit snapd.service has failed.
  473. --
  474. -- The result is RESULT.
  475. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  476. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 2.
  477. -- Subject: Automatic restarting of a unit has been scheduled
  478. -- Defined-By: systemd
  479. -- Support: http://www.ubuntu.com/support
  480. --
  481. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  482. -- the configured Restart= setting for the unit.
  483. Jun 19 06:23:07 jUbuntu systemd[1]: Stopped Snappy daemon.
  484. -- Subject: Unit snapd.service has finished shutting down
  485. -- Defined-By: systemd
  486. -- Support: http://www.ubuntu.com/support
  487. --
  488. -- Unit snapd.service has finished shutting down.
  489. Jun 19 06:23:07 jUbuntu systemd[1]: Starting Snappy daemon...
  490. -- Subject: Unit snapd.service has begun start-up
  491. -- Defined-By: systemd
  492. -- Support: http://www.ubuntu.com/support
  493. --
  494. -- Unit snapd.service has begun starting up.
  495. Jun 19 06:23:07 jUbuntu snapd[996]: AppArmor status: apparmor is enabled and all features are available
  496. Jun 19 06:23:07 jUbuntu snapd[996]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  497. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  498. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  499. Jun 19 06:23:07 jUbuntu systemd[1]: Failed to start Snappy daemon.
  500. -- Subject: Unit snapd.service has failed
  501. -- Defined-By: systemd
  502. -- Support: http://www.ubuntu.com/support
  503. --
  504. -- Unit snapd.service has failed.
  505. --
  506. -- The result is RESULT.
  507. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  508. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 3.
  509. -- Subject: Automatic restarting of a unit has been scheduled
  510. -- Defined-By: systemd
  511. -- Support: http://www.ubuntu.com/support
  512. --
  513. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  514. -- the configured Restart= setting for the unit.
  515. Jun 19 06:23:07 jUbuntu systemd[1]: Stopped Snappy daemon.
  516. -- Subject: Unit snapd.service has finished shutting down
  517. -- Defined-By: systemd
  518. -- Support: http://www.ubuntu.com/support
  519. --
  520. -- Unit snapd.service has finished shutting down.
  521. Jun 19 06:23:07 jUbuntu systemd[1]: Starting Snappy daemon...
  522. -- Subject: Unit snapd.service has begun start-up
  523. -- Defined-By: systemd
  524. -- Support: http://www.ubuntu.com/support
  525. --
  526. -- Unit snapd.service has begun starting up.
  527. Jun 19 06:23:07 jUbuntu snapd[1063]: AppArmor status: apparmor is enabled and all features are available
  528. Jun 19 06:23:07 jUbuntu snapd[1063]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  529. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  530. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  531. Jun 19 06:23:07 jUbuntu systemd[1]: Failed to start Snappy daemon.
  532. -- Subject: Unit snapd.service has failed
  533. -- Defined-By: systemd
  534. -- Support: http://www.ubuntu.com/support
  535. --
  536. -- Unit snapd.service has failed.
  537. --
  538. -- The result is RESULT.
  539. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  540. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 4.
  541. -- Subject: Automatic restarting of a unit has been scheduled
  542. -- Defined-By: systemd
  543. -- Support: http://www.ubuntu.com/support
  544. --
  545. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  546. -- the configured Restart= setting for the unit.
  547. Jun 19 06:23:07 jUbuntu systemd[1]: Stopped Snappy daemon.
  548. -- Subject: Unit snapd.service has finished shutting down
  549. -- Defined-By: systemd
  550. -- Support: http://www.ubuntu.com/support
  551. --
  552. -- Unit snapd.service has finished shutting down.
  553. Jun 19 06:23:07 jUbuntu systemd[1]: Starting Snappy daemon...
  554. -- Subject: Unit snapd.service has begun start-up
  555. -- Defined-By: systemd
  556. -- Support: http://www.ubuntu.com/support
  557. --
  558. -- Unit snapd.service has begun starting up.
  559. Jun 19 06:23:07 jUbuntu snapd[1087]: AppArmor status: apparmor is enabled and all features are available
  560. Jun 19 06:23:07 jUbuntu snapd[1087]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  561. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  562. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  563. Jun 19 06:23:07 jUbuntu systemd[1]: Failed to start Snappy daemon.
  564. -- Subject: Unit snapd.service has failed
  565. -- Defined-By: systemd
  566. -- Support: http://www.ubuntu.com/support
  567. --
  568. -- Unit snapd.service has failed.
  569. --
  570. -- The result is RESULT.
  571. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  572. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
  573. -- Subject: Automatic restarting of a unit has been scheduled
  574. -- Defined-By: systemd
  575. -- Support: http://www.ubuntu.com/support
  576. --
  577. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  578. -- the configured Restart= setting for the unit.
  579. Jun 19 06:23:07 jUbuntu systemd[1]: Stopped Snappy daemon.
  580. -- Subject: Unit snapd.service has finished shutting down
  581. -- Defined-By: systemd
  582. -- Support: http://www.ubuntu.com/support
  583. --
  584. -- Unit snapd.service has finished shutting down.
  585. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Start request repeated too quickly.
  586. Jun 19 06:23:07 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  587. Jun 19 06:23:07 jUbuntu systemd[1]: Failed to start Snappy daemon.
  588. -- Subject: Unit snapd.service has failed
  589. -- Defined-By: systemd
  590. -- Support: http://www.ubuntu.com/support
  591. --
  592. -- Unit snapd.service has failed.
  593. --
  594. -- The result is RESULT.
  595. Jun 19 07:00:08 jUbuntu systemd[1]: Starting Snappy daemon...
  596. -- Subject: Unit snapd.service has begun start-up
  597. -- Defined-By: systemd
  598. -- Support: http://www.ubuntu.com/support
  599. --
  600. -- Unit snapd.service has begun starting up.
  601. Jun 19 07:00:08 jUbuntu snapd[9773]: AppArmor status: apparmor is enabled and all features are available
  602. Jun 19 07:00:08 jUbuntu snapd[9773]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  603. Jun 19 07:00:08 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  604. Jun 19 07:00:08 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  605. Jun 19 07:00:08 jUbuntu systemd[1]: Failed to start Snappy daemon.
  606. -- Subject: Unit snapd.service has failed
  607. -- Defined-By: systemd
  608. -- Support: http://www.ubuntu.com/support
  609. --
  610. -- Unit snapd.service has failed.
  611. --
  612. -- The result is RESULT.
  613. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  614. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 1.
  615. -- Subject: Automatic restarting of a unit has been scheduled
  616. -- Defined-By: systemd
  617. -- Support: http://www.ubuntu.com/support
  618. --
  619. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  620. -- the configured Restart= setting for the unit.
  621. Jun 19 07:00:09 jUbuntu systemd[1]: Stopped Snappy daemon.
  622. -- Subject: Unit snapd.service has finished shutting down
  623. -- Defined-By: systemd
  624. -- Support: http://www.ubuntu.com/support
  625. --
  626. -- Unit snapd.service has finished shutting down.
  627. Jun 19 07:00:09 jUbuntu systemd[1]: Starting Snappy daemon...
  628. -- Subject: Unit snapd.service has begun start-up
  629. -- Defined-By: systemd
  630. -- Support: http://www.ubuntu.com/support
  631. --
  632. -- Unit snapd.service has begun starting up.
  633. Jun 19 07:00:09 jUbuntu snapd[9788]: AppArmor status: apparmor is enabled and all features are available
  634. Jun 19 07:00:09 jUbuntu snapd[9788]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  635. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  636. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  637. Jun 19 07:00:09 jUbuntu systemd[1]: Failed to start Snappy daemon.
  638. -- Subject: Unit snapd.service has failed
  639. -- Defined-By: systemd
  640. -- Support: http://www.ubuntu.com/support
  641. --
  642. -- Unit snapd.service has failed.
  643. --
  644. -- The result is RESULT.
  645. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  646. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 2.
  647. -- Subject: Automatic restarting of a unit has been scheduled
  648. -- Defined-By: systemd
  649. -- Support: http://www.ubuntu.com/support
  650. --
  651. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  652. -- the configured Restart= setting for the unit.
  653. Jun 19 07:00:09 jUbuntu systemd[1]: Stopped Snappy daemon.
  654. -- Subject: Unit snapd.service has finished shutting down
  655. -- Defined-By: systemd
  656. -- Support: http://www.ubuntu.com/support
  657. --
  658. -- Unit snapd.service has finished shutting down.
  659. Jun 19 07:00:09 jUbuntu systemd[1]: Starting Snappy daemon...
  660. -- Subject: Unit snapd.service has begun start-up
  661. -- Defined-By: systemd
  662. -- Support: http://www.ubuntu.com/support
  663. --
  664. -- Unit snapd.service has begun starting up.
  665. Jun 19 07:00:09 jUbuntu snapd[9801]: AppArmor status: apparmor is enabled and all features are available
  666. Jun 19 07:00:09 jUbuntu snapd[9801]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  667. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  668. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  669. Jun 19 07:00:09 jUbuntu systemd[1]: Failed to start Snappy daemon.
  670. -- Subject: Unit snapd.service has failed
  671. -- Defined-By: systemd
  672. -- Support: http://www.ubuntu.com/support
  673. --
  674. -- Unit snapd.service has failed.
  675. --
  676. -- The result is RESULT.
  677. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  678. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 3.
  679. -- Subject: Automatic restarting of a unit has been scheduled
  680. -- Defined-By: systemd
  681. -- Support: http://www.ubuntu.com/support
  682. --
  683. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  684. -- the configured Restart= setting for the unit.
  685. Jun 19 07:00:09 jUbuntu systemd[1]: Stopped Snappy daemon.
  686. -- Subject: Unit snapd.service has finished shutting down
  687. -- Defined-By: systemd
  688. -- Support: http://www.ubuntu.com/support
  689. --
  690. -- Unit snapd.service has finished shutting down.
  691. Jun 19 07:00:09 jUbuntu systemd[1]: Starting Snappy daemon...
  692. -- Subject: Unit snapd.service has begun start-up
  693. -- Defined-By: systemd
  694. -- Support: http://www.ubuntu.com/support
  695. --
  696. -- Unit snapd.service has begun starting up.
  697. Jun 19 07:00:09 jUbuntu snapd[9814]: AppArmor status: apparmor is enabled and all features are available
  698. Jun 19 07:00:09 jUbuntu snapd[9814]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  699. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  700. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  701. Jun 19 07:00:09 jUbuntu systemd[1]: Failed to start Snappy daemon.
  702. -- Subject: Unit snapd.service has failed
  703. -- Defined-By: systemd
  704. -- Support: http://www.ubuntu.com/support
  705. --
  706. -- Unit snapd.service has failed.
  707. --
  708. -- The result is RESULT.
  709. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  710. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 4.
  711. -- Subject: Automatic restarting of a unit has been scheduled
  712. -- Defined-By: systemd
  713. -- Support: http://www.ubuntu.com/support
  714. --
  715. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  716. -- the configured Restart= setting for the unit.
  717. Jun 19 07:00:09 jUbuntu systemd[1]: Stopped Snappy daemon.
  718. -- Subject: Unit snapd.service has finished shutting down
  719. -- Defined-By: systemd
  720. -- Support: http://www.ubuntu.com/support
  721. --
  722. -- Unit snapd.service has finished shutting down.
  723. Jun 19 07:00:09 jUbuntu systemd[1]: Starting Snappy daemon...
  724. -- Subject: Unit snapd.service has begun start-up
  725. -- Defined-By: systemd
  726. -- Support: http://www.ubuntu.com/support
  727. --
  728. -- Unit snapd.service has begun starting up.
  729. Jun 19 07:00:09 jUbuntu snapd[9826]: AppArmor status: apparmor is enabled and all features are available
  730. Jun 19 07:00:09 jUbuntu snapd[9826]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  731. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  732. Jun 19 07:00:09 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  733. Jun 19 07:00:09 jUbuntu systemd[1]: Failed to start Snappy daemon.
  734. -- Subject: Unit snapd.service has failed
  735. -- Defined-By: systemd
  736. -- Support: http://www.ubuntu.com/support
  737. --
  738. -- Unit snapd.service has failed.
  739. --
  740. -- The result is RESULT.
  741. Jun 19 07:00:10 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  742. Jun 19 07:00:10 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
  743. -- Subject: Automatic restarting of a unit has been scheduled
  744. -- Defined-By: systemd
  745. -- Support: http://www.ubuntu.com/support
  746. --
  747. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  748. -- the configured Restart= setting for the unit.
  749. Jun 19 07:00:10 jUbuntu systemd[1]: Stopped Snappy daemon.
  750. -- Subject: Unit snapd.service has finished shutting down
  751. -- Defined-By: systemd
  752. -- Support: http://www.ubuntu.com/support
  753. --
  754. -- Unit snapd.service has finished shutting down.
  755. Jun 19 07:00:10 jUbuntu systemd[1]: snapd.service: Start request repeated too quickly.
  756. Jun 19 07:00:10 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  757. Jun 19 07:00:10 jUbuntu systemd[1]: Failed to start Snappy daemon.
  758. -- Subject: Unit snapd.service has failed
  759. -- Defined-By: systemd
  760. -- Support: http://www.ubuntu.com/support
  761. --
  762. -- Unit snapd.service has failed.
  763. --
  764. -- The result is RESULT.
  765. -- Reboot --
  766. Jun 19 07:22:00 jUbuntu systemd[1]: Starting Snappy daemon...
  767. -- Subject: Unit snapd.service has begun start-up
  768. -- Defined-By: systemd
  769. -- Support: http://www.ubuntu.com/support
  770. --
  771. -- Unit snapd.service has begun starting up.
  772. Jun 19 07:22:01 jUbuntu snapd[779]: AppArmor status: apparmor is enabled and all features are available
  773. Jun 19 07:22:01 jUbuntu snapd[779]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  774. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  775. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  776. Jun 19 07:22:01 jUbuntu systemd[1]: Failed to start Snappy daemon.
  777. -- Subject: Unit snapd.service has failed
  778. -- Defined-By: systemd
  779. -- Support: http://www.ubuntu.com/support
  780. --
  781. -- Unit snapd.service has failed.
  782. --
  783. -- The result is RESULT.
  784. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  785. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 1.
  786. -- Subject: Automatic restarting of a unit has been scheduled
  787. -- Defined-By: systemd
  788. -- Support: http://www.ubuntu.com/support
  789. --
  790. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  791. -- the configured Restart= setting for the unit.
  792. Jun 19 07:22:01 jUbuntu systemd[1]: Stopped Snappy daemon.
  793. -- Subject: Unit snapd.service has finished shutting down
  794. -- Defined-By: systemd
  795. -- Support: http://www.ubuntu.com/support
  796. --
  797. -- Unit snapd.service has finished shutting down.
  798. Jun 19 07:22:01 jUbuntu systemd[1]: Starting Snappy daemon...
  799. -- Subject: Unit snapd.service has begun start-up
  800. -- Defined-By: systemd
  801. -- Support: http://www.ubuntu.com/support
  802. --
  803. -- Unit snapd.service has begun starting up.
  804. Jun 19 07:22:01 jUbuntu snapd[988]: AppArmor status: apparmor is enabled and all features are available
  805. Jun 19 07:22:01 jUbuntu snapd[988]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  806. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  807. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  808. Jun 19 07:22:01 jUbuntu systemd[1]: Failed to start Snappy daemon.
  809. -- Subject: Unit snapd.service has failed
  810. -- Defined-By: systemd
  811. -- Support: http://www.ubuntu.com/support
  812. --
  813. -- Unit snapd.service has failed.
  814. --
  815. -- The result is RESULT.
  816. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  817. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 2.
  818. -- Subject: Automatic restarting of a unit has been scheduled
  819. -- Defined-By: systemd
  820. -- Support: http://www.ubuntu.com/support
  821. --
  822. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  823. -- the configured Restart= setting for the unit.
  824. Jun 19 07:22:01 jUbuntu systemd[1]: Stopped Snappy daemon.
  825. -- Subject: Unit snapd.service has finished shutting down
  826. -- Defined-By: systemd
  827. -- Support: http://www.ubuntu.com/support
  828. --
  829. -- Unit snapd.service has finished shutting down.
  830. Jun 19 07:22:01 jUbuntu systemd[1]: Starting Snappy daemon...
  831. -- Subject: Unit snapd.service has begun start-up
  832. -- Defined-By: systemd
  833. -- Support: http://www.ubuntu.com/support
  834. --
  835. -- Unit snapd.service has begun starting up.
  836. Jun 19 07:22:01 jUbuntu snapd[1025]: AppArmor status: apparmor is enabled and all features are available
  837. Jun 19 07:22:01 jUbuntu snapd[1025]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  838. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  839. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  840. Jun 19 07:22:01 jUbuntu systemd[1]: Failed to start Snappy daemon.
  841. -- Subject: Unit snapd.service has failed
  842. -- Defined-By: systemd
  843. -- Support: http://www.ubuntu.com/support
  844. --
  845. -- Unit snapd.service has failed.
  846. --
  847. -- The result is RESULT.
  848. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  849. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 3.
  850. -- Subject: Automatic restarting of a unit has been scheduled
  851. -- Defined-By: systemd
  852. -- Support: http://www.ubuntu.com/support
  853. --
  854. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  855. -- the configured Restart= setting for the unit.
  856. Jun 19 07:22:01 jUbuntu systemd[1]: Stopped Snappy daemon.
  857. -- Subject: Unit snapd.service has finished shutting down
  858. -- Defined-By: systemd
  859. -- Support: http://www.ubuntu.com/support
  860. --
  861. -- Unit snapd.service has finished shutting down.
  862. Jun 19 07:22:01 jUbuntu systemd[1]: Starting Snappy daemon...
  863. -- Subject: Unit snapd.service has begun start-up
  864. -- Defined-By: systemd
  865. -- Support: http://www.ubuntu.com/support
  866. --
  867. -- Unit snapd.service has begun starting up.
  868. Jun 19 07:22:01 jUbuntu snapd[1090]: AppArmor status: apparmor is enabled and all features are available
  869. Jun 19 07:22:01 jUbuntu snapd[1090]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  870. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  871. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  872. Jun 19 07:22:01 jUbuntu systemd[1]: Failed to start Snappy daemon.
  873. -- Subject: Unit snapd.service has failed
  874. -- Defined-By: systemd
  875. -- Support: http://www.ubuntu.com/support
  876. --
  877. -- Unit snapd.service has failed.
  878. --
  879. -- The result is RESULT.
  880. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  881. Jun 19 07:22:01 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 4.
  882. -- Subject: Automatic restarting of a unit has been scheduled
  883. ...skipping...
  884. -- Subject: Automatic restarting of a unit has been scheduled
  885. -- Defined-By: systemd
  886. -- Support: http://www.ubuntu.com/support
  887. --
  888. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  889. -- the configured Restart= setting for the unit.
  890. Jun 25 08:14:12 jUbuntu systemd[1]: Stopped Snappy daemon.
  891. -- Subject: Unit snapd.service has finished shutting down
  892. -- Defined-By: systemd
  893. -- Support: http://www.ubuntu.com/support
  894. --
  895. -- Unit snapd.service has finished shutting down.
  896. Jun 25 08:14:12 jUbuntu systemd[1]: Starting Snappy daemon...
  897. -- Subject: Unit snapd.service has begun start-up
  898. -- Defined-By: systemd
  899. -- Support: http://www.ubuntu.com/support
  900. --
  901. -- Unit snapd.service has begun starting up.
  902. Jun 25 08:14:12 jUbuntu snapd[1107]: AppArmor status: apparmor is enabled and all features are available
  903. Jun 25 08:14:12 jUbuntu snapd[1107]: error: assert storage root unexpectedly world-writable: /var/lib/snapd/assertions/asserts-v0
  904. Jun 25 08:14:12 jUbuntu systemd[1]: snapd.service: Main process exited, code=exited, status=1/FAILURE
  905. Jun 25 08:14:12 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  906. Jun 25 08:14:12 jUbuntu systemd[1]: Failed to start Snappy daemon.
  907. -- Subject: Unit snapd.service has failed
  908. -- Defined-By: systemd
  909. -- Support: http://www.ubuntu.com/support
  910. --
  911. -- Unit snapd.service has failed.
  912. --
  913. -- The result is RESULT.
  914. Jun 25 08:14:12 jUbuntu systemd[1]: snapd.service: Service hold-off time over, scheduling restart.
  915. Jun 25 08:14:12 jUbuntu systemd[1]: snapd.service: Scheduled restart job, restart counter is at 5.
  916. -- Subject: Automatic restarting of a unit has been scheduled
  917. -- Defined-By: systemd
  918. -- Support: http://www.ubuntu.com/support
  919. --
  920. -- Automatic restarting of the unit snapd.service has been scheduled, as the result for
  921. -- the configured Restart= setting for the unit.
  922. Jun 25 08:14:12 jUbuntu systemd[1]: Stopped Snappy daemon.
  923. -- Subject: Unit snapd.service has finished shutting down
  924. -- Defined-By: systemd
  925. -- Support: http://www.ubuntu.com/support
  926. --
  927. -- Unit snapd.service has finished shutting down.
  928. Jun 25 08:14:12 jUbuntu systemd[1]: snapd.service: Start request repeated too quickly.
  929. Jun 25 08:14:12 jUbuntu systemd[1]: snapd.service: Failed with result 'exit-code'.
  930. Jun 25 08:14:12 jUbuntu systemd[1]: Failed to start Snappy daemon.
  931. -- Subject: Unit snapd.service has failed
  932. -- Defined-By: systemd
  933. -- Support: http://www.ubuntu.com/support
  934. --
  935. -- Unit snapd.service has failed.
  936. --
  937. -- The result is RESULT.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!