Hello。Such an error occurred when Upgrading Fleet, indicating that the connection was rejected, but It was normal for me to link to the database

Hi! The serve command will not set up the database. You can pass the database configuration (mysql_address, mysql_database, mysql_username and mysql_password params) to the prepare db command. Let me know if you continue to have issues!

Then I should have used./ fleet prepare db --mysql_address = XXX :3306 \ --mysql_database = XXX \ --mysql_username = XXX \ --mysql_password = XXX?

Correct. Let me know how this goes!

Below is my result, indicating that I don't know the port, but my port is 3306

@zwass I’m past my current level of understanding. Initially (first screenshot) was incorrectly trying to connect to localhost. It seems like the address change was registered (third screenshot)? Maybe incorrectly.

@demonbhao those backslashes are incorrect

Hello, I have successfully upgraded Fleet, but now I cannot display the IP address of the agent in fleet UI after the successful upgrade😂

Do you mind checking what the response object looks like for the

/hosts

endpoint? In this screenshot I’m using the network tab in chrome’s dev tools.

Hello, this is my response

Normally you do not need to restart osquery after upgrading the Fleet server. It's possible something went wrong in this scenario and it was fixed when osquery restarted.

Ok, I see

If you see something like this again or find a way to reproduce it please let us know so we can investigate further.

Okay, I will.