Having hard time upgrading from 1.7 to 2

Hello. I’m trying to upgrade my 1.7 Influxdb to 2.7.4. As far as i know, i should be upgrading to 2 first.

To use the “upgrade” command, i need to be using “InfluxDB 2.7 influxd binary” apparently, which, i dont know the meaning of. I downloaded the version 2 to my server using the command:

curl -O https://download.influxdata.com/influxdb/releases/influxdb2-2.7.6-1.x86_64.rpm
sudo yum localinstall influxdb2-2.7.6-1.x86_64.rpm
(By the way curl command did nothing, so i used wget instead)

at this part, “sudo yum localinstall” command gives this error:

sudo yum localinstall influxdb2-2.7.6-1.x86_64.rpm
Loaded plugins: langpacks, product-id, rhnplugin, search-disabled-repos, subscription-manager
This system is receiving updates from RHN Classic or Red Hat Satellite.
Cannot open: influxdb2-2.7.6-1.x86_64.rpm. Skipping.
Nothing to do

My system info is:
Linux 3.10.0-1160.90.1.el7.x86_64 x86_64
NAME=“Red Hat Enterprise Linux Server”
VERSION=“7.9 (Maipo)”

What should i be doing right now, can you please guide me?

(as you can understand my knowledge is terribly low at system management and linux, so please be tolerant and clear with me. Thx for your understanding)

Hello. @Aliskus,
I’d actually suggest waiting for 3.x to be released later this summer than upgrade to 2.x. This is because 2.x is significantly different from 1.x. Especially in the query language. It uses Flux which has a non trivial learning curve. However you can query 3.x with influxql, so you’d be able to migrate all of your data. You also have to make DBRP mappings which is tricky too.

Are you able to wait?

You have to unpack the binary next:

Have you tried to follow that guide after the wget?

1 Like

Hi Anais, thanks so much for your return to me on the case. I have bad news and good news.

Unfortunately, i wasn’t able to wait for the 3.x release, as my needs were urgent. I assure you though, when its out, ill give it a try :slight_smile:

Good news is, i was able to complete the upgrading progress after unpacking the binary as you suggested. But, that part was a bit complicated to me at first, and thats why i wasnt able to continue for a while.

Another note is, that i wasnt able to get the file using curl, instead, i used wget, as i told you before. Is there a reason for that you think? Is it the documentation that is mistaken, or me?

Anyways, thanks again for everything. Have a good day!