Happy to do either! I guess a DB backup is easier for you to work with, let
me know how to get that to you (you're after the Postgres db I take it?)

Dylan

On Friday, 1 July 2016, Eric D Helms <[email protected]> wrote:

> Dylan,
>
> You've hit an error that I spent the past two days debugging for another
> user but have not been able to replicate locally. Couple of questions for
> you:
>
> 1) do you have a backup of your 2.4 before upgrading?
> 2) If yes, would you be able to privately share backups of your database
> with me from 2.4? If you are unable to share it out, would you be willing
> to help by doing some live debugging on IRC or some other means?
> On Jul 1, 2016 1:15 AM, "Dylan Baars" <[email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:
>
>> I had a further error, final output below
>>
>> Upgrade Step: restart_services...
>> Upgrade Step: db_seed...
>> Upgrade Step: import_package_groups (this may take a while) ...
>> Upgrade Step: import_rpms (this may take a while) ...
>> Upgrade Step: import_distributions (this may take a while) ...
>> Upgrade Step: import_puppet_modules (this may take a while) ...
>> Upgrade Step: import_subscriptions (this may take a while) ...
>> Upgrade Step: elasticsearch_message...
>> Elasticsearch has been removed as a dependency. The database files can be
>> removed manually with #rm -rf /var/lib/elasticsearch. Some packages are no
>> longer needed and can be removed: #rpm -e ruby193-rubygem-tire
>> tfm-rubygem-tire elasticsearch sigar-java sigar snappy-java lucene4-contrib
>> lucene4
>> Upgrade Step: add_export_distributor (this may take a while) ...
>> Upgrade Step: remove_docker_v1_content (this may take a while) ...
>> Upgrade Step: update_puppet_repository_distributors (this may take a
>> while) ...
>> Upgrade Step: update_subscription_facet_backend_data (this may take a
>> while) ...
>> Upgrade step update_subscription_facet_backend_data failed. Check logs
>> for more information.
>> [root@wellkatello ~]#
>>
>>
>> I've created a ticket for it...
>> http://projects.theforeman.org/issues/15558
>>
>> --
>> 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 [email protected]
>> <javascript:_e(%7B%7D,'cvml','foreman-users%[email protected]');>
>> .
>> To post to this group, send email to [email protected]
>> <javascript:_e(%7B%7D,'cvml','[email protected]');>.
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/foreman-users/86Pt-1v0L1s/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected]
> <javascript:_e(%7B%7D,'cvml','foreman-users%[email protected]');>
> .
> To post to this group, send email to [email protected]
> <javascript:_e(%7B%7D,'cvml','[email protected]');>.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to