Open SimonKaluza opened 7 years ago
i run into the same issue.
The core issue seems to be that the application_unicorn poise-service resource's "start" action is getting triggered before the enable action is run. Because the poise-service's action_enable
method is what actually calls the create_service
and generates the service's upstart template (and the start action is trying to use it before then), I think this calling order needs a restructuring.
This almost always happens because Chef encounters an error and is trying to run queued notifications during shutdown. Look above that for another error message.
Also you do not need to respecify the path
property, it inherits from the application
resource.
During the convergence of our application block, Chef never winds up triggering the application_unicorn's Upstart LWRP provider's Upstart#create_service method that creates the Upstart conf file that governs the app.
Because this conf file never gets generated, Upstart does not recognize the service "my_app_web" and when Chef attempts to restart the service we get the exception output:
Here is our cookbook's full application block: