AEM 6.3 Publisher instance not starting

Avatar

Avatar
Validate 1
Level 1
neilcbs
Level 1

Likes

0 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
neilcbs
Level 1

Likes

0 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile
neilcbs
Level 1

26-10-2018

Good afternoon all.

I wonder if anyone has experienced a similar problem, and identified the root cause and solution.

We have a cron job scheduled to run each night, to execute a script, which shuts down our AEM instance, perform an offline backup, before finally restarting the AEM instance.

One one particular night, the restart failed.  The only error message I can find in the stdout.log on this night was

Error: JMX connector server communication error: service:jmx:rmi://<HOST_NAME>:8463

Could anyone offer any help please?

Replies

Avatar

Avatar
Boost 5
Level 2
chandu_t
Level 2

Likes

7 likes

Total Posts

29 posts

Correct reply

5 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Applaud 5
Affirm 5
View profile

Avatar
Boost 5
Level 2
chandu_t
Level 2

Likes

7 likes

Total Posts

29 posts

Correct reply

5 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Applaud 5
Affirm 5
View profile
chandu_t
Level 2

26-10-2018

Can you attach little more log, before and after ur script trigger. Also did the backup succeed?

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,205 likes

Total Posts

6,410 posts

Correct reply

1,147 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,205 likes

Total Posts

6,410 posts

Correct reply

1,147 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

16-11-2018

Avatar

Avatar
Validate 1
Level 1
neilcbs
Level 1

Likes

0 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
neilcbs
Level 1

Likes

0 likes

Total Posts

4 posts

Correct reply

0 solutions
Top badges earned
Validate 1
View profile
neilcbs
Level 1

20-12-2018

I have, albeit inadvertently managed to recreate the issue, which caused the error

Error: JMX connector server communication error: service:jmx:rmi://<HOST_NAME>:8463

The message was slightly misleading, as the problem seems to be that port 8463 was still listening, when the AEM instance tried to restart after the backup process had failed, due to a full file system.

Having cleared down the file system, we have not seen a re-occurrence of the issue.