Did this ever get fixed?
We use telegraf to monitor passenger-status and send to influx/grafana
We have the same issue, regardless of how we call the passenger-status we
insists passenger isnt running...
On Thursday, July 14, 2016 at 6:01:56 AM UTC+10, Edson Manners wrote:
>
> Thanks for the re
It is a known "issue" and i state "issue" as this is an expected behavior,
If you provision a VM from Foreman it means you wish to control the whole
life cycle of this VM, It acts the same as physical server.
The boot order is set to first boot from network (PXE/etc) after it
finishes the in
Hi,
this is a rather scattered issue with creating VMware virtual machiens
via Foreman and fog-vsphere.
The problem is that any VM that has been created from Foreman has its
Boot Order locked which in turn cannot be changed from the VMs BIOS
afterwards. The process of reversing this on the VMware
Sorry Greg never responded on this but indeed that works :)
(needed it again ;))
Op vrijdag 29 mei 2015 01:27:21 UTC+2 schreef Craig White:
>
> If the perms are 777, it really doesn't matter who the user/group is.
>
> Likely the path to get there... /var/lib/pgsql/backups/ don't permit the
> use
So, still trying to debug this and wanted to update a few things I tried.
First off the template_url above should have been "10.0.10.10".
I also disabled iptables/firewalld on both the smart proxy and the foreman
server to make sure there wasn't something there blocking.
I've monitored the lo
Hi all
It's once again time for the Foreman Community Demo, on Thu 13 Oct. So, join us
for
a review of new & interesting developments from around our community. As ever,
more information is available on the event page [1] and the show agenda is
being compiled at the Foreman wiki [2].
We're keepi
Hi,
Thanks, it redid all and it seems it was some typo in the certs.
The issue I get now is puppetdb:
[root@foreman-01 puppetdb]# /etc/init.d/puppetdb restart
Stopping puppetdb: [ OK ]
Starting puppetdb: bash: /var/log/puppetlabs/puppetdb/puppetdb-daemon
Hello,
We get the following stacktrace for tasks named "[foreman-tasks/action] [E]
uninitialized constant TransportFailure".
Any idea what could be wrong on our side?
2016-10-05 04:17:24 [foreman-tasks/action] [E] uninitialized constant
TransportFailure
2016-10-05 04:17:24 [foreman-tasks/action
On 04/10/16 20:44, Matt . wrote:
> Hi guys,
>
> I followed the manual way from here to upgrade foreman for usage with
> Puppet 4.x but I cannot start my foreman-proxy anymore:
>
> http://projects.theforeman.org/projects/foreman/wiki/Upgrading_from_Puppet_3_to_4
>
>
> [root@foreman-01 ~]# sudo /
Irgendwann am Tue, Oct 04, 2016 um 05:33:22PM -0700, schrieb Poornima
Kshirsagar:
> Hi Team,
>
>
> I'm having problems installing Foreman 1.12 on a fresh installation RHEL 7
> following the Quickstart instructions for "Red Hat Enterprise Linux 7,
> x86_64".
>
> Below command :
>
> # yum-conf
10 matches
Mail list logo
