Not sure how to start with this one. Was testing Foreman 1.8 & Katello 2.2
RC2 install and had synched down the EPEL repo. While synching down the
CentOS repo, I managed to shut down the virtual guest by accident.
Problem: Now I don't think I can get Foreman/Katello to start up at all.
I get a 403 Forbidden when accessing https://foreman.rhel7.local.
This is a pure testing box, so I don't need to recover it, but I am a bit
surprised that things seem to have gone so wrong after a VM shutdown.
httpd error log may help? Check for AVCs too if SELinux is enabled.
···
On 01/04/15 08:58, Duncan Innes wrote:
> Not sure how to start with this one. Was testing Foreman 1.8 & Katello
> 2.2 RC2 install and had synched down the EPEL repo. While synching down
> the CentOS repo, I managed to shut down the virtual guest by accident.
>
> Problem: Now I don't think I can get Foreman/Katello to start up at
> all. I get a 403 Forbidden when accessing https://foreman.rhel7.local.
Thanks Dominic. I rebuild the guest over lunch. Will try a few reboots,
power downs etc. Don't want a Foreman or Katello server to require clean
shutdowns every time.
I have the same issue on my clean install Katello 2.2RC on EL7 dev
instance. Haven't had much time to troubleshoot it other than try
disabling selinux and iptables. No luck with either of those.
I'm able to consistently reproduce it by cleanly installing and then
immediately after the first reboot I get the 403.
Regards,
–Tony
···
On Wednesday, April 1, 2015 at 9:12:08 AM UTC-4, Duncan Innes wrote:
>
> Thanks Dominic. I rebuild the guest over lunch. Will try a few reboots,
> power downs etc. Don't want a Foreman or Katello server to require clean
> shutdowns every time.
>
> Duncan
>
I will investigate this issue and let you know what I find.
Eric
···
On Wed, Apr 1, 2015 at 10:35 AM, Tony Coffman wrote:
On Wednesday, April 1, 2015 at 9:12:08 AM UTC-4, Duncan Innes wrote:
Thanks Dominic. I rebuild the guest over lunch. Will try a few reboots,
power downs etc. Don’t want a Foreman or Katello server to require clean
shutdowns every time.
Duncan
I have the same issue on my clean install Katello 2.2RC on EL7 dev
instance. Haven’t had much time to troubleshoot it other than try
disabling selinux and iptables. No luck with either of those.
I’m able to consistently reproduce it by cleanly installing and then
immediately after the first reboot I get the 403.
On Wednesday, April 1, 2015 at 9:12:08 AM UTC-4, Duncan Innes wrote:
Thanks Dominic. I rebuild the guest over lunch. Will try a few
reboots, power downs etc. Don't want a Foreman or Katello
server to require clean shutdowns every time.
Duncan
I have the same issue on my clean install Katello 2.2RC on EL7 dev
instance. Haven't had much time to troubleshoot it other than try
disabling selinux and iptables. No luck with either of those.
I'm able to consistently reproduce it by cleanly installing and then
immediately after the first reboot I get the 403.
Regards,
--Tony
--
You received this message because you are subscribed to the Google
Groups "foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-dev+unsubscribe@googlegroups.com
<mailto:foreman-dev+unsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
My reinstall was yesterday and things were working when I booted back up
this morning (clean shutdown IIRC).
Doing a dirty shutdown looks to cause the problem. Brandon's fix looks like
it gets everything moving again.
D
···
On Thursday, 2 April 2015 09:33:39 UTC+1, Dominic Cleal wrote:
>
> Looks like Brandon Merjil has found out the cause:
> https://groups.google.com/forum/#!topic/foreman-users/3MHR63htdEQ
>
> --
> Dominic Cleal
> Red Hat Engineering
>
>
