Public bug reported:

Binary package hint: update-manager

During a server upgrade with "sudo do-release-upgrade", I was asked
twice about starting an ssh daemon on port 9004.  This seems like a
handy precaution, but it should only be necessary to ask once.

norman% sudo apt-get install update-manager-core
Reading package lists... Done
Building dependency tree       
Reading state information... Done
update-manager-core is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
norman% sudo do-release-upgrade
Checking for a new ubuntu release
Done Upgrade tool signature
Done Upgrade tool
Done downloading            
extracting '/tmp/tmp_G0z5h/gutsy.tar.gz'
authenticate '/tmp/tmp_G0z5h/gutsy.tar.gz' against 
'/tmp/tmp_G0z5h/gutsy.tar.gz.gpg' 

Reading cache

Checking package manager

Continue running under SSH?
This session appears to be running under ssh. It is not recommended to perform 
an upgrade over ssh at present, because in case of failure it is harder to 
recover.

If you continue, an additional ssh daemon will be started at port '9004'.
Do you want to continue?
Continue [yN] y

Starting additional sshd
To make recovery in case of failure easier an additional sshd will be started 
on port '9004'. If anything goes wrong with the running ssh you can still 
connect to the additional one.

Reading package lists: Donefeisty-security/restricted Packages: 96   
Reading state information: Done
Reading state information: Done
Reading state information: Done
Done http://security.ubuntu.com feisty-security Release.gpg
Done http://archive.canonical.com feisty-commercial Release.gpg
Done http://archive.canonical.com feisty-commercial Release
Done http://gb.archive.ubuntu.com feisty Release.gpg
Done http://gb.archive.ubuntu.com feisty-updates Release.gpg
Done http://gb.archive.ubuntu.com feisty-backports Release.gpg
Done http://security.ubuntu.com feisty-security Release
Hit http://gb.archive.ubuntu.com feisty Release
Done http://gb.archive.ubuntu.com feisty-updates Release
Done http://gb.archive.ubuntu.com feisty-backports Release
Done http://archive.canonical.com feisty-commercial Release
Done http://archive.canonical.com feisty-commercial/main Packages
Done http://security.ubuntu.com feisty-security Release
Done http://security.ubuntu.com feisty-security/main Packages
Done http://security.ubuntu.com feisty-security/restricted Packages
Done http://security.ubuntu.com feisty-security/main Sources
Done http://security.ubuntu.com feisty-security/restricted Sources
Done http://archive.canonical.com feisty-commercial/main Packages
Done http://gb.archive.ubuntu.com feisty Release
Hit http://gb.archive.ubuntu.com feisty/main Packages
Hit http://gb.archive.ubuntu.com feisty/restricted Packages
Hit http://gb.archive.ubuntu.com feisty/universe Packages
Hit http://gb.archive.ubuntu.com feisty/multiverse Packages
Hit http://gb.archive.ubuntu.com feisty/main Sources
Hit http://gb.archive.ubuntu.com feisty/restricted Sources
Done http://gb.archive.ubuntu.com feisty-updates Release
Done http://gb.archive.ubuntu.com feisty-updates/main Packages
Done http://gb.archive.ubuntu.com feisty-updates/restricted Packages
Done http://gb.archive.ubuntu.com feisty-updates/main Sources
Done http://gb.archive.ubuntu.com feisty-updates/restricted Sources
Done http://gb.archive.ubuntu.com feisty-backports Release
Done http://gb.archive.ubuntu.com feisty-backports/main/debian-installer 
Packages
Done http://security.ubuntu.com feisty-security/main Packages
Done http://security.ubuntu.com feisty-security/restricted Packages
Done http://security.ubuntu.com feisty-security/main Sources
Done http://security.ubuntu.com feisty-security/restricted Sources
Done http://gb.archive.ubuntu.com feisty-updates/main Packages
Done http://gb.archive.ubuntu.com feisty-updates/restricted Packages
Done http://gb.archive.ubuntu.com feisty-updates/main Sources
Done http://gb.archive.ubuntu.com feisty-updates/restricted Sources
Done http://gb.archive.ubuntu.com feisty-backports/main/debian-installer 
Packages
Done downloading            
http://gb.archive.ubuntu.com feisty-backports/main/debian-installer Packages: 
96Reading package lists: Done
Reading state information: Done
Reading state information: Done
Reading state information: Done
Done http://gb.archive.ubuntu.com feisty-backports/main/debian-installer 
release-upgrader-dpkg 1.14.5ubuntu11.2
Done http://gb.archive.ubuntu.com feisty-backports/main/debian-installer 
release-upgrader-apt 0.6.46.4ubuntu10.3
Done downloading            

Reading cache

Checking package manager

Continue running under SSH?
This session appears to be running under ssh. It is not recommended to perform 
an upgrade over ssh at present, because in case of failure it is harder to 
recover.

If you continue, an additional ssh daemon will be started at port '9004'.
Do you want to continue?
Continue [yN] y

Starting additional sshd
To make recovery in case of failure easier an additional sshd will be started 
on port '9004'. If anything goes wrong with the running ssh you can still 
connect to the additional one.

Reading package lists: Donefeisty-security/restricted Packages: 96

** Affects: update-manager (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Asked twice about ssh daemon
https://bugs.launchpad.net/bugs/156625
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to