Compute + app server local vs deployed issue!

Rhino Developer compute.rhino3d
, ,
#1

Hi there,

I am trying to build a simple test configurator and deploy it to a production environment. I have run into a strange scenario where the compute server works perfectly when testing locally but once deployed it looks like it’s just returning an empty JSON object without any geometry. There also doesn’t seem to be an easy way to debug this on a deployed AWS EC2 instance.

I’ve been trying to wrap my head around this for a while now and was hoping I could get some direction from the community. Perhaps there is a nuanced issue with how our GH file is set up? We are using all native grasshopper components for this test.

Here are the console outputs in both instances and as you can see the local instance returns 52 meshes where the deployed instance returns a null output.

Console output - Local

Console output_local
Console output_local811×517 22.4 KB

Console output - Deployed

Console output_deployed
Console output_deployed813×722 36 KB

Here is the GH file for good measure.
220119 - Test.gh (20.5 KB)

Any help would be greatly appreciated! :star2:

#2

Update

Hi all,
I also noticed that my local version of Rhino compute is different to the deployed version.
I’ve tried pulling the latest master of compute.rhino3d from GitHub for local debugging and checking its version number and there seems to be no change in the version number.

Could this be why I am not finding the bug locally?

Local version
Local version

Deployed version
deployed version

#3

Hi all,

For those having similar issues - in our case, it turned out to be this cluster of nodes causing the issue and likely the bounding box node that was the culprit!

The GH script worked fine locally but not on the compute server!

Issue solved
Issue solved1060×487 62.2 KB