Katello 3.4.4 Released

Support
1

We are happy to announce the GA of Katello 3.4.4. This release contains a
large number of bug fixes for both small UI issues, user issues found while
using 3.4.4 and developer found issues that we felt would bring more
stability to users.

The highlights are too numerous to outline here, so I would recommend to
please look at the changelog for a full list of changes:

Installation:
https://theforeman.org/plugins/katello/3.4/installation/index.html

Upgrade:
https://theforeman.org/plugins/katello/3.4/upgrade/index.html

Bug reporting

··· ============= If you come across a bug in your testing, please file it and note the version of Katello or Foreman that you're using in the report.

http://projects.theforeman.org/projects/katello/issues/new

–
Eric D. Helms
Red Hat Engineering

2

Hello and thank you for the release. But after i did the update to the
latest version, i can't see and access any repos anymore. I can see the
product but no repos.

··· Am Mittwoch, 2. August 2017 17:51:15 UTC+2 schrieb Eric Helms: > > We are happy to announce the GA of Katello 3.4.4. This release contains a > large number of bug fixes for both small UI issues, user issues found while > using 3.4.4 and developer found issues that we felt would bring more > stability to users. > > The highlights are too numerous to outline here, so I would recommend to > please look at the changelog for a full list of changes: > > https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md > > Installation: > https://theforeman.org/plugins/katello/3.4/installation/index.html > > Upgrade: > https://theforeman.org/plugins/katello/3.4/upgrade/index.html > > > Bug reporting > ============= > If you come across a bug in your testing, please file it and note the > version of Katello or Foreman that you're using in the report. > > http://projects.theforeman.org/projects/katello/issues/new > > -- > Eric D. Helms > Red Hat Engineering >
3

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
fails because http-parser and http-parser-devel are not found. I found
them and had to manually install them.

Then yum update -y
http://yum.theforeman.org/releases/1.15/el7/x86_64/foreman-release.rpm
fails because I have foreman-plugin-1.14.3-1.el7.noarch. Cannot update the
plugins because foreman-release has not been upgraded. I am running this
on a VM so I tried to remove foreman-plugin and go that way. But that
failed miserably. I have tried just manually changing the version numbers
in the foreman repos from 1.14 to 1.15 but still same errors.

Whats the fix for this??? I have to say going from Katello 3.2 to 3.3 was
no where nearly as difficult as this.

Louis

··· On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote: > > We are happy to announce the GA of Katello 3.4.4. This release contains a > large number of bug fixes for both small UI issues, user issues found while > using 3.4.4 and developer found issues that we felt would bring more > stability to users. > > The highlights are too numerous to outline here, so I would recommend to > please look at the changelog for a full list of changes: > > https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md > > Installation: > https://theforeman.org/plugins/katello/3.4/installation/index.html > > Upgrade: > https://theforeman.org/plugins/katello/3.4/upgrade/index.html > > > Bug reporting > ============= > If you come across a bug in your testing, please file it and note the > version of Katello or Foreman that you're using in the report. > > http://projects.theforeman.org/projects/katello/issues/new > > -- > Eric D. Helms > Red Hat Engineering >
4

I love having infinite history… Here is the ouput of the command:
[root@fm yum.repos.d]# yum update
http://yum.theforeman.org/releases/1.15/el7/x86_64/foreman-release.rpm
Loaded plugins: fastestmirror, package_upload, product-id,
search-disabled-repos, subscription-
: manager, tracer_upload
foreman-release.rpm |
16 kB 00:00:00
Examining /var/tmp/yum-root-qoYoPs/foreman-release.rpm:
foreman-release-1.15.3-1.el7.noarch
Marking /var/tmp/yum-root-qoYoPs/foreman-release.rpm as an update to
foreman-release-1.14.3-1.el7.noarch
Resolving Dependencies
–> Running transaction check
—> Package foreman-release.noarch 0:1.14.3-1.el7 will be updated
–> Processing Dependency: foreman-release = 1.14.3-1.el7 for package:
foreman-plugin-1.14.3-1.el7.noarch
Loading mirror speeds from cached hostfile

  • base: ftpmirror.your.org
  • epel: mirror.metrocast.net
  • extras: mirrors.centos.webair.com
  • updates: mirrors.lga7.us.voxel.net
    —> Package foreman-release.noarch 0:1.15.3-1.el7 will be an update
    –> Finished Dependency Resolution
    Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman)
    Requires: foreman-release = 1.14.3-1.el7
    Removing: foreman-release-1.14.3-1.el7.noarch (@foreman)
    foreman-release = 1.14.3-1.el7
    Updated By: foreman-release-1.15.3-1.el7.noarch
    (/foreman-release)
    foreman-release = 1.15.3-1.el7
    Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman)
    foreman-release = 1.14.0-0.1.RC1.el7
    Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman)
    foreman-release = 1.14.0-0.1.RC2.el7
    Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman)
    foreman-release = 1.14.0-0.1.RC3.el7
    Available: foreman-release-1.14.0-1.el7.noarch (foreman)
    foreman-release = 1.14.0-1.el7
    Available: foreman-release-1.14.1-1.el7.noarch (foreman)
    foreman-release = 1.14.1-1.el7
    Available: foreman-release-1.14.2-1.el7.noarch (foreman)
    foreman-release = 1.14.2-1.el7
··· ********************************************************************** yum can be configured to try to resolve such errors by temporarily enabling disabled repos and searching for missing dependencies. To enable this functionality please set 'notify_only=0' in /etc/yum/pluginconf.d/search-disabled-repos.conf **********************************************************************

Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman)
Requires: foreman-release = 1.14.3-1.el7
Removing: foreman-release-1.14.3-1.el7.noarch (@foreman)
foreman-release = 1.14.3-1.el7
Updated By: foreman-release-1.15.3-1.el7.noarch
(/foreman-release)
foreman-release = 1.15.3-1.el7
Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman)
foreman-release = 1.14.0-0.1.RC1.el7
Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman)
foreman-release = 1.14.0-0.1.RC2.el7
Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman)
foreman-release = 1.14.0-0.1.RC3.el7
Available: foreman-release-1.14.0-1.el7.noarch (foreman)
foreman-release = 1.14.0-1.el7
Available: foreman-release-1.14.1-1.el7.noarch (foreman)
foreman-release = 1.14.1-1.el7
Available: foreman-release-1.14.2-1.el7.noarch (foreman)
foreman-release = 1.14.2-1.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Louis

On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:

We are happy to announce the GA of Katello 3.4.4. This release contains a
large number of bug fixes for both small UI issues, user issues found while
using 3.4.4 and developer found issues that we felt would bring more
stability to users.

The highlights are too numerous to outline here, so I would recommend to
please look at the changelog for a full list of changes:

https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md

Installation:
Foreman :: Plugin Manuals

Upgrade:
Foreman :: Plugin Manuals

Bug reporting

If you come across a bug in your testing, please file it and note the
version of Katello or Foreman that you’re using in the report.

Foreman

–
Eric D. Helms
Red Hat Engineering

5

I did a repair on mongodb and that did not help. Looked at the log and
found that the reason it was not starting up was because /var/run/mongodb
was no longer around. From the log:
2017-08-14T17:29:22.938-0400 ERROR: Cannot write pid file to
/var/run/mongodb/mongod.pid: No such file or directory

[root@fm run]# ls -l /var/run/mongodb
ls: cannot access /var/run/mongodb: No such file or directory

Once I created that dir, set its owner/group to mongodb I could start the
DB. Now to figure out what happened to postgresql.

Louis

··· On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote: > > We are happy to announce the GA of Katello 3.4.4. This release contains a > large number of bug fixes for both small UI issues, user issues found while > using 3.4.4 and developer found issues that we felt would bring more > stability to users. > > The highlights are too numerous to outline here, so I would recommend to > please look at the changelog for a full list of changes: > > https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md > > Installation: > https://theforeman.org/plugins/katello/3.4/installation/index.html > > Upgrade: > https://theforeman.org/plugins/katello/3.4/upgrade/index.html > > > Bug reporting > ============= > If you come across a bug in your testing, please file it and note the > version of Katello or Foreman that you're using in the report. > > http://projects.theforeman.org/projects/katello/issues/new > > -- > Eric D. Helms > Red Hat Engineering >
6

As with mongodb postgresql was also complaining about its pid directory:

Aug 15 09:02:35 fm systemd: Starting PostgreSQL database server…
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT LOG: could not bind
IPv6 socket: Cannot assign requested address
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT HINT: Is another
postmaster already running on port 5432? If not, wait a few seconds and
retry.
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT FATAL: could not create
lock file "/var/run/postgresql/.s.PGSQL.5432.lock": No such file or
directory
Aug 15 09:02:36 fm pg_ctl: pg_ctl: could not start server
Aug 15 09:02:36 fm pg_ctl: Examine the log output.

And again once i created the dir /var/run/postgresql and set its
perms/owner/group postgresql starts up fine.

Louis

··· On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote: > > We are happy to announce the GA of Katello 3.4.4. This release contains a > large number of bug fixes for both small UI issues, user issues found while > using 3.4.4 and developer found issues that we felt would bring more > stability to users. > > The highlights are too numerous to outline here, so I would recommend to > please look at the changelog for a full list of changes: > > https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md > > Installation: > https://theforeman.org/plugins/katello/3.4/installation/index.html > > Upgrade: > https://theforeman.org/plugins/katello/3.4/upgrade/index.html > > > Bug reporting > ============= > If you come across a bug in your testing, please file it and note the > version of Katello or Foreman that you're using in the report. > > http://projects.theforeman.org/projects/katello/issues/new > > -- > Eric D. Helms > Red Hat Engineering >
7

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 did the update to the
latest version, i can’t see and access any repos anymore. I can see the
product but no repos.

Am Mittwoch, 2. August 2017 17:51:15 UTC+2 schrieb Eric Helms:

We are happy to announce the GA of Katello 3.4.4. This release contains
a large number of bug fixes for both small UI issues, user issues found
while using 3.4.4 and developer found issues that we felt would bring more
stability to users.

The highlights are too numerous to outline here, so I would recommend to
please look at the changelog for a full list of changes:

https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md

Installation:
Foreman :: Plugin Manuals

Upgrade:
Foreman :: Plugin Manuals

Bug reporting

If you come across a bug in your testing, please file it and note the
version of Katello or Foreman that you’re using in the report.

Foreman

–
Eric D. Helms
Red Hat Engineering

–
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.

8

>
> 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 fails because http-parser and http-parser-devel are not
> found. I found them and had to manually install them.
>

This one is strange, as it appears they pulled these packages from EPEL :confused:
We'll have to investigate this further.

>
> Then yum update -y http://yum.theforeman.org/releases/1.15/el7/x86_64/
> foreman-release.rpm fails because I have foreman-plugin-1.14.3-1.el7.noarch.
> Cannot update the plugins because foreman-release has not been upgraded. I
> am running this on a VM so I tried to remove foreman-plugin and go that
> way. But that failed miserably. I have tried just manually changing the
> version numbers in the foreman repos from 1.14 to 1.15 but still same
> errors.
>
>
Can you give more information regarding your first statement? Why does that
first statement fail? Got yum output?

··· On Mon, Aug 14, 2017 at 12:14 PM, Louis Bohm wrote:

Whats the fix for this??? I have to say going from Katello 3.2 to 3.3 was
no where nearly as difficult as this.

Louis
On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:

We are happy to announce the GA of Katello 3.4.4. This release contains
a large number of bug fixes for both small UI issues, user issues found
while using 3.4.4 and developer found issues that we felt would bring more
stability to users.

The highlights are too numerous to outline here, so I would recommend to
please look at the changelog for a full list of changes:

https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md

Installation:
Foreman :: Plugin Manuals

Upgrade:
Foreman :: Plugin Manuals

Bug reporting

If you come across a bug in your testing, please file it and note the
version of Katello or Foreman that you’re using in the report.

Foreman

–
Eric D. Helms
Red Hat Engineering

–
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.

–
Eric D. Helms
Red Hat Engineering

9

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:
[root@fm yum.repos.d]# yum update http://yum.theforeman.org/
releases/1.15/el7/x86_64/foreman-release.rpm
Loaded plugins: fastestmirror, package_upload, product-id,
search-disabled-repos, subscription-
: manager, tracer_upload
foreman-release.rpm |
16 kB 00:00:00
Examining /var/tmp/yum-root-qoYoPs/foreman-release.rpm:
foreman-release-1.15.3-1.el7.noarch
Marking /var/tmp/yum-root-qoYoPs/foreman-release.rpm as an update to
foreman-release-1.14.3-1.el7.noarch
Resolving Dependencies
–> Running transaction check
—> Package foreman-release.noarch 0:1.14.3-1.el7 will be updated
–> Processing Dependency: foreman-release = 1.14.3-1.el7 for package:
foreman-plugin-1.14.3-1.el7.noarch
Loading mirror speeds from cached hostfile

  • base: ftpmirror.your.org
  • epel: mirror.metrocast.net
  • extras: mirrors.centos.webair.com
  • updates: mirrors.lga7.us.voxel.net
    —> Package foreman-release.noarch 0:1.15.3-1.el7 will be an update
    –> Finished Dependency Resolution
    Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman)
    Requires: foreman-release = 1.14.3-1.el7
    Removing: foreman-release-1.14.3-1.el7.noarch (@foreman)
    foreman-release = 1.14.3-1.el7
    Updated By: foreman-release-1.15.3-1.el7.noarch
    (/foreman-release)
    foreman-release = 1.15.3-1.el7
    Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman)
    foreman-release = 1.14.0-0.1.RC1.el7
    Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman)
    foreman-release = 1.14.0-0.1.RC2.el7
    Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman)
    foreman-release = 1.14.0-0.1.RC3.el7
    Available: foreman-release-1.14.0-1.el7.noarch (foreman)
    foreman-release = 1.14.0-1.el7
    Available: foreman-release-1.14.1-1.el7.noarch (foreman)
    foreman-release = 1.14.1-1.el7
    Available: foreman-release-1.14.2-1.el7.noarch (foreman)
    foreman-release = 1.14.2-1.el7

yum can be configured to try to resolve such errors by temporarily enabling
disabled repos and searching for missing dependencies.
To enable this functionality please set ‘notify_only=0’ in
/etc/yum/pluginconf.d/search-disabled-repos.conf

Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman)
Requires: foreman-release = 1.14.3-1.el7
Removing: foreman-release-1.14.3-1.el7.noarch (@foreman)
foreman-release = 1.14.3-1.el7
Updated By: foreman-release-1.15.3-1.el7.noarch
(/foreman-release)
foreman-release = 1.15.3-1.el7
Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman)
foreman-release = 1.14.0-0.1.RC1.el7
Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman)
foreman-release = 1.14.0-0.1.RC2.el7
Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman)
foreman-release = 1.14.0-0.1.RC3.el7
Available: foreman-release-1.14.0-1.el7.noarch (foreman)
foreman-release = 1.14.0-1.el7
Available: foreman-release-1.14.1-1.el7.noarch (foreman)
foreman-release = 1.14.1-1.el7
Available: foreman-release-1.14.2-1.el7.noarch (foreman)
foreman-release = 1.14.2-1.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Louis

