alessandro mazzoli
2013-Oct-28 16:11 UTC
[Puppet Users] Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init
Hi all, i''m stucked with an error on PE-Mcollective. I have a puppetmaster with PE-Console on it, i have an agent node connected which i want provide to it a module called LAMP, my newbie LAMP module https://github.com/alemazz/lamp.git When i run "puppet agent -t" on the puppetmaster i dont get any error, and the module will install on it, but when i call puppet agent -t on node agent i get this error: Debug: /Schedule[weekly]: Skipping device resources because running on a host Debug: /Schedule[puppet]: Skipping device resources because running on a host *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init* *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init.d* *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective in /etc/init* Debug: Executing ''/etc/init.d/pe-mcollective status'' Debug: Executing ''/etc/init.d/pe-mcollective start'' Notice: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]/ensure: ensure changed ''stopped'' to ''running'' Debug: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: The container Class[Pe_mcollective::Server] will propagate my refresh event Info: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: Unscheduling refresh on Service[pe-mcollective] Debug: Class[Pe_mcollective::Server]: The container Stage[main] will propagate my refresh event Debug: Executing ''/usr/bin/apt-cache policy php5-dev'' Debug: Class[Lamp]: The container Stage[main] will propagate my refresh event Debug: Finishing transaction 87463220 Debug: Storing state Debug: Stored state in 0.05 seconds Notice: Finished catalog run in 15.14 seconds Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson Stderr from the command: stdin: is not a tty Error: /Stage[main]/Lamp/Service[apache2]: Could not evaluate: Execution of ''/sbin/status apache2'' returned 1: status: Unknown job: apache2 Here''s my /etc/init.d on puppetmaster and on agent node -rwxr-xr.x root root pe-mcollective service pe-mcollective status---->running but on /etc/init i dont have pe-mcollective or pe-mcollective.conf, i dont have any .conf on /etc/init.d....is a bug on pe-installer that pe-mcollective service is on /etc/init.d and not on /etc/init? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
alessandro mazzoli
2013-Oct-28 16:16 UTC
[Puppet Users] Re: Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init
Here''s the log: I, [2013-10-28T16:30:07.990102 #1332] INFO -- : activemq.rb:121:in `on_ssl_connecting'' Estblishing SSL session with stomp+ssl://mcollective@sisop-virtualbox:61613 I, [2013-10-28T16:30:07.990465 #1332] INFO -- : activemq.rb:96:in `on_connecting'' TCP Connection attempt 11 to stomp+ssl://mcollective@sisop-virtualbox:61613 E, [2013-10-28T16:30:07.996130 #1332] ERROR -- : activemq.rb:131:in `on_ssl_connectfail'' SSL session creation with stomp+ssl://mcollective@sisop-virtualbox:61613 failed: Co$ I, [2013-10-28T16:30:07.996368 #1332] INFO -- : activemq.rb:111:in `on_connectfail'' TCP Connection to stomp+ssl://mcollective@sisop-virtualbox:61613 failed on attempt 11 I, [2013-10-28T16:30:28.483057 #1332] INFO -- : activemq.rb:121:in `on_ssl_connecting'' Estblishing SSL session with stomp+ssl://mcollective@sisop-virtualbox:61613 I, [2013-10-28T16:30:28.483657 #1332] INFO -- : activemq.rb:96:in `on_connecting'' TCP Connection attempt 12 to stomp+ssl://mcollective@sisop-virtualbox:61613 I, [2013-10-28T16:30:29.645117 #1332] INFO -- : activemq.rb:126:in `on_ssl_connected'' SSL session established with stomp+ssl://mcollective@sisop-virtualbox:61613 I, [2013-10-28T16:30:29.839742 #1332] INFO -- : activemq.rb:101:in `on_connected'' Conncted to stomp+ssl://mcollective@sisop-virtualbox:61613 Il giorno lunedì 28 ottobre 2013 17:11:27 UTC+1, alessandro mazzoli ha scritto:> > Hi all, > i''m stucked with an error on PE-Mcollective. > I have a puppetmaster with PE-Console on it, i have an agent node > connected which i want provide to it a module called LAMP, my newbie LAMP > module > https://github.com/alemazz/lamp.git > > > When i run "puppet agent -t" on the puppetmaster i dont get any error, and > the module will install on it, but when i call puppet agent -t on node > agent i get this error: > > Debug: /Schedule[weekly]: Skipping device resources because running on a > host > Debug: /Schedule[puppet]: Skipping device resources because running on a > host > *Debug: Service[pe-mcollective](provider=upstart): Could not find > pe-mcollective.conf in /etc/init* > *Debug: Service[pe-mcollective](provider=upstart): Could not find > pe-mcollective.conf in /etc/init.d* > *Debug: Service[pe-mcollective](provider=upstart): Could not find > pe-mcollective in /etc/init* > Debug: Executing ''/etc/init.d/pe-mcollective status'' > Debug: Executing ''/etc/init.d/pe-mcollective start'' > Notice: > /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]/ensure: ensure > changed ''stopped'' to ''running'' > Debug: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: The > container Class[Pe_mcollective::Server] will propagate my refresh event > Info: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: > Unscheduling refresh on Service[pe-mcollective] > Debug: Class[Pe_mcollective::Server]: The container Stage[main] will > propagate my refresh event > Debug: Executing ''/usr/bin/apt-cache policy php5-dev'' > Debug: Class[Lamp]: The container Stage[main] will propagate my refresh > event > Debug: Finishing transaction 87463220 > Debug: Storing state > Debug: Stored state in 0.05 seconds > Notice: Finished catalog run in 15.14 seconds > Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson > > > Stderr from the command: > > stdin: is not a tty > Error: /Stage[main]/Lamp/Service[apache2]: Could not evaluate: Execution > of ''/sbin/status apache2'' returned 1: status: Unknown job: apache2 > > > Here''s my /etc/init.d on puppetmaster and on agent node > -rwxr-xr.x root root pe-mcollective > service pe-mcollective status---->running > > but on /etc/init i dont have pe-mcollective or pe-mcollective.conf, i dont > have any .conf on /etc/init.d....is a bug on pe-installer that > pe-mcollective service is on /etc/init.d and not on /etc/init? > > > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
alessandro mazzoli
2013-Oct-28 16:30 UTC
[Puppet Users] Re: Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init
Il giorno lunedì 28 ottobre 2013 17:11:27 UTC+1, alessandro mazzoli ha scritto:> > Hi all, > i''m stucked with an error on PE-Mcollective. > I have a puppetmaster with PE-Console on it, i have an agent node > connected which i want provide to it a module called LAMP, my newbie LAMP > module > https://github.com/alemazz/lamp.git > > > When i run "puppet agent -t" on the puppetmaster i dont get any error, and > the module will install on it, but when i call puppet agent -t on node > agent i get this error: > > Debug: /Schedule[weekly]: Skipping device resources because running on a > host > Debug: /Schedule[puppet]: Skipping device resources because running on a > host > *Debug: Service[pe-mcollective](provider=upstart): Could not find > pe-mcollective.conf in /etc/init* > *Debug: Service[pe-mcollective](provider=upstart): Could not find > pe-mcollective.conf in /etc/init.d* > *Debug: Service[pe-mcollective](provider=upstart): Could not find > pe-mcollective in /etc/init* > Debug: Executing ''/etc/init.d/pe-mcollective status'' > Debug: Executing ''/etc/init.d/pe-mcollective start'' > Notice: > /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]/ensure: ensure > changed ''stopped'' to ''running'' > Debug: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: The > container Class[Pe_mcollective::Server] will propagate my refresh event > Info: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: > Unscheduling refresh on Service[pe-mcollective] > Debug: Class[Pe_mcollective::Server]: The container Stage[main] will > propagate my refresh event > Debug: Executing ''/usr/bin/apt-cache policy php5-dev'' > Debug: Class[Lamp]: The container Stage[main] will propagate my refresh > event > Debug: Finishing transaction 87463220 > Debug: Storing state > Debug: Stored state in 0.05 seconds > Notice: Finished catalog run in 15.14 seconds > Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson > > > Stderr from the command: > > stdin: is not a tty > Error: /Stage[main]/Lamp/Service[apache2]: Could not evaluate: Execution > of ''/sbin/status apache2'' returned 1: status: Unknown job: apache2 > > > Here''s my /etc/init.d on puppetmaster and on agent node > -rwxr-xr.x root root pe-mcollective > service pe-mcollective status---->running > > but on /etc/init i dont have pe-mcollective or pe-mcollective.conf, i dont > have any .conf on /etc/init.d....is a bug on pe-installer that > pe-mcollective service is on /etc/init.d and not on /etc/init? > > > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
alessandro mazzoli
2013-Oct-28 16:31 UTC
[Puppet Users] Re: Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init
fix 1: i syncronized the clocks Il giorno lunedì 28 ottobre 2013 17:11:27 UTC+1, alessandro mazzoli ha scritto:> > Hi all, > i''m stucked with an error on PE-Mcollective. > I have a puppetmaster with PE-Console on it, i have an agent node > connected which i want provide to it a module called LAMP, my newbie LAMP > module > https://github.com/alemazz/lamp.git > > > When i run "puppet agent -t" on the puppetmaster i dont get any error, and > the module will install on it, but when i call puppet agent -t on node > agent i get this error: > > Debug: /Schedule[weekly]: Skipping device resources because running on a > host > Debug: /Schedule[puppet]: Skipping device resources because running on a > host > *Debug: Service[pe-mcollective](provider=upstart): Could not find > pe-mcollective.conf in /etc/init* > *Debug: Service[pe-mcollective](provider=upstart): Could not find > pe-mcollective.conf in /etc/init.d* > *Debug: Service[pe-mcollective](provider=upstart): Could not find > pe-mcollective in /etc/init* > Debug: Executing ''/etc/init.d/pe-mcollective status'' > Debug: Executing ''/etc/init.d/pe-mcollective start'' > Notice: > /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]/ensure: ensure > changed ''stopped'' to ''running'' > Debug: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: The > container Class[Pe_mcollective::Server] will propagate my refresh event > Info: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: > Unscheduling refresh on Service[pe-mcollective] > Debug: Class[Pe_mcollective::Server]: The container Stage[main] will > propagate my refresh event > Debug: Executing ''/usr/bin/apt-cache policy php5-dev'' > Debug: Class[Lamp]: The container Stage[main] will propagate my refresh > event > Debug: Finishing transaction 87463220 > Debug: Storing state > Debug: Stored state in 0.05 seconds > Notice: Finished catalog run in 15.14 seconds > Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson > > > Stderr from the command: > > stdin: is not a tty > Error: /Stage[main]/Lamp/Service[apache2]: Could not evaluate: Execution > of ''/sbin/status apache2'' returned 1: status: Unknown job: apache2 > > > Here''s my /etc/init.d on puppetmaster and on agent node > -rwxr-xr.x root root pe-mcollective > service pe-mcollective status---->running > > but on /etc/init i dont have pe-mcollective or pe-mcollective.conf, i dont > have any .conf on /etc/init.d....is a bug on pe-installer that > pe-mcollective service is on /etc/init.d and not on /etc/init? > > > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
alessandro mazzoli
2013-Oct-28 17:09 UTC
[Puppet Users] Re: Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init
issue still exists Il giorno lunedì 28 ottobre 2013 17:31:40 UTC+1, alessandro mazzoli ha scritto:> > fix 1: i syncronized the clocks > > Il giorno lunedì 28 ottobre 2013 17:11:27 UTC+1, alessandro mazzoli ha > scritto: >> >> Hi all, >> i''m stucked with an error on PE-Mcollective. >> I have a puppetmaster with PE-Console on it, i have an agent node >> connected which i want provide to it a module called LAMP, my newbie LAMP >> module >> https://github.com/alemazz/lamp.git >> >> >> When i run "puppet agent -t" on the puppetmaster i dont get any error, >> and the module will install on it, but when i call puppet agent -t on node >> agent i get this error: >> >> Debug: /Schedule[weekly]: Skipping device resources because running on a >> host >> Debug: /Schedule[puppet]: Skipping device resources because running on a >> host >> *Debug: Service[pe-mcollective](provider=upstart): Could not find >> pe-mcollective.conf in /etc/init* >> *Debug: Service[pe-mcollective](provider=upstart): Could not find >> pe-mcollective.conf in /etc/init.d* >> *Debug: Service[pe-mcollective](provider=upstart): Could not find >> pe-mcollective in /etc/init* >> Debug: Executing ''/etc/init.d/pe-mcollective status'' >> Debug: Executing ''/etc/init.d/pe-mcollective start'' >> Notice: >> /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]/ensure: ensure >> changed ''stopped'' to ''running'' >> Debug: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: The >> container Class[Pe_mcollective::Server] will propagate my refresh event >> Info: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: >> Unscheduling refresh on Service[pe-mcollective] >> Debug: Class[Pe_mcollective::Server]: The container Stage[main] will >> propagate my refresh event >> Debug: Executing ''/usr/bin/apt-cache policy php5-dev'' >> Debug: Class[Lamp]: The container Stage[main] will propagate my refresh >> event >> Debug: Finishing transaction 87463220 >> Debug: Storing state >> Debug: Stored state in 0.05 seconds >> Notice: Finished catalog run in 15.14 seconds >> Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson >> >> >> Stderr from the command: >> >> stdin: is not a tty >> Error: /Stage[main]/Lamp/Service[apache2]: Could not evaluate: Execution >> of ''/sbin/status apache2'' returned 1: status: Unknown job: apache2 >> >> >> Here''s my /etc/init.d on puppetmaster and on agent node >> -rwxr-xr.x root root pe-mcollective >> service pe-mcollective status---->running >> >> but on /etc/init i dont have pe-mcollective or pe-mcollective.conf, i >> dont have any .conf on /etc/init.d....is a bug on pe-installer that >> pe-mcollective service is on /etc/init.d and not on /etc/init? >> >> >> >>-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
alessandro mazzoli
2013-Nov-04 15:22 UTC
[Puppet Users] Re: Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init
FIXED : https://groups.google.com/forum/#!topic/mcollective-users/JBO2BcL8SGA Il giorno lunedì 28 ottobre 2013 17:11:27 UTC+1, alessandro mazzoli ha scritto:> > Hi all, > i''m stucked with an error on PE-Mcollective. > I have a puppetmaster with PE-Console on it, i have an agent node > connected which i want provide to it a module called LAMP, my newbie LAMP > module > https://github.com/alemazz/lamp.git > > > When i run "puppet agent -t" on the puppetmaster i dont get any error, and > the module will install on it, but when i call puppet agent -t on node > agent i get this error: > > Debug: /Schedule[weekly]: Skipping device resources because running on a > host > Debug: /Schedule[puppet]: Skipping device resources because running on a > host > *Debug: Service[pe-mcollective](provider=upstart): Could not find > pe-mcollective.conf in /etc/init* > *Debug: Service[pe-mcollective](provider=upstart): Could not find > pe-mcollective.conf in /etc/init.d* > *Debug: Service[pe-mcollective](provider=upstart): Could not find > pe-mcollective in /etc/init* > Debug: Executing ''/etc/init.d/pe-mcollective status'' > Debug: Executing ''/etc/init.d/pe-mcollective start'' > Notice: > /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]/ensure: ensure > changed ''stopped'' to ''running'' > Debug: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: The > container Class[Pe_mcollective::Server] will propagate my refresh event > Info: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: > Unscheduling refresh on Service[pe-mcollective] > Debug: Class[Pe_mcollective::Server]: The container Stage[main] will > propagate my refresh event > Debug: Executing ''/usr/bin/apt-cache policy php5-dev'' > Debug: Class[Lamp]: The container Stage[main] will propagate my refresh > event > Debug: Finishing transaction 87463220 > Debug: Storing state > Debug: Stored state in 0.05 seconds > Notice: Finished catalog run in 15.14 seconds > Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson > > > Stderr from the command: > > stdin: is not a tty > Error: /Stage[main]/Lamp/Service[apache2]: Could not evaluate: Execution > of ''/sbin/status apache2'' returned 1: status: Unknown job: apache2 > > > Here''s my /etc/init.d on puppetmaster and on agent node > -rwxr-xr.x root root pe-mcollective > service pe-mcollective status---->running > > but on /etc/init i dont have pe-mcollective or pe-mcollective.conf, i dont > have any .conf on /etc/init.d....is a bug on pe-installer that > pe-mcollective service is on /etc/init.d and not on /etc/init? > > > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/449277b8-3692-4924-b733-e60953f665af%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.