Advertisement
tommitchelmore

Untitled

Oct 19th, 2019
91
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 25.45 KB | None | 0 0
  1. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"+ ------------------------------------ +","time":"2019-10-19T09:34:55.448Z","v":0}
  2. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"| Running Pterodactyl Daemon v0.6.12 |","time":"2019-10-19T09:34:55.450Z","v":0}
  3. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"| https://pterodactyl.io |","time":"2019-10-19T09:34:55.450Z","v":0}
  4. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"| Copyright 2015 - 2019 Dane Everitt |","time":"2019-10-19T09:34:55.450Z","v":0}
  5. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"+ ------------------------------------ +","time":"2019-10-19T09:34:55.450Z","v":0}
  6. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Loading modules, this could take a few seconds.","time":"2019-10-19T09:34:55.450Z","v":0}
  7. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Modules loaded, starting Pterodactyl Daemon...","time":"2019-10-19T09:34:55.718Z","v":0}
  8. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Creating keypair to use for SFTP connections.","time":"2019-10-19T09:34:55.734Z","v":0}
  9. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Configuring user pterodactyl (id: 998) as the owner of all server files.","time":"2019-10-19T09:34:56.553Z","v":0}
  10. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Configuring timezone file location...","time":"2019-10-19T09:34:56.556Z","v":0}
  11. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Checking container networking environment...","time":"2019-10-19T09:34:56.558Z","v":0}
  12. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":40,"msg":"No isolated network interface for containers was detected, creating one now.","time":"2019-10-19T09:34:56.566Z","v":0}
  13. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Successfully created new network (pterodactyl_nw) on pterodactyl0 for isolated containers.","time":"2019-10-19T09:35:11.679Z","v":0}
  14. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Ensuring correct network interface for containers...","time":"2019-10-19T09:35:11.680Z","v":0}
  15. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Networking gateway detected as 172.18.0.1 for interface: pterodactyl0.","time":"2019-10-19T09:35:11.689Z","v":0}
  16. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Contacting panel to retrieve a list of currrent Eggs available to the node.","time":"2019-10-19T09:35:11.690Z","v":0}
  17. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Checking existing eggs against Panel response...","time":"2019-10-19T09:35:11.746Z","v":0}
  18. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Beginning server initialization process.","time":"2019-10-19T09:35:11.827Z","v":0}
  19. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Configuring websocket for daemon stats...","time":"2019-10-19T09:35:11.829Z","v":0}
  20. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Configuring internal SFTP server...","time":"2019-10-19T09:35:11.829Z","v":0}
  21. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Pterodactyl Daemon is up-to-date!","time":"2019-10-19T09:35:11.843Z","v":0}
  22. {"name":"wings","hostname":"debian.example.com","pid":15548,"level":30,"msg":"Pterodactyl Daemon is now listening for secure connections on 0.0.0.0:8080","time":"2019-10-19T09:35:11.843Z","v":0}
  23. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"+ ------------------------------------ +","time":"2019-10-19T09:36:35.947Z","v":0}
  24. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"| Running Pterodactyl Daemon v0.6.12 |","time":"2019-10-19T09:36:35.949Z","v":0}
  25. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"| https://pterodactyl.io |","time":"2019-10-19T09:36:35.949Z","v":0}
  26. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"| Copyright 2015 - 2019 Dane Everitt |","time":"2019-10-19T09:36:35.949Z","v":0}
  27. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"+ ------------------------------------ +","time":"2019-10-19T09:36:35.949Z","v":0}
  28. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Loading modules, this could take a few seconds.","time":"2019-10-19T09:36:35.949Z","v":0}
  29. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Modules loaded, starting Pterodactyl Daemon...","time":"2019-10-19T09:36:36.211Z","v":0}
  30. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Configuring user pterodactyl (id: 998) as the owner of all server files.","time":"2019-10-19T09:36:36.276Z","v":0}
  31. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Configuring timezone file location...","time":"2019-10-19T09:36:36.279Z","v":0}
  32. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Checking container networking environment...","time":"2019-10-19T09:36:36.279Z","v":0}
  33. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Found network interface for daemon: pterodactyl_nw","time":"2019-10-19T09:36:36.285Z","v":0}
  34. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Ensuring correct network interface for containers...","time":"2019-10-19T09:36:36.285Z","v":0}
  35. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Networking gateway detected as 172.18.0.1 for interface: pterodactyl0.","time":"2019-10-19T09:36:36.291Z","v":0}
  36. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Contacting panel to retrieve a list of currrent Eggs available to the node.","time":"2019-10-19T09:36:36.292Z","v":0}
  37. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Checking existing eggs against Panel response...","time":"2019-10-19T09:36:36.315Z","v":0}
  38. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Beginning server initialization process.","time":"2019-10-19T09:36:36.317Z","v":0}
  39. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Configuring websocket for daemon stats...","time":"2019-10-19T09:36:36.319Z","v":0}
  40. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Configuring internal SFTP server...","time":"2019-10-19T09:36:36.319Z","v":0}
  41. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Pterodactyl Daemon is up-to-date!","time":"2019-10-19T09:36:36.484Z","v":0}
  42. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Pterodactyl Daemon is now listening for secure connections on 0.0.0.0:8080","time":"2019-10-19T09:36:36.484Z","v":0}
  43. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":40,"msg":"Container was not found. Attempting to recreate it.","time":"2019-10-19T09:45:51.283Z","v":0}
  44. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java, if so it will happen now.","time":"2019-10-19T09:45:51.285Z","v":0}
  45. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java ... this could take a few minutes.","time":"2019-10-19T09:45:52.414Z","v":0}
  46. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":40,"msg":"Server booting is now BLOCKED.","time":"2019-10-19T09:45:58.579Z","v":0}
  47. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2019-10-19T09:45:58.580Z","v":0}
  48. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"file":"/srv/daemon/config/servers/d65bfcbf-2b61-41ff-af08-ed62f80d5b34/install.log","msg":"Writing output of installation process to file.","time":"2019-10-19T09:45:58.603Z","v":0}
  49. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Pulling image alpine:3.9 ... this could take a few minutes.","time":"2019-10-19T09:45:59.636Z","v":0}
  50. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2019-10-19T09:46:00.621Z","v":0}
  51. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":40,"msg":"Server has been suspended.","time":"2019-10-19T09:46:00.623Z","v":0}
  52. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Completed installation process for server.","time":"2019-10-19T09:46:02.978Z","v":0}
  53. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server booting is now UNBLOCKED.","time":"2019-10-19T09:46:02.988Z","v":0}
  54. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server has been unsuspended.","time":"2019-10-19T09:46:02.992Z","v":0}
  55. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Notified remote panel of server install status.","time":"2019-10-19T09:46:03.017Z","v":0}
  56. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server status has been changed to STARTING","time":"2019-10-19T09:46:03.018Z","v":0}
  57. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server status has been changed to STOPPING","time":"2019-10-19T09:46:03.018Z","v":0}
  58. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server status has been changed to OFF","time":"2019-10-19T09:46:03.018Z","v":0}
  59. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java, if so it will happen now.","time":"2019-10-19T09:46:03.022Z","v":0}
  60. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java ... this could take a few minutes.","time":"2019-10-19T09:46:04.095Z","v":0}
  61. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Completed rebuild process for server container.","time":"2019-10-19T09:46:04.205Z","v":0}
  62. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server status has been changed to STARTING","time":"2019-10-19T09:46:04.205Z","v":0}
  63. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server status has been changed to OFF","time":"2019-10-19T09:46:04.508Z","v":0}
  64. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":50,"err":{"message":"(HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default132094912` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default132094912 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 ","name":"Error","stack":"Error: (HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default132094912` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default132094912 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 \n at /srv/daemon/node_modules/docker-modem/lib/modem.js:254:17\n at getCause (/srv/daemon/node_modules/docker-modem/lib/modem.js:284:7)\n at Modem.buildPayload (/srv/daemon/node_modules/docker-modem/lib/modem.js:253:5)\n at IncomingMessage.<anonymous> (/srv/daemon/node_modules/docker-modem/lib/modem.js:229:14)\n at IncomingMessage.emit (events.js:194:15)\n at IncomingMessage.EventEmitter.emit (domain.js:459:23)\n at endReadableNT (_stream_readable.js:1103:12)\n at process._tickCallback (internal/process/next_tick.js:63:19)"},"msg":"(HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default132094912` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default132094912 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 ","time":"2019-10-19T09:46:04.510Z","v":0}
  65. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":50,"err":{"message":"(HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default132094912` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default132094912 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 ","name":"Error","stack":"Error: (HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default132094912` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default132094912 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 \n at /srv/daemon/node_modules/docker-modem/lib/modem.js:254:17\n at getCause (/srv/daemon/node_modules/docker-modem/lib/modem.js:284:7)\n at Modem.buildPayload (/srv/daemon/node_modules/docker-modem/lib/modem.js:253:5)\n at IncomingMessage.<anonymous> (/srv/daemon/node_modules/docker-modem/lib/modem.js:229:14)\n at IncomingMessage.emit (events.js:194:15)\n at IncomingMessage.EventEmitter.emit (domain.js:459:23)\n at endReadableNT (_stream_readable.js:1103:12)\n at process._tickCallback (internal/process/next_tick.js:63:19)"},"msg":"(HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default132094912` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default132094912 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 ","time":"2019-10-19T09:46:04.511Z","v":0}
  66. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server status has been changed to STARTING","time":"2019-10-19T09:48:26.629Z","v":0}
  67. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server status has been changed to STOPPING","time":"2019-10-19T09:48:26.630Z","v":0}
  68. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server status has been changed to OFF","time":"2019-10-19T09:48:26.630Z","v":0}
  69. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java, if so it will happen now.","time":"2019-10-19T09:48:26.639Z","v":0}
  70. {"name":"wings","hostname":"debian.example.com","pid":15753,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java ... this could take a few minutes.","time":"2019-10-19T09:48:27.734Z","v":0}
  71. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Completed rebuild process for server container.","time":"2019-10-19T09:48:27.795Z","v":0}
  72. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server status has been changed to STARTING","time":"2019-10-19T09:48:27.795Z","v":0}
  73. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server status has been changed to OFF","time":"2019-10-19T09:48:28.181Z","v":0}
  74. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":50,"err":{"message":"(HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default596613377` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default596613377 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 ","name":"Error","stack":"Error: (HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default596613377` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default596613377 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 \n at /srv/daemon/node_modules/docker-modem/lib/modem.js:254:17\n at getCause (/srv/daemon/node_modules/docker-modem/lib/modem.js:284:7)\n at Modem.buildPayload (/srv/daemon/node_modules/docker-modem/lib/modem.js:253:5)\n at IncomingMessage.<anonymous> (/srv/daemon/node_modules/docker-modem/lib/modem.js:229:14)\n at IncomingMessage.emit (events.js:194:15)\n at IncomingMessage.EventEmitter.emit (domain.js:441:20)\n at endReadableNT (_stream_readable.js:1103:12)\n at process._tickCallback (internal/process/next_tick.js:63:19)"},"msg":"(HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default596613377` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default596613377 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 ","time":"2019-10-19T09:48:28.181Z","v":0}
  75. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":50,"err":{"message":"(HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default596613377` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default596613377 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 ","name":"Error","stack":"Error: (HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default596613377` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default596613377 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 \n at /srv/daemon/node_modules/docker-modem/lib/modem.js:254:17\n at getCause (/srv/daemon/node_modules/docker-modem/lib/modem.js:284:7)\n at Modem.buildPayload (/srv/daemon/node_modules/docker-modem/lib/modem.js:253:5)\n at IncomingMessage.<anonymous> (/srv/daemon/node_modules/docker-modem/lib/modem.js:229:14)\n at IncomingMessage.emit (events.js:194:15)\n at IncomingMessage.EventEmitter.emit (domain.js:441:20)\n at endReadableNT (_stream_readable.js:1103:12)\n at process._tickCallback (internal/process/next_tick.js:63:19)"},"msg":"(HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default596613377` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default596613377 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 ","time":"2019-10-19T09:48:28.181Z","v":0}
  76. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server status has been changed to STARTING","time":"2019-10-19T09:48:35.821Z","v":0}
  77. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server status has been changed to OFF","time":"2019-10-19T09:48:36.121Z","v":0}
  78. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":50,"err":{"message":"(HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default168265157` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default168265157 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 ","name":"Error","stack":"Error: (HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default168265157` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default168265157 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 \n at /srv/daemon/node_modules/docker-modem/lib/modem.js:254:17\n at getCause (/srv/daemon/node_modules/docker-modem/lib/modem.js:284:7)\n at Modem.buildPayload (/srv/daemon/node_modules/docker-modem/lib/modem.js:253:5)\n at IncomingMessage.<anonymous> (/srv/daemon/node_modules/docker-modem/lib/modem.js:229:14)\n at IncomingMessage.emit (events.js:194:15)\n at IncomingMessage.EventEmitter.emit (domain.js:441:20)\n at endReadableNT (_stream_readable.js:1103:12)\n at process._tickCallback (internal/process/next_tick.js:63:19)"},"msg":"(HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default168265157` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default168265157 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 ","time":"2019-10-19T09:48:36.121Z","v":0}
  79. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server status has been changed to STARTING","time":"2019-10-19T10:01:26.755Z","v":0}
  80. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":30,"msg":"Server status has been changed to OFF","time":"2019-10-19T10:01:27.046Z","v":0}
  81. {"name":"wings","hostname":"debian.example.com","pid":15753,"server":"d65bfcbf-2b61-41ff-af08-ed62f80d5b34","level":50,"err":{"message":"(HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default082122953` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default082122953 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 ","name":"Error","stack":"Error: (HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default082122953` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default082122953 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 \n at /srv/daemon/node_modules/docker-modem/lib/modem.js:254:17\n at getCause (/srv/daemon/node_modules/docker-modem/lib/modem.js:284:7)\n at Modem.buildPayload (/srv/daemon/node_modules/docker-modem/lib/modem.js:253:5)\n at IncomingMessage.<anonymous> (/srv/daemon/node_modules/docker-modem/lib/modem.js:229:14)\n at IncomingMessage.emit (events.js:194:15)\n at IncomingMessage.EventEmitter.emit (domain.js:441:20)\n at endReadableNT (_stream_readable.js:1103:12)\n at process._tickCallback (internal/process/next_tick.js:63:19)"},"msg":"(HTTP code 500) server error - AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser -Kr /var/lib/docker/tmp/docker-default082122953` failed with output: AppArmor parser error for /var/lib/docker/tmp/docker-default082122953 in /etc/apparmor.d/tunables/global at line 17: Could not open 'tunables/proc'\n\nerror: exit status 1 ","time":"2019-10-19T10:01:27.047Z","v":0}
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement