wings.log

{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"+ ------------------------------------ +","time":"2017-11-19T07:33:37.230Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"| Running Pterodactyl Daemon v0.4.5    |","time":"2017-11-19T07:33:37.231Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"|        https://pterodactyl.io        |","time":"2017-11-19T07:33:37.232Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"|  Copyright 2015 - 2017 Dane Everitt  |","time":"2017-11-19T07:33:37.232Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"+ ------------------------------------ +","time":"2017-11-19T07:33:37.232Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Loading modules, this could take a few seconds.","time":"2017-11-19T07:33:37.232Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Modules loaded, starting Pterodactyl Daemon...","time":"2017-11-19T07:33:37.397Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Contacting panel to retrieve a list of currrent services available to the node.","time":"2017-11-19T07:33:37.422Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Checking container networking environment...","time":"2017-11-19T07:33:37.423Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":40,"msg":"No isolated network interface for containers was detected, creating one now.","time":"2017-11-19T07:33:37.429Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Checking current files aganist panel response.","time":"2017-11-19T07:33:37.484Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Successfully created new network (pterodactyl_nw) on pterodactyl0 for isolated containers.","time":"2017-11-19T07:33:52.477Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Configuring timezone file location...","time":"2017-11-19T07:33:52.478Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Checking pterodactyl0 interface and setting configuration values.","time":"2017-11-19T07:33:52.489Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Checking gateway for pterodactyl0","time":"2017-11-19T07:33:52.489Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Gateway detected as 172.18.0.1 for pterodactyl0.","time":"2017-11-19T07:33:52.501Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Attempting to start SFTP service container...","time":"2017-11-19T07:33:52.504Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":40,"msg":"Unable to locate a suitable SFTP container in the configuration, creating one now.","time":"2017-11-19T07:33:52.508Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Checking if we need to update the SFTP container image quay.io/pterodactyl/scrappy:latest, if so it will happen now.","time":"2017-11-19T07:33:52.509Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Pulling image quay.io/pterodactyl/scrappy:latest ... this could take a few minutes.","time":"2017-11-19T07:33:53.898Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"SFTP container successfully booted.","time":"2017-11-19T07:34:01.328Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Attempting to load servers and initialize daemon...","time":"2017-11-19T07:34:01.328Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Configuring websocket for daemon stats...","time":"2017-11-19T07:34:01.334Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Pterodactyl Daemon is up-to-date!","time":"2017-11-19T07:34:01.350Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":1555,"level":30,"msg":"Pterodactyl Daemon is now listening for insecure connections on 0.0.0.0:8080","time":"2017-11-19T07:34:01.353Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"+ ------------------------------------ +","time":"2017-11-19T07:37:34.381Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"| Running Pterodactyl Daemon v0.4.5    |","time":"2017-11-19T07:37:34.383Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"|        https://pterodactyl.io        |","time":"2017-11-19T07:37:34.383Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"|  Copyright 2015 - 2017 Dane Everitt  |","time":"2017-11-19T07:37:34.383Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"+ ------------------------------------ +","time":"2017-11-19T07:37:34.383Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Loading modules, this could take a few seconds.","time":"2017-11-19T07:37:34.383Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Modules loaded, starting Pterodactyl Daemon...","time":"2017-11-19T07:37:34.546Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Contacting panel to retrieve a list of currrent services available to the node.","time":"2017-11-19T07:37:34.572Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Checking container networking environment...","time":"2017-11-19T07:37:34.573Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Found network interface for daemon: pterodactyl_nw","time":"2017-11-19T07:37:34.579Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Configuring timezone file location...","time":"2017-11-19T07:37:34.579Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Checking pterodactyl0 interface and setting configuration values.","time":"2017-11-19T07:37:34.588Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Checking gateway for pterodactyl0","time":"2017-11-19T07:37:34.588Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Gateway detected as 172.18.0.1 for pterodactyl0.","time":"2017-11-19T07:37:34.594Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Attempting to start SFTP service container...","time":"2017-11-19T07:37:34.594Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"SFTP container successfully booted.","time":"2017-11-19T07:37:34.600Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Checking current files aganist panel response.","time":"2017-11-19T07:37:34.629Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Attempting to load servers and initialize daemon...","time":"2017-11-19T07:37:34.633Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Configuring websocket for daemon stats...","time":"2017-11-19T07:37:34.638Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Pterodactyl Daemon is up-to-date!","time":"2017-11-19T07:37:36.131Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":2174,"level":30,"msg":"Pterodactyl Daemon is now listening for insecure connections on 0.0.0.0:8080","time":"2017-11-19T07:37:36.134Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"+ ------------------------------------ +","time":"2017-11-19T08:14:22.392Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"| Running Pterodactyl Daemon v0.4.5    |","time":"2017-11-19T08:14:22.393Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"|        https://pterodactyl.io        |","time":"2017-11-19T08:14:22.393Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"|  Copyright 2015 - 2017 Dane Everitt  |","time":"2017-11-19T08:14:22.393Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"+ ------------------------------------ +","time":"2017-11-19T08:14:22.394Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Loading modules, this could take a few seconds.","time":"2017-11-19T08:14:22.394Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Modules loaded, starting Pterodactyl Daemon...","time":"2017-11-19T08:14:22.558Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Contacting panel to retrieve a list of currrent services available to the node.","time":"2017-11-19T08:14:22.583Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Checking container networking environment...","time":"2017-11-19T08:14:22.584Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Found network interface for daemon: pterodactyl_nw","time":"2017-11-19T08:14:22.590Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Configuring timezone file location...","time":"2017-11-19T08:14:22.590Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Checking pterodactyl0 interface and setting configuration values.","time":"2017-11-19T08:14:22.590Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Checking gateway for pterodactyl0","time":"2017-11-19T08:14:22.590Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Gateway detected as 172.18.0.1 for pterodactyl0.","time":"2017-11-19T08:14:22.597Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Attempting to start SFTP service container...","time":"2017-11-19T08:14:22.604Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"SFTP container successfully booted.","time":"2017-11-19T08:14:22.611Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Checking current files aganist panel response.","time":"2017-11-19T08:14:24.888Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Attempting to load servers and initialize daemon...","time":"2017-11-19T08:14:24.890Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Configuring websocket for daemon stats...","time":"2017-11-19T08:14:24.892Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Pterodactyl Daemon is up-to-date!","time":"2017-11-19T08:14:24.899Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Pterodactyl Daemon is now listening for insecure connections on 0.0.0.0:8080","time":"2017-11-19T08:14:24.902Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"server":"94f6a084-a2a0-477a-bdda-95edd1df6341","level":40,"msg":"Container was not found. Attempting to recreate it.","time":"2017-11-19T08:15:22.118Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java, if so it will happen now.","time":"2017-11-19T08:15:22.119Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java ... this could take a few minutes.","time":"2017-11-19T08:15:23.597Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"server":"94f6a084-a2a0-477a-bdda-95edd1df6341","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T08:15:23.759Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"server":"94f6a084-a2a0-477a-bdda-95edd1df6341","level":40,"msg":"Server booting is now BLOCKED.","time":"2017-11-19T08:15:23.822Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"server":"94f6a084-a2a0-477a-bdda-95edd1df6341","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2017-11-19T08:15:23.823Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"server":"94f6a084-a2a0-477a-bdda-95edd1df6341","level":30,"msg":"Writing output of installation process to file. { file: '/srv/daemon/config/servers/94f6a084-a2a0-477a-bdda-95edd1df6341/install.log' }","time":"2017-11-19T08:15:23.843Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Pulling image alpine:3.4 ... this could take a few minutes.","time":"2017-11-19T08:15:25.022Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"server":"94f6a084-a2a0-477a-bdda-95edd1df6341","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2017-11-19T08:15:26.056Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"server":"94f6a084-a2a0-477a-bdda-95edd1df6341","level":40,"msg":"Server has been suspended.","time":"2017-11-19T08:15:26.112Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"server":"94f6a084-a2a0-477a-bdda-95edd1df6341","level":30,"msg":"Completed installation process for server.","time":"2017-11-19T08:15:35.980Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":60,"msg":"A fatal error was encountered while attempting to create a server. Error: Unable to set ownership of files properly, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:103:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)","time":"2017-11-19T08:15:36.001Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"server":"94f6a084-a2a0-477a-bdda-95edd1df6341","level":40,"msg":"No container ID was defined in the server JSON, skipping container deletion step.","time":"2017-11-19T08:15:36.009Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":30,"msg":"Notified remote panel of server install status.","time":"2017-11-19T08:15:36.048Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"server":"94f6a084-a2a0-477a-bdda-95edd1df6341","level":30,"msg":"Server has been unsuspended.","time":"2017-11-19T08:15:36.086Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":60,"err":{"message":"EACCES: permission denied, rmdir '/srv/daemon-data/bungee_94f6a084'","name":"Error","stack":"Error: EACCES: permission denied, rmdir '/srv/daemon-data/bungee_94f6a084'\n    at Error (native)","code":"EACCES"},"msg":"EACCES: permission denied, rmdir '/srv/daemon-data/bungee_94f6a084'","time":"2017-11-19T08:15:36.113Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6307,"level":50,"err":{"message":"EACCES: permission denied, rmdir '/srv/daemon-data/bungee_94f6a084'","name":"Error","stack":"Error: EACCES: permission denied, rmdir '/srv/daemon-data/bungee_94f6a084'\n    at Error (native)","code":"EACCES"},"msg":"EACCES: permission denied, rmdir '/srv/daemon-data/bungee_94f6a084'","time":"2017-11-19T08:15:36.114Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"+ ------------------------------------ +","time":"2017-11-19T08:21:27.033Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"| Running Pterodactyl Daemon v0.4.5    |","time":"2017-11-19T08:21:27.034Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"|        https://pterodactyl.io        |","time":"2017-11-19T08:21:27.035Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"|  Copyright 2015 - 2017 Dane Everitt  |","time":"2017-11-19T08:21:27.035Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"+ ------------------------------------ +","time":"2017-11-19T08:21:27.035Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Loading modules, this could take a few seconds.","time":"2017-11-19T08:21:27.035Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Modules loaded, starting Pterodactyl Daemon...","time":"2017-11-19T08:21:27.198Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Contacting panel to retrieve a list of currrent services available to the node.","time":"2017-11-19T08:21:27.224Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Checking container networking environment...","time":"2017-11-19T08:21:27.224Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Found network interface for daemon: pterodactyl_nw","time":"2017-11-19T08:21:27.230Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Configuring timezone file location...","time":"2017-11-19T08:21:27.230Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Checking pterodactyl0 interface and setting configuration values.","time":"2017-11-19T08:21:27.231Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Checking gateway for pterodactyl0","time":"2017-11-19T08:21:27.231Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Gateway detected as 172.18.0.1 for pterodactyl0.","time":"2017-11-19T08:21:27.236Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Attempting to start SFTP service container...","time":"2017-11-19T08:21:27.242Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"SFTP container successfully booted.","time":"2017-11-19T08:21:27.246Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Checking current files aganist panel response.","time":"2017-11-19T08:21:30.432Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Attempting to load servers and initialize daemon...","time":"2017-11-19T08:21:30.434Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Configuring websocket for daemon stats...","time":"2017-11-19T08:21:30.436Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":40,"msg":"An error occurred while attempting to check the latest daemon release version.","time":"2017-11-19T08:21:32.237Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Pterodactyl Daemon is now listening for insecure connections on 0.0.0.0:8080","time":"2017-11-19T08:21:32.239Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"server":"05d41756-3fa4-4c45-8aa4-4a88b29749ab","level":40,"msg":"Container was not found. Attempting to recreate it.","time":"2017-11-19T08:21:59.517Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java, if so it will happen now.","time":"2017-11-19T08:21:59.518Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java ... this could take a few minutes.","time":"2017-11-19T08:22:00.869Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"server":"05d41756-3fa4-4c45-8aa4-4a88b29749ab","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T08:22:01.037Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"server":"05d41756-3fa4-4c45-8aa4-4a88b29749ab","level":40,"msg":"Server booting is now BLOCKED.","time":"2017-11-19T08:22:01.094Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"server":"05d41756-3fa4-4c45-8aa4-4a88b29749ab","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2017-11-19T08:22:01.095Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"server":"05d41756-3fa4-4c45-8aa4-4a88b29749ab","level":30,"msg":"Writing output of installation process to file. { file: '/srv/daemon/config/servers/05d41756-3fa4-4c45-8aa4-4a88b29749ab/install.log' }","time":"2017-11-19T08:22:01.118Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Pulling image alpine:3.4 ... this could take a few minutes.","time":"2017-11-19T08:22:02.322Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"server":"05d41756-3fa4-4c45-8aa4-4a88b29749ab","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2017-11-19T08:22:02.784Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"server":"05d41756-3fa4-4c45-8aa4-4a88b29749ab","level":40,"msg":"Server has been suspended.","time":"2017-11-19T08:22:02.830Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"server":"05d41756-3fa4-4c45-8aa4-4a88b29749ab","level":30,"msg":"Completed installation process for server.","time":"2017-11-19T08:22:10.327Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":60,"msg":"A fatal error was encountered while attempting to create a server. Error: Unable to set ownership of files properly, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:103:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)","time":"2017-11-19T08:22:10.348Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"server":"05d41756-3fa4-4c45-8aa4-4a88b29749ab","level":40,"msg":"No container ID was defined in the server JSON, skipping container deletion step.","time":"2017-11-19T08:22:10.358Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"level":30,"msg":"Notified remote panel of server install status.","time":"2017-11-19T08:22:10.398Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"server":"05d41756-3fa4-4c45-8aa4-4a88b29749ab","level":30,"msg":"Server has been unsuspended.","time":"2017-11-19T08:22:10.441Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":6970,"server":"05d41756-3fa4-4c45-8aa4-4a88b29749ab","level":30,"msg":"Server deleted.","time":"2017-11-19T08:22:10.469Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"+ ------------------------------------ +","time":"2017-11-19T08:33:33.305Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"| Running Pterodactyl Daemon v0.4.5    |","time":"2017-11-19T08:33:33.306Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"|        https://pterodactyl.io        |","time":"2017-11-19T08:33:33.307Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"|  Copyright 2015 - 2017 Dane Everitt  |","time":"2017-11-19T08:33:33.307Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"+ ------------------------------------ +","time":"2017-11-19T08:33:33.307Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Loading modules, this could take a few seconds.","time":"2017-11-19T08:33:33.307Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Modules loaded, starting Pterodactyl Daemon...","time":"2017-11-19T08:33:33.470Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Contacting panel to retrieve a list of currrent services available to the node.","time":"2017-11-19T08:33:33.496Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Checking container networking environment...","time":"2017-11-19T08:33:33.497Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Found network interface for daemon: pterodactyl_nw","time":"2017-11-19T08:33:33.503Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Configuring timezone file location...","time":"2017-11-19T08:33:33.503Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Checking pterodactyl0 interface and setting configuration values.","time":"2017-11-19T08:33:33.503Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Checking gateway for pterodactyl0","time":"2017-11-19T08:33:33.503Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Gateway detected as 172.18.0.1 for pterodactyl0.","time":"2017-11-19T08:33:33.509Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Attempting to start SFTP service container...","time":"2017-11-19T08:33:33.515Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"SFTP container successfully booted.","time":"2017-11-19T08:33:33.523Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Checking current files aganist panel response.","time":"2017-11-19T08:33:33.526Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Attempting to load servers and initialize daemon...","time":"2017-11-19T08:33:33.527Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Configuring websocket for daemon stats...","time":"2017-11-19T08:33:33.529Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Pterodactyl Daemon is up-to-date!","time":"2017-11-19T08:33:34.305Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Pterodactyl Daemon is now listening for insecure connections on 0.0.0.0:8080","time":"2017-11-19T08:33:34.308Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"server":"94c42bc8-5858-4bd0-9bf3-b6700f194bde","level":40,"msg":"Container was not found. Attempting to recreate it.","time":"2017-11-19T08:33:46.262Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java, if so it will happen now.","time":"2017-11-19T08:33:46.269Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java ... this could take a few minutes.","time":"2017-11-19T08:33:47.603Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"server":"94c42bc8-5858-4bd0-9bf3-b6700f194bde","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T08:33:47.760Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"server":"94c42bc8-5858-4bd0-9bf3-b6700f194bde","level":40,"msg":"Server booting is now BLOCKED.","time":"2017-11-19T08:33:47.804Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"server":"94c42bc8-5858-4bd0-9bf3-b6700f194bde","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2017-11-19T08:33:47.805Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"server":"94c42bc8-5858-4bd0-9bf3-b6700f194bde","level":30,"msg":"Writing output of installation process to file. { file: '/srv/daemon/config/servers/94c42bc8-5858-4bd0-9bf3-b6700f194bde/install.log' }","time":"2017-11-19T08:33:47.825Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Pulling image alpine:3.4 ... this could take a few minutes.","time":"2017-11-19T08:33:49.031Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"server":"94c42bc8-5858-4bd0-9bf3-b6700f194bde","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2017-11-19T08:33:49.448Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"server":"94c42bc8-5858-4bd0-9bf3-b6700f194bde","level":40,"msg":"Server has been suspended.","time":"2017-11-19T08:33:49.505Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"server":"94c42bc8-5858-4bd0-9bf3-b6700f194bde","level":30,"msg":"Completed installation process for server.","time":"2017-11-19T08:34:01.979Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":60,"msg":"A fatal error was encountered while attempting to create a server. Error: Unable to set ownership of files properly, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:103:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)","time":"2017-11-19T08:34:01.999Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"server":"94c42bc8-5858-4bd0-9bf3-b6700f194bde","level":40,"msg":"No container ID was defined in the server JSON, skipping container deletion step.","time":"2017-11-19T08:34:02.008Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"level":30,"msg":"Notified remote panel of server install status.","time":"2017-11-19T08:34:02.041Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"server":"94c42bc8-5858-4bd0-9bf3-b6700f194bde","level":30,"msg":"Server has been unsuspended.","time":"2017-11-19T08:34:02.087Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":8013,"server":"94c42bc8-5858-4bd0-9bf3-b6700f194bde","level":30,"msg":"Server deleted.","time":"2017-11-19T08:34:02.117Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"+ ------------------------------------ +","time":"2017-11-19T08:50:47.985Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"| Running Pterodactyl Daemon v0.4.5    |","time":"2017-11-19T08:50:47.986Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"|        https://pterodactyl.io        |","time":"2017-11-19T08:50:47.986Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"|  Copyright 2015 - 2017 Dane Everitt  |","time":"2017-11-19T08:50:47.986Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"+ ------------------------------------ +","time":"2017-11-19T08:50:47.986Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Loading modules, this could take a few seconds.","time":"2017-11-19T08:50:47.986Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Modules loaded, starting Pterodactyl Daemon...","time":"2017-11-19T08:50:48.149Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Contacting panel to retrieve a list of currrent services available to the node.","time":"2017-11-19T08:50:48.174Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking container networking environment...","time":"2017-11-19T08:50:48.175Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Found network interface for daemon: pterodactyl_nw","time":"2017-11-19T08:50:48.180Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Configuring timezone file location...","time":"2017-11-19T08:50:48.180Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking pterodactyl0 interface and setting configuration values.","time":"2017-11-19T08:50:48.181Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking gateway for pterodactyl0","time":"2017-11-19T08:50:48.181Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Gateway detected as 172.18.0.1 for pterodactyl0.","time":"2017-11-19T08:50:48.187Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Attempting to start SFTP service container...","time":"2017-11-19T08:50:48.193Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"SFTP container successfully booted.","time":"2017-11-19T08:50:48.200Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking current files aganist panel response.","time":"2017-11-19T08:50:48.981Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Attempting to load servers and initialize daemon...","time":"2017-11-19T08:50:48.983Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Configuring websocket for daemon stats...","time":"2017-11-19T08:50:48.986Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pterodactyl Daemon is up-to-date!","time":"2017-11-19T08:50:48.993Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pterodactyl Daemon is now listening for insecure connections on 0.0.0.0:8080","time":"2017-11-19T08:50:48.995Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":40,"msg":"Container was not found. Attempting to recreate it.","time":"2017-11-19T08:51:12.929Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java, if so it will happen now.","time":"2017-11-19T08:51:12.938Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java ... this could take a few minutes.","time":"2017-11-19T08:51:14.271Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T08:51:14.435Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":40,"msg":"Server booting is now BLOCKED.","time":"2017-11-19T08:51:14.500Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2017-11-19T08:51:14.501Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Writing output of installation process to file. { file: '/srv/daemon/config/servers/cb8bac2f-c6dd-4997-8eeb-bc47a5b57320/install.log' }","time":"2017-11-19T08:51:14.522Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image alpine:3.4 ... this could take a few minutes.","time":"2017-11-19T08:51:15.747Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2017-11-19T08:51:16.309Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":40,"msg":"Server has been suspended.","time":"2017-11-19T08:51:16.357Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Completed installation process for server.","time":"2017-11-19T08:51:22.943Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Server booting is now UNBLOCKED.","time":"2017-11-19T08:51:22.951Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Notified remote panel of server install status.","time":"2017-11-19T08:51:22.982Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T08:51:22.983Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T08:51:22.984Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java, if so it will happen now.","time":"2017-11-19T08:51:22.995Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Server has been unsuspended.","time":"2017-11-19T08:51:22.997Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java ... this could take a few minutes.","time":"2017-11-19T08:51:24.403Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T08:51:24.541Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T08:51:24.541Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Server detected as requiring user interaction, stopping now.","time":"2017-11-19T08:51:29.404Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-11-19T08:51:29.404Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T08:51:29.489Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"cb8bac2f-c6dd-4997-8eeb-bc47a5b57320","level":30,"msg":"Server deleted.","time":"2017-11-19T08:53:01.539Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"msg":"Container was not found. Attempting to recreate it.","time":"2017-11-19T09:02:46.472Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T09:02:46.476Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T09:02:47.855Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T09:02:57.856Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T09:03:01.455Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"msg":"Server booting is now BLOCKED.","time":"2017-11-19T09:03:01.458Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2017-11-19T09:03:01.459Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Writing output of installation process to file. { file: '/srv/daemon/config/servers/7e72e15d-c442-454f-a798-d43b3a3ba0f9/install.log' }","time":"2017-11-19T09:03:01.496Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image alpine:3.4 ... this could take a few minutes.","time":"2017-11-19T09:03:02.784Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2017-11-19T09:03:03.410Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"msg":"Server has been suspended.","time":"2017-11-19T09:03:03.449Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Completed installation process for server.","time":"2017-11-19T09:03:04.157Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server booting is now UNBLOCKED.","time":"2017-11-19T09:03:04.167Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Notified remote panel of server install status.","time":"2017-11-19T09:03:04.213Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T09:03:04.213Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T09:03:04.213Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T09:03:04.221Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server has been unsuspended.","time":"2017-11-19T09:03:04.234Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T09:03:05.626Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T09:03:05.801Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T09:03:05.801Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T09:03:08.335Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"msg":"Server detected as crashed! Attempting server reboot.","time":"2017-11-19T09:03:08.335Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T09:03:08.336Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T09:03:11.278Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"msg":"Server detected as crashed but has crashed within the last 60 seconds, aborting reboot.","time":"2017-11-19T09:03:11.283Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"msg":"Server booting is now BLOCKED.","time":"2017-11-19T09:03:20.337Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2017-11-19T09:03:20.345Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Writing output of installation process to file. { file: '/srv/daemon/config/servers/7e72e15d-c442-454f-a798-d43b3a3ba0f9/install.log' }","time":"2017-11-19T09:03:20.380Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image alpine:3.4 ... this could take a few minutes.","time":"2017-11-19T09:03:21.599Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2017-11-19T09:03:22.033Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"msg":"Server has been suspended.","time":"2017-11-19T09:03:22.082Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Completed installation process for server.","time":"2017-11-19T09:03:24.910Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server booting is now UNBLOCKED.","time":"2017-11-19T09:03:24.926Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Notified remote panel of server install status.","time":"2017-11-19T09:03:24.968Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server has been unsuspended.","time":"2017-11-19T09:03:24.981Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T09:12:02.210Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T09:12:02.211Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T09:12:02.255Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T09:12:03.700Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T09:12:04.022Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T09:12:04.022Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-11-19T09:12:37.577Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T09:12:53.191Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T09:14:28.844Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T09:14:37.146Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"msg":"Container was not found. Attempting to recreate it.","time":"2017-11-19T09:15:52.944Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T09:15:52.947Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T09:15:54.358Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T09:15:54.505Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"msg":"Server booting is now BLOCKED.","time":"2017-11-19T09:15:54.507Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2017-11-19T09:15:54.508Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Writing output of installation process to file. { file: '/srv/daemon/config/servers/0f58ea08-7cc0-4c56-a167-f97219ce1f4a/install.log' }","time":"2017-11-19T09:15:54.562Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image alpine:3.4 ... this could take a few minutes.","time":"2017-11-19T09:15:55.765Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2017-11-19T09:15:56.171Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"msg":"Server has been suspended.","time":"2017-11-19T09:15:56.261Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Completed installation process for server.","time":"2017-11-19T09:15:56.819Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server booting is now UNBLOCKED.","time":"2017-11-19T09:15:56.826Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Notified remote panel of server install status.","time":"2017-11-19T09:15:56.869Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T09:15:56.869Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T09:15:56.869Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T09:15:56.877Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server has been unsuspended.","time":"2017-11-19T09:15:56.890Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T09:15:58.200Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T09:15:58.359Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T09:15:58.360Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T09:16:00.979Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"msg":"Server detected as crashed! Attempting server reboot.","time":"2017-11-19T09:16:00.979Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T09:16:00.979Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T09:16:03.830Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"msg":"Server detected as crashed but has crashed within the last 60 seconds, aborting reboot.","time":"2017-11-19T09:16:03.831Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T09:50:32.076Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T09:51:32.957Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-11-19T09:53:40.811Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T09:53:41.772Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T09:53:41.772Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T09:53:56.171Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-11-19T09:59:51.554Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T09:59:54.776Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T09:59:54.779Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T10:00:03.950Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"msg":"Container was not found. Attempting to recreate it.","time":"2017-11-19T10:05:24.232Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T10:05:24.232Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T10:05:25.535Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T10:05:25.715Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"msg":"Server booting is now BLOCKED.","time":"2017-11-19T10:05:25.718Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2017-11-19T10:05:25.718Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Writing output of installation process to file. { file: '/srv/daemon/config/servers/dcbeba66-5906-480d-a6d4-a8b50c74aaeb/install.log' }","time":"2017-11-19T10:05:25.751Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image alpine:3.4 ... this could take a few minutes.","time":"2017-11-19T10:05:26.939Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2017-11-19T10:05:27.484Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"msg":"Server has been suspended.","time":"2017-11-19T10:05:27.547Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Completed installation process for server.","time":"2017-11-19T10:05:28.228Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server booting is now UNBLOCKED.","time":"2017-11-19T10:05:28.236Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Notified remote panel of server install status.","time":"2017-11-19T10:05:28.286Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T10:05:28.286Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T10:05:28.286Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T10:05:28.297Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server has been unsuspended.","time":"2017-11-19T10:05:28.301Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T10:05:29.609Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T10:05:29.791Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T10:05:29.792Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T10:05:32.398Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"msg":"Server detected as crashed! Attempting server reboot.","time":"2017-11-19T10:05:32.398Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T10:05:32.399Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T10:05:35.273Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"msg":"Server detected as crashed but has crashed within the last 60 seconds, aborting reboot.","time":"2017-11-19T10:05:35.273Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T10:11:12.804Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T10:13:58.551Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"msg":"Container was not found. Attempting to recreate it.","time":"2017-11-19T10:22:20.714Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T10:22:20.714Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T10:22:22.076Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T10:22:22.206Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"msg":"Server booting is now BLOCKED.","time":"2017-11-19T10:22:22.206Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2017-11-19T10:22:22.206Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Writing output of installation process to file. { file: '/srv/daemon/config/servers/d94b1633-b9ad-4443-bfe5-1c59ce7790ab/install.log' }","time":"2017-11-19T10:22:22.230Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image alpine:3.4 ... this could take a few minutes.","time":"2017-11-19T10:22:23.435Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2017-11-19T10:22:23.833Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"msg":"Server has been suspended.","time":"2017-11-19T10:22:23.877Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Completed installation process for server.","time":"2017-11-19T10:22:24.426Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server booting is now UNBLOCKED.","time":"2017-11-19T10:22:24.430Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Notified remote panel of server install status.","time":"2017-11-19T10:22:24.450Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T10:22:24.450Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T10:22:24.451Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T10:22:24.465Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server has been unsuspended.","time":"2017-11-19T10:22:24.467Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T10:22:25.895Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T10:22:26.037Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T10:22:26.038Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T10:22:28.432Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"msg":"Server detected as crashed! Attempting server reboot.","time":"2017-11-19T10:22:28.432Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T10:22:28.432Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T10:22:31.072Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"msg":"Server detected as crashed but has crashed within the last 60 seconds, aborting reboot.","time":"2017-11-19T10:22:31.072Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T10:26:00.706Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T10:28:54.590Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-11-19T10:36:44.230Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T10:36:47.362Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T10:36:47.362Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T10:36:47.363Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T10:36:47.653Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T10:36:49.049Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T10:36:49.328Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T10:36:49.329Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T10:36:57.428Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-11-19T10:37:02.801Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T10:37:09.598Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T10:37:09.598Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T10:37:09.598Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T10:37:10.015Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T10:37:11.504Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T10:37:11.793Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T10:37:11.794Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-11-19T10:37:15.642Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T10:37:19.197Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T10:37:19.197Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T10:37:19.197Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T10:37:19.520Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T10:37:20.846Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T10:37:21.091Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T10:37:21.092Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T10:40:20.982Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T10:40:30.059Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"msg":"Container was not found. Attempting to recreate it.","time":"2017-11-19T16:36:28.173Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T16:36:28.175Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T16:36:29.548Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T16:36:29.783Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"msg":"Server booting is now BLOCKED.","time":"2017-11-19T16:36:29.788Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2017-11-19T16:36:29.788Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Writing output of installation process to file. { file: '/srv/daemon/config/servers/e17db36c-a4f4-4647-bfca-217372d26821/install.log' }","time":"2017-11-19T16:36:29.831Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image alpine:3.4 ... this could take a few minutes.","time":"2017-11-19T16:36:31.001Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2017-11-19T16:36:31.411Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"msg":"Server has been suspended.","time":"2017-11-19T16:36:31.474Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Completed installation process for server.","time":"2017-11-19T16:36:32.099Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server booting is now UNBLOCKED.","time":"2017-11-19T16:36:32.104Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Notified remote panel of server install status.","time":"2017-11-19T16:36:32.140Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T16:36:32.141Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T16:36:32.141Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server has been unsuspended.","time":"2017-11-19T16:36:32.162Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T16:36:32.167Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T16:36:33.586Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T16:36:33.889Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T16:36:33.889Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T16:36:36.312Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"msg":"Server detected as crashed! Attempting server reboot.","time":"2017-11-19T16:36:36.312Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T16:36:36.313Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T16:36:39.061Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"msg":"Server detected as crashed but has crashed within the last 60 seconds, aborting reboot.","time":"2017-11-19T16:36:39.063Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T16:43:34.821Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T16:44:23.480Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"msg":"Server detected as crashed! Attempting server reboot.","time":"2017-11-19T16:44:23.481Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T16:44:23.481Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-11-19T16:44:40.976Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T16:44:41.067Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T16:45:20.627Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T16:47:25.370Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-11-19T16:56:34.427Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T16:56:37.564Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T16:56:37.564Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":60,"err":{"message":"Cannot read property 'length' of undefined","name":"TypeError","stack":"TypeError: Cannot read property 'length' of undefined\n    at Timeout.process [as _onTimeout] (/srv/daemon/src/controllers/server.js:491:85)\n    at ontimeout (timers.js:390:15)\n    at tryOnTimeout (timers.js:250:5)\n    at Timer.listOnTimeout (timers.js:214:5)"},"msg":"A fatal error occured during an operation.","time":"2017-11-19T16:56:39.569Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T16:56:47.445Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T16:59:12.902Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T16:59:20.675Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Container was not found. Attempting to recreate it.","time":"2017-11-19T16:59:21.641Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T16:59:21.642Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T16:59:22.227Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T16:59:23.231Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T16:59:23.502Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server booting is now BLOCKED.","time":"2017-11-19T16:59:23.502Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2017-11-19T16:59:23.503Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Writing output of installation process to file. { file: '/srv/daemon/config/servers/abf3f279-4374-482c-9ead-f36da969e027/install.log' }","time":"2017-11-19T16:59:23.527Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image alpine:3.4 ... this could take a few minutes.","time":"2017-11-19T16:59:24.755Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2017-11-19T16:59:25.232Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server has been suspended.","time":"2017-11-19T16:59:25.289Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Completed installation process for server.","time":"2017-11-19T16:59:25.863Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server booting is now UNBLOCKED.","time":"2017-11-19T16:59:25.866Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Notified remote panel of server install status.","time":"2017-11-19T16:59:25.903Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T16:59:25.903Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T16:59:25.904Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server has been unsuspended.","time":"2017-11-19T16:59:25.925Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T16:59:25.931Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T16:59:27.297Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T16:59:27.591Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T16:59:27.591Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T16:59:30.063Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server detected as crashed! Attempting server reboot.","time":"2017-11-19T16:59:30.063Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T16:59:30.063Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T16:59:32.747Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server detected as crashed but has crashed within the last 60 seconds, aborting reboot.","time":"2017-11-19T16:59:32.748Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T16:59:37.573Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T16:59:43.070Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:00:12.904Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:00:20.679Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:00:22.230Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:00:37.574Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:00:43.073Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:01:12.907Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:01:20.682Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:01:22.233Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:01:37.576Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:01:43.077Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:02:12.910Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:02:20.685Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:02:22.236Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:02:37.580Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:02:43.079Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:03:12.911Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:03:20.688Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:03:22.239Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:03:37.581Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:03:43.081Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:03:56.768Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:03:59.245Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server detected as crashed! Attempting server reboot.","time":"2017-11-19T17:03:59.245Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:03:59.246Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:04:03.336Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server detected as crashed but has crashed within the last 60 seconds, aborting reboot.","time":"2017-11-19T17:04:03.336Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:04:12.914Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:04:20.691Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:04:22.242Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:04:37.584Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:04:43.084Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:05:12.917Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:05:16.126Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:05:18.588Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server detected as crashed! Attempting server reboot.","time":"2017-11-19T17:05:18.589Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:05:18.589Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:05:20.694Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:05:21.390Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server detected as crashed but has crashed within the last 60 seconds, aborting reboot.","time":"2017-11-19T17:05:21.390Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:05:22.244Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:05:37.587Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:05:43.086Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:06:12.920Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:06:20.697Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:06:22.247Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:06:37.590Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:06:43.089Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:07:12.923Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:07:20.703Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:07:22.251Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:07:37.593Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:07:43.091Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:08:12.925Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:08:20.703Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:08:22.256Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:08:37.595Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:08:43.095Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:09:12.927Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:09:20.708Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:09:22.259Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:09:37.599Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:09:43.098Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:10:12.930Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:10:20.710Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:10:22.262Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:10:37.601Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:10:43.101Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:11:12.933Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:11:20.712Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:11:22.265Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:11:37.603Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:11:43.110Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:12:12.935Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:12:20.715Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:12:22.268Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server booting is now BLOCKED.","time":"2017-11-19T17:12:23.193Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2017-11-19T17:12:23.195Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Writing output of installation process to file. { file: '/srv/daemon/config/servers/abf3f279-4374-482c-9ead-f36da969e027/install.log' }","time":"2017-11-19T17:12:23.218Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image alpine:3.4 ... this could take a few minutes.","time":"2017-11-19T17:12:24.385Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2017-11-19T17:12:24.791Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server has been suspended.","time":"2017-11-19T17:12:24.853Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Completed installation process for server.","time":"2017-11-19T17:12:26.657Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server booting is now UNBLOCKED.","time":"2017-11-19T17:12:26.661Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server has been unsuspended.","time":"2017-11-19T17:12:26.767Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Notified remote panel of server install status.","time":"2017-11-19T17:12:26.786Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:12:37.606Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:12:41.694Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:12:41.695Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T17:12:41.716Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T17:12:43.041Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:12:43.111Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T17:12:43.322Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:12:43.322Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-11-19T17:12:47.083Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:12:47.148Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:13:12.938Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:13:20.717Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:13:22.271Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:13:35.837Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:13:37.610Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:13:38.744Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server detected as crashed! Attempting server reboot.","time":"2017-11-19T17:13:38.745Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:13:38.745Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:13:41.574Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server detected as crashed but has crashed within the last 60 seconds, aborting reboot.","time":"2017-11-19T17:13:41.574Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:13:43.114Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:14:12.941Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:14:20.721Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:14:22.273Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:14:37.612Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:14:43.117Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:15:12.944Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:15:20.725Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:15:22.276Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:15:37.615Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:15:43.119Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:16:12.947Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:16:20.727Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:16:22.279Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:16:37.619Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:16:43.122Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:17:12.950Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:17:20.728Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:17:22.282Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:17:37.622Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:17:43.125Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:17:58.948Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:18:01.486Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server detected as crashed! Attempting server reboot.","time":"2017-11-19T17:18:01.486Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:18:01.486Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-11-19T17:18:04.077Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:18:04.339Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:18:12.953Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:18:20.732Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:18:22.286Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:18:37.625Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:18:43.128Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:19:12.956Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:19:20.736Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:19:22.290Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:19:37.628Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:19:43.130Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:20:12.959Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:20:16.745Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:20:19.304Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server detected as crashed! Attempting server reboot.","time":"2017-11-19T17:20:19.304Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:20:19.304Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:20:20.738Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-11-19T17:20:21.256Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:20:21.344Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:20:22.292Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:20:37.633Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:20:43.133Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server booting is now BLOCKED.","time":"2017-11-19T17:20:45.428Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2017-11-19T17:20:45.430Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Writing output of installation process to file. { file: '/srv/daemon/config/servers/abf3f279-4374-482c-9ead-f36da969e027/install.log' }","time":"2017-11-19T17:20:45.457Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image alpine:3.4 ... this could take a few minutes.","time":"2017-11-19T17:20:46.725Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2017-11-19T17:20:47.157Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server has been suspended.","time":"2017-11-19T17:20:47.218Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Completed installation process for server.","time":"2017-11-19T17:20:47.775Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server booting is now UNBLOCKED.","time":"2017-11-19T17:20:47.780Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Notified remote panel of server install status.","time":"2017-11-19T17:20:47.820Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server has been unsuspended.","time":"2017-11-19T17:20:47.838Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:20:57.605Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:20:57.605Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:java-glibc, if so it will happen now.","time":"2017-11-19T17:20:57.623Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:java-glibc ... this could take a few minutes.","time":"2017-11-19T17:20:58.959Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T17:20:59.239Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:20:59.239Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:21:01.799Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server detected as crashed but has crashed within the last 60 seconds, aborting reboot.","time":"2017-11-19T17:21:01.799Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:21:12.961Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:21:20.740Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:21:22.294Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:21:37.636Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:21:43.135Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:22:08.536Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:22:11.083Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server detected as crashed! Attempting server reboot.","time":"2017-11-19T17:22:11.083Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:22:11.084Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:22:12.965Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:22:13.903Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"abf3f279-4374-482c-9ead-f36da969e027","level":40,"msg":"Server detected as crashed but has crashed within the last 60 seconds, aborting reboot.","time":"2017-11-19T17:22:13.903Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:22:20.743Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:22:22.297Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:22:37.639Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:22:43.137Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:23:12.966Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:23:20.744Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:23:22.300Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:23:37.642Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:23:43.140Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:24:12.970Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:24:20.747Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:24:22.303Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:24:37.645Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:24:43.143Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:25:12.973Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:25:20.751Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:25:22.305Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:25:37.649Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:25:43.146Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:26:12.976Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:26:20.754Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:26:22.308Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:26:37.653Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:26:43.149Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:27:12.979Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:27:20.757Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:27:22.310Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:27:37.656Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:27:43.153Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:28:12.981Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:28:20.761Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:28:22.313Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:28:37.659Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:28:43.154Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":40,"msg":"Container was not found. Attempting to recreate it.","time":"2017-11-19T17:28:59.261Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:mono, if so it will happen now.","time":"2017-11-19T17:28:59.262Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:mono ... this could take a few minutes.","time":"2017-11-19T17:29:00.630Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:mono ... this could take a few minutes.","time":"2017-11-19T17:29:10.631Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T17:29:12.752Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":40,"msg":"Server booting is now BLOCKED.","time":"2017-11-19T17:29:12.755Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Blocking server boot until option installation process is completed.","time":"2017-11-19T17:29:12.755Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Writing output of installation process to file. { file: '/srv/daemon/config/servers/2bd36991-8eeb-4df6-bd5c-427ca99b478e/install.log' }","time":"2017-11-19T17:29:12.783Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:29:12.984Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image alpine:3.4 ... this could take a few minutes.","time":"2017-11-19T17:29:14.027Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Temporarily suspending server to avoid mishaps...","time":"2017-11-19T17:29:14.431Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":40,"msg":"Server has been suspended.","time":"2017-11-19T17:29:14.486Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Completed installation process for server.","time":"2017-11-19T17:29:20.538Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Server booting is now UNBLOCKED.","time":"2017-11-19T17:29:20.541Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Notified remote panel of server install status.","time":"2017-11-19T17:29:20.622Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:29:20.622Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:29:20.622Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Server has been unsuspended.","time":"2017-11-19T17:29:20.641Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:mono, if so it will happen now.","time":"2017-11-19T17:29:20.682Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:29:20.763Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:29:22.317Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:mono ... this could take a few minutes.","time":"2017-11-19T17:29:22.521Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T17:29:22.738Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T17:29:22.738Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:29:37.662Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:29:43.157Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:30:12.986Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:30:20.765Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:30:22.321Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-11-19T17:30:33.941Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T17:30:34.038Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:30:37.664Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:30:43.159Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:31:12.988Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:31:20.767Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:31:22.324Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:31:37.667Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:31:43.163Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:32:12.991Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:32:20.770Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:32:22.328Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:32:37.670Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:32:43.165Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:33:12.994Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:33:20.773Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:33:22.331Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:33:37.674Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:33:43.168Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:34:12.996Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:34:20.775Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:34:22.333Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:34:37.678Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:34:43.171Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:35:12.999Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:35:20.779Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:35:22.337Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:35:37.681Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:35:43.174Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:36:13.002Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:36:20.782Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:36:22.340Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:36:37.684Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:36:43.177Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:37:13.005Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:37:20.786Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:37:22.343Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:37:37.686Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:37:43.180Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:38:13.008Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:38:20.788Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:38:22.348Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:38:37.689Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:38:43.184Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:39:13.011Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:39:20.791Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:39:22.351Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:39:37.692Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:39:43.187Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:40:13.015Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:40:20.794Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:40:22.356Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:40:37.696Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:40:43.191Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:41:13.019Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:41:20.797Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:41:22.359Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:41:37.699Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:41:43.196Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:42:13.022Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:42:20.800Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:42:22.363Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:42:37.704Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:42:43.200Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:43:13.025Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:43:20.804Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:43:22.367Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:43:37.705Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:43:43.203Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:44:13.029Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:44:20.806Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:44:22.370Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:44:37.708Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:44:43.206Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:45:13.032Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:45:20.809Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:45:22.372Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:45:37.712Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:45:43.209Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:46:13.035Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:46:20.811Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:46:22.374Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:46:37.713Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:46:43.212Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:47:13.039Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:47:20.814Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:47:22.377Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:47:37.717Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:47:43.216Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:48:13.041Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:48:20.817Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:48:22.381Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:48:37.719Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:48:43.219Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:49:13.044Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:49:20.821Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:49:22.383Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:49:37.724Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:49:43.222Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:50:13.047Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:50:20.824Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:50:22.386Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:50:37.726Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:50:43.225Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:51:13.050Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:51:20.827Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:51:22.388Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:51:37.729Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:51:43.228Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:52:13.053Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:52:20.830Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:52:22.391Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:52:37.732Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:52:43.232Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:53:13.056Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:53:20.833Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:53:22.394Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:53:37.735Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:53:43.234Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:54:13.059Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:54:20.837Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:54:22.396Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:54:37.738Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:54:43.238Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:55:13.062Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:55:20.840Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:55:22.402Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:55:37.739Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:55:43.241Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:56:13.065Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:56:20.843Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:56:22.404Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:56:37.743Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:56:43.244Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:57:13.067Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:57:20.846Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:57:22.407Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:57:37.744Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:57:43.249Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:58:13.069Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:58:20.848Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:58:22.410Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:58:37.747Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:58:43.251Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:59:13.072Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:59:20.850Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:59:22.413Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:59:37.750Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T17:59:43.255Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:00:13.076Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:00:20.853Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:00:22.415Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:00:37.753Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:00:43.257Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:01:13.081Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:01:20.855Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:01:22.420Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:01:37.757Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:01:43.262Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:02:13.086Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:02:20.859Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:02:22.425Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:02:37.761Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:02:43.267Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:03:13.089Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:03:20.863Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:03:22.428Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:03:37.766Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:03:43.270Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:04:13.093Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:04:20.868Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:04:22.433Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:04:37.770Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:04:43.277Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:05:13.097Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:05:20.871Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:05:22.439Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:05:37.774Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T18:05:42.099Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T18:05:42.099Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Checking if we need to update image quay.io/pterodactyl/core:mono, if so it will happen now.","time":"2017-11-19T18:05:42.122Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:05:43.283Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"level":30,"msg":"Pulling image quay.io/pterodactyl/core:mono ... this could take a few minutes.","time":"2017-11-19T18:05:43.448Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Completed rebuild process for server container.","time":"2017-11-19T18:05:43.689Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Server status has been changed to STARTING","time":"2017-11-19T18:05:43.689Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-11-19T18:05:46.268Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"2bd36991-8eeb-4df6-bd5c-427ca99b478e","level":30,"msg":"Server status has been changed to OFF","time":"2017-11-19T18:05:46.334Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:06:13.103Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:06:20.876Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:06:22.442Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:06:37.778Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:06:43.285Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:07:13.107Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:07:20.879Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:07:22.447Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:07:37.784Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:07:43.291Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:08:13.113Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:08:20.883Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:08:22.452Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:08:37.788Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:08:43.294Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:09:13.117Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:09:20.892Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:09:22.466Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:09:37.792Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:09:43.298Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:10:13.121Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:10:20.898Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:10:22.470Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:10:37.796Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:10:43.302Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:11:13.127Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:11:20.902Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:11:22.476Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:11:37.801Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:11:43.307Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:12:13.133Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:12:20.908Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:12:22.482Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:12:37.807Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:12:43.313Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:13:13.137Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:13:20.914Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:13:22.487Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:13:37.812Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:13:43.318Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:14:13.143Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:14:20.917Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:14:22.492Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:14:37.815Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:14:43.322Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:15:13.148Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:15:20.922Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:15:22.499Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:15:37.820Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:15:43.328Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:16:13.155Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:16:20.926Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:16:22.504Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:16:37.826Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:16:43.332Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:17:13.160Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:17:20.931Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:17:22.508Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:17:37.831Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:17:43.336Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:18:13.164Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:18:20.938Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:18:22.514Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:18:37.838Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:18:43.343Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:19:13.171Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:19:20.949Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:19:22.519Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:19:37.843Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:19:43.347Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:20:13.175Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:20:20.953Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:20:22.524Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:20:37.850Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:20:43.352Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:21:13.180Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:21:20.956Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:21:22.528Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:21:37.854Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:21:43.358Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:22:13.185Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:22:20.961Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:22:22.534Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:22:37.858Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:22:43.364Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:23:13.189Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:23:20.965Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:23:22.538Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:23:37.863Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:23:43.369Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:24:13.193Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:24:20.971Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:24:22.543Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:24:37.867Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:24:43.373Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:25:13.198Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:25:20.977Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:25:22.547Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:25:37.872Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:25:43.379Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:26:13.202Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:26:20.980Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:26:22.552Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:26:37.878Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:26:43.385Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:27:13.207Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:27:20.985Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:27:22.557Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:27:37.882Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:27:43.390Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:28:13.214Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:28:20.990Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:28:22.561Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:28:37.889Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:28:43.397Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:29:13.219Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:29:20.994Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:29:22.565Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:29:37.894Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:29:43.401Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:30:13.224Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:30:20.999Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:30:22.571Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:30:37.900Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:30:43.407Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:31:13.229Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:31:21.004Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:31:22.576Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:31:37.905Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:31:43.412Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:32:13.234Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:32:21.010Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:32:22.579Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:32:37.910Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:32:43.418Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:33:13.239Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:33:21.015Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:33:22.584Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:33:37.915Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:33:43.424Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:34:13.245Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:34:21.020Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:34:22.589Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:34:37.920Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:34:43.431Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:35:13.249Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:35:21.025Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:35:22.595Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:35:37.927Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:35:43.436Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:36:13.253Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:36:21.031Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:36:22.600Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:36:37.931Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:36:43.440Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:37:13.260Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:37:21.038Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:37:22.605Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:37:37.937Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:37:43.445Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:38:13.264Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:38:21.045Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:38:22.610Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:38:37.944Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:38:43.452Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:39:13.271Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:39:21.050Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:39:22.616Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:39:37.950Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:39:43.458Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:40:13.278Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:40:21.057Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:40:22.622Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:40:37.957Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:40:43.464Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:41:13.283Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:41:21.062Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:41:22.628Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:41:37.964Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:41:43.470Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:42:13.290Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:42:21.068Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:42:22.635Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:42:37.970Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:42:43.476Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:43:13.296Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:43:21.076Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:43:22.643Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:43:37.978Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:43:43.482Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:44:13.301Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:44:21.081Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:44:22.648Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:44:37.985Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:44:43.487Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:45:13.307Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:45:21.087Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:45:22.655Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:45:37.992Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:45:43.493Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:46:13.312Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:46:21.093Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:46:22.662Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:46:38.000Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:46:43.499Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:47:13.317Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:47:21.100Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:47:22.668Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:47:38.004Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:47:43.505Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:48:13.324Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:48:21.106Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:48:22.674Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:48:38.010Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:48:43.509Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:49:13.331Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:49:21.112Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:49:22.679Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:49:38.016Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:49:43.520Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:50:13.337Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:50:21.118Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:50:22.685Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:50:38.022Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:50:43.525Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:51:13.341Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:51:21.126Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:51:22.691Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:51:38.028Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:51:43.530Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:52:13.349Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:52:21.131Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:52:22.697Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:52:38.032Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:52:43.537Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:53:13.356Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:53:21.138Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:53:22.703Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:53:38.039Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:53:43.543Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:54:13.362Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:54:21.144Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:54:22.709Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:54:38.045Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:54:43.548Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:55:13.369Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:55:21.150Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:55:22.715Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:55:38.051Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:55:43.552Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:56:13.375Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:56:21.155Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:56:22.719Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:56:38.055Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:56:43.557Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:57:13.381Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:57:21.160Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:57:22.724Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:57:38.060Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:57:43.563Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:58:13.387Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:58:21.167Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:58:22.730Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:58:38.065Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:58:43.567Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:59:13.393Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:59:21.172Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:59:22.737Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:59:38.071Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T18:59:43.573Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:00:13.396Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:00:21.179Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:00:22.742Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:00:38.077Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:00:43.577Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:01:13.401Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:01:21.184Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:01:22.747Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:01:38.083Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:01:43.584Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:02:13.406Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:02:21.191Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:02:22.750Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:02:38.090Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:02:43.590Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:03:13.412Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:03:21.196Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:03:22.755Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:03:38.094Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:03:43.595Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:04:13.420Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:04:21.200Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:04:22.760Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:04:38.100Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:04:43.601Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:05:13.425Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:05:21.205Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:05:22.766Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:05:38.105Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:05:43.613Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:06:13.428Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:06:21.210Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:06:22.771Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:06:38.110Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:06:43.617Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:07:13.434Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:07:21.216Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:07:22.777Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:07:38.116Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:07:43.623Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:08:13.439Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:08:21.222Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:08:22.780Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:08:38.119Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:08:43.629Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:09:13.442Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:09:21.227Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:09:22.785Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:09:38.124Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:09:43.634Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:10:13.446Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:10:21.233Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:10:22.788Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:10:38.130Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:10:43.638Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:11:13.451Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:11:21.236Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:11:22.793Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:11:38.134Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:11:43.644Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:12:13.456Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:12:21.241Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:12:22.798Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:12:38.139Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:12:43.649Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:13:13.460Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:13:21.247Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:13:22.802Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:13:38.146Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:13:43.674Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:14:13.464Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:14:21.255Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:14:22.806Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:14:38.150Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:14:43.659Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:15:13.468Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:15:21.263Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:15:22.812Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:15:38.155Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:15:43.665Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:16:13.473Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:16:21.267Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:16:22.816Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:16:38.161Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:16:43.670Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:17:13.477Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:17:21.271Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:17:22.821Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:17:38.167Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:17:43.676Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:18:13.483Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:18:21.275Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:18:22.824Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:18:38.172Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:18:43.679Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:19:13.488Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:19:21.281Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:19:22.827Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:19:38.176Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:19:43.686Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:20:13.493Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:20:21.286Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:20:22.833Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:20:38.182Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:20:43.690Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:21:13.497Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:21:21.291Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:21:22.839Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:21:38.187Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:21:43.695Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:22:13.501Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:22:21.294Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:22:22.842Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:22:38.193Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:22:43.700Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:23:13.505Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:23:21.298Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:23:22.847Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:23:38.198Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:23:43.705Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:24:13.512Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:24:21.302Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:24:22.852Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:24:38.204Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:24:43.709Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:25:13.516Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:25:21.308Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:25:22.858Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:25:38.207Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:25:43.712Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:26:13.521Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:26:21.313Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:26:22.863Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:26:38.212Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:26:43.717Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:27:13.528Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:27:21.318Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:27:22.867Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:27:38.216Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:27:43.722Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:28:13.534Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:28:21.322Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:28:22.872Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:28:38.222Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:28:43.727Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:29:13.538Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:29:21.327Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:29:22.875Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:29:38.227Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:29:43.732Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:30:13.543Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:30:21.331Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:30:22.880Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:30:38.238Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:30:43.737Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:31:13.548Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:31:21.335Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:31:22.886Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:31:38.242Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:31:43.741Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:32:13.552Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:32:21.341Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:32:22.892Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:32:38.247Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:32:43.746Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:33:13.557Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:33:21.345Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:33:22.898Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:33:38.253Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:33:43.750Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:34:13.561Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:34:21.348Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:34:22.901Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:34:38.257Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:34:43.754Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:35:13.566Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:35:21.353Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:35:22.904Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:35:38.261Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:35:43.759Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:36:13.570Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:36:21.358Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:36:22.909Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:36:38.265Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:36:43.763Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:37:13.574Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:37:21.363Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:37:22.915Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:37:38.270Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:37:43.767Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:38:13.579Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:38:21.368Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:38:22.919Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:38:38.274Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:38:43.772Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:39:13.583Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:39:21.372Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:39:22.923Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:39:38.279Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:39:43.777Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:40:13.591Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:40:21.378Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:40:22.929Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:40:38.283Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:40:43.782Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:41:13.596Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:41:21.381Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:41:22.935Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:41:38.290Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:41:43.787Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:42:13.601Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:42:21.385Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:42:22.940Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:42:38.295Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:42:43.793Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:43:13.606Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:43:21.391Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:43:22.945Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:43:38.300Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:43:43.795Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:44:13.610Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:44:21.394Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:44:22.950Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:44:38.305Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:44:43.799Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:45:13.615Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:45:21.399Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:45:22.955Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:45:38.309Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:45:43.804Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:46:13.620Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:46:21.403Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:46:22.959Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:46:38.314Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:46:43.808Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:47:13.625Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:47:21.408Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:47:22.963Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:47:38.317Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:47:43.813Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:48:13.630Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:48:21.414Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:48:22.968Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:48:38.322Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:48:43.817Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:49:13.633Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:49:21.418Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:49:22.973Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:49:38.326Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:49:43.821Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:50:13.637Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:50:21.424Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:50:22.977Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:50:38.330Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:50:43.825Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:51:13.641Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:51:21.430Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:51:22.981Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:51:38.334Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:51:43.828Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:52:13.645Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:52:21.434Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:52:22.987Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:52:38.339Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:52:43.834Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:53:13.651Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:53:21.439Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:53:22.992Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:53:38.343Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:53:43.840Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:54:13.656Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:54:21.443Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:54:22.996Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:54:38.347Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:54:43.843Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:55:13.661Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:55:21.448Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:55:23.000Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:55:38.353Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:55:43.847Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:56:13.665Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:56:21.451Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:56:23.003Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:56:38.356Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:56:43.852Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:57:13.671Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:57:21.456Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:57:23.007Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:57:38.360Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:57:43.857Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:58:13.676Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:58:21.460Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:58:23.011Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:58:38.364Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:58:43.861Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:59:13.681Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:59:21.467Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:59:23.018Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:59:38.367Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T19:59:43.866Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:00:13.687Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:00:21.473Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:00:23.021Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:00:38.371Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:00:43.869Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:01:13.692Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:01:21.479Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:01:23.025Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:01:38.376Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:01:43.872Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:02:13.699Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:02:21.486Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:02:23.029Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:02:38.380Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:02:43.877Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:03:13.703Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:03:21.491Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:03:23.032Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:03:38.384Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:03:43.882Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:04:13.709Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:04:21.497Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:04:23.038Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:04:38.388Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:04:43.890Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:05:13.714Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:05:21.503Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:05:23.041Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:05:38.393Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:05:43.893Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:06:13.720Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:06:21.507Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:06:23.047Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:06:38.398Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:06:43.897Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:07:13.726Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:07:21.512Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:07:23.052Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:07:38.403Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:07:43.904Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:08:13.732Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:08:21.519Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:08:23.056Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:08:38.408Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:08:43.911Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:09:13.737Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:09:21.522Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:09:23.062Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:09:38.414Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:09:43.915Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:10:13.742Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:10:21.526Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:10:23.066Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:10:38.419Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:10:43.921Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:11:13.749Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:11:21.530Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:11:23.070Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:11:38.426Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:11:43.927Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:12:13.754Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:12:21.536Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:12:23.074Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:12:38.431Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:12:43.934Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:13:13.758Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:13:21.542Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:13:23.079Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:13:38.434Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:13:43.939Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:14:13.762Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:14:21.553Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:14:23.084Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:14:38.440Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:14:43.945Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:15:13.770Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:15:21.553Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:15:23.090Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:15:38.446Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:15:43.951Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:16:13.777Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:16:21.557Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:16:23.099Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:16:38.453Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:16:43.957Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:17:13.782Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:17:21.563Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:17:23.101Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:17:38.458Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:17:43.962Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:18:13.788Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:18:21.569Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:18:23.106Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:18:38.463Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:18:43.966Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:19:13.792Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:19:21.574Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:19:23.113Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:19:38.470Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:19:43.973Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:20:13.799Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:20:21.580Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:20:23.118Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:20:38.475Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:20:43.977Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:21:13.804Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:21:21.587Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:21:23.125Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:21:38.480Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:21:43.983Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:22:13.810Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:22:21.590Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:22:23.131Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:22:38.486Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:22:43.987Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:23:13.815Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:23:21.597Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:23:23.136Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:23:38.492Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:23:43.993Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:24:13.822Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:24:21.602Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:24:23.140Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:24:38.496Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:24:43.998Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:25:13.827Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:25:21.609Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:25:23.146Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:25:38.502Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:25:44.003Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:26:13.832Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:26:21.613Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:26:23.149Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:26:38.507Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:26:44.008Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:27:13.837Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:27:21.619Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:27:23.153Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:27:38.512Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:27:44.011Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:28:13.843Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:28:21.625Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:28:23.159Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:28:38.517Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:28:44.016Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:29:13.847Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:29:21.629Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:29:23.165Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:29:38.522Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:29:44.020Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:30:13.851Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:30:21.636Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:30:23.172Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:30:38.527Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:30:44.026Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:31:13.856Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:31:21.641Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:31:23.176Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:31:38.533Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:31:44.032Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:32:13.862Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:32:21.646Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:32:23.181Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:32:38.539Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:32:44.038Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:33:13.867Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:33:21.650Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:33:23.188Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:33:38.545Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:33:44.043Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:34:13.873Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:34:21.656Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:34:23.193Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:34:38.551Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:34:44.047Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:35:13.878Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:35:21.661Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:35:23.198Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:35:38.558Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:35:44.051Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:36:13.883Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:36:21.667Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:36:23.206Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":9289,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:36:38.563Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"+ ------------------------------------ +","time":"2017-11-19T20:36:39.645Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"| Running Pterodactyl Daemon v0.4.5    |","time":"2017-11-19T20:36:39.647Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"|        https://pterodactyl.io        |","time":"2017-11-19T20:36:39.647Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"|  Copyright 2015 - 2017 Dane Everitt  |","time":"2017-11-19T20:36:39.647Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"+ ------------------------------------ +","time":"2017-11-19T20:36:39.647Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Loading modules, this could take a few seconds.","time":"2017-11-19T20:36:39.647Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Modules loaded, starting Pterodactyl Daemon...","time":"2017-11-19T20:36:39.975Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Contacting panel to retrieve a list of currrent services available to the node.","time":"2017-11-19T20:36:40.010Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Checking container networking environment...","time":"2017-11-19T20:36:40.011Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Found network interface for daemon: pterodactyl_nw","time":"2017-11-19T20:36:40.018Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Configuring timezone file location...","time":"2017-11-19T20:36:40.018Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Checking pterodactyl0 interface and setting configuration values.","time":"2017-11-19T20:36:40.019Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Checking gateway for pterodactyl0","time":"2017-11-19T20:36:40.019Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Gateway detected as 172.18.0.1 for pterodactyl0.","time":"2017-11-19T20:36:40.028Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Attempting to start SFTP service container...","time":"2017-11-19T20:36:40.035Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Checking current files aganist panel response.","time":"2017-11-19T20:36:40.062Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"SFTP container successfully booted.","time":"2017-11-19T20:36:40.081Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Attempting to load servers and initialize daemon...","time":"2017-11-19T20:36:40.081Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T20:36:40.159Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T20:36:40.161Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T20:36:40.162Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T20:36:40.163Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Server status has been changed to ON","time":"2017-11-19T20:36:40.164Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":30,"msg":"Daemon detected that the server container is currently running, re-attaching to it now!","time":"2017-11-19T20:36:40.172Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":30,"msg":"Daemon detected that the server container is currently running, re-attaching to it now!","time":"2017-11-19T20:36:40.172Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":30,"msg":"Daemon detected that the server container is currently running, re-attaching to it now!","time":"2017-11-19T20:36:40.172Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":30,"msg":"Daemon detected that the server container is currently running, re-attaching to it now!","time":"2017-11-19T20:36:40.173Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":30,"msg":"Daemon detected that the server container is currently running, re-attaching to it now!","time":"2017-11-19T20:36:40.173Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Configuring websocket for daemon stats...","time":"2017-11-19T20:36:40.205Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"msg":"Unable to assign permissions on startup for this server. Are all of the files in the correct location?","time":"2017-11-19T20:36:40.207Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"msg":"Unable to assign permissions on startup for this server. Are all of the files in the correct location?","time":"2017-11-19T20:36:40.207Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"msg":"Unable to assign permissions on startup for this server. Are all of the files in the correct location?","time":"2017-11-19T20:36:40.207Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"msg":"Unable to assign permissions on startup for this server. Are all of the files in the correct location?","time":"2017-11-19T20:36:40.207Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"msg":"Unable to assign permissions on startup for this server. Are all of the files in the correct location?","time":"2017-11-19T20:36:40.208Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Pterodactyl Daemon is up-to-date!","time":"2017-11-19T20:36:40.362Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"level":30,"msg":"Pterodactyl Daemon is now listening for insecure connections on 0.0.0.0:8080","time":"2017-11-19T20:36:40.365Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:37:40.182Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:37:40.182Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:37:40.182Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:37:40.183Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:37:40.183Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:38:40.186Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:38:40.187Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:38:40.187Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:38:40.187Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:38:40.187Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:39:40.175Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:39:40.176Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:39:40.180Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:39:40.192Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:39:40.193Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:40:40.179Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:40:40.180Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:40:40.184Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:40:40.190Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:40:40.195Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:41:40.182Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:41:40.182Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:41:40.186Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:41:40.193Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:41:40.200Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:42:40.189Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:42:40.189Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:42:40.190Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:42:40.196Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:42:40.203Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:43:40.204Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:43:40.204Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:43:40.205Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:43:40.205Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:43:40.209Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:44:40.190Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:44:40.196Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:44:40.205Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:44:40.205Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:44:40.214Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:45:40.197Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:45:40.197Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:45:40.207Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:45:40.207Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:45:40.217Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:46:40.200Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:46:40.201Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:46:40.212Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:46:40.213Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:46:40.220Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:47:40.204Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"e17db36c-a4f4-4647-bfca-217372d26821","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:47:40.205Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"7e72e15d-c442-454f-a798-d43b3a3ba0f9","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:47:40.211Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"dcbeba66-5906-480d-a6d4-a8b50c74aaeb","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:47:40.215Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"d94b1633-b9ad-4443-bfe5-1c59ce7790ab","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with code 1 signal null.\n    at ChildProcess.Exec.on (/srv/daemon/src/controllers/fs.js:85:29)\n    at emitTwo (events.js:106:13)\n    at ChildProcess.emit (events.js:191:7)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)"},"msg":"Unable to determine size of server data folder, exited with code 1 signal null.","time":"2017-11-19T20:47:40.223Z","v":0}
{"name":"wings","hostname":"Ubuntu-1604-xenial-64-minimal","pid":5019,"server":"0f58ea08-7cc0-4c56-a167-f97219ce1f4a","level":40,"err":{"message":"Unable to determine size of server data folder, exited with code 1 signal null.","name":"Error","stack":"Error: Unable to determine size of server data folder, exited with co