IMPORTANT ANNOUNCEMENT: On May 6, 2024, Carbon Black User eXchange (UeX) and Case Management will move to a new platform!
The Community will be in read-only mode starting April 19th, 7:00 AM PDT. Check out the blog post!
You will still be able to use the case portal to create and interact with your support cases until the transition, view more information here!

EDR: Upgrading to a new Version - rpmnew files

EDR: Upgrading to a new Version - rpmnew files

Environment

  • EDR: All Supported Versions

Objective

  • If there are any custom settings in the EDR Configuration, a message while running /usr/share/cb/cbupgrade stating that .rpmnew files have been created and these settings need to be moved over before the upgrade can complete may be seen. This solution helps understand how to migrate these changes.
        This is a article attached imageThis is a article attached image

Resolution

 1. Before make any changes, backup the original configuration file. For Example:

cp /etc/cb/nginx/conf.d/cb.conf /etc/cb/nginx/conf.d/cb.conf.bakDATE

2. Determine the differences between the files

    A. Lines unique to the first file are displayed with a greater than sign (>) at their start, while lines unique to the second file start with a less than sign (<).

diff config.conf config.conf.rpmnew

    B. Display two files in columns:

diff -y config.conf config.conf.rpmnew

    C. Display context around differences:

diff -c config.conf config.conf.rpmnew

3. Once changes have been migrated over, rename the config.rpmnew file as config.VERSION.changes

mv config.conf.rpmnew config.conf.VERSION.changes

4. Once all .rpmnew changes have been migrated and the files renamed, run the upgrade utility:

/usr/share/cb/cbupgrade

Additional Notes

For more information on .rpmnew files check out this link: Dealing with .rpmnew and .rpmsave files | Linux.com | The source for Linux information
Note that there are significant changes in 5.2 to the nginx configuration files. Read more about it here: 5.2 Nginx Configuration Changes

  • If seeing /etc/cb/solr/core_conf/cbevents/conf/solrconfig.xml.template then it's possible to keep the original and rename the .rpmnew file. These changes were made to address performance issues on the server. 
    • Verify that these are the only differences between the two files:
      • solrconfig.xml.template:
<int name="maxMergeAtOnce">10</int>

<int name="segmentsPerTier">10</int>
  • solrconfig.xml.template.rpmnew:
<int name="maxMergeAtOnce">12</int>

<int name="segmentsPerTier">24</int>
  • Rename the .rpmnew file:
mv /etc/cb/solr/core_conf/cbevents/conf/solrconfig.xml.template.rpmnew /etc/cb/solr/core_conf/cbevents/conf/solrconfig.xml.template.VERSION.default

Related Content


Labels (1)
Tags (2)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎10-12-2016
Views:
3605
Contributors