RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
I am trying to use a small, custom upstart script to run apache tomcat. This works very well in Fedora 11 (upstart-0.3.9-24) but does not seem to work in RHEL 6 (upstart-0.6.3-5). Here is the script:

=====================================
start on tomcat-start
respawn
exec /opt/tomcat/bin/catalina.sh run
=====================================

When I run the following command, nothing happens:
# initctl emit tomcat-start

I also tried the simple "bounce" example from the upstart website and it doesn't work on RHEL 6 either (but works on FC11, like the above script):
http://upstart.ubuntu.com/getting-started.html

Version-Release number of selected component (if applicable):
upstart-0.6.3-5

How reproducible:
Always

Steps to Reproduce:
1. Install a new upstart script
2. Try to run script using start or emit command
3.
  
Actual results:
Nothing happens if script is event based and emit command is used. When invoked using the "initctl start" command, an "Unknown job" error is received.

Expected results:
Script should run.

Additional info:

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Where is your job located and what is job file name? Since upstart-0.6.5 upstart jobs moved to /etc/init and job description files must have .conf suffix.

# cat > /etc/init/tomcat.conf << EOF
> start on tomcat-start
> respawn
> exec /opt/tomcat/bin/catalina.sh run
> EOF

# initctl status tomcat
tomcat stop/waiting

# start tomcat
start: Job failed to start

Job failed just because I don't have any  /opt/tomcat/bin/catalina.sh.

Thanks very much Petr. That was indeed the problem.

What's the best place to find documentation on upstart 0.6.5? I have a problem with another job too that was working in FC11, but I want to make sure it's not a config issue like this one before reporting anything.

The most actual documentation can be found in man pages - init(8), init(5), initctl(8)   telinit(8), runlevel(7), startup(7), starting(7), started(7), stopping(7), stopped(7)