Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API Token field gets blanked on server restart #157

Open
daveh79 opened this issue May 21, 2018 · 7 comments
Open

API Token field gets blanked on server restart #157

daveh79 opened this issue May 21, 2018 · 7 comments
Labels

Comments

@daveh79
Copy link

daveh79 commented May 21, 2018

Every time we restart the Team City server the API Token field in the Slack Notifications settings window is removed. Do you know why this would happen?
2018-05-21 11_00_44-teamcity

@daveh79
Copy link
Author

daveh79 commented May 22, 2018

I ran an upgrade to version 2017.2.4 this morning and it also blanked out the API Token field.

@marvin-w
Copy link
Collaborator

Thanks @daveh79. Do you have any logs from your server which you might be able to share with us?

This is only for the case that we can't reproduce the issue.

@marvin-w marvin-w added the bug label May 22, 2018
@daveh79
Copy link
Author

daveh79 commented May 22, 2018

Sure, here you go.
teamcity-server.log

@marvin-w
Copy link
Collaborator

Thanks @daveh79.

It appears that your slack URL is broken (I'm unsure if thats connected to the mentioned issue):

[2018-05-22 08:01:57,152] WARN - jetbrains.buildServer.SERVER - .slack.com java.net.UnknownHostException: .slack.com

@daveh79
Copy link
Author

daveh79 commented May 22, 2018

I agree that the slack URL is broken but we think it's because the API Token is being removed.

@marvin-w
Copy link
Collaborator

marvin-w commented May 22, 2018

Yea, could be. I'm very busy lately, I hope I can take a look into it soon but I can't promise anything.

@daveh79
Copy link
Author

daveh79 commented May 22, 2018

No problem. It does work if we keep an eye on the API token field. If you look in the log file from 5/18 and after that should maybe help you find the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants