After doing a clean install of Katello2.2/Foreman 1.8.0RC2 on CentOS 7.1406
and 7.1503 I can access the Web UI and manage the system. After doing a
kernel update on the system and rebooting, the Web UI displays Forbidden to
access "/"
The httpd error_log showed that the pid file for passenger could not be
found at /var/run/rubygem-passenger/passenger.1.0.3446
I created the rubygem-passenger directory and restarted the httpd process
and the Web UI works again, but after another reboot to see if the settings
would stay, the rubygem-passenger directory was deleted and the Web UI came
up with the forbidden error again.
I have also wiped this VM and created 2 new VM's to see if this was
repeatable and it was.
What needs to be done to keep this from happening.
So I think I found the cause of my problem.
The pid file directory that is referenced by mod_passenger is
/var/run/rubygem-passenger
The /usr/lib/tmpfiles.d/rubygem-pasenger.conf file from the
rubygem-passenger RPM, creates /var/run/passenger instead
I changed the tmpfiles.d conf to match the request from mod_passenger for
the time being and it is working fine.
···
On Thursday, April 2, 2015 at 4:12:35 PM UTC+9, Brandon Merjil wrote:
>
> After doing a clean install of Katello2.2/Foreman 1.8.0RC2 on CentOS
> 7.1406 and 7.1503 I can access the Web UI and manage the system. After
> doing a kernel update on the system and rebooting, the Web UI displays
> Forbidden to access "/"
> The httpd error_log showed that the pid file for passenger could not be
> found at /var/run/rubygem-passenger/passenger.1.0.3446
> I created the rubygem-passenger directory and restarted the httpd process
> and the Web UI works again, but after another reboot to see if the settings
> would stay, the rubygem-passenger directory was deleted and the Web UI came
> up with the forbidden error again.
>
> I have also wiped this VM and created 2 new VM's to see if this was
> repeatable and it was.
>
> What needs to be done to keep this from happening.
>
Good catch, could you file a bug please?
http://projects.theforeman.org/projects/rpms/issues/new
···
--
Dominic Cleal
Red Hat Engineering
On 02/04/15 08:18, Brandon Merjil wrote:
So I think I found the cause of my problem.
The pid file directory that is referenced by mod_passenger is
/var/run/rubygem-passenger
The /usr/lib/tmpfiles.d/rubygem-pasenger.conf file from the
rubygem-passenger RPM, creates /var/run/passenger instead
I changed the tmpfiles.d conf to match the request from mod_passenger
for the time being and it is working fine.
On Thursday, April 2, 2015 at 4:12:35 PM UTC+9, Brandon Merjil wrote:
After doing a clean install of Katello2.2/Foreman 1.8.0RC2 on CentOS
7.1406 and 7.1503 I can access the Web UI and manage the system.
After doing a kernel update on the system and rebooting, the Web UI
displays Forbidden to access "/"
The httpd error_log showed that the pid file for passenger could not
be found at /var/run/rubygem-passenger/passenger.1.0.3446
I created the rubygem-passenger directory and restarted the httpd
process and the Web UI works again, but after another reboot to see
if the settings would stay, the rubygem-passenger directory was
deleted and the Web UI came up with the forbidden error again.
I have also wiped this VM and created 2 new VM's to see if this was
repeatable and it was.
What needs to be done to keep this from happening.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
Created bug report
http://projects.theforeman.org/issues/10001
Thanks.
···
On Thursday, April 2, 2015 at 5:31:06 PM UTC+9, Dominic Cleal wrote:
>
> Good catch, could you file a bug please?
>
> http://projects.theforeman.org/projects/rpms/issues/new
>
> --
> Dominic Cleal
> Red Hat Engineering
>
> On 02/04/15 08:18, Brandon Merjil wrote:
> > So I think I found the cause of my problem.
> >
> > The pid file directory that is referenced by mod_passenger is
> > /var/run/rubygem-passenger
> > The /usr/lib/tmpfiles.d/rubygem-pasenger.conf file from the
> > rubygem-passenger RPM, creates /var/run/passenger instead
> >
> > I changed the tmpfiles.d conf to match the request from mod_passenger
> > for the time being and it is working fine.
> >
> > On Thursday, April 2, 2015 at 4:12:35 PM UTC+9, Brandon Merjil wrote:
> >
> > After doing a clean install of Katello2.2/Foreman 1.8.0RC2 on CentOS
> > 7.1406 and 7.1503 I can access the Web UI and manage the system.
> > After doing a kernel update on the system and rebooting, the Web UI
> > displays Forbidden to access "/"
> > The httpd error_log showed that the pid file for passenger could not
> > be found at /var/run/rubygem-passenger/passenger.1.0.3446
> > I created the rubygem-passenger directory and restarted the httpd
> > process and the Web UI works again, but after another reboot to see
> > if the settings would stay, the rubygem-passenger directory was
> > deleted and the Web UI came up with the forbidden error again.
> >
> > I have also wiped this VM and created 2 new VM's to see if this was
> > repeatable and it was.
> >
> > What needs to be done to keep this from happening.
> >
> > --
>
Thanks for the report! Packages are building now into nightly and I'll
include them in 1.8.0-RC3 if all is well.
···
--
Dominic Cleal
Red Hat Engineering
On 02/04/15 09:49, Brandon Merjil wrote:
Created bug report
Bug #10001: [Foreman] Rubygem-passenger 4.0.18 - Packaging - Foreman
Thanks.
On Thursday, April 2, 2015 at 5:31:06 PM UTC+9, Dominic Cleal wrote:
Good catch, could you file a bug please?
http://projects.theforeman.org/projects/rpms/issues/new
<http://projects.theforeman.org/projects/rpms/issues/new>
--
Dominic Cleal
Red Hat Engineering
On 02/04/15 08:18, Brandon Merjil wrote:
> So I think I found the cause of my problem.
>
> The pid file directory that is referenced by mod_passenger is
> /var/run/rubygem-passenger
> The /usr/lib/tmpfiles.d/rubygem-pasenger.conf file from the
> rubygem-passenger RPM, creates /var/run/passenger instead
>
> I changed the tmpfiles.d conf to match the request from mod_passenger
> for the time being and it is working fine.
>
> On Thursday, April 2, 2015 at 4:12:35 PM UTC+9, Brandon Merjil wrote:
>
> After doing a clean install of Katello2.2/Foreman 1.8.0RC2 on
CentOS
> 7.1406 and 7.1503 I can access the Web UI and manage the system.
> After doing a kernel update on the system and rebooting, the
Web UI
> displays Forbidden to access "/"
> The httpd error_log showed that the pid file for passenger
could not
> be found at /var/run/rubygem-passenger/passenger.1.0.3446
> I created the rubygem-passenger directory and restarted the httpd
> process and the Web UI works again, but after another reboot
to see
> if the settings would stay, the rubygem-passenger directory was
> deleted and the Web UI came up with the forbidden error again.
>
> I have also wiped this VM and created 2 new VM's to see if
this was
> repeatable and it was.
>
> What needs to be done to keep this from happening.
>
> --
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
