Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

AEM 6.3 - AEM crashes after installing package in Package manager

Avatar

Level 4

Hi all,

I have a fresh AEM 6.3 installation and have been working with package manager.

I took an existing AEM site and created a package from it on another build location. I didnt take anything from the system files, mostly just /apps/[sitename], /content/[sitename], /content/dam/[sitename] /etc/acs-commons/

I installed the package on my fresh build and then AEM crashed. I got several of these messages on the package manager screen.

1262711_pastedImage_0.png

The logfile has a bunch of stuff in it as well, mostly errors that they can't find an email for my username (bf), which would make sense since I did not add an email and things such as warnings that I need to allow a certain mime type when importing a file. The package says it installed correctly,  but now there is a httperror 500 when AEM tries to start. The package says it installed correctly, but when trying to do anything in AEM this message appears.

1262712_pastedImage_1.png

The log file details this

It looks like it is trying to authenticate user 'Admin' and then gets a connection refused. Why would my connection on localhost be refused? This was from installing a simple package. It didnt have any major system files, I just wanted to import templates, content, and small site that existed on my other server.

My ideas - I've tried clearing the indexes folder, and that gave me a 403 service not found. Is the /etc/acs-commons/ folder not exportable? Thats the only other one that I could see that didnt have any content. This error also appears after restarting AEM, and restarting my server in general.

Any ideas would be helpful for me to troubleshoot/learn a bit more about the AEM package manager process.

Thanks,

Brendan

1 Accepted Solution

Avatar

Correct answer by
Level 4

Hi zeeshank,

Great idea to log in that way. I was able to change the logging to Error logging and found that my package did indeed cause this. It looks like it was trying to load some stuff that wasn't there.

I can get to the URL. and while I can't exactly see anything from the site that I was pushing, I can work with this!

Thanks for your support.

Brendan

View solution in original post

8 Replies

Avatar

Level 4

My main question is really, what could have been in the package that crashes the entire application? Did I do something wrong when creating this package? Here are the files I included. I've pushed full sites before without seeing much problems, but they were small, simple one page sites for testing.

1262713_pastedImage_0.png

Avatar

Level 4

Can you provide how big is the package?

Did you try to open the package?

Did you check replication agent log? Did you check if replication agent is enabled although it should worry in this case because you are installing in author

Did you select "replicate" package from package manager?

Avatar

Level 5

Hi Brendan,

After seeing the screenshots .exe popup coming into your windows is no way related to installing the Package unless and until you write some service that start just after the installation and that service initiate Batch file to run some process(.exe file) otherwise it is not related to your popup.It may be some virus that initiate that (.exe).

After  lots of popup their may me a chance of stopping of AEM service that leads to stop AEM server and you are not able to access anything due to AEM server(Jetty) stop.

I saw the logs these logs are due to replication is active on your author.When you start AEM it check the replication agents.These logs doesn't say anything related to package installation error.

Thanks

Avatar

Level 4

Diego,

My package is 294 KB

I can open the package and see that it looks good from my end (no corrupted files etc)

I tried to log the replication manager here - http://host:port/system/console/configMgr, as per this article Frequently Asked Questions - AEM and I got a 500 error because its trying to log in. Is there somewhere else I can check for this log file?

Zeeshank,

That could be it. So it is because it is technically trying to start two replication agents on the same user? How would I be able to check if one is already started, and could I kill the process then try starting AEM again? I got the same error when restarting my server. It could be starting two automatically when I start AEM.

Brendan

Avatar

Level 5

Did you restart the AEM Server?

AEM replication log will be available to particular replication agent by clicking the View Log below the replication,

you configure will give you replication log.

After restrting the AEM server what is happening are you able to access the http://<host>:<port>/crx/de ?

Avatar

Level 4

Hi zeeshank,

I restarted the AEM instance. I can get to CRXDE lite, when I do it looks like this. I havent configured it yet, seeing as this is a fresh install. Each other link takes me to a login screen, except the login screen is that http 500 error.

1265187_pastedImage_0.png

Avatar

Level 5

Hi brender,

It is coming blank because you are not login as admin .Login as admin .Below is the Screen-shot where you will see the pop-up after clicking the red rectangular box(shown in screenshot).Fill the username and password will propt the whole content tree on the left side.

login_pop_up.png

if you get whole data on left-side that means you can access you url.

Avatar

Correct answer by
Level 4

Hi zeeshank,

Great idea to log in that way. I was able to change the logging to Error logging and found that my package did indeed cause this. It looks like it was trying to load some stuff that wasn't there.

I can get to the URL. and while I can't exactly see anything from the site that I was pushing, I can work with this!

Thanks for your support.

Brendan