Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM 6.5 Bundles in resolved state don't start, no logs being written

Avatar

Avatar
Boost 1
Level 1
gwenh37601470
Level 1

Likes

2 likes

Total Posts

3 posts

Correct Reply

1 solution
Top badges earned
Boost 1
Affirm 1
View profile

Avatar
Boost 1
Level 1
gwenh37601470
Level 1

Likes

2 likes

Total Posts

3 posts

Correct Reply

1 solution
Top badges earned
Boost 1
Affirm 1
View profile
gwenh37601470
Level 1

29-12-2020

Hi,

 

I have installed bundle, all the dependencies got resolved also but it don't go to Active State.

When I click start on /system/console/bundles on a resolved bundle I got no logs on error.log or upgrade.log or any log I could see, even request.log don't seem to be writing anything. I've changed the log level to trace on all logs but makes no difference.

Please note that on normal usage logs are being written, they are just not writing anything when I click on start on this resolved bundle.

 

I've also try to check some answers on this community, I don't have installed ACS AEM Commons and I don't have a bundle activator configured.

I'm deploying the package using autoInstallPackage of content-package-maven-plugin.

 

I don't have any OSGi unsatisfied state component in my bundle, at least from  /system/console/bundles/bundleX/ I don't have any unresolved or red item.

Last but not least I've already installed a author instance from scratch using AEM 6.5 but the issues seems to persist.

 

So my question is, where can I get some logs or trace what is happening?

Is there any kind of procedures I can follow to check this issue?

 
logs osgi resolved start

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 1
Level 1
gwenh37601470
Level 1

Likes

2 likes

Total Posts

3 posts

Correct Reply

1 solution
Top badges earned
Boost 1
Affirm 1
View profile

Avatar
Boost 1
Level 1
gwenh37601470
Level 1

Likes

2 likes

Total Posts

3 posts

Correct Reply

1 solution
Top badges earned
Boost 1
Affirm 1
View profile
gwenh37601470
Level 1

30-12-2020

After several try and error tentatives I figure out it was related with installation dependencies order.

Defining an alternate order on 

content-package-maven-plugin
configuration/embeddeds/embedded/target/X

was enough to solve my issue.

I couldn't figure out why logs didn't show anything related but I guess that is another topic.

Appreciate If anyone have more details on that.

Answers (1)

Answers (1)

Avatar

Avatar
Validate 1
MVP
shelly-goel
MVP

Likes

155 likes

Total Posts

298 posts

Correct Reply

82 solutions
Top badges earned
Validate 1
Shape 1
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Validate 1
MVP
shelly-goel
MVP

Likes

155 likes

Total Posts

298 posts

Correct Reply

82 solutions
Top badges earned
Validate 1
Shape 1
Ignite 1
Give Back 5
Give Back 3
View profile
shelly-goel
MVP

29-12-2020

@gwenh37601470 

Did you try restarting the instance (already with this bundle issue) and see errors related to this bundle in the logs?