I'm at a loss here, out of my depth, and am not finding enough information
out there to diagnose this myself. I have a Foreman 1.14.3 installation
running on CentOS 7.3. All was well, today there were a bunch of CentOS
upgrades and I installed them (I've done this before). I rebooted the
server when I had time and Foreman now isn't working. There are some
Foreman related processes running, I've turned on debug and looked over
production.log, but I still can't find what's wrong. The web-interface
isn't running/refusing connections.
The only message I see of note in the production.log is that postgresql
isn't available, but it is up and running, so I was thinking that's just a
timeout issue until postgresql gets up and running.
Anyone have time to help out a Foreman novice? I've put the contents of
production.log up at http://termbin.com/jrhv
Any help would be appreciated!
For anyone wondering, the problem was tracked down to an upgrade for httpd
in CentOS, it restored the default configuration files which resulted in a
conflict with two virtual-hosts fighting for port 443. Removing the default
config files fixes the issue.
Many thanks to Meltro and aitrus, for helping me out on #theforeman.
That should fix any configuration issues, at least.
Regards,
j
···
From: "Scott Lopez"
To: "Foreman Users"
Sent: Friday, April 14, 2017 11:20:52 AM
Subject: [foreman-users] Forman was working, after CentOS update, dead. help?
Thanks for any assistance in advance!
I’m at a loss here, out of my depth, and am not finding enough information out there to diagnose this myself. I have a Foreman 1.14.3 installation running on CentOS 7.3. All was well, today there were a bunch of CentOS upgrades and I installed them (I’ve done this before). I rebooted the server when I had time and Foreman now isn’t working. There are some Foreman related processes running, I’ve turned on debug and looked over production.log, but I still can’t find what’s wrong. The web-interface isn’t running/refusing connections.
The only message I see of note in the production.log is that postgresql isn’t available, but it is up and running, so I was thinking that’s just a timeout issue until postgresql gets up and running.
Anyone have time to help out a Foreman novice? I’ve put the contents of production.log up at http://termbin.com/jrhv
Any help would be appreciated!
and that fixed whatever was wrong. It appears to be working ok now. Thank
you for your help!
···
On Friday, April 14, 2017 at 1:00:39 PM UTC-5, Jason B. Nance wrote:
>
> Hi Scott,
>
> There's a chance that a default configuration was put in place by an RPM
> that is causing issues. Try running:
>
> foreman-installer --scenario --upgrade
>
> That should fix any configuration issues, at least.
>
> Regards,
>
> j
>
>
> ------------------------------
> *From: *"Scott Lopez" <sco...@gmail.com >
> *To: *"Foreman Users" <forema...@googlegroups.com >
> *Sent: *Friday, April 14, 2017 11:20:52 AM
> *Subject: *[foreman-users] Forman was working, after CentOS update, dead.
> help?
>
> Thanks for any assistance in advance!
>
> I'm at a loss here, out of my depth, and am not finding enough information
> out there to diagnose this myself. I have a Foreman 1.14.3 installation
> running on CentOS 7.3. All was well, today there were a bunch of CentOS
> upgrades and I installed them (I've done this before). I rebooted the
> server when I had time and Foreman now isn't working. There are some
> Foreman related processes running, I've turned on debug and looked over
> production.log, but I still can't find what's wrong. The web-interface
> isn't running/refusing connections.
>
> The only message I see of note in the production.log is that postgresql
> isn't available, but it is up and running, so I was thinking that's just a
> timeout issue until postgresql gets up and running.
>
> Anyone have time to help out a Foreman novice? I've put the contents of
> production.log up at http://termbin.com/jrhv
> Any help would be appreciated!
>
> Thank you.
>
> --
> 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-user...@googlegroups.com .
> To post to this group, send email to forema...@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
Deep breath taken, I am glad we have our puppet installer. (Cleaning
my lips with a tissue now).
LZ
···
On Fri, Apr 14, 2017 at 9:41 PM, Scott Lopez wrote:
> For anyone wondering, the problem was tracked down to an upgrade for httpd
> in CentOS, it restored the default configuration files which resulted in a
> conflict with two virtual-hosts fighting for port 443. Removing the default
> config files fixes the issue.
>
> Many thanks to Meltro and aitrus, for helping me out on #theforeman.
>
> --
> 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.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
