I’ve been trying to migrate to 2.0 on renkulab but am running into some issues deploying an external environment. Unfortunately it is impossible to diagnose what is actually causing the issue because the logs are not available. See the attached screenshot. I cannot retrieve the logs at any point. Not during instantiation of the session and not in the session overview. Is this a known issue?
@CodingKaiser can you please share a link to your project where this is occurring. Also can you start and leave your failing session running. I can take a look at it from our end and see what the problem is. As far I can tell you currently do not have a running session.
In some cases if the session cannot be scheduled or something else goes wrong then there are no logs because nothing has started at all so that logs can be generated.
Probably that is what happened because I just tried to deploy this container again and this time it worked without issue and I was able to see the logs as well. How can I tell if the session cannot be schedules vs that something is wrong?
@CodingKaiser you should be getting an error message and the state of the session should be “failed” if the scheduling fails. But the scheduling can fail for several reasons. And it seems that we did not catch the case that affected you. There really isn’t anything more you could have done. I will go thorough our logs to find the reason and then we can improve the code on our end to communicate the state better.