Can't upgrade ubuntu 16.04 to 18.04 LTS
I need some help. When i try to upgrade ubuntu 16.04 to 18.04 via update manager, It shows an X mark and closes on the preparing stage. And when i try it via terminal. I get this:
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://us.archive.ubuntu.com/ubuntu xenial InRelease
Fetched 0 B in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
Restoring original system state
Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
Can someone please help me? Thanks.
EDIT: Oh, And btw. I lost my usb. So i can't do a clean install. And my system is a Dell Latitude E7240.
File /var/log/dist-upgrade/main.log:
2018-09-26 13:58:15,662 INFO Using config files '['./DistUpgrade.cfg.xenial']'
2018-09-26 13:58:15,663 INFO uname information: 'Linux rami-Latitude-E7240 4.4.0-135-generic #161~14.04.1-Ubuntu SMP Tue Aug 28 11:17:49 UTC 2018 x86_64'
2018-09-26 13:58:15,754 INFO apt version: '1.2.10ubuntu1'
2018-09-26 13:58:15,755 INFO python version: '3.5.1+ (default, Mar 30 2016, 22:46:26)
[GCC 5.3.1 20160330]'
2018-09-26 13:58:15,756 INFO release-upgrader version '18.04.24' started
2018-09-26 13:58:15,840 INFO locale: 'en_US' 'UTF-8'
2018-09-26 13:58:16,158 DEBUG Using 'DistUpgradeViewGtk3' view
2018-09-26 13:58:16,214 DEBUG enable dpkg --force-overwrite
2018-09-26 13:58:16,234 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'
2018-09-26 13:58:17,061 DEBUG lsb-release: 'xenial'
2018-09-26 13:58:17,061 DEBUG _pythonSymlinkCheck run
2018-09-26 13:58:17,062 DEBUG openCache()
2018-09-26 13:58:17,062 DEBUG No such plugin directory: ./plugins
2018-09-26 13:58:17,062 DEBUG plugins for condition 'PreCacheOpen' are ''
2018-09-26 13:58:17,062 DEBUG plugins for condition 'bionicPreCacheOpen' are ''
2018-09-26 13:58:17,062 DEBUG plugins for condition 'from_xenialPreCacheOpen' are ''
2018-09-26 13:58:17,062 DEBUG quirks: running PreCacheOpen
2018-09-26 13:58:17,062 DEBUG running Quirks.PreCacheOpen
2018-09-26 13:58:17,342 DEBUG /openCache(), new cache size 12180
2018-09-26 13:58:17,342 DEBUG need_server_mode(): run in 'desktop' mode, (because of pkg 'ubuntu-desktop')
2018-09-26 13:58:17,343 DEBUG checkViewDepends()
2018-09-26 13:58:17,343 DEBUG running doUpdate() (showErrors=False)
2018-09-26 13:58:17,805 DEBUG openCache()
2018-09-26 13:58:18,083 DEBUG /openCache(), new cache size 12180
2018-09-26 13:58:18,083 DEBUG doPostInitialUpdate
2018-09-26 13:58:18,083 DEBUG plugins for condition 'PostInitialUpdate' are ''
2018-09-26 13:58:18,083 DEBUG plugins for condition 'bionicPostInitialUpdate' are ''
2018-09-26 13:58:18,083 DEBUG plugins for condition 'from_xenialPostInitialUpdate' are ''
2018-09-26 13:58:18,084 DEBUG quirks: running bionicPostInitialUpdate
2018-09-26 13:58:18,084 DEBUG running Quirks.bionicPostInitialUpdate
2018-09-26 13:58:18,119 DEBUG abort called
2018-09-26 13:58:18,120 DEBUG openCache()
2018-09-26 13:58:18,120 DEBUG failed to SystemUnLock() (E:Not locked)
2018-09-26 13:58:18,404 DEBUG /openCache(), new cache size 12180
16.04 upgrade 18.04
|
show 8 more comments
I need some help. When i try to upgrade ubuntu 16.04 to 18.04 via update manager, It shows an X mark and closes on the preparing stage. And when i try it via terminal. I get this:
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://us.archive.ubuntu.com/ubuntu xenial InRelease
Fetched 0 B in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
Restoring original system state
Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
Can someone please help me? Thanks.
EDIT: Oh, And btw. I lost my usb. So i can't do a clean install. And my system is a Dell Latitude E7240.
File /var/log/dist-upgrade/main.log:
2018-09-26 13:58:15,662 INFO Using config files '['./DistUpgrade.cfg.xenial']'
2018-09-26 13:58:15,663 INFO uname information: 'Linux rami-Latitude-E7240 4.4.0-135-generic #161~14.04.1-Ubuntu SMP Tue Aug 28 11:17:49 UTC 2018 x86_64'
2018-09-26 13:58:15,754 INFO apt version: '1.2.10ubuntu1'
2018-09-26 13:58:15,755 INFO python version: '3.5.1+ (default, Mar 30 2016, 22:46:26)
[GCC 5.3.1 20160330]'
2018-09-26 13:58:15,756 INFO release-upgrader version '18.04.24' started
2018-09-26 13:58:15,840 INFO locale: 'en_US' 'UTF-8'
2018-09-26 13:58:16,158 DEBUG Using 'DistUpgradeViewGtk3' view
2018-09-26 13:58:16,214 DEBUG enable dpkg --force-overwrite
2018-09-26 13:58:16,234 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'
2018-09-26 13:58:17,061 DEBUG lsb-release: 'xenial'
2018-09-26 13:58:17,061 DEBUG _pythonSymlinkCheck run
2018-09-26 13:58:17,062 DEBUG openCache()
2018-09-26 13:58:17,062 DEBUG No such plugin directory: ./plugins
2018-09-26 13:58:17,062 DEBUG plugins for condition 'PreCacheOpen' are ''
2018-09-26 13:58:17,062 DEBUG plugins for condition 'bionicPreCacheOpen' are ''
2018-09-26 13:58:17,062 DEBUG plugins for condition 'from_xenialPreCacheOpen' are ''
2018-09-26 13:58:17,062 DEBUG quirks: running PreCacheOpen
2018-09-26 13:58:17,062 DEBUG running Quirks.PreCacheOpen
2018-09-26 13:58:17,342 DEBUG /openCache(), new cache size 12180
2018-09-26 13:58:17,342 DEBUG need_server_mode(): run in 'desktop' mode, (because of pkg 'ubuntu-desktop')
2018-09-26 13:58:17,343 DEBUG checkViewDepends()
2018-09-26 13:58:17,343 DEBUG running doUpdate() (showErrors=False)
2018-09-26 13:58:17,805 DEBUG openCache()
2018-09-26 13:58:18,083 DEBUG /openCache(), new cache size 12180
2018-09-26 13:58:18,083 DEBUG doPostInitialUpdate
2018-09-26 13:58:18,083 DEBUG plugins for condition 'PostInitialUpdate' are ''
2018-09-26 13:58:18,083 DEBUG plugins for condition 'bionicPostInitialUpdate' are ''
2018-09-26 13:58:18,083 DEBUG plugins for condition 'from_xenialPostInitialUpdate' are ''
2018-09-26 13:58:18,084 DEBUG quirks: running bionicPostInitialUpdate
2018-09-26 13:58:18,084 DEBUG running Quirks.bionicPostInitialUpdate
2018-09-26 13:58:18,119 DEBUG abort called
2018-09-26 13:58:18,120 DEBUG openCache()
2018-09-26 13:58:18,120 DEBUG failed to SystemUnLock() (E:Not locked)
2018-09-26 13:58:18,404 DEBUG /openCache(), new cache size 12180
16.04 upgrade 18.04
What are the contents of file/var/log/dist-upgrade/apt.log?
– Marcos Zolnowski
Sep 26 '18 at 20:12
Log time: 2018-09-26 11:31:46.931805 & Log time: 2018-09-26 11:31:47.694061 & Log time: 2018-09-26 11:31:47.970591
– RamiTrainFan2018
Sep 26 '18 at 20:17
Kind of empty. Well, what about/var/log/dist-upgrade/main.log?
– Marcos Zolnowski
Sep 26 '18 at 20:55
I can't do it. It has too much info
– RamiTrainFan2018
Sep 26 '18 at 20:57
Edit the question, put the contents there.
– Marcos Zolnowski
Sep 26 '18 at 20:58
|
show 8 more comments
I need some help. When i try to upgrade ubuntu 16.04 to 18.04 via update manager, It shows an X mark and closes on the preparing stage. And when i try it via terminal. I get this:
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://us.archive.ubuntu.com/ubuntu xenial InRelease
Fetched 0 B in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
Restoring original system state
Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
Can someone please help me? Thanks.
EDIT: Oh, And btw. I lost my usb. So i can't do a clean install. And my system is a Dell Latitude E7240.
File /var/log/dist-upgrade/main.log:
2018-09-26 13:58:15,662 INFO Using config files '['./DistUpgrade.cfg.xenial']'
2018-09-26 13:58:15,663 INFO uname information: 'Linux rami-Latitude-E7240 4.4.0-135-generic #161~14.04.1-Ubuntu SMP Tue Aug 28 11:17:49 UTC 2018 x86_64'
2018-09-26 13:58:15,754 INFO apt version: '1.2.10ubuntu1'
2018-09-26 13:58:15,755 INFO python version: '3.5.1+ (default, Mar 30 2016, 22:46:26)
[GCC 5.3.1 20160330]'
2018-09-26 13:58:15,756 INFO release-upgrader version '18.04.24' started
2018-09-26 13:58:15,840 INFO locale: 'en_US' 'UTF-8'
2018-09-26 13:58:16,158 DEBUG Using 'DistUpgradeViewGtk3' view
2018-09-26 13:58:16,214 DEBUG enable dpkg --force-overwrite
2018-09-26 13:58:16,234 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'
2018-09-26 13:58:17,061 DEBUG lsb-release: 'xenial'
2018-09-26 13:58:17,061 DEBUG _pythonSymlinkCheck run
2018-09-26 13:58:17,062 DEBUG openCache()
2018-09-26 13:58:17,062 DEBUG No such plugin directory: ./plugins
2018-09-26 13:58:17,062 DEBUG plugins for condition 'PreCacheOpen' are ''
2018-09-26 13:58:17,062 DEBUG plugins for condition 'bionicPreCacheOpen' are ''
2018-09-26 13:58:17,062 DEBUG plugins for condition 'from_xenialPreCacheOpen' are ''
2018-09-26 13:58:17,062 DEBUG quirks: running PreCacheOpen
2018-09-26 13:58:17,062 DEBUG running Quirks.PreCacheOpen
2018-09-26 13:58:17,342 DEBUG /openCache(), new cache size 12180
2018-09-26 13:58:17,342 DEBUG need_server_mode(): run in 'desktop' mode, (because of pkg 'ubuntu-desktop')
2018-09-26 13:58:17,343 DEBUG checkViewDepends()
2018-09-26 13:58:17,343 DEBUG running doUpdate() (showErrors=False)
2018-09-26 13:58:17,805 DEBUG openCache()
2018-09-26 13:58:18,083 DEBUG /openCache(), new cache size 12180
2018-09-26 13:58:18,083 DEBUG doPostInitialUpdate
2018-09-26 13:58:18,083 DEBUG plugins for condition 'PostInitialUpdate' are ''
2018-09-26 13:58:18,083 DEBUG plugins for condition 'bionicPostInitialUpdate' are ''
2018-09-26 13:58:18,083 DEBUG plugins for condition 'from_xenialPostInitialUpdate' are ''
2018-09-26 13:58:18,084 DEBUG quirks: running bionicPostInitialUpdate
2018-09-26 13:58:18,084 DEBUG running Quirks.bionicPostInitialUpdate
2018-09-26 13:58:18,119 DEBUG abort called
2018-09-26 13:58:18,120 DEBUG openCache()
2018-09-26 13:58:18,120 DEBUG failed to SystemUnLock() (E:Not locked)
2018-09-26 13:58:18,404 DEBUG /openCache(), new cache size 12180
16.04 upgrade 18.04
I need some help. When i try to upgrade ubuntu 16.04 to 18.04 via update manager, It shows an X mark and closes on the preparing stage. And when i try it via terminal. I get this:
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://us.archive.ubuntu.com/ubuntu xenial InRelease
Fetched 0 B in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
Restoring original system state
Aborting
Reading package lists... Done
Building dependency tree
Reading state information... Done
Can someone please help me? Thanks.
EDIT: Oh, And btw. I lost my usb. So i can't do a clean install. And my system is a Dell Latitude E7240.
File /var/log/dist-upgrade/main.log:
2018-09-26 13:58:15,662 INFO Using config files '['./DistUpgrade.cfg.xenial']'
2018-09-26 13:58:15,663 INFO uname information: 'Linux rami-Latitude-E7240 4.4.0-135-generic #161~14.04.1-Ubuntu SMP Tue Aug 28 11:17:49 UTC 2018 x86_64'
2018-09-26 13:58:15,754 INFO apt version: '1.2.10ubuntu1'
2018-09-26 13:58:15,755 INFO python version: '3.5.1+ (default, Mar 30 2016, 22:46:26)
[GCC 5.3.1 20160330]'
2018-09-26 13:58:15,756 INFO release-upgrader version '18.04.24' started
2018-09-26 13:58:15,840 INFO locale: 'en_US' 'UTF-8'
2018-09-26 13:58:16,158 DEBUG Using 'DistUpgradeViewGtk3' view
2018-09-26 13:58:16,214 DEBUG enable dpkg --force-overwrite
2018-09-26 13:58:16,234 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'
2018-09-26 13:58:17,061 DEBUG lsb-release: 'xenial'
2018-09-26 13:58:17,061 DEBUG _pythonSymlinkCheck run
2018-09-26 13:58:17,062 DEBUG openCache()
2018-09-26 13:58:17,062 DEBUG No such plugin directory: ./plugins
2018-09-26 13:58:17,062 DEBUG plugins for condition 'PreCacheOpen' are ''
2018-09-26 13:58:17,062 DEBUG plugins for condition 'bionicPreCacheOpen' are ''
2018-09-26 13:58:17,062 DEBUG plugins for condition 'from_xenialPreCacheOpen' are ''
2018-09-26 13:58:17,062 DEBUG quirks: running PreCacheOpen
2018-09-26 13:58:17,062 DEBUG running Quirks.PreCacheOpen
2018-09-26 13:58:17,342 DEBUG /openCache(), new cache size 12180
2018-09-26 13:58:17,342 DEBUG need_server_mode(): run in 'desktop' mode, (because of pkg 'ubuntu-desktop')
2018-09-26 13:58:17,343 DEBUG checkViewDepends()
2018-09-26 13:58:17,343 DEBUG running doUpdate() (showErrors=False)
2018-09-26 13:58:17,805 DEBUG openCache()
2018-09-26 13:58:18,083 DEBUG /openCache(), new cache size 12180
2018-09-26 13:58:18,083 DEBUG doPostInitialUpdate
2018-09-26 13:58:18,083 DEBUG plugins for condition 'PostInitialUpdate' are ''
2018-09-26 13:58:18,083 DEBUG plugins for condition 'bionicPostInitialUpdate' are ''
2018-09-26 13:58:18,083 DEBUG plugins for condition 'from_xenialPostInitialUpdate' are ''
2018-09-26 13:58:18,084 DEBUG quirks: running bionicPostInitialUpdate
2018-09-26 13:58:18,084 DEBUG running Quirks.bionicPostInitialUpdate
2018-09-26 13:58:18,119 DEBUG abort called
2018-09-26 13:58:18,120 DEBUG openCache()
2018-09-26 13:58:18,120 DEBUG failed to SystemUnLock() (E:Not locked)
2018-09-26 13:58:18,404 DEBUG /openCache(), new cache size 12180
16.04 upgrade 18.04
16.04 upgrade 18.04
edited Sep 26 '18 at 21:36
Marcos Zolnowski
1032
1032
asked Sep 26 '18 at 18:51
RamiTrainFan2018RamiTrainFan2018
115
115
What are the contents of file/var/log/dist-upgrade/apt.log?
– Marcos Zolnowski
Sep 26 '18 at 20:12
Log time: 2018-09-26 11:31:46.931805 & Log time: 2018-09-26 11:31:47.694061 & Log time: 2018-09-26 11:31:47.970591
– RamiTrainFan2018
Sep 26 '18 at 20:17
Kind of empty. Well, what about/var/log/dist-upgrade/main.log?
– Marcos Zolnowski
Sep 26 '18 at 20:55
I can't do it. It has too much info
– RamiTrainFan2018
Sep 26 '18 at 20:57
Edit the question, put the contents there.
– Marcos Zolnowski
Sep 26 '18 at 20:58
|
show 8 more comments
What are the contents of file/var/log/dist-upgrade/apt.log?
– Marcos Zolnowski
Sep 26 '18 at 20:12
Log time: 2018-09-26 11:31:46.931805 & Log time: 2018-09-26 11:31:47.694061 & Log time: 2018-09-26 11:31:47.970591
– RamiTrainFan2018
Sep 26 '18 at 20:17
Kind of empty. Well, what about/var/log/dist-upgrade/main.log?
– Marcos Zolnowski
Sep 26 '18 at 20:55
I can't do it. It has too much info
– RamiTrainFan2018
Sep 26 '18 at 20:57
Edit the question, put the contents there.
– Marcos Zolnowski
Sep 26 '18 at 20:58
What are the contents of file
/var/log/dist-upgrade/apt.log?– Marcos Zolnowski
Sep 26 '18 at 20:12
What are the contents of file
/var/log/dist-upgrade/apt.log?– Marcos Zolnowski
Sep 26 '18 at 20:12
Log time: 2018-09-26 11:31:46.931805 & Log time: 2018-09-26 11:31:47.694061 & Log time: 2018-09-26 11:31:47.970591
– RamiTrainFan2018
Sep 26 '18 at 20:17
Log time: 2018-09-26 11:31:46.931805 & Log time: 2018-09-26 11:31:47.694061 & Log time: 2018-09-26 11:31:47.970591
– RamiTrainFan2018
Sep 26 '18 at 20:17
Kind of empty. Well, what about
/var/log/dist-upgrade/main.log?– Marcos Zolnowski
Sep 26 '18 at 20:55
Kind of empty. Well, what about
/var/log/dist-upgrade/main.log?– Marcos Zolnowski
Sep 26 '18 at 20:55
I can't do it. It has too much info
– RamiTrainFan2018
Sep 26 '18 at 20:57
I can't do it. It has too much info
– RamiTrainFan2018
Sep 26 '18 at 20:57
Edit the question, put the contents there.
– Marcos Zolnowski
Sep 26 '18 at 20:58
Edit the question, put the contents there.
– Marcos Zolnowski
Sep 26 '18 at 20:58
|
show 8 more comments
2 Answers
2
active
oldest
votes
Still researching but running it all under strace suggests that the last failure before the Abort is trying to run something snap related - /tmp/ubuntu-release-upgrader-9dqwuool/imported/snap debug connectivity which is dying with error: cannot communicate with server: Post http://localhost/v2/debug: dial unix /run/snapd.socket: connect: connection refused
Ah, in fact, snap debug connectivity blows up when run directly, service snapd status says Active: failed (Result: start-limit-hit); running service snapd start results in a status of Active: active (running) and then snap debug connectivity says Connectivity status: * PASS... and then do-release-upgrade actually makes progress.
Based on other search results, please note that this only applies if your main.log goes immediately from running Quirks.bionicPostInitialUpdate to abort called -- if there's anything else in there it's probably not this.
It looks like this might relate to https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1780841 (which seems to be what implements the feature that doesn't work here.)
add a comment |
I had the same issue, Ubuntu 16 LTS to Ubuntu 18.04 LTS upgrade failed to start.
Using the graphical upgrade tool it stops quickly after 'preparing', not saying anything.
Using do-release-upgrade it stops at:
2019-03-08 23:55:58,515 DEBUG running Quirks.bionicPostInitialUpdate
2019-03-08 23:55:58,524 DEBUG abort called
It proved to be the snap daemon not running (systemctl status snapd) on my system causing the upgrade to fail without further notice.
New contributor
Arno is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f1078692%2fcant-upgrade-ubuntu-16-04-to-18-04-lts%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Still researching but running it all under strace suggests that the last failure before the Abort is trying to run something snap related - /tmp/ubuntu-release-upgrader-9dqwuool/imported/snap debug connectivity which is dying with error: cannot communicate with server: Post http://localhost/v2/debug: dial unix /run/snapd.socket: connect: connection refused
Ah, in fact, snap debug connectivity blows up when run directly, service snapd status says Active: failed (Result: start-limit-hit); running service snapd start results in a status of Active: active (running) and then snap debug connectivity says Connectivity status: * PASS... and then do-release-upgrade actually makes progress.
Based on other search results, please note that this only applies if your main.log goes immediately from running Quirks.bionicPostInitialUpdate to abort called -- if there's anything else in there it's probably not this.
It looks like this might relate to https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1780841 (which seems to be what implements the feature that doesn't work here.)
add a comment |
Still researching but running it all under strace suggests that the last failure before the Abort is trying to run something snap related - /tmp/ubuntu-release-upgrader-9dqwuool/imported/snap debug connectivity which is dying with error: cannot communicate with server: Post http://localhost/v2/debug: dial unix /run/snapd.socket: connect: connection refused
Ah, in fact, snap debug connectivity blows up when run directly, service snapd status says Active: failed (Result: start-limit-hit); running service snapd start results in a status of Active: active (running) and then snap debug connectivity says Connectivity status: * PASS... and then do-release-upgrade actually makes progress.
Based on other search results, please note that this only applies if your main.log goes immediately from running Quirks.bionicPostInitialUpdate to abort called -- if there's anything else in there it's probably not this.
It looks like this might relate to https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1780841 (which seems to be what implements the feature that doesn't work here.)
add a comment |
Still researching but running it all under strace suggests that the last failure before the Abort is trying to run something snap related - /tmp/ubuntu-release-upgrader-9dqwuool/imported/snap debug connectivity which is dying with error: cannot communicate with server: Post http://localhost/v2/debug: dial unix /run/snapd.socket: connect: connection refused
Ah, in fact, snap debug connectivity blows up when run directly, service snapd status says Active: failed (Result: start-limit-hit); running service snapd start results in a status of Active: active (running) and then snap debug connectivity says Connectivity status: * PASS... and then do-release-upgrade actually makes progress.
Based on other search results, please note that this only applies if your main.log goes immediately from running Quirks.bionicPostInitialUpdate to abort called -- if there's anything else in there it's probably not this.
It looks like this might relate to https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1780841 (which seems to be what implements the feature that doesn't work here.)
Still researching but running it all under strace suggests that the last failure before the Abort is trying to run something snap related - /tmp/ubuntu-release-upgrader-9dqwuool/imported/snap debug connectivity which is dying with error: cannot communicate with server: Post http://localhost/v2/debug: dial unix /run/snapd.socket: connect: connection refused
Ah, in fact, snap debug connectivity blows up when run directly, service snapd status says Active: failed (Result: start-limit-hit); running service snapd start results in a status of Active: active (running) and then snap debug connectivity says Connectivity status: * PASS... and then do-release-upgrade actually makes progress.
Based on other search results, please note that this only applies if your main.log goes immediately from running Quirks.bionicPostInitialUpdate to abort called -- if there's anything else in there it's probably not this.
It looks like this might relate to https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1780841 (which seems to be what implements the feature that doesn't work here.)
answered Dec 13 '18 at 3:39
eichineichin
513
513
add a comment |
add a comment |
I had the same issue, Ubuntu 16 LTS to Ubuntu 18.04 LTS upgrade failed to start.
Using the graphical upgrade tool it stops quickly after 'preparing', not saying anything.
Using do-release-upgrade it stops at:
2019-03-08 23:55:58,515 DEBUG running Quirks.bionicPostInitialUpdate
2019-03-08 23:55:58,524 DEBUG abort called
It proved to be the snap daemon not running (systemctl status snapd) on my system causing the upgrade to fail without further notice.
New contributor
Arno is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I had the same issue, Ubuntu 16 LTS to Ubuntu 18.04 LTS upgrade failed to start.
Using the graphical upgrade tool it stops quickly after 'preparing', not saying anything.
Using do-release-upgrade it stops at:
2019-03-08 23:55:58,515 DEBUG running Quirks.bionicPostInitialUpdate
2019-03-08 23:55:58,524 DEBUG abort called
It proved to be the snap daemon not running (systemctl status snapd) on my system causing the upgrade to fail without further notice.
New contributor
Arno is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I had the same issue, Ubuntu 16 LTS to Ubuntu 18.04 LTS upgrade failed to start.
Using the graphical upgrade tool it stops quickly after 'preparing', not saying anything.
Using do-release-upgrade it stops at:
2019-03-08 23:55:58,515 DEBUG running Quirks.bionicPostInitialUpdate
2019-03-08 23:55:58,524 DEBUG abort called
It proved to be the snap daemon not running (systemctl status snapd) on my system causing the upgrade to fail without further notice.
New contributor
Arno is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I had the same issue, Ubuntu 16 LTS to Ubuntu 18.04 LTS upgrade failed to start.
Using the graphical upgrade tool it stops quickly after 'preparing', not saying anything.
Using do-release-upgrade it stops at:
2019-03-08 23:55:58,515 DEBUG running Quirks.bionicPostInitialUpdate
2019-03-08 23:55:58,524 DEBUG abort called
It proved to be the snap daemon not running (systemctl status snapd) on my system causing the upgrade to fail without further notice.
New contributor
Arno is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Arno is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 29 mins ago
ArnoArno
12
12
New contributor
Arno is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Arno is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Arno is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1078692%2fcant-upgrade-ubuntu-16-04-to-18-04-lts%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
What are the contents of file
/var/log/dist-upgrade/apt.log?– Marcos Zolnowski
Sep 26 '18 at 20:12
Log time: 2018-09-26 11:31:46.931805 & Log time: 2018-09-26 11:31:47.694061 & Log time: 2018-09-26 11:31:47.970591
– RamiTrainFan2018
Sep 26 '18 at 20:17
Kind of empty. Well, what about
/var/log/dist-upgrade/main.log?– Marcos Zolnowski
Sep 26 '18 at 20:55
I can't do it. It has too much info
– RamiTrainFan2018
Sep 26 '18 at 20:57
Edit the question, put the contents there.
– Marcos Zolnowski
Sep 26 '18 at 20:58