Closed gregorskii closed 6 years ago
Looks like this might just be AEM taking a ton of memory to boot up. I'll follow up if I find anything, but the cookbook is getting AEM to the point where it starts running.
Ya still getting it. Seems like AEM tries to start but never does. After 15 mins or so.
Looking further it looks like it never starts the AEM quickstart. The login URL is not resolvable, I increased the delay and retry count to connect to the login URL to ensure the AEM startup had enough time to run then I see this in the error.log of AEM:
△ chef/cookbooks/aem_author kitchen converge default-centos-73
-----> Starting Kitchen (v1.16.0)
-----> Creating <default-centos-73>...
Waiting for URL...
...
In another tab:
[vagrant@default-centos-73 logs]$ tail -f error.log
/libs/cq/core/content/login.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /libs/cq/core/content/login.html not found
This is working... seemed to be a looooooonnnnggg wait for it to come on.
I did have to update the validation urls:
default['aem']['author']['validation_urls'] = [
'http://localhost:4502/libs/granite/core/content/login.html',
'http://localhost:4502/damadmin',
'http://localhost:4502/miscadmin',
'http://localhost:4502/system/console/bundles'
]
Hi there,
Has anyone tried using AEM 6.3, Centos 7.3, and Java 8 with this package?
I'm using test Kitchen to test out the build before using Packer to build it on AWS. In both cases, I get an extreme memory leak that crashes either the AWS instance or my local machine when using test kitchen.
I would like to ignore the Packer side of it for this inquiry and focus on the test Kitchen side as it's more standard.
I am using Berks with my cookbook which relies on version 2.2.0:
My kitchen.yml defines a Vagrant box using chef-solo as its provisioner I wanted to use solo because that's what Packer uses:
My attributes are:
And my recipe:
The Chef output is all correct, it hangs at the last step when trying to query the AEM URL:
Memory usage goes up from here and consumes the machine.
Logging in: