WAAE - startup scripts

[Legacy User]

AutoSys is not starting automatically after reboot, even though I installed it with those options checked. Is anyone willing to share a Linux rc3.d list or have any wisdom to share? The default for the AutoSys services is "S11". I'm wondering if they should start later.

Thanks!

Jennifer

[Zenghui Liu]

Hi Jennifer,

 

On my RHEL environment, the installation sets the service level to "35"  when I select to start up the AutoSys services on systme reboot automatically.

 

Hope the following information helps:

 

chkconfig --list waae_sched.U14

waae_sched.U14  0:off   1:off   2:off   3:on    4:off   5:on    6:off

 

# ls -l /etc/rc3.d/*waae_sched*

lrwxrwxrwx. 1 root root 24 Jul  9  2015 /etc/rc3.d/S29waae_sched.U14 -> ../init.d/waae_sched.U14

 

# grep chkconfig /etc/init.d/waae_sched.U14

# chkconfig: 35 99 00

 

Thanks,

Jack

[Legacy User]

Thanks, Jack. I'm not an SA, and I could be wrong, but I think that "35" means that it's set to start at run levels 3 and 5. What is your rc3.d file named?

[Zenghui Liu]

You're welcome, Jennifer.

The file under /etc/rc3.d/ is named S29waae_sched.U14 as shown in the output of "ls -l /etc/rc3.d/*waae_sched*.  It's a soft link to /etc/init.d/waae_sched.U14.

 

# ls -l /etc/rc3.d/*waae_sched*

lrwxrwxrwx. 1 root root 24 Jul  9  2015 /etc/rc3.d/S29waae_sched.U14 -> ../init.d/waae_sched.U14

 

Note that U14 is my WAAE Instance ID.

 

 

Thanks,Jack

[Steve Carrobis]

if it did not come up after reboot. You should find out how they rebooted the box.

As you know there’s more than one flavor of reboot ☺

 

 

Steve C.

[Legacy User]

Good question. This is on a cloud server, and I just click "reboot". I submitted a question to the cloud team, asking what command is issued for the reboot. Thanks.

[Roya Phamgia-Piroux]

Hi  Jennifer,

 

I verified on my machine with Linux RedHat 6.2 :

 

# more /etc/redhat-release

Red Hat Enterprise Linux Server release 6.2 (Santiago)

 

Please proceed by the following steps to verify your current configuration :

 

1. The automatic startup scripts are created under /etc/init.d directory and begin with waae* :

 

# ls -al /etc/init.d/waae_*

 

-rwxr-xr-x. 1 root root 6124 Mar 12  2015 /etc/init.d/waae_agent-WA_AGENT

-rwxr-xr-x. 1 root root 6531 Mar 12  2015 /etc/init.d/waae_sched.ACE

-rwxr-xr-x. 1 root root 6330 Mar 12  2015 /etc/init.d/waae_server.ACE

 

2. There is a link from /etc/rc3.d to these scripts under /etc/init.d:

 

# ls -al /etc/rc3.d/*waae*

 

lrwxrwxrwx 1 root root 29 Mar 12  2015 /etc/rc3.d/S29waae_agent-WA_AGENT -> ../init.d/waae_agent-WA_AGENT

lrwxrwxrwx 1 root root 24 Mar 12  2015 /etc/rc3.d/S29waae_sched.ACE -> ../init.d/waae_sched.ACE

lrwxrwxrwx 1 root root 25 Mar 12  2015 /etc/rc3.d/S29waae_server.ACE -> ../init.d/waae_server.ACE

 

 

3. Then use the “chkconfig --list service-name” command to verify the run level :

 

# chkconfig --list waae_agent-WA_AGENT

waae_agent-WA_AGENT 0:off   1:off   2:off 3:on    4:off   5:on 6:off

 

# chkconfig --list waae_sched.ACE

waae_sched.ORA 0:off   1:off   2:off 3:on    4:off   5:on 6:off

 

# chkconfig --list waae_server.ACE

waae_server.ORA 0:off 1:off   2:off   3:on 4:off   5:on    6:off

 

4.  If you do not have the above or similar settings, the first step will be to copy

the waae* startup scripts under /etc/init.d directory if they are not there.

 

In case you do not have them, you can get them from another instance or we may provide them to you.

 

5. Then you can use the “chkconfig --add” command to add the services :

 

# chkconfig waae_agent-WA_AGENT --add

 

# chkconfig  waae_sched.ACE --add

 

# chkconfig waae_server.ACE --add

 

6. Then use the following commands to set the run level to 3 and 5 :

 

# chkconfig waae_agent-WA_AGENT on --level 3

# chkconfig waae_agent-WA_AGENT on --level 5

 

# chkconfig waae_sched.ACE on --level 3

# chkconfig waae_sched.ACE on --level 5

 

# chkconfig  waae_server.ACE on --level 3

# chkconfig  waae_server.ACE on --level 5

 

Note,  in my tests I could add one run level at a time.

 

7. Run again the “chkconfig --list service-name” command to make sure the services are setup correctly :

 

# chkconfig --list waae_agent-WA_AGENT

 

waae_agent-WA_AGENT     0:off 1:off   2:off   3:on 4:off   5:on    6:off

 

# chkconfig --list waae_sched.ACE

 

waae_sched.ORA  0:off 1:off   2:off   3:on 4:off   5:on    6:off

 

# chkconfig --list waae_server.ACE

 

waae_server.ORA 0:off   1:off 2:off   3:on    4:off 5:on    6:off

 

 

Please note I did the above verification on Linux Red Hat 6.2. 

 

The commands and settings may be slightly different on different Linux flavors.

 

I hope this can help.

 

Thanks,

Roya

[len.rawling]

Hi Jennifer, I had a similar issue with my Solaris machines.

My fix was to edit the init files themselves and look for the profile.CA lookup call. 

Instead of sourcing only the "profile.CA" file the whole /etc/profile is re-read in to get the autosys variables set up ( in our environment this causes issues because of CA's requirement that only Bourne Shell command syntax is allowed). 

Changed to only source /etc/profile.CA and the startup issues went away.