On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:

We are happy to announce the GA of Katello 3.4.4. This release contains
a large number of bug fixes for both small UI issues, user issues found
while using 3.4.4 and developer found issues that we felt would bring more
stability to users.

The highlights are too numerous to outline here, so I would recommend to
please look at the changelog for a full list of changes:

https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md

Installation:
Foreman :: Plugin Manuals

Upgrade:
Foreman :: Plugin Manuals

Bug reporting

If you come across a bug in your testing, please file it and note the
version of Katello or Foreman that you’re using in the report.

Foreman

–
Eric D. Helms
Red Hat Engineering

–
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.

–
Eric D. Helms
Red Hat Engineering

10

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 sockets available, shutting down

So I took a look and noticed that Listen 443 was listed twice. Once in /etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf. Thats not good. So I commented out the one in ports.conf and restarted it.

Now when it fails I get a log more information. From /var/log/httpd/error_log I see:

[Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No such file or directory: AH01515: mod_mime_magic: can't read magic file /etc/httpd/NEVER_EVER_USE
[Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
[Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538 ]: Options: { 'analytics_log_user' => 'nobody', 'default_group' => 'nobody', 'default_python' => 'python', 'default_ruby' => 'ruby', 'default_user' => 'nobody', 'log_level' => '0', 'max_pool_size' => '12', 'passenger_root' => '/usr/share/passenger//phusion_passenger/locations.ini', 'passenger_version' => '4.0.53', 'pool_idle_time' => '300', 'prestart_urls' => 'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=', 'temp_dir' => '/tmp', 'union_station_gateway_address' => 'gateway.unionstationapp.com', 'union_station_gateway_port' => '443', 'user_switching' => 'true', 'web_server_passenger_version' => '4.0.53', 'web_server_pid' => '2600', 'web_server_type' => 'apache', 'web_server_worker_gid' => '48', 'web_server_worker_uid' => '48' }
[ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780 agents/HelperAgent/Main.cpp:650 ]: PassengerHelperAgent online, listening at unix:/tmp/passenger.1.0.2600/generation-0/request
[ 2017-08-15 09:25:32.6930 2609/7fd0539ea880 agents/LoggingAgent/Main.cpp:321 ]: PassengerLoggingAgent online, listening at unix:/tmp/passenger.1.0.2600/generation-0/logging
[ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728 ]: All Phusion Passenger agents started!
[Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module access_compat_module is already loaded, skipping
[Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module actions_module is already loaded, skipping
[Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module alias_module is already loaded, skipping
[Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module auth_basic_module is already loaded, skipping
[Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module auth_digest_module is already loaded, skipping
[Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module authn_anon_module is already loaded, skipping
[Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module authn_core_module is already loaded, skipping
[Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module authn_dbm_module is already loaded, skipping
[Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module authn_file_module is already loaded, skipping
[Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module authz_core_module is already loaded, skipping
[Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module authz_dbm_module is already loaded, skipping
[Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module authz_groupfile_module is already loaded, skipping
[Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module authz_host_module is already loaded, skipping
[Tue Aug 15 09:25:32.749164 2017] [so:warn] [pid 2600] AH01574: module authz_owner_module is already loaded, skipping
[Tue Aug 15 09:25:32.749263 2017] [so:warn] [pid 2600] AH01574: module authz_user_module is already loaded, skipping
[Tue Aug 15 09:25:32.749294 2017] [so:warn] [pid 2600] AH01574: module autoindex_module is already loaded, skipping
[Tue Aug 15 09:25:32.749316 2017] [so:warn] [pid 2600] AH01574: module cache_module is already loaded, skipping
[Tue Aug 15 09:25:32.749985 2017] [so:warn] [pid 2600] AH01574: module deflate_module is already loaded, skipping
[Tue Aug 15 09:25:32.750009 2017] [so:warn] [pid 2600] AH01574: module dir_module is already loaded, skipping
[Tue Aug 15 09:25:32.750350 2017] [so:warn] [pid 2600] AH01574: module env_module is already loaded, skipping
[Tue Aug 15 09:25:32.750379 2017] [so:warn] [pid 2600] AH01574: module expires_module is already loaded, skipping
[Tue Aug 15 09:25:32.750398 2017] [so:warn] [pid 2600] AH01574: module ext_filter_module is already loaded, skipping
[Tue Aug 15 09:25:32.750420 2017] [so:warn] [pid 2600] AH01574: module filter_module is already loaded, skipping
[Tue Aug 15 09:25:32.750523 2017] [so:warn] [pid 2600] AH01574: module headers_module is already loaded, skipping
[Tue Aug 15 09:25:32.750630 2017] [so:warn] [pid 2600] AH01574: module include_module is already loaded, skipping
[Tue Aug 15 09:25:32.750973 2017] [so:warn] [pid 2600] AH01574: module log_config_module is already loaded, skipping
[Tue Aug 15 09:25:32.750998 2017] [so:warn] [pid 2600] AH01574: module logio_module is already loaded, skipping
[Tue Aug 15 09:25:32.751015 2017] [so:warn] [pid 2600] AH01574: module mime_magic_module is already loaded, skipping
[Tue Aug 15 09:25:32.751036 2017] [so:warn] [pid 2600] AH01574: module mime_module is already loaded, skipping
[Tue Aug 15 09:25:32.751127 2017] [so:warn] [pid 2600] AH01574: module negotiation_module is already loaded, skipping
[Tue Aug 15 09:25:32.751626 2017] [so:warn] [pid 2600] AH01574: module rewrite_module is already loaded, skipping
[Tue Aug 15 09:25:32.751655 2017] [so:warn] [pid 2600] AH01574: module setenvif_module is already loaded, skipping
[Tue Aug 15 09:25:32.752388 2017] [so:warn] [pid 2600] AH01574: module socache_shmcb_module is already loaded, skipping
[Tue Aug 15 09:25:32.752593 2017] [so:warn] [pid 2600] AH01574: module substitute_module is already loaded, skipping
[Tue Aug 15 09:25:32.752622 2017] [so:warn] [pid 2600] AH01574: module suexec_module is already loaded, skipping
[Tue Aug 15 09:25:32.752799 2017] [so:warn] [pid 2600] AH01574: module unixd_module is already loaded, skipping
[Tue Aug 15 09:25:32.752995 2017] [so:warn] [pid 2600] AH01574: module version_module is already loaded, skipping
[Tue Aug 15 09:25:32.753025 2017] [so:warn] [pid 2600] AH01574: module vhost_alias_module is already loaded, skipping
[Tue Aug 15 09:25:32.753069 2017] [so:warn] [pid 2600] AH01574: module dav_module is already loaded, skipping
[Tue Aug 15 09:25:32.753092 2017] [so:warn] [pid 2600] AH01574: module dav_fs_module is already loaded, skipping
[Tue Aug 15 09:25:32.754627 2017] [so:warn] [pid 2600] AH01574: module mpm_prefork_module is already loaded, skipping
[Tue Aug 15 09:25:32.754686 2017] [so:warn] [pid 2600] AH01574: module proxy_module is already loaded, skipping
[Tue Aug 15 09:25:32.756981 2017] [so:warn] [pid 2600] AH01574: module proxy_http_module is already loaded, skipping
[Tue Aug 15 09:25:32.757423 2017] [so:warn] [pid 2600] AH01574: module ssl_module is already loaded, skipping
[Tue Aug 15 09:25:32.757480 2017] [so:warn] [pid 2600] AH01574: module systemd_module is already loaded, skipping
[Tue Aug 15 09:25:32.757586 2017] [so:warn] [pid 2600] AH01574: module cgi_module is already loaded, skipping
[Tue Aug 15 09:25:32.766868 2017] [alias:warn] [pid 2600] AH00671: The Alias directive in /etc/httpd/conf.d/autoindex.conf at line 21 will probably never match because it overlaps an earlier Alias.
[Tue Aug 15 09:25:32.767816 2017] [mime_magic:error] [pid 2600] (2)No such file or directory: AH01515: mod_mime_magic: can't read magic file /etc/httpd/NEVER_EVER_USE
[Tue Aug 15 09:25:32.767851 2017] [auth_digest:notice] [pid 2600] AH01757: generating secret for digest authentication …
[Tue Aug 15 09:25:32.767898 2017] [auth_digest:error] [pid 2600] (2)No such file or directory: AH01762: Failed to create shared memory segment on file /run/httpd/authdigest_shm.2600
[Tue Aug 15 09:25:32.767917 2017] [auth_digest:error] [pid 2600] (2)No such file or directory: AH01760: failed to initialize shm - all nonce-count checking, one-time nonces, and MD5-sess algorithm disabled
[Tue Aug 15 09:25:32.767924 2017] [:emerg] [pid 2600] AH00020: Configuration Failed, exiting
/usr/share/passenger/helper-scripts/prespawn:113:in initialize&#39;: No route to host - connect(2) (Errno::EHOSTUNREACH) from /usr/share/passenger/helper-scripts/prespawn:113:innew'
from /usr/share/passenger/helper-scripts/prespawn:113:in rescue in connect&#39; from /usr/share/passenger/helper-scripts/prespawn:111:inconnect'
from /usr/share/passenger/helper-scripts/prespawn:87:in socket&#39; from /usr/share/passenger/helper-scripts/prespawn:91:inhead_request'
from /usr/share/passenger/helper-scripts/prespawn:153:in &lt;main&gt;&#39; /usr/share/passenger/helper-scripts/prespawn:113:ininitialize': No route to host - connect(2) (Errno::EHOSTUNREACH)
from /usr/share/passenger/helper-scripts/prespawn:113:in new&#39; from /usr/share/passenger/helper-scripts/prespawn:113:inrescue in connect'
from /usr/share/passenger/helper-scripts/prespawn:111:in connect&#39; from /usr/share/passenger/helper-scripts/prespawn:120:inconnect'
from /usr/share/passenger/helper-scripts/prespawn:87:in socket&#39; from /usr/share/passenger/helper-scripts/prespawn:91:inhead_request'
from /usr/share/passenger/helper-scripts/prespawn:153:in &lt;main&gt;&#39; /usr/share/passenger/helper-scripts/prespawn:113:ininitialize': No route to host - connect(2) (Errno::EHOSTUNREACH)
from /usr/share/passenger/helper-scripts/prespawn:113:in new&#39; from /usr/share/passenger/helper-scripts/prespawn:113:inrescue in connect'
from /usr/share/passenger/helper-scripts/prespawn:111:in connect&#39; from /usr/share/passenger/helper-scripts/prespawn:120:inconnect'
from /usr/share/passenger/helper-scripts/prespawn:87:in socket&#39; from /usr/share/passenger/helper-scripts/prespawn:91:inhead_request'
from /usr/share/passenger/helper-scripts/prespawn:153:in `<main>'

Starting at the top I do not see the module mod_mime_magic being loaded from any of the conf files.

Any ideas on what I do now?

Louis

··· > On Aug 15, 2017, at 9:06 AM, Louis Bohm wrote: > > As with mongodb postgresql was also complaining about its pid directory: > > Aug 15 09:02:35 fm systemd: Starting PostgreSQL database server... > Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT LOG: could not bind IPv6 socket: Cannot assign requested address > Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry. > Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT FATAL: could not create lock file "/var/run/postgresql/.s.PGSQL.5432.lock": No such file or directory > Aug 15 09:02:36 fm pg_ctl: pg_ctl: could not start server > Aug 15 09:02:36 fm pg_ctl: Examine the log output. > > And again once i created the dir /var/run/postgresql and set its perms/owner/group postgresql starts up fine. > > Louis > > On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote: > We are happy to announce the GA of Katello 3.4.4. This release contains a large number of bug fixes for both small UI issues, user issues found while using 3.4.4 and developer found issues that we felt would bring more stability to users. > > The highlights are too numerous to outline here, so I would recommend to please look at the changelog for a full list of changes: > > https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md > > Installation: > https://theforeman.org/plugins/katello/3.4/installation/index.html > > Upgrade: > https://theforeman.org/plugins/katello/3.4/upgrade/index.html > > > Bug reporting > ============= > If you come across a bug in your testing, please file it and note the > version of Katello or Foreman that you're using in the report. > > http://projects.theforeman.org/projects/katello/issues/new > > -- > Eric D. Helms > Red Hat Engineering > > -- > You received this message because you are subscribed to a topic in the Google Groups "Foreman users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/Gmo72QQW86A/unsubscribe . > To unsubscribe from this group and all its topics, 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 .
11

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 9, 2017 3:31 AM, "'Denis Müller' via Foreman users" < > forema...@googlegroups.com > wrote: > >> Hello and thank you for the release. But after i did the update to the >> latest version, i can't see and access any repos anymore. I can see the >> product but no repos. >> >> Am Mittwoch, 2. August 2017 17:51:15 UTC+2 schrieb Eric Helms: >>> >>> We are happy to announce the GA of Katello 3.4.4. This release contains >>> a large number of bug fixes for both small UI issues, user issues found >>> while using 3.4.4 and developer found issues that we felt would bring more >>> stability to users. >>> >>> The highlights are too numerous to outline here, so I would recommend to >>> please look at the changelog for a full list of changes: >>> >>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md >>> >>> Installation: >>> https://theforeman.org/plugins/katello/3.4/installation/index.html >>> >>> Upgrade: >>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html >>> >>> >>> Bug reporting >>> ============= >>> If you come across a bug in your testing, please file it and note the >>> version of Katello or Foreman that you're using in the report. >>> >>> http://projects.theforeman.org/projects/katello/issues/new >>> >>> -- >>> Eric D. Helms >>> Red Hat Engineering >>> >> -- >> 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. >> >
12

Thank you.

This time I tried something different. Before doing anything I removed foreman-plugin. Then I started the upgrade. I will let you know how it goes.

Louis

··· > On Aug 14, 2017, at 4:36 PM, Eric D Helms wrote: > > 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 <louisbohm@gmail.com > wrote: > I love having infinite history... Here is the ouput of the command: > [root@fm yum.repos.d]# yum update http://yum.theforeman.org/releases/1.15/el7/x86_64/foreman-release.rpm > Loaded plugins: fastestmirror, package_upload, product-id, search-disabled-repos, subscription- > : manager, tracer_upload > foreman-release.rpm | 16 kB 00:00:00 > Examining /var/tmp/yum-root-qoYoPs/foreman-release.rpm: foreman-release-1.15.3-1.el7.noarch > Marking /var/tmp/yum-root-qoYoPs/foreman-release.rpm as an update to foreman-release-1.14.3-1.el7.noarch > Resolving Dependencies > --> Running transaction check > ---> Package foreman-release.noarch 0:1.14.3-1.el7 will be updated > --> Processing Dependency: foreman-release = 1.14.3-1.el7 for package: foreman-plugin-1.14.3-1.el7.noarch > Loading mirror speeds from cached hostfile > * base: ftpmirror.your.org > * epel: mirror.metrocast.net > * extras: mirrors.centos.webair.com > * updates: mirrors.lga7.us.voxel.net > ---> Package foreman-release.noarch 0:1.15.3-1.el7 will be an update > --> Finished Dependency Resolution > Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman) > Requires: foreman-release = 1.14.3-1.el7 > Removing: foreman-release-1.14.3-1.el7.noarch (@foreman) > foreman-release = 1.14.3-1.el7 > Updated By: foreman-release-1.15.3-1.el7.noarch (/foreman-release) > foreman-release = 1.15.3-1.el7 > Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman) > foreman-release = 1.14.0-0.1.RC1.el7 > Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman) > foreman-release = 1.14.0-0.1.RC2.el7 > Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman) > foreman-release = 1.14.0-0.1.RC3.el7 > Available: foreman-release-1.14.0-1.el7.noarch (foreman) > foreman-release = 1.14.0-1.el7 > Available: foreman-release-1.14.1-1.el7.noarch (foreman) > foreman-release = 1.14.1-1.el7 > Available: foreman-release-1.14.2-1.el7.noarch (foreman) > foreman-release = 1.14.2-1.el7 > ********************************************************************** > yum can be configured to try to resolve such errors by temporarily enabling > disabled repos and searching for missing dependencies. > To enable this functionality please set 'notify_only=0' in /etc/yum/pluginconf.d/search-disabled-repos.conf > ********************************************************************** > > Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman) > Requires: foreman-release = 1.14.3-1.el7 > Removing: foreman-release-1.14.3-1.el7.noarch (@foreman) > foreman-release = 1.14.3-1.el7 > Updated By: foreman-release-1.15.3-1.el7.noarch (/foreman-release) > foreman-release = 1.15.3-1.el7 > Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman) > foreman-release = 1.14.0-0.1.RC1.el7 > Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman) > foreman-release = 1.14.0-0.1.RC2.el7 > Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman) > foreman-release = 1.14.0-0.1.RC3.el7 > Available: foreman-release-1.14.0-1.el7.noarch (foreman) > foreman-release = 1.14.0-1.el7 > Available: foreman-release-1.14.1-1.el7.noarch (foreman) > foreman-release = 1.14.1-1.el7 > Available: foreman-release-1.14.2-1.el7.noarch (foreman) > foreman-release = 1.14.2-1.el7 > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest > > Louis > > On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote: > We are happy to announce the GA of Katello 3.4.4. This release contains a large number of bug fixes for both small UI issues, user issues found while using 3.4.4 and developer found issues that we felt would bring more stability to users. > > The highlights are too numerous to outline here, so I would recommend to please look at the changelog for a full list of changes: > > https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md > > Installation: > https://theforeman.org/plugins/katello/3.4/installation/index.html > > Upgrade: > https://theforeman.org/plugins/katello/3.4/upgrade/index.html > > > Bug reporting > ============= > If you come across a bug in your testing, please file it and note the > version of Katello or Foreman that you're using in the report. > > http://projects.theforeman.org/projects/katello/issues/new > > -- > Eric D. Helms > Red Hat Engineering > > -- > 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 . > > > > -- > Eric D. Helms > Red Hat Engineering > > -- > You received this message because you are subscribed to a topic in the Google Groups "Foreman users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/Gmo72QQW86A/unsubscribe . > To unsubscribe from this group and all its topics, 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 .
13

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 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 sockets available, shutting down

So I took a look and noticed that Listen 443 was listed twice. Once in
/etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf. Thats not
good. So I commented out the one in ports.conf and restarted it.

Now when it fails I get a log more information. From
/var/log/httpd/error_log I see:

[Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No such
file or directory: AH01515: mod_mime_magic: can’t read magic file
/etc/httpd/NEVER_EVER_USE
[Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init:
Name-based SSL virtual hosts only work for clients with TLS server name
indication support (RFC 4366)
[Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232:
suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538
]: Options: { ‘analytics_log_user’ => ‘nobody’, ‘default_group’ =>
‘nobody’, ‘default_python’ => ‘python’, ‘default_ruby’ => ‘ruby’,
‘default_user’ => ‘nobody’, ‘log_level’ => ‘0’, ‘max_pool_size’ => ‘12’,
‘passenger_root’ => ‘/usr/share/passenger//phusion_passenger/locations.ini’,
‘passenger_version’ => ‘4.0.53’, ‘pool_idle_time’ => ‘300’, ‘prestart_urls’
=> ‘aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29t
OjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=’, ‘temp_dir’ => ‘/tmp’,
‘union_station_gateway_address’ => ‘gateway.unionstationapp.com’,
‘union_station_gateway_port’ => ‘443’, ‘user_switching’ => ‘true’,
‘web_server_passenger_version’ => ‘4.0.53’, ‘web_server_pid’ => ‘2600’,
‘web_server_type’ => ‘apache’, ‘web_server_worker_gid’ => ‘48’,
‘web_server_worker_uid’ => ‘48’ }
[ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780 agents/HelperAgent/Main.cpp:650
]: PassengerHelperAgent online, listening at unix:/tmp/passenger.1.0.2600/
generation-0/request
[ 2017-08-15 09:25:32.6930 2609/7fd0539ea880 agents/LoggingAgent/Main.cpp:321
]: PassengerLoggingAgent online, listening at unix:/tmp/passenger.1.0.2600/
generation-0/logging
[ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728
]: All Phusion Passenger agents started!
[Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module
access_compat_module is already loaded, skipping
[Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module
actions_module is already loaded, skipping
[Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module
alias_module is already loaded, skipping
[Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module
auth_basic_module is already loaded, skipping
[Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module
auth_digest_module is already loaded, skipping
[Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module
authn_anon_module is already loaded, skipping
[Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module
authn_core_module is already loaded, skipping
[Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module
authn_dbm_module is already loaded, skipping
[Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module
authn_file_module is already loaded, skipping
[Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module
authz_core_module is already loaded, skipping
[Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module
authz_dbm_module is already loaded, skipping
[Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module
authz_groupfile_module is already loaded, skipping
[Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module
authz_host_module is already loaded, skipping
[Tue Aug 15 09:25:32.749164 2017] [so:warn] [pid 2600] AH01574: module
authz_owner_module is already loaded, skipping
[Tue Aug 15 09:25:32.749263 2017] [so:warn] [pid 2600] AH01574: module
authz_user_module is already loaded, skipping
[Tue Aug 15 09:25:32.749294 2017] [so:warn] [pid 2600] AH01574: module
autoindex_module is already loaded, skipping
[Tue Aug 15 09:25:32.749316 2017] [so:warn] [pid 2600] AH01574: module
cache_module is already loaded, skipping
[Tue Aug 15 09:25:32.749985 2017] [so:warn] [pid 2600] AH01574: module
deflate_module is already loaded, skipping
[Tue Aug 15 09:25:32.750009 2017] [so:warn] [pid 2600] AH01574: module
dir_module is already loaded, skipping
[Tue Aug 15 09:25:32.750350 2017] [so:warn] [pid 2600] AH01574: module
env_module is already loaded, skipping
[Tue Aug 15 09:25:32.750379 2017] [so:warn] [pid 2600] AH01574: module
expires_module is already loaded, skipping
[Tue Aug 15 09:25:32.750398 2017] [so:warn] [pid 2600] AH01574: module
ext_filter_module is already loaded, skipping
[Tue Aug 15 09:25:32.750420 2017] [so:warn] [pid 2600] AH01574: module
filter_module is already loaded, skipping
[Tue Aug 15 09:25:32.750523 2017] [so:warn] [pid 2600] AH01574: module
headers_module is already loaded, skipping
[Tue Aug 15 09:25:32.750630 2017] [so:warn] [pid 2600] AH01574: module
include_module is already loaded, skipping
[Tue Aug 15 09:25:32.750973 2017] [so:warn] [pid 2600] AH01574: module
log_config_module is already loaded, skipping
[Tue Aug 15 09:25:32.750998 2017] [so:warn] [pid 2600] AH01574: module
logio_module is already loaded, skipping
[Tue Aug 15 09:25:32.751015 2017] [so:warn] [pid 2600] AH01574: module
mime_magic_module is already loaded, skipping
[Tue Aug 15 09:25:32.751036 2017] [so:warn] [pid 2600] AH01574: module
mime_module is already loaded, skipping
[Tue Aug 15 09:25:32.751127 2017] [so:warn] [pid 2600] AH01574: module
negotiation_module is already loaded, skipping
[Tue Aug 15 09:25:32.751626 2017] [so:warn] [pid 2600] AH01574: module
rewrite_module is already loaded, skipping
[Tue Aug 15 09:25:32.751655 2017] [so:warn] [pid 2600] AH01574: module
setenvif_module is already loaded, skipping
[Tue Aug 15 09:25:32.752388 2017] [so:warn] [pid 2600] AH01574: module
socache_shmcb_module is already loaded, skipping
[Tue Aug 15 09:25:32.752593 2017] [so:warn] [pid 2600] AH01574: module
substitute_module is already loaded, skipping
[Tue Aug 15 09:25:32.752622 2017] [so:warn] [pid 2600] AH01574: module
suexec_module is already loaded, skipping
[Tue Aug 15 09:25:32.752799 2017] [so:warn] [pid 2600] AH01574: module
unixd_module is already loaded, skipping
[Tue Aug 15 09:25:32.752995 2017] [so:warn] [pid 2600] AH01574: module
version_module is already loaded, skipping
[Tue Aug 15 09:25:32.753025 2017] [so:warn] [pid 2600] AH01574: module
vhost_alias_module is already loaded, skipping
[Tue Aug 15 09:25:32.753069 2017] [so:warn] [pid 2600] AH01574: module
dav_module is already loaded, skipping
[Tue Aug 15 09:25:32.753092 2017] [so:warn] [pid 2600] AH01574: module
dav_fs_module is already loaded, skipping
[Tue Aug 15 09:25:32.754627 2017] [so:warn] [pid 2600] AH01574: module
mpm_prefork_module is already loaded, skipping
[Tue Aug 15 09:25:32.754686 2017] [so:warn] [pid 2600] AH01574: module
proxy_module is already loaded, skipping
[Tue Aug 15 09:25:32.756981 2017] [so:warn] [pid 2600] AH01574: module
proxy_http_module is already loaded, skipping
[Tue Aug 15 09:25:32.757423 2017] [so:warn] [pid 2600] AH01574: module
ssl_module is already loaded, skipping
[Tue Aug 15 09:25:32.757480 2017] [so:warn] [pid 2600] AH01574: module
systemd_module is already loaded, skipping
[Tue Aug 15 09:25:32.757586 2017] [so:warn] [pid 2600] AH01574: module
cgi_module is already loaded, skipping
[Tue Aug 15 09:25:32.766868 2017] [alias:warn] [pid 2600] AH00671: The
Alias directive in /etc/httpd/conf.d/autoindex.conf at line 21 will
probably never match because it overlaps an earlier Alias.
[Tue Aug 15 09:25:32.767816 2017] [mime_magic:error] [pid 2600] (2)No such
file or directory: AH01515: mod_mime_magic: can’t read magic file
/etc/httpd/NEVER_EVER_USE
[Tue Aug 15 09:25:32.767851 2017] [auth_digest:notice] [pid 2600] AH01757:
generating secret for digest authentication …
[Tue Aug 15 09:25:32.767898 2017] [auth_digest:error] [pid 2600] (2)No
such file or directory: AH01762: Failed to create shared memory segment on
file /run/httpd/authdigest_shm.2600
[Tue Aug 15 09:25:32.767917 2017] [auth_digest:error] [pid 2600] (2)No
such file or directory: AH01760: failed to initialize shm - all nonce-count
checking, one-time nonces, and MD5-sess algorithm disabled
[Tue Aug 15 09:25:32.767924 2017] [:emerg] [pid 2600] AH00020:
Configuration Failed, exiting
/usr/share/passenger/helper-scripts/prespawn:113:in initialize': No route to host - connect(2) (Errno::EHOSTUNREACH) from /usr/share/passenger/helper-scripts/prespawn:113:innew’
from /usr/share/passenger/helper-scripts/prespawn:113:in rescue in connect' from /usr/share/passenger/helper-scripts/prespawn:111:inconnect’
from /usr/share/passenger/helper-scripts/prespawn:87:in socket' from /usr/share/passenger/helper-scripts/prespawn:91:inhead_request’
from /usr/share/passenger/helper-scripts/prespawn:153:in <main>' /usr/share/passenger/helper-scripts/prespawn:113:ininitialize’: No
route to host - connect(2) (Errno::EHOSTUNREACH)
from /usr/share/passenger/helper-scripts/prespawn:113:in new' from /usr/share/passenger/helper-scripts/prespawn:113:inrescue in
connect’
from /usr/share/passenger/helper-scripts/prespawn:111:in connect' from /usr/share/passenger/helper-scripts/prespawn:120:inconnect’
from /usr/share/passenger/helper-scripts/prespawn:87:in socket' from /usr/share/passenger/helper-scripts/prespawn:91:inhead_request’
from /usr/share/passenger/helper-scripts/prespawn:153:in <main>' /usr/share/passenger/helper-scripts/prespawn:113:ininitialize’: No
route to host - connect(2) (Errno::EHOSTUNREACH)
from /usr/share/passenger/helper-scripts/prespawn:113:in new' from /usr/share/passenger/helper-scripts/prespawn:113:inrescue in
connect’
from /usr/share/passenger/helper-scripts/prespawn:111:in connect' from /usr/share/passenger/helper-scripts/prespawn:120:inconnect’
from /usr/share/passenger/helper-scripts/prespawn:87:in socket' from /usr/share/passenger/helper-scripts/prespawn:91:inhead_request’
from /usr/share/passenger/helper-scripts/prespawn:153:in `’

Starting at the top I do not see the module mod_mime_magic being loaded
from any of the conf files.

Any ideas on what I do now?

Louis

On Aug 15, 2017, at 9:06 AM, Louis Bohm louisbohm@gmail.com wrote:

As with mongodb postgresql was also complaining about its pid directory:

Aug 15 09:02:35 fm systemd: Starting PostgreSQL database server…
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT LOG: could not bind
IPv6 socket: Cannot assign requested address
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT HINT: Is another
postmaster already running on port 5432? If not, wait a few seconds and
retry.
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT FATAL: could not
create lock file “/var/run/postgresql/.s.PGSQL.5432.lock”: No such file
or directory
Aug 15 09:02:36 fm pg_ctl: pg_ctl: could not start server
Aug 15 09:02:36 fm pg_ctl: Examine the log output.

And again once i created the dir /var/run/postgresql and set its
perms/owner/group postgresql starts up fine.

Louis

On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:

We are happy to announce the GA of Katello 3.4.4. This release contains
a large number of bug fixes for both small UI issues, user issues found
while using 3.4.4 and developer found issues that we felt would bring more
stability to users.

The highlights are too numerous to outline here, so I would recommend to
please look at the changelog for a full list of changes:

https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md

Installation:
Foreman :: Plugin Manuals

Upgrade:
Foreman :: Plugin Manuals

Bug reporting

If you come across a bug in your testing, please file it and note the
version of Katello or Foreman that you’re using in the report.

Foreman

–
Eric D. Helms
Red Hat Engineering

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/foreman-users/Gmo72QQW86A/unsubscribe.
To unsubscribe from this group and all its topics, 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.

–
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.

–
Eric D. Helms
Red Hat Engineering

14

U have to refresh your installation.

"foreman-installer --scenario katello -i" - "Save and run" did the job for
me. Ater that u can see your repos again.

··· Am Mittwoch, 9. August 2017 17:59:25 UTC+2 schrieb Mario Gamboa: > > 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 9, 2017 3:31 AM, "'Denis Müller' via Foreman users" < >> forema...@googlegroups.com> wrote: >> >>> Hello and thank you for the release. But after i did the update to the >>> latest version, i can't see and access any repos anymore. I can see the >>> product but no repos. >>> >>> Am Mittwoch, 2. August 2017 17:51:15 UTC+2 schrieb Eric Helms: >>>> >>>> We are happy to announce the GA of Katello 3.4.4. This release >>>> contains a large number of bug fixes for both small UI issues, user issues >>>> found while using 3.4.4 and developer found issues that we felt would bring >>>> more stability to users. >>>> >>>> The highlights are too numerous to outline here, so I would recommend >>>> to please look at the changelog for a full list of changes: >>>> >>>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md >>>> >>>> Installation: >>>> https://theforeman.org/plugins/katello/3.4/installation/index.html >>>> >>>> Upgrade: >>>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html >>>> >>>> >>>> Bug reporting >>>> ============= >>>> If you come across a bug in your testing, please file it and note the >>>> version of Katello or Foreman that you're using in the report. >>>> >>>> http://projects.theforeman.org/projects/katello/issues/new >>>> >>>> -- >>>> Eric D. Helms >>>> Red Hat Engineering >>>> >>> -- >>> 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. >>> >>
15

So this time when I did yum update http://yum.theforeman.org/releases/1.15/el7/x86_64/foreman-release.rpm it worked. However, the next step yum update -y foreman-release-scll found nothing to update.
[root@fm ~]# yum update -y foreman-release-scl
Loaded plugins: fastestmirror, package_upload, product-id, search-disabled-repos, subscription-
: manager, tracer_upload
Loading mirror speeds from cached hostfile

Shouldn’t there be updates in this step?

Louis

··· > On Aug 14, 2017, at 5:29 PM, Louis Bohm wrote: > > Thank you. > > This time I tried something different. Before doing anything I removed foreman-plugin. Then I started the upgrade. I will let you know how it goes. > > Louis >> On Aug 14, 2017, at 4:36 PM, Eric D Helms <ericdhelms@gmail.com > wrote: >> >> 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 <louisbohm@gmail.com > wrote: >> I love having infinite history... Here is the ouput of the command: >> [root@fm yum.repos.d]# yum update http://yum.theforeman.org/releases/1.15/el7/x86_64/foreman-release.rpm >> Loaded plugins: fastestmirror, package_upload, product-id, search-disabled-repos, subscription- >> : manager, tracer_upload >> foreman-release.rpm | 16 kB 00:00:00 >> Examining /var/tmp/yum-root-qoYoPs/foreman-release.rpm: foreman-release-1.15.3-1.el7.noarch >> Marking /var/tmp/yum-root-qoYoPs/foreman-release.rpm as an update to foreman-release-1.14.3-1.el7.noarch >> Resolving Dependencies >> --> Running transaction check >> ---> Package foreman-release.noarch 0:1.14.3-1.el7 will be updated >> --> Processing Dependency: foreman-release = 1.14.3-1.el7 for package: foreman-plugin-1.14.3-1.el7.noarch >> Loading mirror speeds from cached hostfile >> * base: ftpmirror.your.org >> * epel: mirror.metrocast.net >> * extras: mirrors.centos.webair.com >> * updates: mirrors.lga7.us.voxel.net >> ---> Package foreman-release.noarch 0:1.15.3-1.el7 will be an update >> --> Finished Dependency Resolution >> Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman) >> Requires: foreman-release = 1.14.3-1.el7 >> Removing: foreman-release-1.14.3-1.el7.noarch (@foreman) >> foreman-release = 1.14.3-1.el7 >> Updated By: foreman-release-1.15.3-1.el7.noarch (/foreman-release) >> foreman-release = 1.15.3-1.el7 >> Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman) >> foreman-release = 1.14.0-0.1.RC1.el7 >> Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman) >> foreman-release = 1.14.0-0.1.RC2.el7 >> Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman) >> foreman-release = 1.14.0-0.1.RC3.el7 >> Available: foreman-release-1.14.0-1.el7.noarch (foreman) >> foreman-release = 1.14.0-1.el7 >> Available: foreman-release-1.14.1-1.el7.noarch (foreman) >> foreman-release = 1.14.1-1.el7 >> Available: foreman-release-1.14.2-1.el7.noarch (foreman) >> foreman-release = 1.14.2-1.el7 >> ********************************************************************** >> yum can be configured to try to resolve such errors by temporarily enabling >> disabled repos and searching for missing dependencies. >> To enable this functionality please set 'notify_only=0' in /etc/yum/pluginconf.d/search-disabled-repos.conf >> ********************************************************************** >> >> Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman) >> Requires: foreman-release = 1.14.3-1.el7 >> Removing: foreman-release-1.14.3-1.el7.noarch (@foreman) >> foreman-release = 1.14.3-1.el7 >> Updated By: foreman-release-1.15.3-1.el7.noarch (/foreman-release) >> foreman-release = 1.15.3-1.el7 >> Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman) >> foreman-release = 1.14.0-0.1.RC1.el7 >> Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman) >> foreman-release = 1.14.0-0.1.RC2.el7 >> Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman) >> foreman-release = 1.14.0-0.1.RC3.el7 >> Available: foreman-release-1.14.0-1.el7.noarch (foreman) >> foreman-release = 1.14.0-1.el7 >> Available: foreman-release-1.14.1-1.el7.noarch (foreman) >> foreman-release = 1.14.1-1.el7 >> Available: foreman-release-1.14.2-1.el7.noarch (foreman) >> foreman-release = 1.14.2-1.el7 >> You could try using --skip-broken to work around the problem >> You could try running: rpm -Va --nofiles --nodigest >> >> Louis >> >> On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote: >> We are happy to announce the GA of Katello 3.4.4. This release contains a large number of bug fixes for both small UI issues, user issues found while using 3.4.4 and developer found issues that we felt would bring more stability to users. >> >> The highlights are too numerous to outline here, so I would recommend to please look at the changelog for a full list of changes: >> >> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md >> >> Installation: >> https://theforeman.org/plugins/katello/3.4/installation/index.html >> >> Upgrade: >> https://theforeman.org/plugins/katello/3.4/upgrade/index.html >> >> >> Bug reporting >> ============= >> If you come across a bug in your testing, please file it and note the >> version of Katello or Foreman that you're using in the report. >> >> http://projects.theforeman.org/projects/katello/issues/new >> >> -- >> Eric D. Helms >> Red Hat Engineering >> >> -- >> 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 . >> >> >> >> -- >> Eric D. Helms >> Red Hat Engineering >> >> -- >> You received this message because you are subscribed to a topic in the Google Groups "Foreman users" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/Gmo72QQW86A/unsubscribe . >> To unsubscribe from this group and all its topics, 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 . >
16

No. Its not on the Katello upgrade page. Am I supposed to?

Louis

··· > On Aug 15, 2017, at 10:59 AM, Eric D Helms wrote: > > You ran 'foreman-installer --upgrade' once you updated the RPMs? > > On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm <louisbohm@gmail.com > 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 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 sockets available, shutting down > > So I took a look and noticed that Listen 443 was listed twice. Once in /etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf. Thats not good. So I commented out the one in ports.conf and restarted it. > > Now when it fails I get a log more information. From /var/log/httpd/error_log I see: > > [Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No such file or directory: AH01515: mod_mime_magic: can't read magic file /etc/httpd/NEVER_EVER_USE > [Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366) > [Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) > [ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538 ]: Options: { 'analytics_log_user' => 'nobody', 'default_group' => 'nobody', 'default_python' => 'python', 'default_ruby' => 'ruby', 'default_user' => 'nobody', 'log_level' => '0', 'max_pool_size' => '12', 'passenger_root' => '/usr/share/passenger//phusion_passenger/locations.ini', 'passenger_version' => '4.0.53', 'pool_idle_time' => '300', 'prestart_urls' => 'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=', 'temp_dir' => '/tmp', 'union_station_gateway_address' => 'gateway.unionstationapp.com ', 'union_station_gateway_port' => '443', 'user_switching' => 'true', 'web_server_passenger_version' => '4.0.53', 'web_server_pid' => '2600', 'web_server_type' => 'apache', 'web_server_worker_gid' => '48', 'web_server_worker_uid' => '48' } > [ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780 agents/HelperAgent/Main.cpp:650 ]: PassengerHelperAgent online, listening at unix:/tmp/passenger.1.0.2600/generation-0/request > [ 2017-08-15 09:25:32.6930 2609/7fd0539ea880 agents/LoggingAgent/Main.cpp:321 ]: PassengerLoggingAgent online, listening at unix:/tmp/passenger.1.0.2600/generation-0/logging > [ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728 ]: All Phusion Passenger agents started! > [Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module access_compat_module is already loaded, skipping > [Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module actions_module is already loaded, skipping > [Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module alias_module is already loaded, skipping > [Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module auth_basic_module is already loaded, skipping > [Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module auth_digest_module is already loaded, skipping > [Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module authn_anon_module is already loaded, skipping > [Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module authn_core_module is already loaded, skipping > [Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module authn_dbm_module is already loaded, skipping > [Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module authn_file_module is already loaded, skipping > [Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module authz_core_module is already loaded, skipping > [Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module authz_dbm_module is already loaded, skipping > [Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module authz_groupfile_module is already loaded, skipping > [Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module authz_host_module is already loaded, skipping > [Tue Aug 15 09:25:32.749164 2017] [so:warn] [pid 2600] AH01574: module authz_owner_module is already loaded, skipping > [Tue Aug 15 09:25:32.749263 2017] [so:warn] [pid 2600] AH01574: module authz_user_module is already loaded, skipping > [Tue Aug 15 09:25:32.749294 2017] [so:warn] [pid 2600] AH01574: module autoindex_module is already loaded, skipping > [Tue Aug 15 09:25:32.749316 2017] [so:warn] [pid 2600] AH01574: module cache_module is already loaded, skipping > [Tue Aug 15 09:25:32.749985 2017] [so:warn] [pid 2600] AH01574: module deflate_module is already loaded, skipping > [Tue Aug 15 09:25:32.750009 2017] [so:warn] [pid 2600] AH01574: module dir_module is already loaded, skipping > [Tue Aug 15 09:25:32.750350 2017] [so:warn] [pid 2600] AH01574: module env_module is already loaded, skipping > [Tue Aug 15 09:25:32.750379 2017] [so:warn] [pid 2600] AH01574: module expires_module is already loaded, skipping > [Tue Aug 15 09:25:32.750398 2017] [so:warn] [pid 2600] AH01574: module ext_filter_module is already loaded, skipping > [Tue Aug 15 09:25:32.750420 2017] [so:warn] [pid 2600] AH01574: module filter_module is already loaded, skipping > [Tue Aug 15 09:25:32.750523 2017] [so:warn] [pid 2600] AH01574: module headers_module is already loaded, skipping > [Tue Aug 15 09:25:32.750630 2017] [so:warn] [pid 2600] AH01574: module include_module is already loaded, skipping > [Tue Aug 15 09:25:32.750973 2017] [so:warn] [pid 2600] AH01574: module log_config_module is already loaded, skipping > [Tue Aug 15 09:25:32.750998 2017] [so:warn] [pid 2600] AH01574: module logio_module is already loaded, skipping > [Tue Aug 15 09:25:32.751015 2017] [so:warn] [pid 2600] AH01574: module mime_magic_module is already loaded, skipping > [Tue Aug 15 09:25:32.751036 2017] [so:warn] [pid 2600] AH01574: module mime_module is already loaded, skipping > [Tue Aug 15 09:25:32.751127 2017] [so:warn] [pid 2600] AH01574: module negotiation_module is already loaded, skipping > [Tue Aug 15 09:25:32.751626 2017] [so:warn] [pid 2600] AH01574: module rewrite_module is already loaded, skipping > [Tue Aug 15 09:25:32.751655 2017] [so:warn] [pid 2600] AH01574: module setenvif_module is already loaded, skipping > [Tue Aug 15 09:25:32.752388 2017] [so:warn] [pid 2600] AH01574: module socache_shmcb_module is already loaded, skipping > [Tue Aug 15 09:25:32.752593 2017] [so:warn] [pid 2600] AH01574: module substitute_module is already loaded, skipping > [Tue Aug 15 09:25:32.752622 2017] [so:warn] [pid 2600] AH01574: module suexec_module is already loaded, skipping > [Tue Aug 15 09:25:32.752799 2017] [so:warn] [pid 2600] AH01574: module unixd_module is already loaded, skipping > [Tue Aug 15 09:25:32.752995 2017] [so:warn] [pid 2600] AH01574: module version_module is already loaded, skipping > [Tue Aug 15 09:25:32.753025 2017] [so:warn] [pid 2600] AH01574: module vhost_alias_module is already loaded, skipping > [Tue Aug 15 09:25:32.753069 2017] [so:warn] [pid 2600] AH01574: module dav_module is already loaded, skipping > [Tue Aug 15 09:25:32.753092 2017] [so:warn] [pid 2600] AH01574: module dav_fs_module is already loaded, skipping > [Tue Aug 15 09:25:32.754627 2017] [so:warn] [pid 2600] AH01574: module mpm_prefork_module is already loaded, skipping > [Tue Aug 15 09:25:32.754686 2017] [so:warn] [pid 2600] AH01574: module proxy_module is already loaded, skipping > [Tue Aug 15 09:25:32.756981 2017] [so:warn] [pid 2600] AH01574: module proxy_http_module is already loaded, skipping > [Tue Aug 15 09:25:32.757423 2017] [so:warn] [pid 2600] AH01574: module ssl_module is already loaded, skipping > [Tue Aug 15 09:25:32.757480 2017] [so:warn] [pid 2600] AH01574: module systemd_module is already loaded, skipping > [Tue Aug 15 09:25:32.757586 2017] [so:warn] [pid 2600] AH01574: module cgi_module is already loaded, skipping > [Tue Aug 15 09:25:32.766868 2017] [alias:warn] [pid 2600] AH00671: The Alias directive in /etc/httpd/conf.d/autoindex.conf at line 21 will probably never match because it overlaps an earlier Alias. > [Tue Aug 15 09:25:32.767816 2017] [mime_magic:error] [pid 2600] (2)No such file or directory: AH01515: mod_mime_magic: can't read magic file /etc/httpd/NEVER_EVER_USE > [Tue Aug 15 09:25:32.767851 2017] [auth_digest:notice] [pid 2600] AH01757: generating secret for digest authentication ... > [Tue Aug 15 09:25:32.767898 2017] [auth_digest:error] [pid 2600] (2)No such file or directory: AH01762: Failed to create shared memory segment on file /run/httpd/authdigest_shm.2600 > [Tue Aug 15 09:25:32.767917 2017] [auth_digest:error] [pid 2600] (2)No such file or directory: AH01760: failed to initialize shm - all nonce-count checking, one-time nonces, and MD5-sess algorithm disabled > [Tue Aug 15 09:25:32.767924 2017] [:emerg] [pid 2600] AH00020: Configuration Failed, exiting > /usr/share/passenger/helper-scripts/prespawn:113:in `initialize': No route to host - connect(2) (Errno::EHOSTUNREACH) > from /usr/share/passenger/helper-scripts/prespawn:113:in `new' > from /usr/share/passenger/helper-scripts/prespawn:113:in `rescue in connect' > from /usr/share/passenger/helper-scripts/prespawn:111:in `connect' > from /usr/share/passenger/helper-scripts/prespawn:87:in `socket' > from /usr/share/passenger/helper-scripts/prespawn:91:in `head_request' > from /usr/share/passenger/helper-scripts/prespawn:153:in `' > /usr/share/passenger/helper-scripts/prespawn:113:in `initialize': No route to host - connect(2) (Errno::EHOSTUNREACH) > from /usr/share/passenger/helper-scripts/prespawn:113:in `new' > from /usr/share/passenger/helper-scripts/prespawn:113:in `rescue in connect' > from /usr/share/passenger/helper-scripts/prespawn:111:in `connect' > from /usr/share/passenger/helper-scripts/prespawn:120:in `connect' > from /usr/share/passenger/helper-scripts/prespawn:87:in `socket' > from /usr/share/passenger/helper-scripts/prespawn:91:in `head_request' > from /usr/share/passenger/helper-scripts/prespawn:153:in `' > /usr/share/passenger/helper-scripts/prespawn:113:in `initialize': No route to host - connect(2) (Errno::EHOSTUNREACH) > from /usr/share/passenger/helper-scripts/prespawn:113:in `new' > from /usr/share/passenger/helper-scripts/prespawn:113:in `rescue in connect' > from /usr/share/passenger/helper-scripts/prespawn:111:in `connect' > from /usr/share/passenger/helper-scripts/prespawn:120:in `connect' > from /usr/share/passenger/helper-scripts/prespawn:87:in `socket' > from /usr/share/passenger/helper-scripts/prespawn:91:in `head_request' > from /usr/share/passenger/helper-scripts/prespawn:153:in `' > > Starting at the top I do not see the module mod_mime_magic being loaded from any of the conf files. > > Any ideas on what I do now? > > Louis > >> On Aug 15, 2017, at 9:06 AM, Louis Bohm <louisbohm@gmail.com > wrote: >> >> As with mongodb postgresql was also complaining about its pid directory: >> >> Aug 15 09:02:35 fm systemd: Starting PostgreSQL database server... >> Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT LOG: could not bind IPv6 socket: Cannot assign requested address >> Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry. >> Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT FATAL: could not create lock file "/var/run/postgresql/.s.PGSQL.5432.lock": No such file or directory >> Aug 15 09:02:36 fm pg_ctl: pg_ctl: could not start server >> Aug 15 09:02:36 fm pg_ctl: Examine the log output. >> >> And again once i created the dir /var/run/postgresql and set its perms/owner/group postgresql starts up fine. >> >> Louis >> >> On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote: >> We are happy to announce the GA of Katello 3.4.4. This release contains a large number of bug fixes for both small UI issues, user issues found while using 3.4.4 and developer found issues that we felt would bring more stability to users. >> >> The highlights are too numerous to outline here, so I would recommend to please look at the changelog for a full list of changes: >> >> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md >> >> Installation: >> https://theforeman.org/plugins/katello/3.4/installation/index.html >> >> Upgrade: >> https://theforeman.org/plugins/katello/3.4/upgrade/index.html >> >> >> Bug reporting >> ============= >> If you come across a bug in your testing, please file it and note the >> version of Katello or Foreman that you're using in the report. >> >> http://projects.theforeman.org/projects/katello/issues/new >> >> -- >> Eric D. Helms >> Red Hat Engineering >> >> -- >> You received this message because you are subscribed to a topic in the Google Groups "Foreman users" group. >> To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/Gmo72QQW86A/unsubscribe . >> To unsubscribe from this group and all its topics, 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 . > > > -- > 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 op
17

So I continued on with a yum clean all and a yum -y update. They went fine. So then I tried foreman-installer —scenario katello —upgrade and that failed on mongoldb and then postgresql.

[root@fm ~]# foreman-installer --scenario katello --upgrade
Upgrading, to monitor the progress on all related services, please do:
foreman-tail | tee upgrade-$(date +%Y-%m-%d-%H%M).log
Upgrade Step: stop_services…
/usr/sbin/service-wait goferd stop
Redirecting to /bin/systemctl stop goferd.service

/usr/sbin/service-wait foreman-tasks stop
Redirecting to /bin/systemctl stop foreman-tasks.service

/usr/sbin/service-wait httpd stop
Redirecting to /bin/systemctl stop httpd.service

/usr/sbin/service-wait pulp_celerybeat stop
Redirecting to /bin/systemctl stop pulp_celerybeat.service

/usr/sbin/service-wait foreman-proxy stop
Redirecting to /bin/systemctl stop foreman-proxy.service

/usr/sbin/service-wait pulp_streamer stop
Redirecting to /bin/systemctl stop pulp_streamer.service

/usr/sbin/service-wait pulp_resource_manager stop
Redirecting to /bin/systemctl stop pulp_resource_manager.service

/usr/sbin/service-wait pulp_workers stop
Redirecting to /bin/systemctl stop pulp_workers.service

/usr/sbin/service-wait tomcat stop
Redirecting to /bin/systemctl stop tomcat.service

/usr/sbin/service-wait squid stop
Redirecting to /bin/systemctl stop squid.service

/usr/sbin/service-wait qdrouterd stop
Redirecting to /bin/systemctl stop qdrouterd.service

/usr/sbin/service-wait qpidd stop
Redirecting to /bin/systemctl stop qpidd.service

Success!
katello-service stop --exclude mongod,postgresql finished successfully!
Upgrade Step: start_databases…
/usr/sbin/service-wait mongod start
Redirecting to /bin/systemctl start mongod.service
Job for mongod.service failed because the control process exited with error code. See "systemctl status mongod.service" and "journalctl -xe" for details.

/usr/sbin/service-wait postgresql start
Redirecting to /bin/systemctl start postgresql.service
Job for postgresql.service failed because the control process exited with error code. See "systemctl status postgresql.service" and "journalctl -xe" for details.
touch: cannot touch ‘/var/lock/subsys/postgresql’: No such file or directory
head: cannot open ‘/var/lib/pgsql/data/postmaster.pid’ for reading: No such file or directory

Some services failed to start: mongod
katello-service start --only mongod,postgresql failed! Check the output for error!
Upgrade step start_databases failed. Check logs for more information.

And here is the mongodb errors:
[root@fm ~]# systemctl status mongod.service -l
● mongod.service - High-performance, schema-free document-oriented database
Loaded: loaded (/usr/lib/systemd/system/mongod.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2017-08-14 17:41:50 EDT; 3min 15s ago
Process: 13607 ExecStart=/usr/bin/mongod $OPTIONS run (code=exited, status=1/FAILURE)

Aug 14 17:41:50 fm.tdsops.com systemd[1]: Starting High-performance, schema-free document-oriented database…
Aug 14 17:41:50 fm.tdsops.com mongod[13607]: about to fork child process, waiting until server is ready for connections.
Aug 14 17:41:50 fm.tdsops.com mongod[13607]: forked process: 13609
Aug 14 17:41:50 fm.tdsops.com mongod[13607]: ERROR: child process failed, exited with error number 1
Aug 14 17:41:50 fm.tdsops.com systemd[1]: mongod.service: control process exited, code=exited status=1
Aug 14 17:41:50 fm.tdsops.com systemd[1]: Failed to start High-performance, schema-free document-oriented database.
Aug 14 17:41:50 fm.tdsops.com systemd[1]: Unit mongod.service entered failed state.
Aug 14 17:41:50 fm.tdsops.com systemd[1]: mongod.service failed.
and the postgresql errors:
[root@fm ~]# systemctl status postgresql.service -l
● postgresql.service - PostgreSQL database server
Loaded: loaded (/etc/systemd/system/postgresql.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2017-08-14 17:41:58 EDT; 4min 10s ago
Process: 13644 ExecStart=/usr/bin/pg_ctl start -D ${PGDATA} -s -o -p ${PGPORT} -w -t 300 (code=exited, status=1/FAILURE)
Process: 13637 ExecStartPre=/usr/bin/postgresql-check-db-dir ${PGDATA} (code=exited, status=0/SUCCESS)

Aug 14 17:41:57 fm.tdsops.com systemd[1]: Starting PostgreSQL database server…
Aug 14 17:41:57 fm.tdsops.com pg_ctl[13644]: 2017-08-14 17:41:57 EDT LOG: could not bind IPv6 socket: Cannot assign requested address
Aug 14 17:41:57 fm.tdsops.com pg_ctl[13644]: 2017-08-14 17:41:57 EDT HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
Aug 14 17:41:57 fm.tdsops.com pg_ctl[13644]: 2017-08-14 17:41:57 EDT FATAL: could not create lock file "/var/run/postgresql/.s.PGSQL.5432.lock": No such file or directory
Aug 14 17:41:58 fm.tdsops.com pg_ctl[13644]: pg_ctl: could not start server
Aug 14 17:41:58 fm.tdsops.com pg_ctl[13644]: Examine the log output.
Aug 14 17:41:58 fm.tdsops.com systemd[1]: postgresql.service: control process exited, code=exited status=1
Aug 14 17:41:58 fm.tdsops.com systemd[1]: Failed to start PostgreSQL database server.
Aug 14 17:41:58 fm.tdsops.com systemd[1]: Unit postgresql.service entered failed state.
Aug 14 17:41:58 fm.tdsops.com systemd[1]: postgresql.service failed.

Should I point out that this system was working perfectly fine before the upgrade. Glad I have a VM snapshot to fall back on.

Louis

··· > On Aug 14, 2017, at 5:36 PM, Louis Bohm wrote: > > So this time when I did yum update http://yum.theforeman.org/releases/1.15/el7/x86_64/foreman-release.rpm it worked. However, the next step yum update -y foreman-release-scll found nothing to update. > [root@fm ~]# yum update -y foreman-release-scl > Loaded plugins: fastestmirror, package_upload, product-id, search-disabled-repos, subscription- > : manager, tracer_upload > Loading mirror speeds from cached hostfile > * base: mirrors.lga7.us.voxel.net > * epel: mirrors.mit.edu > * extras: mirrors.tripadvisor.com > * updates: mirror.trouble-free.net > No packages marked for update > > Shouldn’t there be updates in this step? > > Louis >> On Aug 14, 2017, at 5:29 PM, Louis Bohm <louisbohm@gmail.com > wrote: >> >> Thank you. >> >> This time I tried something different. Before doing anything I removed foreman-plugin. Then I started the upgrade. I will let you know how it goes. >> >> Louis >>> On Aug 14, 2017, at 4:36 PM, Eric D Helms <ericdhelms@gmail.com > wrote: >>> >>> 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 <louisbohm@gmail.com > wrote: >>> I love having infinite history... Here is the ouput of the command: >>> [root@fm yum.repos.d]# yum update http://yum.theforeman.org/releases/1.15/el7/x86_64/foreman-release.rpm >>> Loaded plugins: fastestmirror, package_upload, product-id, search-disabled-repos, subscription- >>> : manager, tracer_upload >>> foreman-release.rpm | 16 kB 00:00:00 >>> Examining /var/tmp/yum-root-qoYoPs/foreman-release.rpm: foreman-release-1.15.3-1.el7.noarch >>> Marking /var/tmp/yum-root-qoYoPs/foreman-release.rpm as an update to foreman-release-1.14.3-1.el7.noarch >>> Resolving Dependencies >>> --> Running transaction check >>> ---> Package foreman-release.noarch 0:1.14.3-1.el7 will be updated >>> --> Processing Dependency: foreman-release = 1.14.3-1.el7 for package: foreman-plugin-1.14.3-1.el7.noarch >>> Loading mirror speeds from cached hostfile >>> * base: ftpmirror.your.org >>> * epel: mirror.metrocast.net >>> * extras: mirrors.centos.webair.com >>> * updates: mirrors.lga7.us.voxel.net >>> ---> Package foreman-release.noarch 0:1.15.3-1.el7 will be an update >>> --> Finished Dependency Resolution >>> Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman) >>> Requires: foreman-release = 1.14.3-1.el7 >>> Removing: foreman-release-1.14.3-1.el7.noarch (@foreman) >>> foreman-release = 1.14.3-1.el7 >>> Updated By: foreman-release-1.15.3-1.el7.noarch (/foreman-release) >>> foreman-release = 1.15.3-1.el7 >>> Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman) >>> foreman-release = 1.14.0-0.1.RC1.el7 >>> Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman) >>> foreman-release = 1.14.0-0.1.RC2.el7 >>> Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman) >>> foreman-release = 1.14.0-0.1.RC3.el7 >>> Available: foreman-release-1.14.0-1.el7.noarch (foreman) >>> foreman-release = 1.14.0-1.el7 >>> Available: foreman-release-1.14.1-1.el7.noarch (foreman) >>> foreman-release = 1.14.1-1.el7 >>> Available: foreman-release-1.14.2-1.el7.noarch (foreman) >>> foreman-release = 1.14.2-1.el7 >>> ********************************************************************** >>> yum can be configured to try to resolve such errors by temporarily enabling >>> disabled repos and searching for missing dependencies. >>> To enable this functionality please set 'notify_only=0' in /etc/yum/pluginconf.d/search-disabled-repos.conf >>> ********************************************************************** >>> >>> Error: Package: foreman-plugin-1.14.3-1.el7.noarch (@foreman) >>> Requires: foreman-release = 1.14.3-1.el7 >>> Removing: foreman-release-1.14.3-1.el7.noarch (@foreman) >>> foreman-release = 1.14.3-1.el7 >>> Updated By: foreman-release-1.15.3-1.el7.noarch (/foreman-release) >>> foreman-release = 1.15.3-1.el7 >>> Available: foreman-release-1.14.0-0.1.RC1.el7.noarch (foreman) >>> foreman-release = 1.14.0-0.1.RC1.el7 >>> Available: foreman-release-1.14.0-0.1.RC2.el7.noarch (foreman) >>> foreman-release = 1.14.0-0.1.RC2.el7 >>> Available: foreman-release-1.14.0-0.1.RC3.el7.noarch (foreman) >>> foreman-release = 1.14.0-0.1.RC3.el7 >>> Available: foreman-release-1.14.0-1.el7.noarch (foreman) >>> foreman-release = 1.14.0-1.el7 >>> Available: foreman-release-1.14.1-1.el7.noarch (foreman) >>> foreman-release = 1.14.1-1.el7 >>> Available: foreman-release-1.14.2-1.el7.noarch (foreman) >>> foreman-release = 1.14.2-1.el7 >>> You could try using --skip-broken to work around the problem >>> You could try running: rpm -Va --nofiles --nodigest >>> >>> Louis >>> >>> On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote: >>> We are happy to announce the GA of Katello 3.4.4. This release contains a large number of bug fixes for both small UI issues, user issues found while using 3.4.4 and developer found issues that we felt would bring more stability to users. >>> >>> The highlights are too numerous to outline here, so I would recommend to please look at the changelog for a full list of changes: >>> >>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md >>> >>> Installation: >>> https://theforeman.org/plugins/katello/3.4/installation/index.html >>> >>> Upgrade: >>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html >>> >>> >>> Bug reporting >>> ============= >>> If you come across a bug in your testing, please file it and note the >>> version of Katello or Foreman that you're using in the report. >>> >>> http://projects.theforeman.org/projects/katello/issues/new >>> >>> -- >>> Eric D. Helms >>> Red Hat Engineering >>> >>> -- >>> 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 . >>> >>> >>> >>> -- >>> Eric D. Helms >>> Red Hat Engineering >>> >>> -- >>> You received this message because you are subscribed to a topic in the Google Groups "Foreman users" group. >>> To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/Gmo72QQW86A/unsubscribe . >>> To unsubscribe from this group and all its topics, 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 . >> >
18

Absolutely, every time. Can you double check? Or show a screenshot of what
you looked at that didn't have it?

··· On Aug 15, 2017 11:48 AM, "Louis Bohm" wrote:

No. Its not on the Katello upgrade page. Am I supposed to?

Louis

On Aug 15, 2017, at 10:59 AM, Eric D Helms ericdhelms@gmail.com wrote:

You ran ‘foreman-installer --upgrade’ once you updated the RPMs?

On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm louisbohm@gmail.com 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 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 sockets available, shutting down

So I took a look and noticed that Listen 443 was listed twice. Once in
/etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf. Thats not
good. So I commented out the one in ports.conf and restarted it.

Now when it fails I get a log more information. From
/var/log/httpd/error_log I see:

[Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No
such file or directory: AH01515: mod_mime_magic: can’t read magic file
/etc/httpd/NEVER_EVER_USE
[Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init:
Name-based SSL virtual hosts only work for clients with TLS server name
indication support (RFC 4366)
[Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232:
suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538
]: Options: { ‘analytics_log_user’ => ‘nobody’, ‘default_group’ =>
‘nobody’, ‘default_python’ => ‘python’, ‘default_ruby’ => ‘ruby’,
‘default_user’ => ‘nobody’, ‘log_level’ => ‘0’, ‘max_pool_size’ => ‘12’,
‘passenger_root’ => ‘/usr/share/passenger//phusion_passenger/locations.ini’,
‘passenger_version’ => ‘4.0.53’, ‘pool_idle_time’ => ‘300’, ‘prestart_urls’
=> ‘aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29
tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=’, ‘temp_dir’ => ‘/tmp’,
‘union_station_gateway_address’ => ‘gateway.unionstationapp.com’,
‘union_station_gateway_port’ => ‘443’, ‘user_switching’ => ‘true’,
‘web_server_passenger_version’ => ‘4.0.53’, ‘web_server_pid’ => ‘2600’,
‘web_server_type’ => ‘apache’, ‘web_server_worker_gid’ => ‘48’,
‘web_server_worker_uid’ => ‘48’ }
[ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780
agents/HelperAgent/Main.cpp:650 ]: PassengerHelperAgent online,
listening at unix:/tmp/passenger.1.0.2600/generation-0/request
[ 2017-08-15 09:25:32.6930 2609/7fd0539ea880
agents/LoggingAgent/Main.cpp:321 ]: PassengerLoggingAgent online,
listening at unix:/tmp/passenger.1.0.2600/generation-0/logging
[ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728
]: All Phusion Passenger agents started!
[Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module
access_compat_module is already loaded, skipping
[Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module
actions_module is already loaded, skipping
[Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module
alias_module is already loaded, skipping
[Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module
auth_basic_module is already loaded, skipping
[Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module
auth_digest_module is already loaded, skipping
[Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module
authn_anon_module is already loaded, skipping
[Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module
authn_core_module is already loaded, skipping
[Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module
authn_dbm_module is already loaded, skipping
[Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module
authn_file_module is already loaded, skipping
[Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module
authz_core_module is already loaded, skipping
[Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module
authz_dbm_module is already loaded, skipping
[Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module
authz_groupfile_module is already loaded, skipping
[Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module
authz_host_module is already loaded, skipping
[Tue Aug 15 09:25:32.749164 2017] [so:warn] [pid 2600] AH01574: module
authz_owner_module is already loaded, skipping
[Tue Aug 15 09:25:32.749263 2017] [so:warn] [pid 2600] AH01574: module
authz_user_module is already loaded, skipping
[Tue Aug 15 09:25:32.749294 2017] [so:warn] [pid 2600] AH01574: module
autoindex_module is already loaded, skipping
[Tue Aug 15 09:25:32.749316 2017] [so:warn] [pid 2600] AH01574: module
cache_module is already loaded, skipping
[Tue Aug 15 09:25:32.749985 2017] [so:warn] [pid 2600] AH01574: module
deflate_module is already loaded, skipping
[Tue Aug 15 09:25:32.750009 2017] [so:warn] [pid 2600] AH01574: module
dir_module is already loaded, skipping
[Tue Aug 15 09:25:32.750350 2017] [so:warn] [pid 2600] AH01574: module
env_module is already loaded, skipping
[Tue Aug 15 09:25:32.750379 2017] [so:warn] [pid 2600] AH01574: module
expires_module is already loaded, skipping
[Tue Aug 15 09:25:32.750398 2017] [so:warn] [pid 2600] AH01574: module
ext_filter_module is already loaded, skipping
[Tue Aug 15 09:25:32.750420 2017] [so:warn] [pid 2600] AH01574: module
filter_module is already loaded, skipping
[Tue Aug 15 09:25:32.750523 2017] [so:warn] [pid 2600] AH01574: module
headers_module is already loaded, skipping
[Tue Aug 15 09:25:32.750630 2017] [so:warn] [pid 2600] AH01574: module
include_module is already loaded, skipping
[Tue Aug 15 09:25:32.750973 2017] [so:warn] [pid 2600] AH01574: module
log_config_module is already loaded, skipping
[Tue Aug 15 09:25:32.750998 2017] [so:warn] [pid 2600] AH01574: module
logio_module is already loaded, skipping
[Tue Aug 15 09:25:32.751015 2017] [so:warn] [pid 2600] AH01574: module
mime_magic_module is already loaded, skipping
[Tue Aug 15 09:25:32.751036 2017] [so:warn] [pid 2600] AH01574: module
mime_module is already loaded, skipping
[Tue Aug 15 09:25:32.751127 2017] [so:warn] [pid 2600] AH01574: module
negotiation_module is already loaded, skipping
[Tue Aug 15 09:25:32.751626 2017] [so:warn] [pid 2600] AH01574: module
rewrite_module is already loaded, skipping
[Tue Aug 15 09:25:32.751655 2017] [so:warn] [pid 2600] AH01574: module
setenvif_module is already loaded, skipping
[Tue Aug 15 09:25:32.752388 2017] [so:warn] [pid 2600] AH01574: module
socache_shmcb_module is already loaded, skipping
[Tue Aug 15 09:25:32.752593 2017] [so:warn] [pid 2600] AH01574: module
substitute_module is already loaded, skipping
[Tue Aug 15 09:25:32.752622 2017] [so:warn] [pid 2600] AH01574: module
suexec_module is already loaded, skipping
[Tue Aug 15 09:25:32.752799 2017] [so:warn] [pid 2600] AH01574: module
unixd_module is already loaded, skipping
[Tue Aug 15 09:25:32.752995 2017] [so:warn] [pid 2600] AH01574: module
version_module is already loaded, skipping
[Tue Aug 15 09:25:32.753025 2017] [so:warn] [pid 2600] AH01574: module
vhost_alias_module is already loaded, skipping
[Tue Aug 15 09:25:32.753069 2017] [so:warn] [pid 2600] AH01574: module
dav_module is already loaded, skipping
[Tue Aug 15 09:25:32.753092 2017] [so:warn] [pid 2600] AH01574: module
dav_fs_module is already loaded, skipping
[Tue Aug 15 09:25:32.754627 2017] [so:warn] [pid 2600] AH01574: module
mpm_prefork_module is already loaded, skipping
[Tue Aug 15 09:25:32.754686 2017] [so:warn] [pid 2600] AH01574: module
proxy_module is already loaded, skipping
[Tue Aug 15 09:25:32.756981 2017] [so:warn] [pid 2600] AH01574: module
proxy_http_module is already loaded, skipping
[Tue Aug 15 09:25:32.757423 2017] [so:warn] [pid 2600] AH01574: module
ssl_module is already loaded, skipping
[Tue Aug 15 09:25:32.757480 2017] [so:warn] [pid 2600] AH01574: module
systemd_module is already loaded, skipping
[Tue Aug 15 09:25:32.757586 2017] [so:warn] [pid 2600] AH01574: module
cgi_module is already loaded, skipping
[Tue Aug 15 09:25:32.766868 2017] [alias:warn] [pid 2600] AH00671: The
Alias directive in /etc/httpd/conf.d/autoindex.conf at line 21 will
probably never match because it overlaps an earlier Alias.
[Tue Aug 15 09:25:32.767816 2017] [mime_magic:error] [pid 2600] (2)No
such file or directory: AH01515: mod_mime_magic: can’t read magic file
/etc/httpd/NEVER_EVER_USE
[Tue Aug 15 09:25:32.767851 2017] [auth_digest:notice] [pid 2600]
AH01757: generating secret for digest authentication …
[Tue Aug 15 09:25:32.767898 2017] [auth_digest:error] [pid 2600] (2)No
such file or directory: AH01762: Failed to create shared memory segment on
file /run/httpd/authdigest_shm.2600
[Tue Aug 15 09:25:32.767917 2017] [auth_digest:error] [pid 2600] (2)No
such file or directory: AH01760: failed to initialize shm - all nonce-count
checking, one-time nonces, and MD5-sess algorithm disabled
[Tue Aug 15 09:25:32.767924 2017] [:emerg] [pid 2600] AH00020:
Configuration Failed, exiting
/usr/share/passenger/helper-scripts/prespawn:113:in initialize': No route to host - connect(2) (Errno::EHOSTUNREACH) from /usr/share/passenger/helper-scripts/prespawn:113:innew’
from /usr/share/passenger/helper-scripts/prespawn:113:in rescue in connect' from /usr/share/passenger/helper-scripts/prespawn:111:inconnect’
from /usr/share/passenger/helper-scripts/prespawn:87:in socket' from /usr/share/passenger/helper-scripts/prespawn:91:inhead_request’
from /usr/share/passenger/helper-scripts/prespawn:153:in <main>' /usr/share/passenger/helper-scripts/prespawn:113:ininitialize’: No
route to host - connect(2) (Errno::EHOSTUNREACH)
from /usr/share/passenger/helper-scripts/prespawn:113:in new' from /usr/share/passenger/helper-scripts/prespawn:113:inrescue in
connect’
from /usr/share/passenger/helper-scripts/prespawn:111:in connect' from /usr/share/passenger/helper-scripts/prespawn:120:inconnect’
from /usr/share/passenger/helper-scripts/prespawn:87:in socket' from /usr/share/passenger/helper-scripts/prespawn:91:inhead_request’
from /usr/share/passenger/helper-scripts/prespawn:153:in <main>' /usr/share/passenger/helper-scripts/prespawn:113:ininitialize’: No
route to host - connect(2) (Errno::EHOSTUNREACH)
from /usr/share/passenger/helper-scripts/prespawn:113:in new' from /usr/share/passenger/helper-scripts/prespawn:113:inrescue in
connect’
from /usr/share/passenger/helper-scripts/prespawn:111:in connect' from /usr/share/passenger/helper-scripts/prespawn:120:inconnect’
from /usr/share/passenger/helper-scripts/prespawn:87:in socket' from /usr/share/passenger/helper-scripts/prespawn:91:inhead_request’
from /usr/share/passenger/helper-scripts/prespawn:153:in `’

Starting at the top I do not see the module mod_mime_magic being loaded
from any of the conf files.

Any ideas on what I do now?

Louis

On Aug 15, 2017, at 9:06 AM, Louis Bohm louisbohm@gmail.com wrote:

As with mongodb postgresql was also complaining about its pid directory:

Aug 15 09:02:35 fm systemd: Starting PostgreSQL database server…
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT LOG: could not bind
IPv6 socket: Cannot assign requested address
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT HINT: Is another
postmaster already running on port 5432? If not, wait a few seconds and
retry.
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT FATAL: could not
create lock file “/var/run/postgresql/.s.PGSQL.5432.lock”: No such file
or directory
Aug 15 09:02:36 fm pg_ctl: pg_ctl: could not start server
Aug 15 09:02:36 fm pg_ctl: Examine the log output.

And again once i created the dir /var/run/postgresql and set its
perms/owner/group postgresql starts up fine.

Louis

On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:

We are happy to announce the GA of Katello 3.4.4. This release contains
a large number of bug fixes for both small UI issues, user issues found
while using 3.4.4 and developer found issues that we felt would bring more
stability to users.

The highlights are too numerous to outline here, so I would recommend to
please look at the changelog for a full list of changes:

https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md

Installation:
Foreman :: Plugin Manuals

Upgrade:
Foreman :: Plugin Manuals

Bug reporting

If you come across a bug in your testing, please file it and note the
version of Katello or Foreman that you’re using in the report.

Foreman

–
Eric D. Helms
Red Hat Engineering

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/to
pic/foreman-users/Gmo72QQW86A/unsubscribe.
To unsubscribe from this group and all its topics, 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.

–
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.

–
Eric D. Helms
Red Hat Engineering

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/foreman-users/Gmo72QQW86A/unsubscribe.
To unsubscribe from this group and all its topics, 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.

–
You received this mes

19

Here is the documentation and it does not show it. I also do not remember it when I went from 3.2 to 3.3. But I will run it.

Louis

··· > On Aug 15, 2017, at 11:59 AM, Eric D Helms wrote: > > Absolutely, every time. Can you double check? Or show a screenshot of what you looked at that didn't have it? > > > On Aug 15, 2017 11:48 AM, "Louis Bohm" <louisbohm@gmail.com > wrote: > No. Its not on the Katello upgrade page. Am I supposed to? > > Louis >> On Aug 15, 2017, at 10:59 AM, Eric D Helms <ericdhelms@gmail.com > wrote: >> >> You ran 'foreman-installer --upgrade' once you updated the RPMs? >> >> On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm <louisbohm@gmail.com > 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 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 sockets available, shutting down >> >> So I took a look and noticed that Listen 443 was listed twice. Once in /etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf. Thats not good. So I commented out the one in ports.conf and restarted it. >> >> Now when it fails I get a log more information. From /var/log/httpd/error_log I see: >> >> [Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No such file or directory: AH01515: mod_mime_magic: can't read magic file /etc/httpd/NEVER_EVER_USE >> [Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366) >> [Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) >> [ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:538 ]: Options: { 'analytics_log_user' => 'nobody', 'default_group' => 'nobody', 'default_python' => 'python', 'default_ruby' => 'ruby', 'default_user' => 'nobody', 'log_level' => '0', 'max_pool_size' => '12', 'passenger_root' => '/usr/share/passenger//phusion_passenger/locations.ini', 'passenger_version' => '4.0.53', 'pool_idle_time' => '300', 'prestart_urls' => 'aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=', 'temp_dir' => '/tmp', 'union_station_gateway_address' => 'gateway.unionstationapp.com ', 'union_station_gateway_port' => '443', 'user_switching' => 'true', 'web_server_passenger_version' => '4.0.53', 'web_server_pid' => '2600', 'web_server_type' => 'apache', 'web_server_worker_gid' => '48', 'web_server_worker_uid' => '48' } >> [ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780 agents/HelperAgent/Main.cpp:650 ]: PassengerHelperAgent online, listening at unix:/tmp/passenger.1.0.2600/generation-0/request >> [ 2017-08-15 09:25:32.6930 2609/7fd0539ea880 agents/LoggingAgent/Main.cpp:321 ]: PassengerLoggingAgent online, listening at unix:/tmp/passenger.1.0.2600/generation-0/logging >> [ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780 agents/Watchdog/Main.cpp:728 ]: All Phusion Passenger agents started! >> [Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module access_compat_module is already loaded, skipping >> [Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module actions_module is already loaded, skipping >> [Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module alias_module is already loaded, skipping >> [Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module auth_basic_module is already loaded, skipping >> [Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module auth_digest_module is already loaded, skipping >> [Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module authn_anon_module is already loaded, skipping >> [Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module authn_core_module is already loaded, skipping >> [Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module authn_dbm_module is already loaded, skipping >> [Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module authn_file_module is already loaded, skipping >> [Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module authz_core_module is already loaded, skipping >> [Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module authz_dbm_module is already loaded, skipping >> [Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module authz_groupfile_module is already loaded, skipping >> [Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module authz_host_module is already loaded, skipping >> [Tue Aug 15 09:25:32.749164 2017] [so:warn] [pid 2600] AH01574: module authz_owner_module is already loaded, skipping >> [Tue Aug 15 09:25:32.749263 2017] [so:warn] [pid 2600] AH01574: module authz_user_module is already loaded, skipping >> [Tue Aug 15 09:25:32.749294 2017] [so:warn] [pid 2600] AH01574: module autoindex_module is already loaded, skipping >> [Tue Aug 15 09:25:32.749316 2017] [so:warn] [pid 2600] AH01574: module cache_module is already loaded, skipping >> [Tue Aug 15 09:25:32.749985 2017] [so:warn] [pid 2600] AH01574: module deflate_module is already loaded, skipping >> [Tue Aug 15 09:25:32.750009 2017] [so:warn] [pid 2600] AH01574: module dir_module is already loaded, skipping >> [Tue Aug 15 09:25:32.750350 2017] [so:warn] [pid 2600] AH01574: module env_module is already loaded, skipping >> [Tue Aug 15 09:25:32.750379 2017] [so:warn] [pid 2600] AH01574: module expires_module is already loaded, skipping >> [Tue Aug 15 09:25:32.750398 2017] [so:warn] [pid 2600] AH01574: module ext_filter_module is already loaded, skipping >> [Tue Aug 15 09:25:32.750420 2017] [so:warn] [pid 2600] AH01574: module filter_module is already loaded, skipping >> [Tue Aug 15 09:25:32.750523 2017] [so:warn] [pid 2600] AH01574: module headers_module is already loaded, skipping >> [Tue Aug 15 09:25:32.750630 2017] [so:warn] [pid 2600] AH01574: module include_module is already loaded, skipping >> [Tue Aug 15 09:25:32.750973 2017] [so:warn] [pid 2600] AH01574: module log_config_module is already loaded, skipping >> [Tue Aug 15 09:25:32.750998 2017] [so:warn] [pid 2600] AH01574: module logio_module is already loaded, skipping >> [Tue Aug 15 09:25:32.751015 2017] [so:warn] [pid 2600] AH01574: module mime_magic_module is already loaded, skipping >> [Tue Aug 15 09:25:32.751036 2017] [so:warn] [pid 2600] AH01574: module mime_module is already loaded, skipping >> [Tue Aug 15 09:25:32.751127 2017] [so:warn] [pid 2600] AH01574: module negotiation_module is already loaded, skipping >> [Tue Aug 15 09:25:32.751626 2017] [so:warn] [pid 2600] AH01574: module rewrite_module is already loaded, skipping >> [Tue Aug 15 09:25:32.751655 2017] [so:warn] [pid 2600] AH01574: module setenvif_module is already loaded, skipping >> [Tue Aug 15 09:25:32.752388 2017] [so:warn] [pid 2600] AH01574: module socache_shmcb_module is already loaded, skipping >> [Tue Aug 15 09:25:32.752593 2017] [so:warn] [pid 2600] AH01574: module substitute_module is already loaded, skipping >> [Tue Aug 15 09:25:32.752622 2017] [so:warn] [pid 2600] AH01574: module suexec_module is already loaded, skipping >> [Tue Aug 15 09:25:32.752799 2017] [so:warn] [pid 2600] AH01574: module unixd_module is already loaded, skipping >> [Tue Aug 15 09:25:32.752995 2017] [so:warn] [pid 2600] AH01574: module version_module is already loaded, skipping >> [Tue Aug 15 09:25:32.753025 2017] [so:warn] [pid 2600] AH01574: module vhost_alias_module is already loaded, skipping >> [Tue Aug 15 09:25:32.753069 2017] [so:warn] [pid 2600] AH01574: module dav_module is already loaded, skipping >> [Tue Aug 15 09:25:32.753092 2017] [so:warn] [pid 2600] AH01574: module dav_fs_module is already loaded, skipping >> [Tue Aug 15 09:25:32.754627 2017] [so:warn] [pid 2600] AH01574: module mpm_prefork_module is already loaded, skipping >> [Tue Aug 15 09:25:32.754686 2017] [so:warn] [pid 2600] AH01574: module proxy_module is already loaded, skipping >> [Tue Aug 15 09:25:32.756981 2017] [so:warn] [pid 2600] AH01574: module proxy_http_module is already loaded, skipping >> [Tue Aug 15 09:25:32.757423 2017] [so:warn] [pid 2600] AH01574: module ssl_module is already loaded, skipping >> [Tue Aug 15 09:25:32.757480 2017] [so:warn] [pid 2600] AH01574: module systemd_module is already loaded, skipping >> [Tue Aug 15 09:25:32.757586 2017] [so:warn] [pid 2600] AH01574: module cgi_module is already loaded, skipping >> [Tue Aug 15 09:25:32.766868 2017] [alias:warn] [pid 2600] AH00671: The Alias directive in /etc/httpd/conf.d/autoindex.co nf at line 21 will probably never match because it overlaps an earlier Alias. >> [Tue Aug 15 09:25:32.767816 2017] [mime_magic:error] [pid 2600] (2)No such file or directory: AH01515: mod_mime_magic: can't read magic file /etc/httpd/NEVER_EVER_USE >> [Tue Aug 15 09:25:32.767851 2017] [auth_digest:notice] [pid 2600] AH01757: generating secret for digest authentication ... >> [Tue Aug 15 09:25:32.767898 2017] [auth_digest:error] [pid 2600] (2)No such file or directory: AH01762: Failed to create shared memory segment on file /run/httpd/authdigest_shm.2600 >> [Tue Aug 15 09:25:32.767917 2017] [auth_digest:error] [pid 2600] (2)No such file or directory: AH01760: failed to initialize shm - all nonce-count checking, one-time nonces, and MD5-sess algorithm disabled >> [Tue Aug 15 09:25:32.767924 2017] [:emerg] [pid 2600] AH00020: Configuration Failed, exiting >> /usr/share/passenger/helper-scripts/prespawn:113:in `initialize': No route to host - connect(2) (Errno::EHOSTUNREACH) >> from /usr/share/passenger/helper-scripts/prespawn:113:in `new' >> from /usr/share/passenger/helper-scripts/prespawn:113:in `rescue in connect' >> from /usr/share/passenger/helper-scripts/prespawn:111:in `connect' >> from /usr/share/passenger/helper-scripts/prespawn:87:in `socket' >> from /usr/share/passenger/helper-scripts/prespawn:91:in `head_request' >> from /usr/share/passenger/helper-scripts/prespawn:153:in `' >> /usr/share/passenger/helper-scripts/prespawn:113:in `initialize': No route to host - connect(2) (Errno::EHOSTUNREACH) >> from /usr/share/passenger/helper-scripts/prespawn:113:in `new' >> from /usr/share/passenger/helper-scripts/prespawn:113:in `rescue in connect' >> from /usr/share/passenger/helper-scripts/prespawn:111:in `connect' >> from /usr/share/passenger/helper-scripts/prespawn:120:in `connect' >> from /usr/share/passenger/helper-scripts/prespawn:87:in `socket' >> from /usr/share/passenger/helper-scripts/prespawn:91:in `head_request' >> from /usr/share/passenger/helper-scripts/prespawn:153:in `' >> /usr/share/passenger/helper-scripts/prespawn:113:in `initialize': No route to host - connect(2) (Errno::EHOSTUNREACH) >> from /usr/share/passenger/helper-scripts/prespawn:113:in `new' >> from /usr/share/passenger/helper-scripts/prespawn:113:in `rescue in connect' >> from /usr/share/passenger/helper-scripts/prespawn:111:in `connect' >> from /usr/share/passenger/helper-scripts/prespawn:120:in `connect' >> from /usr/share/passenger/helper-scripts/prespawn:87:in `socket' >> from /usr/share/passenger/helper-scripts/prespawn:91:in `head_request' >> from /usr/share/passenger/helper-scripts/prespawn:153:in `' >> >> Starting at the top I do not see the module mod_mime_magic being loaded from any of the conf files. >> >> Any ideas on what I do now? >> >> Louis >> >>> On Aug 15, 2017, at 9:06 AM, Louis Bohm <louisbohm@gmail.com > wrote: >>> >>> As with mongodb postgresql was also complaining about its pid directory: >>> >>> Aug 15 09:02:35 fm systemd: Starting PostgreSQL database server... >>> Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT LOG: could not bind IPv6 socket: Cannot assign requested address >>> Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry. >>> Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT FATAL: could not create lock file "/var/run/postgresql/.s.PGSQL.5432.lock": No such file or directory >>> Aug 15 09:02:36 fm pg_ctl: pg_ctl: could not start server >>> Aug 15 09:02:36 fm pg_ctl: Examine the log output. >>> >>> And again once i created the dir /var/run/postgresql and set its perms/owner/group postgresql starts up fine. >>> >>> Louis >>> >>> On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote: >>> We are happy to announce the GA of Katello 3.4.4. This release contains a large number of bug fixes for both small UI issues, user issues found while using 3.4.4 and developer found issues that we felt would bring more stability to users. >>> >>> The highlights are too numerous to outline here, so I would recommend to please look at the changelog for a full list of changes: >>> >>> https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md >>> >>> Installation: >>> https://theforeman.org/plugins/katello/3.4/installation/index.html >>> >>> Upgrade: >>> https://theforeman.org/plugins/katello/3.4/upgrade/index.html >>> >>> >>> Bug reporting >>> ============= >>> If you come across a bug in your testing, please file it and note the >>> version of Katello or Foreman that you're using in the report. >>> >>> http://projects.theforeman.org/projects/katello/issues/new >>> >>> -- >>> Eric D. Helms >>> Red Hat Engineering >>> >>> -- >>> You received this message because you are subscribed to a topic in the Google Groups "Foreman users" group. >>> To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/Gmo72QQW86A/unsubscribe . >>> To unsubscribe from this group and all its topics, send an email to foreman-users+unsubscribe@googlegroups.com . >>> To post to this group, send email to foreman-users@googlegroups.com <mailto:foreman-user
20

I did not see anything included. But every upgrade both minor and patch,
since before 2.4 has required using the installer with --upgrade.

Per – Foreman :: Plugin Manuals

Check Step 5

··· On Aug 15, 2017 12:03 PM, "Louis Bohm" wrote:

Here is the documentation and it does not show it. I also do not remember
it when I went from 3.2 to 3.3. But I will run it.

Louis

On Aug 15, 2017, at 11:59 AM, Eric D Helms eric.d.helms@gmail.com wrote:

Absolutely, every time. Can you double check? Or show a screenshot of what
you looked at that didn’t have it?

On Aug 15, 2017 11:48 AM, “Louis Bohm” louisbohm@gmail.com wrote:

No. Its not on the Katello upgrade page. Am I supposed to?

Louis

On Aug 15, 2017, at 10:59 AM, Eric D Helms ericdhelms@gmail.com wrote:

You ran ‘foreman-installer --upgrade’ once you updated the RPMs?

On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm louisbohm@gmail.com 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 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 sockets available, shutting down

So I took a look and noticed that Listen 443 was listed twice. Once in
/etc/httpd/conf/ports.conf and /etc/httpd/conf.d/ssl.conf. Thats not
good. So I commented out the one in ports.conf and restarted it.

Now when it fails I get a log more information. From
/var/log/httpd/error_log I see:

[Tue Aug 15 09:25:32.571019 2017] [mime_magic:error] [pid 2600] (2)No
such file or directory: AH01515: mod_mime_magic: can’t read magic file
/etc/httpd/NEVER_EVER_USE
[Tue Aug 15 09:25:32.607742 2017] [ssl:warn] [pid 2600] AH02292: Init:
Name-based SSL virtual hosts only work for clients with TLS server name
indication support (RFC 4366)
[Tue Aug 15 09:25:32.607817 2017] [suexec:notice] [pid 2600] AH01232:
suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[ 2017-08-15 09:25:32.6255 2601/7f5dfa9d0780
agents/Watchdog/Main.cpp:538 ]: Options: { ‘analytics_log_user’ =>
‘nobody’, ‘default_group’ => ‘nobody’, ‘default_python’ => ‘python’,
‘default_ruby’ => ‘ruby’, ‘default_user’ => ‘nobody’, ‘log_level’ => ‘0’,
‘max_pool_size’ => ‘12’, ‘passenger_root’ => ‘/usr/share/passenger//phusion_passenger/locations.ini’,
‘passenger_version’ => ‘4.0.53’, ‘pool_idle_time’ => ‘300’, ‘prestart_urls’
=> ‘aHR0cDovL2ZtLnRkc29wcy5jb206ODAAaHR0cHM6Ly9mbS50ZHNvcHMuY29
tOjQ0MwBodHRwczovL2ZtLnRkc29wcy5jb206ODE0MAA=’, ‘temp_dir’ => ‘/tmp’,
‘union_station_gateway_address’ => ‘gateway.unionstationapp.com’,
‘union_station_gateway_port’ => ‘443’, ‘user_switching’ => ‘true’,
‘web_server_passenger_version’ => ‘4.0.53’, ‘web_server_pid’ => ‘2600’,
‘web_server_type’ => ‘apache’, ‘web_server_worker_gid’ => ‘48’,
‘web_server_worker_uid’ => ‘48’ }
[ 2017-08-15 09:25:32.6409 2604/7f6b7cdbb780
agents/HelperAgent/Main.cpp:650 ]: PassengerHelperAgent online,
listening at unix:/tmp/passenger.1.0.2600/generation-0/request
[ 2017-08-15 09:25:32.6930 2609/7fd0539ea880
agents/LoggingAgent/Main.cpp:321 ]: PassengerLoggingAgent online,
listening at unix:/tmp/passenger.1.0.2600/generation-0/logging
[ 2017-08-15 09:25:32.6940 2601/7f5dfa9d0780
agents/Watchdog/Main.cpp:728 ]: All Phusion Passenger agents started!
[Tue Aug 15 09:25:32.747844 2017] [so:warn] [pid 2600] AH01574: module
access_compat_module is already loaded, skipping
[Tue Aug 15 09:25:32.747904 2017] [so:warn] [pid 2600] AH01574: module
actions_module is already loaded, skipping
[Tue Aug 15 09:25:32.747920 2017] [so:warn] [pid 2600] AH01574: module
alias_module is already loaded, skipping
[Tue Aug 15 09:25:32.748254 2017] [so:warn] [pid 2600] AH01574: module
auth_basic_module is already loaded, skipping
[Tue Aug 15 09:25:32.748281 2017] [so:warn] [pid 2600] AH01574: module
auth_digest_module is already loaded, skipping
[Tue Aug 15 09:25:32.748296 2017] [so:warn] [pid 2600] AH01574: module
authn_anon_module is already loaded, skipping
[Tue Aug 15 09:25:32.748311 2017] [so:warn] [pid 2600] AH01574: module
authn_core_module is already loaded, skipping
[Tue Aug 15 09:25:32.748637 2017] [so:warn] [pid 2600] AH01574: module
authn_dbm_module is already loaded, skipping
[Tue Aug 15 09:25:32.748664 2017] [so:warn] [pid 2600] AH01574: module
authn_file_module is already loaded, skipping
[Tue Aug 15 09:25:32.748894 2017] [so:warn] [pid 2600] AH01574: module
authz_core_module is already loaded, skipping
[Tue Aug 15 09:25:32.749096 2017] [so:warn] [pid 2600] AH01574: module
authz_dbm_module is already loaded, skipping
[Tue Aug 15 09:25:32.749125 2017] [so:warn] [pid 2600] AH01574: module
authz_groupfile_module is already loaded, skipping
[Tue Aug 15 09:25:32.749143 2017] [so:warn] [pid 2600] AH01574: module
authz_host_module is already loaded, skipping
[Tue Aug 15 09:25:32.749164 2017] [so:warn] [pid 2600] AH01574: module
authz_owner_module is already loaded, skipping
[Tue Aug 15 09:25:32.749263 2017] [so:warn] [pid 2600] AH01574: module
authz_user_module is already loaded, skipping
[Tue Aug 15 09:25:32.749294 2017] [so:warn] [pid 2600] AH01574: module
autoindex_module is already loaded, skipping
[Tue Aug 15 09:25:32.749316 2017] [so:warn] [pid 2600] AH01574: module
cache_module is already loaded, skipping
[Tue Aug 15 09:25:32.749985 2017] [so:warn] [pid 2600] AH01574: module
deflate_module is already loaded, skipping
[Tue Aug 15 09:25:32.750009 2017] [so:warn] [pid 2600] AH01574: module
dir_module is already loaded, skipping
[Tue Aug 15 09:25:32.750350 2017] [so:warn] [pid 2600] AH01574: module
env_module is already loaded, skipping
[Tue Aug 15 09:25:32.750379 2017] [so:warn] [pid 2600] AH01574: module
expires_module is already loaded, skipping
[Tue Aug 15 09:25:32.750398 2017] [so:warn] [pid 2600] AH01574: module
ext_filter_module is already loaded, skipping
[Tue Aug 15 09:25:32.750420 2017] [so:warn] [pid 2600] AH01574: module
filter_module is already loaded, skipping
[Tue Aug 15 09:25:32.750523 2017] [so:warn] [pid 2600] AH01574: module
headers_module is already loaded, skipping
[Tue Aug 15 09:25:32.750630 2017] [so:warn] [pid 2600] AH01574: module
include_module is already loaded, skipping
[Tue Aug 15 09:25:32.750973 2017] [so:warn] [pid 2600] AH01574: module
log_config_module is already loaded, skipping
[Tue Aug 15 09:25:32.750998 2017] [so:warn] [pid 2600] AH01574: module
logio_module is already loaded, skipping
[Tue Aug 15 09:25:32.751015 2017] [so:warn] [pid 2600] AH01574: module
mime_magic_module is already loaded, skipping
[Tue Aug 15 09:25:32.751036 2017] [so:warn] [pid 2600] AH01574: module
mime_module is already loaded, skipping
[Tue Aug 15 09:25:32.751127 2017] [so:warn] [pid 2600] AH01574: module
negotiation_module is already loaded, skipping
[Tue Aug 15 09:25:32.751626 2017] [so:warn] [pid 2600] AH01574: module
rewrite_module is already loaded, skipping
[Tue Aug 15 09:25:32.751655 2017] [so:warn] [pid 2600] AH01574: module
setenvif_module is already loaded, skipping
[Tue Aug 15 09:25:32.752388 2017] [so:warn] [pid 2600] AH01574: module
socache_shmcb_module is already loaded, skipping
[Tue Aug 15 09:25:32.752593 2017] [so:warn] [pid 2600] AH01574: module
substitute_module is already loaded, skipping
[Tue Aug 15 09:25:32.752622 2017] [so:warn] [pid 2600] AH01574: module
suexec_module is already loaded, skipping
[Tue Aug 15 09:25:32.752799 2017] [so:warn] [pid 2600] AH01574: module
unixd_module is already loaded, skipping
[Tue Aug 15 09:25:32.752995 2017] [so:warn] [pid 2600] AH01574: module
version_module is already loaded, skipping
[Tue Aug 15 09:25:32.753025 2017] [so:warn] [pid 2600] AH01574: module
vhost_alias_module is already loaded, skipping
[Tue Aug 15 09:25:32.753069 2017] [so:warn] [pid 2600] AH01574: module
dav_module is already loaded, skipping
[Tue Aug 15 09:25:32.753092 2017] [so:warn] [pid 2600] AH01574: module
dav_fs_module is already loaded, skipping
[Tue Aug 15 09:25:32.754627 2017] [so:warn] [pid 2600] AH01574: module
mpm_prefork_module is already loaded, skipping
[Tue Aug 15 09:25:32.754686 2017] [so:warn] [pid 2600] AH01574: module
proxy_module is already loaded, skipping
[Tue Aug 15 09:25:32.756981 2017] [so:warn] [pid 2600] AH01574: module
proxy_http_module is already loaded, skipping
[Tue Aug 15 09:25:32.757423 2017] [so:warn] [pid 2600] AH01574: module
ssl_module is already loaded, skipping
[Tue Aug 15 09:25:32.757480 2017] [so:warn] [pid 2600] AH01574: module
systemd_module is already loaded, skipping
[Tue Aug 15 09:25:32.757586 2017] [so:warn] [pid 2600] AH01574: module
cgi_module is already loaded, skipping
[Tue Aug 15 09:25:32.766868 2017] [alias:warn] [pid 2600] AH00671: The
Alias directive in /etc/httpd/conf.d/autoindex.conf at line 21 will
probably never match because it overlaps an earlier Alias.
[Tue Aug 15 09:25:32.767816 2017] [mime_magic:error] [pid 2600] (2)No
such file or directory: AH01515: mod_mime_magic: can’t read magic file
/etc/httpd/NEVER_EVER_USE
[Tue Aug 15 09:25:32.767851 2017] [auth_digest:notice] [pid 2600]
AH01757: generating secret for digest authentication …
[Tue Aug 15 09:25:32.767898 2017] [auth_digest:error] [pid 2600] (2)No
such file or directory: AH01762: Failed to create shared memory segment on
file /run/httpd/authdigest_shm.2600
[Tue Aug 15 09:25:32.767917 2017] [auth_digest:error] [pid 2600] (2)No
such file or directory: AH01760: failed to initialize shm - all nonce-count
checking, one-time nonces, and MD5-sess algorithm disabled
[Tue Aug 15 09:25:32.767924 2017] [:emerg] [pid 2600] AH00020:
Configuration Failed, exiting
/usr/share/passenger/helper-scripts/prespawn:113:in initialize': No route to host - connect(2) (Errno::EHOSTUNREACH) from /usr/share/passenger/helper-scripts/prespawn:113:innew’
from /usr/share/passenger/helper-scripts/prespawn:113:in rescue in connect' from /usr/share/passenger/helper-scripts/prespawn:111:inconnect’
from /usr/share/passenger/helper-scripts/prespawn:87:in socket' from /usr/share/passenger/helper-scripts/prespawn:91:inhead_request’
from /usr/share/passenger/helper-scripts/prespawn:153:in <main>' /usr/share/passenger/helper-scripts/prespawn:113:ininitialize’: No
route to host - connect(2) (Errno::EHOSTUNREACH)
from /usr/share/passenger/helper-scripts/prespawn:113:in new' from /usr/share/passenger/helper-scripts/prespawn:113:inrescue in
connect’
from /usr/share/passenger/helper-scripts/prespawn:111:in connect' from /usr/share/passenger/helper-scripts/prespawn:120:inconnect’
from /usr/share/passenger/helper-scripts/prespawn:87:in socket' from /usr/share/passenger/helper-scripts/prespawn:91:inhead_request’
from /usr/share/passenger/helper-scripts/prespawn:153:in <main>' /usr/share/passenger/helper-scripts/prespawn:113:ininitialize’: No
route to host - connect(2) (Errno::EHOSTUNREACH)
from /usr/share/passenger/helper-scripts/prespawn:113:in new' from /usr/share/passenger/helper-scripts/prespawn:113:inrescue in
connect’
from /usr/share/passenger/helper-scripts/prespawn:111:in connect' from /usr/share/passenger/helper-scripts/prespawn:120:inconnect’
from /usr/share/passenger/helper-scripts/prespawn:87:in socket' from /usr/share/passenger/helper-scripts/prespawn:91:inhead_request’
from /usr/share/passenger/helper-scripts/prespawn:153:in `’

Starting at the top I do not see the module mod_mime_magic being loaded
from any of the conf files.

Any ideas on what I do now?

Louis

On Aug 15, 2017, at 9:06 AM, Louis Bohm louisbohm@gmail.com wrote:

As with mongodb postgresql was also complaining about its pid directory:

Aug 15 09:02:35 fm systemd: Starting PostgreSQL database server…
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT LOG: could not bind
IPv6 socket: Cannot assign requested address
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT HINT: Is another
postmaster already running on port 5432? If not, wait a few seconds and
retry.
Aug 15 09:02:35 fm pg_ctl: 2017-08-15 09:02:35 EDT FATAL: could not
create lock file “/var/run/postgresql/.s.PGSQL.5432.lock”: No such file
or directory
Aug 15 09:02:36 fm pg_ctl: pg_ctl: could not start server
Aug 15 09:02:36 fm pg_ctl: Examine the log output.

And again once i created the dir /var/run/postgresql and set its
perms/owner/group postgresql starts up fine.

Louis

On Wednesday, August 2, 2017 at 11:51:15 AM UTC-4, Eric Helms wrote:

We are happy to announce the GA of Katello 3.4.4. This release
contains a large number of bug fixes for both small UI issues, user issues
found while using 3.4.4 and developer found issues that we felt would bring
more stability to users.

The highlights are too numerous to outline here, so I would recommend
to please look at the changelog for a full list of changes:

https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md

Installation:
Foreman :: Plugin Manuals

Upgrade:
Foreman :: Plugin Manuals

Bug reporting

If you come across a bug in your testing, please file it and note the
version of Katello or Foreman that you’re using in the report.

Foreman

–
Eric D. Helms
Red Hat Engineering

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/to
pic/foreman-users/Gmo72QQW86A/unsubscribe.
To unsubscribe from this group and all its topics, 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.

–
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