Issue with AEM 5.6.1 Publish Instance as Author

[NitroHazeDev]

Hello,

Is anyone facing an issue with Publish behaving as an author instance with sidekick appearing. I have started the publish instance with 'publish' as run mode, i still see the issue.

Regards,

NZ

[Sham_HC · Accepted solution]

If for any reason run mode is not defined it takes default as author. Go to osgi console and in sling settings verify the value.

Couple of mistakes that cause this are

1)   While Installing fresh cq publish instance without no sample context.   During this I have see not passing correct parameter into option r

2)    Start up script will be modified OR copied from author & forgot to change the run mode.

3)     Modifying the sling.properties

[NitroHazeDev]

Sham HC wrote...

If for any reason run mode is not defined it takes default as author. Go to osgi console and in sling settings verify the value.

Couple of mistakes that cause this are

1)   While Installing fresh cq publish instance without no sample context.   During this I have see not passing correct parameter into option r

2)    Start up script will be modified OR copied from author & forgot to change the run mode.

3)     Modifying the sling.properties

Hello Sham,

In server.bat i have set the runmode, but in slingsettings i still see 

Run Modes = [samplecontent, author, crx2, crx3mongo]

Initially i started fresh instance with -p4503, the instance started with port 4503 and then i edited server.bat . Have i missed anything?

In server.bat, i have changed port to 4503 and added runmode as below. 

::* TCP port used for stop and status scripts
if not defined CQ_PORT set CQ_PORT=4503

::* hostname of the interface that this server should listen to
:: if not defined CQ_HOST set CQ_HOST=

::* runmode(s)
if not defined CQ_RUNMODE set CQ_RUNMODE=publish

[NitroHazeDev]

Is there something missing here Sham? Please let me know.

[Sham_HC]

*   Verify the jar name. Also if instance already running as author instead of converting into publish. Please start the fresh instance because all acl would have been set already.    

*    If already running  publish instance automatically converted into author without touching sling.properties or startup then file a daycare with all the logs.

*     server.bat , Are you running as service?