Linux init script for AEM

[Former Community Member]

Hi,

I have followed the steps on this article https://helpx.adobe.com/experience-manager/kb/linux-init-script.html to create the linux init script for AEM. But when I start the service, it shows the following error message:

Jul 20 03:31:32 localhost.localdomain systemd[1]: Starting SYSV: This service manages the Adobe Experience Manager java process....
Jul 20 03:31:32 localhost.localdomain su[8065]: (to admin) root on none
Jul 20 03:31:32 localhost.localdomain aem6[8063]: Starting AEM services: Last login: Wed Jul 20 03:30:24 EDT 2016
Jul 20 03:31:32 localhost.localdomain systemd[1]: PID file /crx-quickstart/conf/aem.pid not readable (yet?) after start.
Jul 20 03:31:32 localhost.localdomain systemd[1]: Failed to start SYSV: This service manages the Adobe Experience Manager java process..
Jul 20 03:31:32 localhost.localdomain systemd[1]: Unit aem6.service entered failed state.
Jul 20 03:31:32 localhost.localdomain systemd[1]: aem6.service failed.

May I know what is the cause of this error. I can start the AEM when I use the start script directly /crx-quickstart/bin/start.

Thanks in advance,

[kautuk_sahni · Accepted solution]

Hi

Which Linux version are you working on ?

The article your are referring here is very old article, where init.d was in use. Currently System.d has replaced init.d. 

Please read this :- http://www.tecmint.com/systemd-replaces-init-in-linux/

//

systemd vs init

                                                                                                                                                   

Features	init	systemd
DBus Dependency – Mandatory	No	Yes
Device based Activation	No	Yes
Device dependency configuration with udev	No	Yes
Timer based Activation	Cron/at	Proprietary
Quota Management	No	Yes
Automatic Service Dependency Handling	No	Yes
Kills users Process at logout	No	Yes
Swap Management	No	Yes
SELinux integration	No	Yes
Support for Encrypted HDD	No	Yes
Static kernle module loading	No	Yes
GUI	No	Yes
List all the child processes	No	Yes
Sysv compatible	Yes	Yes
Interactive booting	No	Yes
Portable to non x86	Yes	No
Adopted on	Several Distro	Several Distro
Parallel service startup	No	Yes
Resource limit per service	No	Yes
Easy extensible startup script	Yes	No
Separate Code and Configuration File	Yes	No
Automatic dependency calculation	No	Yes
Verbose debug	Yes	No
Version	N/A	V44+
Size	560 KB	N/A
Number of Files	75 files	900 files + glib + DBus
Lines of code – LOC	15000 (Approx)	224000 (Approx) (inc Codes, comments and white space) 125000 (Approx) (acctual code)

Please read this old Forum post for some help:- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

I hope this will help you.

Thanks and Regards

Kautuk Sahni 

[Former Community Member]

Thanks, I am using Redhat 7.2, is it must use system.d instead of init.d?

[kautuk_sahni]

Qian416 wrote...

Thanks, I am using Redhat 7.2, is it must use system.d instead of init.d?

It has "systemd".

Reference Link:- https://access.redhat.com/articles/754933

//Although the systemd process replaces the init process (quite literally, /sbin/init is now a symbolic link to /usr/lib/systemd/systemd) for starting services at boot time

~kautuk

[Former Community Member]

Thanks, this helps a lot.

I have managed to find this article helps a lot on creating the aem service using systemD.

http://blogs.perficient.com/adobe/2016/06/17/start-aem-automatically-using-systemd/