I see this was fixed by pull request, so thanks!
On Sun, Dec 15, 2013 at 7:30 PM, Morgan Bickle <[email protected]> wrote: > I can start the Tomcat server fine if I log into the host and run >> /etc/init.d/tomcat start, but no matter of Ansible scripting will start it >> remotely for some reason. > > > I had this same issue on CentOS 5.9 and Oracle Linux 5.9. > Changing the start tomcat task from *started* to *restarted *in the > roles/tomcat/tasks/main.yml file seemed make the problem go away. > > - name: Start Tomcat >> service: name=tomcat state=restarted enabled=yes > > > I haven't been able to figure out why though the init.d start up script > looks good to me. > > > On Wednesday, November 6, 2013 7:40:17 PM UTC-5, AmiableAlbion wrote: >> >> Hi, >> I am experiencing the same issue using this same Ansible example. Perhaps >> I am also being bitten by the non-standard init script issue. My behavior >> is exactly like Jean-Philippe's: I can start the Tomcat server fine if I >> log into the host and run /etc/init.d/tomcat start, but no matter of >> Ansible scripting will start it remotely for some reason. >> >> I have confirmed that after a package installation of "tomcat6.noarch" >> via yum works as expected with the service init script /etc/init.d/tomcat6. >> If I shut it down on the host and run a simple playbook from my master to >> start it and wait, everything completes successfully. >> >> Any ideas why the example init script Tim wrote would behave this way, >> that is, run fine from the command line and not from a playbook? >> >> Thanks >> Albion >> >> >> >> On Thursday, September 26, 2013 8:28:35 AM UTC-7, Timothy Gerla wrote: >>> >>> Hi everyone, just saw this. >>> >>> Confession time! I wrote the Tomcat example and for various reasons I >>> decided to not use the OS packaged version of Tomcat and instead used >>> an example initscript provided by Apache. I tested it pretty >>> carefully, though. I will dig in when I have a chance soon and see if >>> I can reproduce this problem. >>> >>> -Tim >>> >>> On Thu, Sep 26, 2013 at 7:36 AM, James Cammarata >>> <[email protected]> wrote: >>> > How did you install tomcat, and what OS are you running on? If you're >>> using >>> > a packaged version, you shouldn't need to redo the init script. >>> > >>> > >>> > On Thu, Sep 26, 2013 at 9:26 AM, Jean-Philippe Caruana < >>> [email protected]> >>> > wrote: >>> >> >>> >> Le 26/09/2013 15:07, Serge van Ginderachter a écrit : >>> >> > >>> >> > On 26 September 2013 14:57, Jean-Philippe Caruana < >>> [email protected] >>> >> > <mailto:[email protected]>> wrote: >>> >> > >>> >> > > "a pretty standard one" >>> >> > > >>> >> > > What does that mean? :) >>> >> > >>> >> > It means the standard file (from ansible examples) with a few >>> tweaks >>> >> > (JDK as a parameter). >>> >> > >>> >> > >>> >> > The question was about the init script, ansible-examples doesn't >>> carry >>> >> > one for tomcat AFAIK. >>> >> > I presume you meant the standard tomcat upstream init script, or >>> the one >>> >> > provided by your package. >>> >> >>> >> It took it from >>> >> >>> >> https://github.com/ansible/ansible-examples/blob/master/ >>> tomcat-standalone/roles/tomcat/files/tomcat-initscript.sh >>> >> and changed a few things, jdk path for example. >>> >> >>> >> > I'd recommend running that manually with the test module hacking >>> script, >>> >> > and debugging the service module script to see what happens. >>> >> >>> >> "sudo service tomcat start" works fine by itself. >>> >> I don't understand with "test module hacking". >>> >> >>> >> -- Jean-Philippe Caruana >>> >> >>> >> -- >>> >> You received this message because you are subscribed to the Google >>> Groups >>> >> "Ansible Project" group. >>> >> To unsubscribe from this group and stop receiving emails from it, >>> send an >>> >> email to [email protected]. >>> >> For more options, visit https://groups.google.com/groups/opt_out. >>> > >>> > >>> > >>> > >>> > -- >>> > >>> > James Cammarata <[email protected]> >>> > Sr. Software Engineer, AnsibleWorks, Inc. >>> > http://www.ansibleworks.com/ >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups >>> > "Ansible Project" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> an >>> > email to [email protected]. >>> > For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >>> -- >>> Tim Gerla >>> [email protected] >>> >> -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > > For more options, visit https://groups.google.com/groups/opt_out. > -- Michael DeHaan <[email protected]> CTO, AnsibleWorks, Inc. http://www.ansibleworks.com/ -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
