I can confirm that the code for the upstart jobs in 14.04 behaves as you
describe. However, this seems to be the first time since 14.04
released, two years ago, that someone has noticed this behavior and
considered it to warrant a bug report.
While switching to runlevel 1 and back *should* restore the consoles,
this is not at all a common maintenance operation. Ubuntu users will
normally reboot instead of switching between runlevels in this manner.
Added to this that you have marked this bug as 'medium' severity, thus
meaning that it does not rise to the level of a stable release update;
and the fact that fixing this in 14.04 would be non-trivial; I am
declining this bug as 'wontfix'.
For Ubuntu 16.04, consoles are implemented differently via systemd. If
you see any bugs in the handling of runlevel switches with systemd, it
would be useful to know this so that we might fix them before 16.04 GA.
** Package changed: ubuntu => upstart (Ubuntu)
** Changed in: upstart (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1557990
Title:
[upstart] console access of the server is lost when trying to change
runlevel 3 from runlevel 1
Status in upstart package in Ubuntu:
Won't Fix
Bug description:
Problem Description
============================
console access is lost if #init 3 ; is run from #init 1 ;
---uname output---
4.2.0-30-generic #35~14.04.1-Ubuntu SMP Fri Feb 19 15:23:48 UTC 2016 ppc64le
ppc64le ppc64le GNU/Linux
Machine Type = 8247-22L
Steps to Reproduce
====================================
login to console of ubuntu 14.04.4 system (either on bare-metal or PowerVM
based lpar ) , use ipmitool console for bare-metal, use mkvterm console from
hmc for PowerVM based lpar.
#runlevel ; to check the current default run level
#init 1;
#init 3; or ; #exit
Console access is lost [hung] cannot regain the console, only
solution is reboot of the server.
=========console logs=======
root@ltcbrazos2-lp18:~# init 1
root@ltcbrazos2-lp18:~# Skip stopping firewall: ufw (not enabled)
wait-for-state stop/waiting
* Stopping rsync daemon rsync [ OK
]
[ OK
]
* Killing all remaining processes...
[fail]
* Will now switch to single-user mode
Give root password for maintenance
(or type Control-D to continue):
root@ltcbrazos2-lp18:~#
root@ltcbrazos2-lp18:~#
root@ltcbrazos2-lp18:~# runlevel
1 S
root@ltcbrazos2-lp18:~# init 3
root@ltcbrazos2-lp18:~# exit
* Restoring resolver state... [ OK
]
===========================
Console is hung indefinitely, no login prompt is offered
===========================
Please note the system successfully goes to #init 3 ;
network comes back, SSH works, but cannot access the system via any console.
Userspace rpm: upstart
== Comment: #2 - NAVEED A. UPPINANGADY SALIH <naveed...@in.ibm.com> -
2016-02-26 07:28:47 ==
(In reply to comment #1)
> Hi Naveed,
>
> Can you please check for 'who -r' once you switch to runlevel 3 ?
> What is the intention of the exit command here ? Is it for you to terminate
> your session ? Is the terminal available for you to execute other commands
> as well or does it hang at that stage as well?
>
> Thank you.
you can access the system via terminal using ssh even though console is not
accessible
==========
root@ltcbrazos2-lp18:~# who -r
run-level 3 2016-02-26 07:14 last=S
==========
I think "exit" or "init 3" either of the command does same from runlevel 1 ?
Correct me if I am wrong.
from ssh session if "init 6" or "init 1" is issued again, we are able
to access the console again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1557990/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
