Any idea if there are any plans to make HTTP Direct available also for Solo topology?

anyone running datomic on-prem inside a ions setup? (I'm worried about deps conflicts)

Hi, i just tried my first ‘from scratch’ install of the separate DC storage and compute stacks

I’m getting an ApplicationDoesNotExistException when I try to push. I’ve poked around a bit, and I do see the code deploy app, etc

look at your newly created compute stack in cloudformation dashboard go to outputs and find the name of the codeDeployApplication

make sure that’s the same as what you’re using also check that your AWS creds (and region) you’re using to push are correct for that account

dammit lol. had already checked all of those things. I’m running with God creds.. but sorta forgot to set AWS_PROFILE 😉

Ok running into another (I think actual) issue. the log is full of streams that appear to be the result of instances cycling due to this msg “:datomic.cluster-node/-main failed: Production Compute Stack not found for query group”. I’ve only installed storage and compute

when you ran the compute stack, are you sure you used the compute template and not the query group template by accident?

I’ll retry it but 99.9% certain that I didn’t Is there anything unique in the QG outputs, that I could use as a quick sanity check?

well actually, just reviewing the parameters. None of the QG stuff like “max query group instances” is there

what version ar eyou launching?

latest 482-8794

and the log errors are showing up in the datomic stream for this system?

and from the template

{
	"AWSTemplateFormatVersion": "2010-09-09",
	"Description": "Creates compute resources needed to run Datomic.",

yeah

i tried a deploy

and got that ‘failed because too many instances failed deployment’ msg

then started digging

and the ASG activity history is full of Terminating/Launching messages

from the failed deploy is the system up and running normally prior to doing a deploy?

yeah, this is the one I’ve been working on. THe ‘cycling’ doens’t appear to ahve started until I tried the deploy

what is the application name in your ion-config and what is the deploy command you’re running

and I was just using ion-started to test the deployment

:app-name "ps-cp"}

same as the stack

ag

ah

the compute stack?

and didn’t override the app name

that’s the issue i think

sorry the “system name”

ok?

look at the outputs of your compute group stack

i have ps-cp and ps-cp-compute

ok

SystemName ?

so your CodeDeployApplicationName needs to match

does it?

and then when you run the deploy what’s the command? the group needs to match the CodeDeployDeploymentGroup

ah.. hmm. i was just using the output of :push

but it’s setting the :group to the name of the compute stack

which should match the CodeDeployDeploymentGroup

ah yes it does

hrm. guess that’s not the issue

CodeDeployApplicationName	ps-cp
CodeDeployDeploymentGroup	ps-cp-compute
SystemName	ps-cp

from the outputs

Over in CodeDeploy I have a ps-cp app with a ps-cp-compute deployment group

hrm

and the only thing that’s different (we’ve dozens of solo and prod sized stacks) in the large is that I did the separate stacks from the outset vs the marketplace->first upgrade, etc

that definitely shouldn’t matter

yeah I didn’t think it would

and theres not much in the logs. each stream is the same 4 lines of what looks like normal startup housekeeping, then the error

can you paste the full error line?

sure

`

it’s definitely trying to launch a query group

notice: "IndexGroup?": false,

@eoliphant can you file a ticket (<mailto:[email protected]|[email protected]>) and we’ll look further into it

@eoliphant can you try deleting the compute stack and re-creating it?

hey sorry stepped away for a sec will retry

@eoliphant also, can you provide the first lines of log from when you originally created the stack (when it succeeded originally)?

in particular, the one with the configuration information in it

sure

let me find it

there’s quite a few of them now lol

well this is peculiar, the oldest one I can find is showing the same thing. ugh.. in any case deleting the compute now

will delete all the streams, etc as well

ok it’s taking forever, I’d added a VPC endpoint, and forgot to remove it before I started, I thought I caught it before it got there, but I suspect we’re in CF’s 60 min timeout

@eoliphant do you have a lot of ASGs in your account (like more than 50)?

55

🙂

and it’s back up and went right to blowing up

some sort of AWS API paging issue?

i believe we have a bug when you have > 50 ASGs in an account

we’ll work on a fix for the next release

what do I get? 🙂

ok cool, thx

I’m going to see if i can do some cleanup

in the meantime