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