···
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 /etc/init.d/foreman-proxy restart
> Stopping foreman-proxy: foreman-proxy was not running. [FAILED]
> Starting foreman-proxy:
> /usr/lib/ruby/gems/1.8/gems/bundler-1.5.3/lib/bundler/shared_helpers.rb:52:in
> `chdir': Permission denied - /root (Errno::EACCES)
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.log:
Permission denied
[FAILED]
cat: /var/run/puppetlabs/puppetdb/puppetdb: No such file or directory
I'm not sure what happens here, rights seem to be OK.
Cheers,
Matt
···
Op woensdag 5 oktober 2016 10:12:49 UTC+2 schreef Dominic Cleal:
>
> 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 /etc/init.d/foreman-proxy restart
> > Stopping foreman-proxy: foreman-proxy was not running. [FAILED]
> > Starting foreman-proxy:
> >
> /usr/lib/ruby/gems/1.8/gems/bundler-1.5.3/lib/bundler/shared_helpers.rb:52:in
>
> > `chdir': Permission denied - /root (Errno::EACCES)
>
> Use "service foreman-proxy restart" instead, it clears out your current
> environment and path better than calling an init.d script directly.
>
> (http://projects.theforeman.org/issues/16111)
>
> --
> Dominic Cleal
> dom...@cleal.org
>
