Sponsored Content
Full Discussion: Unable to take console
Operating Systems Solaris Unable to take console Post 302633903 by methyl on Wednesday 2nd of May 2012 04:05:03 PM
Old 05-02-2012
Please post what Hardware make and model and what Operating System and version you are running.

Were you able to become the root user by another means?

Is this a sudden fault on a reliable system or a problem on a new system?

Please post the contents of /etc/inittab .

Quick check in memory to see if there are lots of processes for the same user or lots of the same process (or both):
Code:
ps -fuplhw
ps -ef|grep "plathwsvcd"

Just Googled plathwsvcd and got a lot of hits for this name and your symptoms related to firmware revisions on Sun hardware.
 

10 More Discussions You Might Find Interesting

1. HP-UX

Root account disabled and unable to access console

Hi, hope someone could help me here: Our root account was disabled on our production server this morning and usually we would login at the console to re-enable the account. However we are unable to get a login prompt at the console. The console displays the 8 options along the bottom and a... (2 Replies)
Discussion started by: AaronC
2 Replies

2. HP-UX

Unable to login at console and telnet

Hi friend, I'm facing a problem to access the console and telnet to the HP ux 11 server due to the system file is full. How to access this server via single mode and how to mount the folder / and folder /var? thanks. vestro (1 Reply)
Discussion started by: vestro
1 Replies

3. Solaris

sun 8 unable to communicate through console

Hi : I have a e450 sun server that I just started up and I connect my laptop to the serial connection using a null modem cable and it just does not connect. I use hyperterminal, I dont connect a keyboard to the sun machine? Any ideas? Thanks a lot Al (3 Replies)
Discussion started by: alanj4
3 Replies

4. Infrastructure Monitoring

unable to load console info in SUNMC 4.0

hi all, unable to load console info in SUNMC 4.0 in alarm it is giving error info i.e..Agent on host (.....),1161 port not responding. plz try to solve the problem Regards spandhan (5 Replies)
Discussion started by: spandhan
5 Replies

5. Solaris

unable to load console info in SUNMC 4.0

Hi all, unable to load console info in SUNMC 4.0 in alarm it is giving error info i.e..Agent on host (.....),1161 port not responding. Iam using M9000 server solaris 10 plz try to solve the problem Regards spandhan (0 Replies)
Discussion started by: spandhan
0 Replies

6. Solaris

E25k domain server am unable to access console.

Hi Guys, I am working on the e25k server. There is 4 domain configured Once domain is down So I tried to access the console for the problem domain. using console -d B but its showing following error message. bash-2.05$ console -d B Domain administration permissions... (3 Replies)
Discussion started by: arumsun
3 Replies

7. AIX

Unable to Switch tasks when trying to open console window in HMC

Hi, I am trying to open a console window through the HMC. When I choose to do this the toolbar at the top left of the HMC screen show 'Open Terminal Window'. However when I click on it I am getting the error - "The tsak you want to switch to is an applet based task, which dowes not support... (1 Reply)
Discussion started by: jimthompson
1 Replies

8. AIX

P550 Unable to access Console

I have recently aquired the following machine: IBM,9113-550 Up until yesterday we could connect a dumb terminal to serial port 1 and get console login. However the dumb terminal died. We are now using a laptop with a null modem cable attached to serial port 1. This works perfectly for all of... (1 Reply)
Discussion started by: rsw7724
1 Replies

9. Solaris

Unable to start webconsole:console

Here is issue... bash-3.00# svcs system/webconsole:console STATE STIME FMRI maintenance 1:15:54 svc:/system/webconsole:console bash-3.00# svcadm clear svc:/system/webconsole:console bash-3.00# svcs -a |grep /system/webconsole offline* 1:20:44... (0 Replies)
Discussion started by: lingeshwaran
0 Replies

10. Solaris

Unable to login via console mode to non-global zone

tldr; We've installed a non-global-zone from a unified archive which once booted, we're unable to gain access to the system either through zlogin or zlogin -C. Errors; svc.startd: instance svc:/system/console-login:default exited with status 127 Investigation; 1) Already opened a SR with... (1 Reply)
Discussion started by: samthewildone
1 Replies
init(8) 						      System Manager's Manual							   init(8)

NAME
init - Process control initialization SYNOPSIS
/sbin/init [0123456789MmQqSs] DESCRIPTION
The init program initializes the system by creating and controlling processes. The processes run by init at each run level are defined in the inittab file. The init program reads and processes the entries in the inittab file. The init program considers the system to be in a run level at any given time; each run level has a specific group of processes that run at that level. The init program operates in one of eleven run levels: 0-9 and Ss. Of these, only 0, s, 2, and 3 are configured in the inittab file by default. The run level changes when a privileged user invokes init. The new init sends appropriate signals to the original init that tell it which run level to change to. Running the init program is the last step in the boot process after the root file system is mounted. The init program scans the inittab file and looks for an entry with the initdefault keyword. If the entry is there, init uses the run level specified in that entry as the initial run level to enter. If the entry is not found in the inittab file or if the inittab file does not exist, init requests that the user enter a run level from the system console, /dev/console. If the user enters the letter s, init enters single user state, assigns the virtual console terminal to the user's terminal and opens it for reading and writing. The su command is invoked and the system displays a message on the console stating the location of the virtual console. To change the run level, the user specifies either the 0, 2, 3, or s flag. For the first post-boot execution of init to a run level other than single user, it searches the inittab file for entries at the new run level that have the boot or bootwait keywords. If the run level that is specified matches the entry, the init program acts on these entries before processing other entries in the inittab file. Any special initialization of the system, such as checking and mounting file systems, takes place before users are allowed on the system. The init program then scans the inittab file to find all entries that are to be handled for that level. Before starting a new process, init reads each entry in the inittab file, and for each entry that should be respawned, init forks a child process. After spawning all required processes, init waits for one of its descendant processes to stop, a power-fail signal, or a signal that it should change the run level. If one of the preceding three conditions occurs, init reexamines the inittab file. You can add new entries to the inittab file, but init does not reexamine the file until one of the three previous conditions actually occurs. To immedi- ately reexamine the inittab file, invoke the init program with the q flag. FLAGS
Shuts down and halts the system. Changes the run level to a multiuser state with local processes and daemons. Changes the run level to a multiuser state with remote processes and daemons. Changes run level to that specified by the number flag in the /etc/inittab file. If no such entry exists, no action is taken and no message is output. Moves control to the console device and halts to single-user mode. Forces init to reexamine the entries in the inittab file and terminates any live processes which have had their configuration entries removed from /etc/inittab. Users should be aware that when a getty(8) line has been removed from /etc/inittab, and a login shell is active on the ter- minal line that was formerly designated in inittab as a getty entry, the login shell will be killed. Changes the run level to a single user state with only the essential kernel services. FILES
Specifies the command path Specifies the init command control file Specifies the permanent login accounting file RELATED INFORMATION
Commands: getty(8), rc0(8), rc2(8), rc3(8), shutdown(8) Calls: kill(2), reboot(2) Files: inittab(4) delim off init(8)
All times are GMT -4. The time now is 10:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy