[foreman-users] Re: Katello 3.4 -> 3.5 Upgrade Step: db_seed... taking a LOOONG time.
Ignore this. I finally killed the update then rebooted and started the
foreman-installer again. Ran about 10 minutes but it fully completed.
Louis
On Tuesday, December 19, 2017 at 1:13:11 PM UTC-5, Louis Bohm wrote:
>
> Performed the upgrade and ran the foreman-installer upgrade step. After a
> few stops and starts I got it to fully complete as bellow.
>
> [root@fm run]# 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
>
> /usr/sbin/service-wait postgresql start
> Redirecting to /bin/systemctl start postgresql.service
>
> Success!
> katello-service start --only mongod,postgresql finished successfully!
> Upgrade Step: update_http_conf...
> grep -F -q 'Include "/etc/httpd/conf.modules.d/*.conf"'
> /etc/httpd/conf/httpd.conf ||echo -e '=
> 2.4>
> Include "/etc/httpd/conf.modules.d/*.conf"
> '>> /etc/httpd/conf/httpd.conf
> finished successfully!
> Upgrade Step: migrate_pulp...
> grep -qe '7.[[:digit:]]' /etc/redhat-release finished successfully!
> sed -i -e 's?/var/run/mongodb/mongodb.pid?/var/run/mongodb/mongod.pid?g'
> /etc/mongod.conf finished successfully!
> 12180
> pgrep mongod finished successfully!
> Attempting to connect to localhost:27017
> Attempting to connect to localhost:27017
> Write concern for Mongo connection: {}
> Loading content types.
> Loading type descriptors []
> Parsing type descriptors
> Validating type descriptor syntactic integrity
> Validating type descriptor semantic integrity
> Loading unit model: docker_blob = pulp_docker.plugins.models:Blob
> Loading unit model: docker_manifest = pulp_docker.plugins.models:Manifest
> Loading unit model: docker_image = pulp_docker.plugins.models:Image
> Loading unit model: docker_tag = pulp_docker.plugins.models:Tag
> Loading unit model: puppet_module = pulp_puppet.plugins.db.models:Module
> Loading unit model: erratum = pulp_rpm.plugins.db.models:Errata
> Loading unit model: distribution = pulp_rpm.plugins.db.models:Distribution
> Loading unit model: srpm = pulp_rpm.plugins.db.models:SRPM
> Loading unit model: package_group = pulp_rpm.plugins.db.models:PackageGroup
> Loading unit model: package_category =
> pulp_rpm.plugins.db.models:PackageCategory
> Loading unit model: iso = pulp_rpm.plugins.db.models:ISO
> Loading unit model: package_environment =
> pulp_rpm.plugins.db.models:PackageEnvironment
> Loading unit model: drpm = pulp_rpm.plugins.db.models:DRPM
> Loading unit model: package_langpacks =
> pulp_rpm.plugins.db.models:PackageLangpacks
> Loading unit model: rpm = pulp_rpm.plugins.db.models:RPM
> Loading unit model: yum_repo_metadata_file =
> pulp_rpm.plugins.db.models:YumMetadataFile
> Updating the database with types []
> Found the following type definitions that were not present in the update
> collection [puppet_module, drpm, package_langpacks, erratum, docker_blob,
> docker_manifest, yum_repo_metadata_file, package_group, package_category,
> iso, package_environment, docker_tag, srpm, rpm, distribution, docker_image]
> Updating the database with types [puppet_module, drpm, package_langpacks,
[foreman-users] Katello 3.4 -> 3.5 Upgrade Step: db_seed... taking a LOOONG time.
Performed the upgrade and ran the foreman-installer upgrade step. After a
few stops and starts I got it to fully complete as bellow.
[root@fm run]# 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
/usr/sbin/service-wait postgresql start
Redirecting to /bin/systemctl start postgresql.service
Success!
katello-service start --only mongod,postgresql finished successfully!
Upgrade Step: update_http_conf...
grep -F -q 'Include "/etc/httpd/conf.modules.d/*.conf"'
/etc/httpd/conf/httpd.conf ||echo -e '=
2.4>
Include "/etc/httpd/conf.modules.d/*.conf"
'>> /etc/httpd/conf/httpd.conf finished
successfully!
Upgrade Step: migrate_pulp...
grep -qe '7.[[:digit:]]' /etc/redhat-release finished successfully!
sed -i -e 's?/var/run/mongodb/mongodb.pid?/var/run/mongodb/mongod.pid?g'
/etc/mongod.conf finished successfully!
12180
pgrep mongod finished successfully!
Attempting to connect to localhost:27017
Attempting to connect to localhost:27017
Write concern for Mongo connection: {}
Loading content types.
Loading type descriptors []
Parsing type descriptors
Validating type descriptor syntactic integrity
Validating type descriptor semantic integrity
Loading unit model: docker_blob = pulp_docker.plugins.models:Blob
Loading unit model: docker_manifest = pulp_docker.plugins.models:Manifest
Loading unit model: docker_image = pulp_docker.plugins.models:Image
Loading unit model: docker_tag = pulp_docker.plugins.models:Tag
Loading unit model: puppet_module = pulp_puppet.plugins.db.models:Module
Loading unit model: erratum = pulp_rpm.plugins.db.models:Errata
Loading unit model: distribution = pulp_rpm.plugins.db.models:Distribution
Loading unit model: srpm = pulp_rpm.plugins.db.models:SRPM
Loading unit model: package_group = pulp_rpm.plugins.db.models:PackageGroup
Loading unit model: package_category =
pulp_rpm.plugins.db.models:PackageCategory
Loading unit model: iso = pulp_rpm.plugins.db.models:ISO
Loading unit model: package_environment =
pulp_rpm.plugins.db.models:PackageEnvironment
Loading unit model: drpm = pulp_rpm.plugins.db.models:DRPM
Loading unit model: package_langpacks =
pulp_rpm.plugins.db.models:PackageLangpacks
Loading unit model: rpm = pulp_rpm.plugins.db.models:RPM
Loading unit model: yum_repo_metadata_file =
pulp_rpm.plugins.db.models:YumMetadataFile
Updating the database with types []
Found the following type definitions that were not present in the update
collection [puppet_module, drpm, package_langpacks, erratum, docker_blob,
docker_manifest, yum_repo_metadata_file, package_group, package_category,
iso, package_environment, docker_tag, srpm, rpm, distribution, docker_image]
Updating the database with types [puppet_module, drpm, package_langpacks,
erratum, docker_blob, docker_manifest, yum_repo_metadata_file,
package_group, package_category, iso, package_environment, docker_tag,
distribution, rpm, srpm, docker_image]
Content types loaded.
Ensuring the admin role and user are in place.
Admin role and user are in place.
Beginning database migrations.
Migration package pulp.server.db.migrations is up to date at version 28
Migration package pulp_docker.plugins.migrations is up to date at version 3
Migration package pulp_puppet.plugins.migrations is up to date at version 5
Migration package pulp_rpm.plugins.migrations is up to date at version 39
Loading unit model: docker_blob = pulp_docker.plugins.models:Blob
Loading unit model: docker_manifest = pulp_docker.plugins.models:Manifest
[foreman-users] Katello 3.4 Content View Filter not honored
I am running Katello 3.4 where I have a Content View with the repositories CentOS 6 and CentOS7 Base, Extras, Updates, and EPEL. Also in this content view I have a filter. The filter is a RPM exclude filter for things like *httpd* *mod_ssl* and some others that cannot be easily upgraded. I just applied all updates and Errata to all the hosts in this content view and when I went back to check I noticed 2 out of 20 hosts that had packages under Packages -> Applicable that were in the exclude filter. I have ensured that the Published and Promoted views of this Content View had the filter in it before the view was Published and Promoted. So as I understand it the hosts using this Content View should not even show RPMs listed in the Exclude filter. Is this a bug? Is there anyway on the client side to see what filter has been applied to it? (As a verification.) Am I doing the filtering correctly? I would like to avoid putting the filter in every hosts yum.conf but I will if the filter in Katello is not working right. Thanks Louis -- 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+unsubscr...@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.
Re: [foreman-users] Katello 3.4.4 Released
We took a deeper look at the errors from apache and found that /etc/httpd there
is a symlink for run to /run/httpd. That link was broken as /run/httpd got
blown away somehow. We recreated the links and was able to start apache fine.
I am re-running the upgrade step now.
Louis
> On Aug 16, 2017, at 3:13 PM, Eric D Helms <ericdhe...@gmail.com> wrote:
>
> The installer run fails even when you comment out the line in ports.conf?
>
> On Wed, Aug 16, 2017 at 9:27 AM, Louis Bohm <louisb...@gmail.com
> <mailto:louisb...@gmail.com>> wrote:
> No. I re-ran it yesterday with the —scenario and with out it. In both cases
> it stops with trying to update apache and fails.
>
> Louis
>
>> On Aug 16, 2017, at 9:26 AM, Eric D Helms <eric.d.he...@gmail.com
>> <mailto:eric.d.he...@gmail.com>> wrote:
>>
>> What happens if you rerun the installer? Does it succeed?
>>
>> On Aug 16, 2017 7:16 AM, "Louis Bohm" <louisb...@gmail.com
>> <mailto:louisb...@gmail.com>> wrote:
>> Any suggestions since my last post? Should I revert the VM and start over?
>>
>> Louis
>>
>>> On Aug 15, 2017, at 12:33 PM, Louis Bohm <louisb...@gmail.com
>>> <mailto:louisb...@gmail.com>> wrote:
>>>
>>> I commented out the Listen 443 line from /etc/httpd/conf.d/ports.conf.
>>>
>>> Louis
>>>> On Aug 15, 2017, at 12:23 PM, Eric D Helms <eric.d.he...@gmail.com
>>>> <mailto:eric.d.he...@gmail.com>> wrote:
>>>>
>>>> Which one did you remove? The one from sleeping.conf?
>>>>
>>>>
>>>> On Aug 15, 2017 12:12 PM, "Louis Bohm" <louisb...@gmail.com
>>>> <mailto:louisb...@gmail.com>> wrote:
>>>> OK. I see what you are saying and that is what I ran: foreman-installer
>>>> --scenario katello —upgrade
>>>>
>>>> When I run foreman-installer --scenario katello —upgrade apache fails to
>>>> start up. When I fist look at the logs I see 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 <http://0.0.0.0:443/>
>>>>
>>>> If I remove one of the Listen 443 in the configurations and manually start
>>>> apache with katello-services —only httpd I then get these errors:
>>>>
>>>> [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 <http://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 agen
Re: [foreman-users] Katello 3.4.4 Released
No. I re-ran it yesterday with the —scenario and with out it. In both cases
it stops with trying to update apache and fails.
Louis
> On Aug 16, 2017, at 9:26 AM, Eric D Helms <eric.d.he...@gmail.com> wrote:
>
> What happens if you rerun the installer? Does it succeed?
>
> On Aug 16, 2017 7:16 AM, "Louis Bohm" <louisb...@gmail.com
> <mailto:louisb...@gmail.com>> wrote:
> Any suggestions since my last post? Should I revert the VM and start over?
>
> Louis
>
>> On Aug 15, 2017, at 12:33 PM, Louis Bohm <louisb...@gmail.com
>> <mailto:louisb...@gmail.com>> wrote:
>>
>> I commented out the Listen 443 line from /etc/httpd/conf.d/ports.conf.
>>
>> Louis
>>> On Aug 15, 2017, at 12:23 PM, Eric D Helms <eric.d.he...@gmail.com
>>> <mailto:eric.d.he...@gmail.com>> wrote:
>>>
>>> Which one did you remove? The one from sleeping.conf?
>>>
>>>
>>> On Aug 15, 2017 12:12 PM, "Louis Bohm" <louisb...@gmail.com
>>> <mailto:louisb...@gmail.com>> wrote:
>>> OK. I see what you are saying and that is what I ran: foreman-installer
>>> --scenario katello —upgrade
>>>
>>> When I run foreman-installer --scenario katello —upgrade apache fails to
>>> start up. When I fist look at the logs I see 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 <http://0.0.0.0:443/>
>>>
>>> If I remove one of the Listen 443 in the configurations and manually start
>>> apache with katello-services —only httpd I then get these errors:
>>>
>>> [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 <http://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 alr
Re: [foreman-users] Katello 3.4.4 Released
Any suggestions since my last post? Should I revert the VM and start over?
Louis
> On Aug 15, 2017, at 12:33 PM, Louis Bohm <louisb...@gmail.com> wrote:
>
> I commented out the Listen 443 line from /etc/httpd/conf.d/ports.conf.
>
> Louis
>> On Aug 15, 2017, at 12:23 PM, Eric D Helms <eric.d.he...@gmail.com
>> <mailto:eric.d.he...@gmail.com>> wrote:
>>
>> Which one did you remove? The one from sleeping.conf?
>>
>>
>> On Aug 15, 2017 12:12 PM, "Louis Bohm" <louisb...@gmail.com
>> <mailto:louisb...@gmail.com>> wrote:
>> OK. I see what you are saying and that is what I ran: foreman-installer
>> --scenario katello —upgrade
>>
>> When I run foreman-installer --scenario katello —upgrade apache fails to
>> start up. When I fist look at the logs I see 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 <http://0.0.0.0:443/>
>>
>> If I remove one of the Listen 443 in the configurations and manually start
>> apache with katello-services —only httpd I then get these errors:
>>
>> [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 <http://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: modu
Re: [foreman-users] Katello 3.4.4 Released
I commented out the Listen 443 line from /etc/httpd/conf.d/ports.conf.
Louis
> On Aug 15, 2017, at 12:23 PM, Eric D Helms <eric.d.he...@gmail.com> wrote:
>
> Which one did you remove? The one from sleeping.conf?
>
>
> On Aug 15, 2017 12:12 PM, "Louis Bohm" <louisb...@gmail.com
> <mailto:louisb...@gmail.com>> wrote:
> OK. I see what you are saying and that is what I ran: foreman-installer
> --scenario katello —upgrade
>
> When I run foreman-installer --scenario katello —upgrade apache fails to
> start up. When I fist look at the logs I see 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 <http://0.0.0.0:443/>
>
> If I remove one of the Listen 443 in the configurations and manually start
> apache with katello-services —only httpd I then get these errors:
>
> [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 <http://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: m
Re: [foreman-users] Katello 3.4.4 Released
rrno::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 `’
Louis
> On Aug 15, 2017, at 12:06 PM, Eric D Helms <eric.d.he...@gmail.com> wrote:
>
> 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 -- https://theforeman.org/plugins/katello/3.4/upgrade/index.html
> <https://theforeman.org/plugins/katello/3.4/upgrade/index.html>
>
> Check Step 5
>
> On Aug 15, 2017 12:03 PM, "Louis Bohm" <louisb...@gmail.com
> <mailto:louisb...@gmail.com>> 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.he...@gmail.com
>> <mailto:eric.d.he...@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" <louisb...@gmail.com
>> <mailto:louisb...@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 <ericdhe...@gmail.com
>>> <mailto:ericdhe...@gmail.com>> wrote:
>>>
>>> You ran 'foreman-installer --upgrade' once you updated the RPMs?
>>>
>>> On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm <louisb...@gmail.com
>>> <mailto:louisb...@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 <http://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 <http://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-1
Re: [foreman-users] Katello 3.4.4 Released
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.he...@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" <louisb...@gmail.com
> <mailto:louisb...@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 <ericdhe...@gmail.com
>> <mailto:ericdhe...@gmail.com>> wrote:
>>
>> You ran 'foreman-installer --upgrade' once you updated the RPMs?
>>
>> On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm <louisb...@gmail.com
>> <mailto:louisb...@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 <http://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 <http://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
Re: [foreman-users] Katello 3.4.4 Released
No. Its not on the Katello upgrade page. Am I supposed to?
Louis
> On Aug 15, 2017, at 10:59 AM, Eric D Helms <ericdhe...@gmail.com> wrote:
>
> You ran 'foreman-installer --upgrade' once you updated the RPMs?
>
> On Tue, Aug 15, 2017 at 9:31 AM, Louis Bohm <louisb...@gmail.com
> <mailto:louisb...@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 <http://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 <http://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] A
Re: [foreman-users] Re: Katello 3.4.4 Released
enger/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 <louisb...@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 > <https://github.com/Katello/katello/blob/KATELLO-3.4/CHANGELOG.md> > > Installation: > https://theforeman.org/plugins/katello/3.4/installation/index.html > <https://theforeman.org/plugins/katello/3.4/installation/index.html> > > Upgrade: > https://theforeman.org/plugins/katello/3.4/upgrade/index.html > <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 > <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 > <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+unsubscr...@googlegroups.com > <mailto:foreman-users+unsubscr...@googlegroups.com>. > To post to this group, send email to foreman-users@googlegroups.com > <mailto:foreman-users@googlegroups.com>. > Visit this group at https://groups.google.com/group/foreman-users > <https://groups.google.com/group/foreman-users>. > For more options, visit https://groups.google.com/d/optout > <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+unsubscr...@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.
[foreman-users] Re: Katello 3.4.4 Released
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 the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@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.
[foreman-users] Re: Katello 3.4.4 Released
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 > -- 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+unsubscr...@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.
Re: [foreman-users] Katello 3.4.4 Released
g_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 <louisb...@gmail.com> wrote: > > So this time when I did yum update > http://yum.theforeman.org/releases/1.15/el7/x86_64/foreman-release.rpm > <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 <http://mirrors.lga7.us.voxel.net/> > * epel: mirrors.mit.edu <http://mirrors.mit.edu/> > * extras: mirrors.tripadvisor.com <http://mirrors.tripadvisor.com/> > * updates: mirror.trouble-free.net <http://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 <louisb...@gmail.com >> <mailto:louisb...@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 <ericdhe...@gmail.com >>> <mailto:ericdhe...@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 <louisb...@gmail.com >>> <mailto:louisb...@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 >>> <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 <http://ftpmirror.your.org/> >>> * epel: mirror.metrocast.net <http://mirror.metrocast.net/> >>> * extras: mirrors.centos.webair.com <http://mirrors.centos.webair.com/> >>> * updates: mirrors.lga7.us.voxel.net <http://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) >>>fo
Re: [foreman-users] Katello 3.4.4 Released
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 <louisb...@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 <ericdhe...@gmail.com >> <mailto:ericdhe...@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 <louisb...@gmail.com >> <mailto:louisb...@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 >> <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 <http://ftpmirror.your.org/> >> * epel: mirror.metrocast.net <http://mirror.metrocast.net/> >> * extras: mirrors.centos.webair.com <http://mirrors.centos.webair.com/> >> * updates: mirrors.lga7.us.voxel.net <http://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)
Re: [foreman-users] Katello 3.4.4 Released
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 <ericdhe...@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 <louisb...@gmail.com > <mailto:louisb...@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 > <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 <http://ftpmirror.your.org/> > * epel: mirror.metrocast.net <http://mirror.metrocast.net/> > * extras: mirrors.centos.webair.com <http://mirrors.centos.webair.com/> > * updates: mirrors.lga7.us.voxel.net <http://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:
[foreman-users] Re: Katello 3.4.4 Released
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 > -- 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+unsubscr...@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.
