mssql on ubuntu will not start, cannot update 404
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I did a routine Ubuntu system update for security patches today (2018-02-21)... mssql will no longer start or update, seeing failures in error log, systemctl and update output with 404 like:
Err:13 https://packages.microsoft.com/ubuntu/16.04/mssql-server xenial/main amd64 Packages
404 Not Found
Problem: routine update breaks my vanilla Ubuntu 16 LTS with mssql-server instance. No other substantive info obvious to me looking in logs, etc...
sql-server ubuntu
asked Feb 21 '18 at 23:28
jimmontjimmont
1505
bumped to the homepage by Community♦ 21 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I did a routine Ubuntu system update for security patches today (2018-02-21)... mssql will no longer start or update, seeing failures in error log, systemctl and update output with 404 like:
Err:13 https://packages.microsoft.com/ubuntu/16.04/mssql-server xenial/main amd64 Packages
404 Not Found
Problem: routine update breaks my vanilla Ubuntu 16 LTS with mssql-server instance. No other substantive info obvious to me looking in logs, etc...
sql-server ubuntu
asked Feb 21 '18 at 23:28
jimmontjimmont
1505
bumped to the homepage by Community♦ 21 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I did a routine Ubuntu system update for security patches today (2018-02-21)... mssql will no longer start or update, seeing failures in error log, systemctl and update output with 404 like:
Err:13 https://packages.microsoft.com/ubuntu/16.04/mssql-server xenial/main amd64 Packages
404 Not Found
Problem: routine update breaks my vanilla Ubuntu 16 LTS with mssql-server instance. No other substantive info obvious to me looking in logs, etc...
sql-server ubuntu
asked Feb 21 '18 at 23:28
jimmontjimmont
1505
I did a routine Ubuntu system update for security patches today (2018-02-21)... mssql will no longer start or update, seeing failures in error log, systemctl and update output with 404 like:
Err:13 https://packages.microsoft.com/ubuntu/16.04/mssql-server xenial/main amd64 Packages
404 Not Found
Problem: routine update breaks my vanilla Ubuntu 16 LTS with mssql-server instance. No other substantive info obvious to me looking in logs, etc...
sql-server ubuntu
sql-server ubuntu
asked Feb 21 '18 at 23:28
jimmontjimmont
1505
asked Feb 21 '18 at 23:28
jimmontjimmont
1505
asked Feb 21 '18 at 23:28
jimmontjimmont
1505
asked Feb 21 '18 at 23:28
jimmontjimmont
1505
asked Feb 21 '18 at 23:28
jimmontjimmont
1505
1505
bumped to the homepage by Community♦ 21 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 21 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Fixed by guessing this was due to a server update and the source url changed. I added the current source per their instructions https://docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-ubuntu
This added the NEW source with a sudo add-apt-repository ... per the docs. I then manually comment-out (or you can remove) the old 404 source in /etc/apt/sources.list.
Finally sudo apt-get update -y ... and start the server and I can again see it running (netstat or whatever to see the service up).
To be clear the URL changed:
from
https://packages.microsoft.com/ubuntu/16.04/mssql-server
to https://packages.microsoft.com/ubuntu/16.04/mssql-server-2017
Comment: adding '-2017' to sources, or changing sources for existing installations is highly likely to both break them and makes these sources look dated, possibly all goals driving the change. That sucks.
answered Feb 21 '18 at 23:28
jimmontjimmont
1505
The version without the version is from pre-RTM. I don’t think they changed it to break you and make your life suck. They added version so that in 6 months or 9 months or 2 years or whenever, the server would know if you meant to retrieve SQL 2017 or SQL 2018/2019/whatever.
– Aaron Bertrand♦
Feb 22 '18 at 6:53
Thanks @AaronBertrand without knowing more than my limited experience adding the version/nuance in the url "-2017" would be preferred from the beginning simply because it doesn't require a change in the future. I could be wrong for reasons I cannot currently see clearly.
– jimmont
Feb 23 '18 at 20:46
1
It's software, made by humans. Humans are imperfect.
– Aaron Bertrand♦
Feb 23 '18 at 22:38
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f198521%2fmssql-on-ubuntu-will-not-start-cannot-update-404%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Fixed by guessing this was due to a server update and the source url changed. I added the current source per their instructions https://docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-ubuntu
This added the NEW source with a sudo add-apt-repository ... per the docs. I then manually comment-out (or you can remove) the old 404 source in /etc/apt/sources.list.
Finally sudo apt-get update -y ... and start the server and I can again see it running (netstat or whatever to see the service up).
To be clear the URL changed:
from
https://packages.microsoft.com/ubuntu/16.04/mssql-server
to https://packages.microsoft.com/ubuntu/16.04/mssql-server-2017
Comment: adding '-2017' to sources, or changing sources for existing installations is highly likely to both break them and makes these sources look dated, possibly all goals driving the change. That sucks.
answered Feb 21 '18 at 23:28
jimmontjimmont
1505
The version without the version is from pre-RTM. I don’t think they changed it to break you and make your life suck. They added version so that in 6 months or 9 months or 2 years or whenever, the server would know if you meant to retrieve SQL 2017 or SQL 2018/2019/whatever.
– Aaron Bertrand♦
Feb 22 '18 at 6:53
Thanks @AaronBertrand without knowing more than my limited experience adding the version/nuance in the url "-2017" would be preferred from the beginning simply because it doesn't require a change in the future. I could be wrong for reasons I cannot currently see clearly.
– jimmont
Feb 23 '18 at 20:46
1
It's software, made by humans. Humans are imperfect.
– Aaron Bertrand♦
Feb 23 '18 at 22:38
add a comment |
Fixed by guessing this was due to a server update and the source url changed. I added the current source per their instructions https://docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-ubuntu
This added the NEW source with a sudo add-apt-repository ... per the docs. I then manually comment-out (or you can remove) the old 404 source in /etc/apt/sources.list.
Finally sudo apt-get update -y ... and start the server and I can again see it running (netstat or whatever to see the service up).
To be clear the URL changed:
from
https://packages.microsoft.com/ubuntu/16.04/mssql-server
to https://packages.microsoft.com/ubuntu/16.04/mssql-server-2017
Comment: adding '-2017' to sources, or changing sources for existing installations is highly likely to both break them and makes these sources look dated, possibly all goals driving the change. That sucks.
answered Feb 21 '18 at 23:28
jimmontjimmont
1505
The version without the version is from pre-RTM. I don’t think they changed it to break you and make your life suck. They added version so that in 6 months or 9 months or 2 years or whenever, the server would know if you meant to retrieve SQL 2017 or SQL 2018/2019/whatever.
– Aaron Bertrand♦
Feb 22 '18 at 6:53
Thanks @AaronBertrand without knowing more than my limited experience adding the version/nuance in the url "-2017" would be preferred from the beginning simply because it doesn't require a change in the future. I could be wrong for reasons I cannot currently see clearly.
– jimmont
Feb 23 '18 at 20:46
1
It's software, made by humans. Humans are imperfect.
– Aaron Bertrand♦
Feb 23 '18 at 22:38
add a comment |
Fixed by guessing this was due to a server update and the source url changed. I added the current source per their instructions https://docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-ubuntu
This added the NEW source with a sudo add-apt-repository ... per the docs. I then manually comment-out (or you can remove) the old 404 source in /etc/apt/sources.list.
Finally sudo apt-get update -y ... and start the server and I can again see it running (netstat or whatever to see the service up).
To be clear the URL changed:
from
https://packages.microsoft.com/ubuntu/16.04/mssql-server
to https://packages.microsoft.com/ubuntu/16.04/mssql-server-2017
Comment: adding '-2017' to sources, or changing sources for existing installations is highly likely to both break them and makes these sources look dated, possibly all goals driving the change. That sucks.
answered Feb 21 '18 at 23:28
jimmontjimmont
1505
Fixed by guessing this was due to a server update and the source url changed. I added the current source per their instructions https://docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-ubuntu
This added the NEW source with a sudo add-apt-repository ... per the docs. I then manually comment-out (or you can remove) the old 404 source in /etc/apt/sources.list.
Finally sudo apt-get update -y ... and start the server and I can again see it running (netstat or whatever to see the service up).
To be clear the URL changed:
from
https://packages.microsoft.com/ubuntu/16.04/mssql-server
to https://packages.microsoft.com/ubuntu/16.04/mssql-server-2017
Comment: adding '-2017' to sources, or changing sources for existing installations is highly likely to both break them and makes these sources look dated, possibly all goals driving the change. That sucks.
answered Feb 21 '18 at 23:28
jimmontjimmont
1505
answered Feb 21 '18 at 23:28
jimmontjimmont
1505
answered Feb 21 '18 at 23:28
jimmontjimmont
1505
answered Feb 21 '18 at 23:28
jimmontjimmont
1505
1505
The version without the version is from pre-RTM. I don’t think they changed it to break you and make your life suck. They added version so that in 6 months or 9 months or 2 years or whenever, the server would know if you meant to retrieve SQL 2017 or SQL 2018/2019/whatever.
– Aaron Bertrand♦
Feb 22 '18 at 6:53
Thanks @AaronBertrand without knowing more than my limited experience adding the version/nuance in the url "-2017" would be preferred from the beginning simply because it doesn't require a change in the future. I could be wrong for reasons I cannot currently see clearly.
– jimmont
Feb 23 '18 at 20:46
1
It's software, made by humans. Humans are imperfect.
– Aaron Bertrand♦
Feb 23 '18 at 22:38
add a comment |
The version without the version is from pre-RTM. I don’t think they changed it to break you and make your life suck. They added version so that in 6 months or 9 months or 2 years or whenever, the server would know if you meant to retrieve SQL 2017 or SQL 2018/2019/whatever.
– Aaron Bertrand♦
Feb 22 '18 at 6:53
Thanks @AaronBertrand without knowing more than my limited experience adding the version/nuance in the url "-2017" would be preferred from the beginning simply because it doesn't require a change in the future. I could be wrong for reasons I cannot currently see clearly.
– jimmont
Feb 23 '18 at 20:46
1
It's software, made by humans. Humans are imperfect.
– Aaron Bertrand♦
Feb 23 '18 at 22:38
The version without the version is from pre-RTM. I don’t think they changed it to break you and make your life suck. They added version so that in 6 months or 9 months or 2 years or whenever, the server would know if you meant to retrieve SQL 2017 or SQL 2018/2019/whatever.
– Aaron Bertrand♦
Feb 22 '18 at 6:53
The version without the version is from pre-RTM. I don’t think they changed it to break you and make your life suck. They added version so that in 6 months or 9 months or 2 years or whenever, the server would know if you meant to retrieve SQL 2017 or SQL 2018/2019/whatever.
– Aaron Bertrand♦
Feb 22 '18 at 6:53
Thanks @AaronBertrand without knowing more than my limited experience adding the version/nuance in the url "-2017" would be preferred from the beginning simply because it doesn't require a change in the future. I could be wrong for reasons I cannot currently see clearly.
– jimmont
Feb 23 '18 at 20:46
Thanks @AaronBertrand without knowing more than my limited experience adding the version/nuance in the url "-2017" would be preferred from the beginning simply because it doesn't require a change in the future. I could be wrong for reasons I cannot currently see clearly.
– jimmont
Feb 23 '18 at 20:46
1
1
It's software, made by humans. Humans are imperfect.
– Aaron Bertrand♦
Feb 23 '18 at 22:38
It's software, made by humans. Humans are imperfect.
– Aaron Bertrand♦
Feb 23 '18 at 22:38
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f198521%2fmssql-on-ubuntu-will-not-start-cannot-update-404%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
