[Pulp-list] Can't run pulp after upgrade?
Urwin, Paul
paul.urwin at jpmchase.com
Thu May 22 16:32:01 UTC 2014
Ah I didn't spot the failure message in stderr/stdout before:
[root at myhostname ~]# sudo -u apache /usr/bin/pulp-manage-db
Loading content types.
/usr/lib/python2.6/site-packages/pulp/server/db/connection.py:135: DeprecationWarning: The safe parameter is deprecated. Please use write concern options instead.
return method(*args, **kwargs)
Content types loaded.
Ensuring the admin role and user are in place.
Admin role and user are in place.
Beginning database migrations.
Applying pulp.server.db.migrations version 9
Applying migration pulp.server.db.migrations.0009_qpid_queues failed. See log for details.
Migration package pulp_puppet.plugins.migrations is up to date at version 2
Migration package pulp_rpm.plugins.migrations is up to date at version 15
Database migrations complete.
/var/log/messages says it needs qpidtoollibs:
May 22 11:19:16 myhostname pulp: pulp.server.db.manage:INFO: Loading content types.
May 22 11:19:16 myhostname pulp: db:INFO: Loading type descriptors [iso_support.json, rpm_support.json, puppet.json]
May 22 11:19:16 myhostname pulp: db:INFO: Parsing type descriptors
May 22 11:19:16 myhostname pulp: db:INFO: Validating type descriptor syntactic integrity
May 22 11:19:16 myhostname pulp: db:INFO: Validating type descriptor semantic integrity
May 22 11:19:16 myhostname pulp: db:INFO: Updating the database with types [iso, distribution, drpm, erratum, package_group, package_category, package_environment, rpm, srpm, yum_repo_metadata_file, puppet_module]
May 22 11:19:20 myhostname pulp: pulp.server.db.manage:INFO: Content types loaded.
May 22 11:19:20 myhostname pulp: pulp.server.db.manage:INFO: Ensuring the admin role and user are in place.
May 22 11:19:20 myhostname pulp: pulp.server.db.connection:INFO: Attempting Database connection with seeds = localhost:27017
May 22 11:19:20 myhostname pulp: pulp.server.db.connection:INFO: Connection Arguments: {'max_pool_size': 10}
May 22 11:19:20 myhostname pulp: pulp.server.db.connection:INFO: Database connection established with: seeds = localhost:27017, name = pulp_database
May 22 11:19:20 myhostname pulp: pulp.server.db.manage:INFO: Admin role and user are in place.
May 22 11:19:20 myhostname pulp: pulp.server.db.manage:INFO: Beginning database migrations.
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:INFO: Applying pulp.server.db.migrations version 9
May 22 11:19:21 myhostname pulp: pulp.server.db.migrations.0009_qpid_queues:ERROR: Migration 0009 did not run because the python package qpidtoollibs is not installed. Please install qpidtoollibs and rerun the migrations.
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:CRITICAL: Applying migration pulp.server.db.migrations.0009_qpid_queues failed.
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:CRITICAL: Migration 0009 did not run because the python package qpidtoollibs is not installed. Please install qpidtoollibs and rerun the migrations.
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:CRITICAL: Traceback (most recent call last):
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/server/db/manage.py", line 86, in migrate_database
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:CRITICAL: update_current_version=not options.test)
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/server/db/migrate/models.py", line 161, in apply_migration
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:CRITICAL: migration.migrate()
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/server/db/migrations/0009_qpid_queues.py", line 56, in migrate
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:CRITICAL: raise Exception(msg)
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:CRITICAL: Exception: Migration 0009 did not run because the python package qpidtoollibs is not installed. Please install qpidtoollibs and rerun the migrations.
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:CRITICAL:
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:INFO: Migration package pulp_puppet.plugins.migrations is up to date at version 2
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:INFO: Migration package pulp_rpm.plugins.migrations is up to date at version 15
May 22 11:19:21 myhostname pulp: pulp.server.db.manage:INFO: Database migrations complete.
....So I've installed the qpid-tools package, and run again:
Loading content types.
/usr/lib/python2.6/site-packages/pulp/server/db/connection.py:135: DeprecationWarning: The safe parameter is deprecated. Please use write concern options instead.
return method(*args, **kwargs)
Content types loaded.
Ensuring the admin role and user are in place.
Admin role and user are in place.
Beginning database migrations.
Applying pulp.server.db.migrations version 9
Applying migration pulp.server.db.migrations.0009_qpid_queues failed. See log for details.
Migration package pulp_puppet.plugins.migrations is up to date at version 2
Migration package pulp_rpm.plugins.migrations is up to date at version 15
Database migrations complete.
This time /var/log/messages says it failed because a queue was in use:
May 22 11:24:50 myhostname pulp: pulp.server.db.manage:INFO: Loading content types.
May 22 11:24:50 myhostname pulp: db:INFO: Loading type descriptors [iso_support.json, rpm_support.json, puppet.json]
May 22 11:24:50 myhostname pulp: db:INFO: Parsing type descriptors
May 22 11:24:50 myhostname pulp: db:INFO: Validating type descriptor syntactic integrity
May 22 11:24:50 myhostname pulp: db:INFO: Validating type descriptor semantic integrity
May 22 11:24:50 myhostname pulp: db:INFO: Updating the database with types [iso, distribution, drpm, erratum, package_group, package_category, package_environment, rpm, srpm, yum_repo_metadata_file, pup
pet_module]
May 22 11:24:53 myhostname pulp: pulp.server.db.manage:INFO: Content types loaded.
May 22 11:24:53 myhostname pulp: pulp.server.db.manage:INFO: Ensuring the admin role and user are in place.
May 22 11:24:53 myhostname pulp: pulp.server.db.connection:INFO: Attempting Database connection with seeds = localhost:27017
May 22 11:24:53 myhostname pulp: pulp.server.db.connection:INFO: Connection Arguments: {'max_pool_size': 10}
May 22 11:24:53 myhostname pulp: pulp.server.db.connection:INFO: Database connection established with: seeds = localhost:27017, name = pulp_database
May 22 11:24:53 myhostname pulp: pulp.server.db.manage:INFO: Admin role and user are in place.
May 22 11:24:53 myhostname pulp: pulp.server.db.manage:INFO: Beginning database migrations.
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:INFO: Applying pulp.server.db.migrations version 9
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: Applying migration pulp.server.db.migrations.0009_qpid_queues failed.
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: Cannot delete queue kvm-guest-70-consumer; queue in use
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: Traceback (most recent call last):
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/server/db/manage.py", line 86, in migrate_database
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: update_current_version=not options.test)
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/server/db/migrate/models.py", line 161, in apply_migration
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: migration.migrate()
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/server/db/migrations/0009_qpid_queues.py", line 70, in migrate
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: _migrate_agent_queues(broker)
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/server/db/migrations/0009_qpid_queues.py", line 97, in _migrate_agent_queues
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: _del_agent_queues(broker)
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/pulp/server/db/migrations/0009_qpid_queues.py", line 129, in _del_agent_queues
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: broker.delQueue(name)
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/qpidtoollibs/broker.py", line 258, in delQueue
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: self._tmpQueueCheck(name, options)
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: File "/usr/lib/python2.6/site-packages/qpidtoollibs/broker.py", line 286, in _tmpQueueCheck
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: raise Exception(msg)
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL: Exception: Cannot delete queue kvm-guest-70-consumer; queue in use
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:CRITICAL:
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:INFO: Migration package pulp_puppet.plugins.migrations is up to date at version 2
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:INFO: Migration package pulp_rpm.plugins.migrations is up to date at version 15
May 22 11:24:54 myhostname pulp: pulp.server.db.manage:INFO: Database migrations complete.
This feels like progress.... How do I free up that queue?
Thanks!
Paul
-----Original Message-----
From: pulp-list-bounces at redhat.com [mailto:pulp-list-bounces at redhat.com] On Behalf Of Randy Barlow
Sent: 22 May 2014 17:11
To: pulp-list at redhat.com
Subject: Re: [Pulp-list] Can't run pulp after upgrade?
On 05/22/2014 12:08 PM, Urwin, Paul wrote:
> It seems that this is because of a failed database migration. /var/log/messages has:
>
> May 22 02:46:44 myhostname pulp:
> pulp.server.webservices.application:CRITICAL:
> *************************************************************
> May 22 02:46:44 myhostname pulp: pulp.server.webservices.application:CRITICAL: The Pulp server failed to start due to the following reasons:
> May 22 02:46:44 myhostname pulp: pulp.server.webservices.application:ERROR: The database has not been migrated to the current version. Run pulp-manage-db and restart the application.
> May 22 02:46:44 myhostname pulp: pulp.server.webservices.application:ERROR: Traceback (most recent call last):
> May 22 02:46:44 myhostname pulp: pulp.server.webservices.application:ERROR: File "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py", line 147, in wsgi_application
> May 22 02:46:44 myhostname pulp: pulp.server.webservices.application:ERROR: _initialize_pulp()
> May 22 02:46:44 myhostname pulp: pulp.server.webservices.application:ERROR: File "/usr/lib/python2.6/site-packages/pulp/server/webservices/application.py", line 102, in _initialize_pulp
> May 22 02:46:44 myhostname pulp: pulp.server.webservices.application:ERROR: migration_models.check_package_versions()
> May 22 02:46:44 myhostname pulp: pulp.server.webservices.application:ERROR: File "/usr/lib/python2.6/site-packages/pulp/server/db/migrate/models.py", line 291, in check_package_versions
> May 22 02:46:44 myhostname pulp: pulp.server.webservices.application:ERROR: raise Exception(error_message)
> May 22 02:46:44 myhostname pulp: pulp.server.webservices.application:ERROR: InitializationException: The database has not been migrated to the current version. Run pulp-manage-db and restart the application.
> May 22 02:46:44 myhostname pulp:
> pulp.server.webservices.application:CRITICAL:
> *************************************************************
>
> Is there anyway to debug this or is it basically toasted?
Hi Paul!
Can you rerun pulp-manage-db and give us its stdout/stderr output, as well as the logs captured while it is running? I think that will help us identify the problem.
--
Randy Barlow
Raleigh, NC, USA
This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates.
This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.
More information about the Pulp-list
mailing list