Hi Corentin,
The only option we have is installing from gems.
This is I believe possible as soon as you have ruby and rubygems installed.
Keep in mind that the documentation you will find (like the one from
Martin Alfke, wo did a successful install of puppet 2.x) installed the
2.x version of puppet.
You are looking to get the 3.7.4 version installed, and a recent version
of facter is also needed.
If someone has dome experience installing a 3.x series of puppet, this
would be great to hear about it.
Grts
Johan
On 23/03/15 16:04, Corentin Blanche wrote:
Hi everyone,
It would be very nice to have any feedback on how to have a
*functionnal PE Agent on HP-UX *as the one from Michael Glatz:
Agent
OS: *HP-UX 11.31 Itanium*
Ruby: 1.9.1 (depot from iexpress)
Puppet 2.7.12 - Installed from Source
Facter 1.6.7 - Installed from Source
Thank you for any replies :)
Have a pretty nice day.
Kindest Regards,
Le mardi 18 mars 2014 16:15:08 UTC+1, Rick Copley a écrit :
Hi, has anyone had success getting a puppet agent to run in HP-UX
11.31?
On Thursday, April 5, 2012 11:32:15 AM UTC-4, Justin Stoller wrote:
On Thu, Apr 5, 2012 at 8:22 AM, Nan Liu <n...@puppetlabs.com>
wrote:
On Thu, Apr 5, 2012 at 2:57 PM, Michael Glatz
<mfg...@gmail.com> wrote:
> Removing the default group worked for the most part but
I am still
> running into some issues
>
> It cataloged correctly and even ran the test class I created
>
> notice: Starting Puppet client version 2.7.12
> debug: Finishing transaction 545631632
> debug: Loaded state in 0.00 seconds
> processor - invalid major number
> usage: lsdev [-h] [-d driver | -C class] [-b
block_major] [-c
> char_major]
> [-e major] [major] ...
> uname: illegal option -- p
> usage: uname [-amnrsvil] [-S nodename]
> debug: catalog supports formats: b64_zlib_yaml dot
marshal pson raw
> yaml; using pson
> debug: Using cached certificate for ca
> debug: Using cached certificate for <agent>
> debug: Using cached certificate_revocation_list for ca
> info: Caching catalog for <agent>
> debug: Creating default schedules
> debug: Loaded state in 0.00 seconds
> info: Applying configuration version '1333637360'
> debug: /Schedule[daily]: Skipping device resources
because running on
> a host
> debug: /Schedule[monthly]: Skipping device resources
because running
> on a host
> debug: /Schedule[hourly]: Skipping device resources
because running on
> a host
> notice:
/Stage[main]/Core_permissions/File[/etc/fstab]/group: group
> changed 'sys' to 'root'
> debug: /Stage[main]/Core_permissions/File[/etc/fstab]:
The container
> Class[Core_permissions] will propagate my refresh event
> notice:
/Stage[main]/Core_permissions/File[/etc/crontab]/ensure:
> created
> debug: /Stage[main]/Core_permissions/File[/etc/crontab]:
The container
> Class[Core_permissions] will propagate my refresh event
> notice:
/Stage[main]/Core_permissions/File[/etc/passwd]/group: group
> changed 'sys' to 'root'
> notice:
/Stage[main]/Core_permissions/File[/etc/passwd]/mode: mode
> changed '0444' to '0644'
> debug: /Stage[main]/Core_permissions/File[/etc/passwd]:
The container
> Class[Core_permissions] will propagate my refresh event
> debug: /Stage[main]/Core_permissions/File[/etc/passwd]:
The container
> Class[Core_permissions] will propagate my refresh event
> debug: Class[Core_permissions]: The container
Stage[main] will
> propagate my refresh event
> debug: /Schedule[never]: Skipping device resources
because running on
> a host
> debug: /Schedule[weekly]: Skipping device resources
because running on
> a host
> debug: /Schedule[puppet]: Skipping device resources
because running on
> a host
> debug: Finishing transaction 549485440
> debug: Storing state
> debug: Stored state in 0.04 seconds
> notice: Finished catalog run in 0.11 seconds
> debug: Value of 'preferred_serialization_format' (pson)
is invalid for
> report, using default (yaml)
> debug: report supports formats: b64_zlib_yaml marshal
raw yaml; using
> yaml
>
> I am now receiving this issue again
>
> mporting report report-14137-1.yaml at 2012-04-05 10:49 EDT
> undefined method `each' for nil:NilClass
> Backtrace
>
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:202:in
> `extended'
>
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in
`each'
>
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in
> `extended'
>
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in
> `extend'
>
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in
> `extended'
>
/opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in
> `extend'
>
/opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in
> `create_from_yaml'
>
/opt/puppet/share/puppet-dashboard/app/models/report.rb:86:in
> `create_from_yaml_file'
If you are using ruby 1.9.1, it is known to be problematic:
http://docs.puppetlabs.com/guides/faq.html
<http://docs.puppetlabs.com/guides/faq.html>
> Also it automatically added the node back to default,
anyway to
> prevent that?
Looks like there's a background task automatically adding
nodes. I
don't know a good way around this issue. You can move the
pe-* class
to another group but you will need to manually add nodes
to that group
afterwards.
There's a cron job that calls a rake task that will
automatically add nodes that it knows about to the default
group. You will most likely need to
A) move the offending classes out of the default group as Nan
suggests, or
B) disable the cron job and manually add new nodes to the
appropriate groups, or
C) write a new cron job/rake task that will only add the nodes
you want.
See /etc/cron.d/default-add-all-nodes
on your PE console node.
- Justin
HTH,
Nan
--
You received this message because you are subscribed to
the Google Groups "Puppet Users" group.
To post to this group, send email to
puppet...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
<http://groups.google.com/group/puppet-users?hl=en>.
--
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+unsubscr...@googlegroups.com
<mailto:puppet-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/58123b60-84da-4ce3-af47-b8a273ef91d3%40googlegroups.com
<https://groups.google.com/d/msgid/puppet-users/58123b60-84da-4ce3-af47-b8a273ef91d3%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
Johan De Wit
Open Source Consultant
Red Hat Certified Engineer (805008667232363)
Puppet Certified Professional 2013/2014 (PCP0000006)
Puppet Certified Intstructor
blog : http://johan.koewacht.net/
_________________________________________________________
Open-Future Phone +32 (0)2/255 70 70
Zavelstraat 72 Fax +32 (0)2/255 70 71
3071 KORTENBERG Mobile +32 (0)474/42 40 73
BELGIUM http://www.open-future.be
_________________________________________________________
Next Events:
Puppet Fundamentals |
http://www.open-future.be/puppet-fundamentals-training-16th-till-18th-march
Puppet Architect |
http://www.open-future.be/puppet-architect-training-19th-till-20th-march
Puppet Practitioner |
http://www.open-future.be/puppet-practitioner-training-14th-till-16th-april
Linux Training | http://www.open-future.be/linux-training-20th-till-24th-april
Bacula Administrator 1 |
http://www.open-future.be/bacula-administrator-i-training-28th-till-30th-april
Zabbix Certified Specialist |
http://www.open-future.be/zabbix-certified-specialist-training-4th-till-6th-may
Zabbix Certified Professional |
http://www.open-future.be/zabbix-certified-professional-training-7th-till-8th-may
Subscribe to our newsletter | http://eepurl.com/BUG8H
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/55107695.6030807%40open-future.be.
For more options, visit https://groups.google.com/d/optout.
