xyeLz
commented
7 years ago As mentioned above, thorough testing was not completed. I can safely say that it does not appear to be what I had initially thought in regards to "disallowed text". I had thought that this might be related to changing the "Option Tag" without rebooting the daemon, though. That was the only repeatable behavior I was able to find. For example, I have two Call of Duty 4 service options. I configured them originally with "promod:ne" and "promod:eu". After a few days of testing, I decided to change the "Option Tag" to more accurately reflect the mod names so I changed them to "pml220_ne" and "pml220_eu" respectively. Upon attempting to start a new server (for either of them), I began receiving the error message that I posted above. If I changed them back to their initial values, they seemed to start successfully. I decided to troubleshoot by changing the values back to the desired values (pml220_x) and then restarted the daemon. After doing this, I was able to create a server using the new "Option Tag". However, while the server does start successfully, I am still randomly receiving the error shown above.
Here is an example. I was starting/stopping two of the servers which have a very similar configuration. The errors seem to happen somewhat randomly, so I'm wondering if it has nothing to do with the startup/stopping of the containers. You'll see below that it happened once, 11 seconds after the container stopped. Also, the log became littered with these errors about 4 minutes after the container was started (at 15:25:55). It also is still occurring (I have a ton of errors from 15:29:02). It doesn't seem to be related to the stopping/starting of the containers, however it used to always show up then and would prevent the container from starting successfully. The errors don't appear to be affecting the containers now, but I'm curious why they're occurring.
ta (/srv/daemon/src/controllers/docker.js:225:29)\n at emitOne (events.js:96:13)\n at Carrier.emit (events.js:188:7)"},"msg":"A fatal error occured during an operation.","time":"2017-05-21T15:19:37.754Z","v":0}
{"name":"wings","hostname":"a9e2caaf331f","pid":17,"server":"447ede15-04db-46f9-90a2-2ec5056dac7f","level":30,"msg":"Server status has been changed to STARTING","time":"2017-05-21T15:20:12.445Z","v":0}
{"name":"wings","hostname":"a9e2caaf331f","pid":17,"server":"447ede15-04db-46f9-90a2-2ec5056dac7f","level":30,"msg":"Server status has been changed to ON","time":"2017-05-21T15:20:19.567Z","v":0}
{"name":"wings","hostname":"a9e2caaf331f","pid":17,"server":"447ede15-04db-46f9-90a2-2ec5056dac7f","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-05-21T15:21:01.419Z","v":0}
{"name":"wings","hostname":"a9e2caaf331f","pid":17,"server":"447ede15-04db-46f9-90a2-2ec5056dac7f","level":30,"msg":"Server status has been changed to OFF","time":"2017-05-21T15:21:11.471Z","v":0}
{"name":"wings","hostname":"a9e2caaf331f","pid":17,"server":"447ede15-04db-46f9-90a2-2ec5056dac7f","level":30,"msg":"Server status has been changed to STARTING","time":"2017-05-21T15:21:29.761Z","v":0}
{"name":"wings","hostname":"a9e2caaf331f","pid":17,"server":"447ede15-04db-46f9-90a2-2ec5056dac7f","level":30,"msg":"Server status has been changed to ON","time":"2017-05-21T15:21:36.848Z","v":0}
{"name":"wings","hostname":"a9e2caaf331f","pid":17,"server":"ba793f41-c49f-4e07-bed0-25616449100b","level":30,"msg":"Server status has been changed to STOPPING","time":"2017-05-21T15:22:01.753Z","v":0}
{"name":"wings","hostname":"a9e2caaf331f","pid":17,"server":"ba793f41-c49f-4e07-bed0-25616449100b","level":30,"msg":"Server status has been changed to OFF","time":"2017-05-21T15:22:11.781Z","v":0}
{"name":"wings","hostname":"a9e2caaf331f","pid":17,"level":60,"err":{"message":"Cannot read property 'startup' of undefined","name":"TypeError","stack":"TypeError: Cannot read property 'startup' of undefined\n at Async.parallel (/srv/daemon/src/services/index.js:177:49)\n at /srv/daemon/node_modules/async/dist/async.js:3830:24\n at eachOfArrayLike (/srv/daemon/node_modules/async/dist/async.js:1003:9)\n at eachOf (/srv/daemon/node_modules/async/dist/async.js:1051:5)\n at _parallel (/srv/daemon/node_modules/async/dist/async.js:3829:5)\n at Object.parallelLimit [as parallel] (/srv/daemon/node_modules/async/dist/async.js:3912:5)\n at Service.onConsole (/srv/daemon/src/services/index.js:147:15)\n at Server.output (/srv/daemon/src/controllers/server.js:347:22)\n at Carrier.carry.data (/srv/daemon/src/controllers/docker.js:225:29)\n at emitOne (events.js:96:13)\n at Carrier.emit (events.js:188:7)"},"msg":"A fatal error occured during an operation.","time":"2017-05-21T15:22:20.752Z","v":0}```
DaneEveritt
I have not thoroughly tested this but upon initial configuration, it appears as if the "Option Tag" section of a Service Option cannot have an underline in it. I will do more testing tomorrow but basically, I was using promod:ne for an option tag and then changed this to pml220_ne. I then began receiving the following errors during the server startup:
Once I changed this back to promod:ne, I had no more problems. Like I said, I haven't thoroughly tested this since it could certainly be something else, but I figured I'd at least mention it.