Upgrading from 1.8.3 to 2.0.2 - no data in measurement

Hi,

I am testing the upgrade process from 1.8.3 to 2.0.2 on my development environment. Influxdb 1.8.3 was installed using apt. I used the ‘influxd upgrade’ command and finished the initial setup process. After logging in to UI I can see that the database (bucket) and measurement were moved, but there are no data (fields) in measurement. Is that a bug in v2.0.2 or am I doing something wrong?

My system: Debian 4.19.152-1
In 1.8.3 ‘auth-enabled’ is set to true
Steps that I’ve done:

  1. Downloaded influxdb 2.0.1 and unpacked it.
  2. Copied influx and influxd files to /usr/bin
  3. Stopped influxdb (systemctl stop influxdb)
  4. Run influxd upgrade
  5. Start influxdb (using command: influxd)

I also have a question. Do you plan to add availability to install influxdb 2.0 using apt? If yes, would it be possible to upgrade from 1.8 to 2.0 using apt?
Do you also plan to add starting influxdb as a service (using systemctl start influxdb)?

There was some sort of bug in Influxdb UI and that’s why I didn’t see the fields, but they were there. I have a couple of other questions:

  1. Documentation says that Influxdb 2.0 API is compatible with 1.x API, but I it says that in the password field I need to put the token. Is there any way to authenticate using login&password the same as in v1.8? I have a mobile app where the password is stored in the app, so production update from 1.8 to 2.0 seems impossible for me. I also cannot authenticate when I put username and the token in password field. I always get “401 Unauthorized” error.

I received help on Github. To authenticate using old API (login & password) you need to create user using influx v1 auth command.
So my remaining questions are:
Do you plan to add availability to install influxdb 2.0 using apt? If yes, would it be possible to upgrade from 1.8 to 2.0 using apt?
Do you also plan to add starting influxdb as a service (using systemctl start influxdb)?

1 Like

Hi @szerwi, yes we do plan to support installing V2 via apt soon. I haven’t been directly involved in that effort, but I believe the current plan is to:

  1. Change the V2 package name from “influxdb” to “influxdb2”, to prevent accidental upgrades
  2. Require the “influxdb” package to be uninstalled before “influxdb2” can be installed
  3. After installing “influxdb2”, print a message describing how to run “influxd upgrade” on your V1 data

We’re eager to hear community feedback on this plan before we release it, if you have thoughts.

1 Like

@dan-moran Thank you for the answer. Right now I don’t have any suggestions, I just hope it will be released soon so I will be able to easily update from 1.8 to 2.0 on my production environment :slight_smile: