Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

initscript missing / fail to launch the newly created instance #139

Open
pmauduit opened this issue Jul 5, 2015 · 0 comments
Open

initscript missing / fail to launch the newly created instance #139

pmauduit opened this issue Jul 5, 2015 · 0 comments

Comments

@pmauduit
Copy link
Member

pmauduit commented Jul 5, 2015

In a catalog run:

==> default: Notice: /Stage[main]/Georchestra::Geoserver/Georchestra::Geoserver::Worker[geoserver0]/Georchestra::Module[geoserver0]/Tomcat::Instance[geoserver0]/Tomcat::Instance::Config[geoserver0]/File[/etc/init.d/tomcat-geoserver0]/ensure: created
==> default: Error: Could not start Service[tomcat-geoserver0]: Execution of '/usr/sbin/service tomcat-geoserver0 start' returned 6: Failed to start tomcat-geoserver0.service: Unit tomcat-geoserver0.service failed to load: No such file or directory.
==> default: Wrapped exception:
==> default: Execution of '/usr/sbin/service tomcat-geoserver0 start' returned 6: Failed to start tomcat-geoserver0.service: Unit tomcat-geoserver0.service failed to load: No such file or directory.
==> default: Error: /Stage[main]/Georchestra::Geoserver/Georchestra::Geoserver::Worker[geoserver0]/Georchestra::Module[geoserver0]/Tomcat::Instance[geoserver0]/Tomcat::Instance::Service[geoserver0]/Service[tomcat-geoserver0]/ensure: change from stopped to running failed: Could not start Service[tomcat-geoserver0]: Execution of '/usr/sbin/service tomcat-geoserver0 start' returned 6: Failed to start tomcat-geoserver0.service: Unit tomcat-geoserver0.service failed to load: No such file or directory.

When connecting to the machine and launching the instance by hand (after the failing puppet run), using service tomcat-geoserve0 start, the instance can be launched with no error.

Is there a missing sync() somewhere, to ensure the init scripts are actually created before trying to launch the instance ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant