AWS EC2 instance of Openstudio-server
I've never had an issue launching a new instance of the Openstudio-server. For some reason though, the latest instance seems to be configured differently.
See the attached screenshots. The workers are look like they are throwing errors, and eventually the simulations start looking funny. For example, the delta time is negative? I am using the latest dockerize branches. Not sure if anyone is experiencing similar issues.
C:\fakepath\Console output.tiff
C:\fakepath\Simulation Results.tiff
Any subsequent set of simulations I launch, seem to hang in a "queue" mode. It is almost like the workers aren't being deployed by the server.
I have seen this behavior recently also. Just for comparison, which OS Server version are you using? I am still using an "older" one: 1.21.16.
Hi-
That is a great question! My dockerfile simply states "latest" as in
You're right, I should try rolling back to an earlier version if I can find one on the dockerhub. Good call.
But no real luck there, the oldest image on there is "latest" :\
i'm a little confused, you are using your own docker containers and not AWS, right? The messages in the worker are not concerning, just a bunch of warnings. I bet your issue lies in the reporting or outputs section. make sure the objective functions are typed in correctly as far as measure name and variable name goes. also that the measure is 2.0 compatible.
I am using AWS actually. I had an old AWS instance that was about a month old. Yesterday, it started acting funny. So I used
docker-machine stop <machine name> and docker-machine rm <machine name>
. I've been informed I was supposed to delete my volume before I did this, which I have not been doing.Unfortunately, once you've removed with the docker-machine command, the volume is no longer visible. So I don't know if it exists somewhere. I'm trying to work this out.
@BrianLBall what is odd is that I have been using the EXACT same spreadsheets as before, and had success.
okay, so you are provisioning your own AWS instance. neat. yeah, you might want to do the following to clear out the volume: docker volume ls docker volume rm xxx docker volume create --name=osdata docker-compose up &
click on the datapoint json link for the completed ones. i bet you will some message in there about objective functions not being found. verify that the measure.variable name is consistent with whats in the analysis.json