You ran 'foreman-installer --upgrade' once you updated the RPMs?
On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm wrote:
> I re-ran the foreman-installer —scenario katello —upgrade and it got as
> far as apache. The apache upgrade failed. The foreman log says this:
>
> Aug 15
I re-ran the foreman-installer —scenario katello —upgrade and it got as far as
apache. The apache upgrade failed. The foreman log says this:
Aug 15 09:22:45 fm httpd: (98)Address already in use: AH00072: make_sock: could
not bind to address 0.0.0.0:443
Aug 15 09:22:45 fm httpd: no listening
I would recommend removing foreman-plugin and then doing the upgrade.
That's not a package that is typically installed or required on a system.
On Mon, Aug 14, 2017 at 3:47 PM, Louis Bohm wrote:
> I love having infinite history... Here is the ouput of the command:
>
On Mon, Aug 14, 2017 at 12:14 PM, Louis Bohm wrote:
>
> Having major issues upgrading from Katello 3.3 to 3.4 on CentOS 7.3.1611.
>
> For starters running: yum update -y http://fedorapeople.org/
> groups/katello/releases/yum/3.4/katello/el7/x86_64/katello-
> repos-latest.rpm
i have same issue
no redhat repos and no access to them neither
On Wednesday, August 9, 2017 at 1:54:04 PM UTC+2, Eric Helms wrote:
>
> Few questions to help us debug:
>
> 1) Are all repos missing from the UI? Just custom? Just red hat repos?
> 2) Do clients have repo access still?
>
> On Aug
Few questions to help us debug:
1) Are all repos missing from the UI? Just custom? Just red hat repos?
2) Do clients have repo access still?
On Aug 9, 2017 3:31 AM, "'Denis Müller' via Foreman users" <
foreman-users@googlegroups.com> wrote:
> Hello and thank you for the release. But after i