Login or Register to Ask a Question and Join Our Community


UNIX for Beginners Questions & Answers

No init messages display during startup/shutdown

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums UNIX for Beginners Questions & Answers No init messages display during startup/shutdown
# 1  
Old 03-18-2017
No init messages display during startup/shutdown
This question is more in the line of how init messages get sent to a console during startup/shutdown. My problem has to do with exporting a VM from AWS to KVM (and a retry on virtual box). I am looking for a understanding on how init messages are sent to a device and what controls them My two servers listed below are Centos. Any help in this understanding would be greatly appreciated. Any additional knowledge on how AWS is modify this would also be appreciated.

I have exported two VM's. Both imports successfully on virtualbox and kvm but one allows you to login (login prompt) and the other never comes to the login prompt. For the VM that allows log in I have edited /default/grub2 and removed silent and added text and regenerated the grub.conf. I also put a exit in the /etc/init.d/netconsole so that it doesn't run. I still dont get any init messages to the console when I reboot. I need to determine how to do this so I can make the changes to a EC2 VM so when I export it again and try to run it in virtualbox and KVM it will list a service that it is getting hung up on. Any help would be greatly appreciated

Thanks
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Startup and shutdown script

Hi all, I'm writing a script to stop & start oracle: su - oracle -c "sqlplus / as sysdba" -c "shutdown immediate">> ${log} 2>&1 The {log} refers to the log file. The part in bold gives error: /usr/sbin/shutdown: Only root can run /usr/sbin/shutdown Pls suggest how to correct this. ... (5 Replies)
Discussion started by: frum
5 Replies

2. AIX

Auto startup and shutdown in AIX

Hi All, I would like to schedule auto IPL (shutdown and start-up) by using a shell script. Can you please give me some idea? want to test on my lab box first. shell script should bring AIX LPAR down and then need to start/activate the LPAR after 30 min any idea is highly... (3 Replies)
Discussion started by: System Admin 77
3 Replies

3. Shell Programming and Scripting

Automatic shutdown and startup of Tomcat in Solaris

Dear Experts , I want to stop and Start tomcat at the time of shutdown and startup of our server . I was trying to stop tomcat with following command # su - dm -c "/export/home/Finder/FinderWeb/jakarta-tomcat-3.3.1a/bin/shutdown.sh" but i am getting following error. Please suggest .... (1 Reply)
Discussion started by: Amit.saini333
1 Replies

4. AIX

Startup/shutdown scripts in AIX

hi, If we place Sxx (startup script) and Kxx(shutdown script) in /etc/rc.d/rc2.d,then it would start and stop automatically(assume they are linked to other script that actually starts/stops). is there really a link needed here to /etc/rc.d/init.d? if not,what is the use of this directory..?... (1 Reply)
Discussion started by: to_bsr
1 Replies

5. Solaris

Startup and shutdown a server

Are rc scripts executed serially or all at the same time. Is there a way to see this happen? A log file or the syslogd? This is Solaris 10. (2 Replies)
Discussion started by: djehresmann
2 Replies

6. UNIX for Dummies Questions & Answers

Where is the shutdown/startup log?

Having difficulty trying to locate startup and shutdown messages. I had a bunch of servers shutdown over the weekend (due to a scheduled power outage) and upon reboot a lot of the filesystems weren't mounted and several processes weren't started... I checked /var/adm/messages and can't locate... (2 Replies)
Discussion started by: jamie_collins
2 Replies

7. Solaris

difference between init and shutdown

Hi, Am new to solaris.Can anyone explains me the difference between using init and shutdown command. As per my knowledge shutdown will give notification to users, is there anything apart from that. thanks in advance. (6 Replies)
Discussion started by: rogerben
6 Replies

8. SuSE

How to record shutdown/startup messages

The wtmp file records all logins and logouts. Its format is exactly like utmp except that a null user name indicates a logout on the associated terminal. Furthermore, the terminal name "~" with user name "shutdown" or "reboot" indicates a system shutdown or reboot and the pair of terminal names... (1 Reply)
Discussion started by: Laksmi
1 Replies

9. UNIX for Dummies Questions & Answers

init issue on startup

Hi, I modified my inittab file in the /etc directory. When I started up my machine, system hangs on initialization. I'm trying to remove what I added in the inittab file so that everything is back to normal. I'm using AIX 5 and I would like to boot up so I can get back into a regular... (0 Replies)
Discussion started by: dhuser
0 Replies

10. AIX

Startup/Shutdown scripts

I understand that by putting in entries into the /etc/inittab file. We can actually call the our scripts during startup. mkitab "start_server:2:once:sh /scripts/startserver.sh" Would the system wait for startserver.sh finish executing before it goes to another entry? and how long would it... (1 Reply)
Discussion started by: vincente
1 Replies
Login or Register to Ask a Question

LEARN ABOUT LINUX

init

init(8) 						      System Manager's Manual							   init(8)

NAME

       init - Upstart process management daemon

SYNOPSIS

       init [OPTION]...

DESCRIPTION

       init  is the parent of all processes on the system, it is executed by the kernel and is responsible for starting all other processes; it is
       the parent of all processes whose natural parents have died and it is responsible for reaping those when they die.

       Processes managed by init are known as jobs and are defined by files in the /etc/init directory.  See init(5) for more details on configur-
       ing Upstart.

   Events
       init(8)	is an event-based init daemon.	This means that jobs will be automatically started and stopped by changes that occur to the system
       state, including as a result of jobs starting and stopping.

       This is different to dependency-based init daemons which start a specified set of goal jobs, and resolve the order in which they should	be
       started and other jobs required by iterating their dependencies.

       For  more information on starting and stopping jobs, as well as emitting events that will automatically start and stop jobs, see the manual
       page for the initctl(8) tool.

       The primary event is the startup(7) event, emitted when the daemon has finished loading its configuration.  Other  useful  events  are  the
       starting(7), started(7), stopping(7) and stopped(7) events emitted as jobs change state.

       See upstart-events(7) for a summary of well-known events.

   System V compatibility
       The  Upstart  init(8)  daemon  does  not keep track of runlevels itself, instead they are implemented entirely by its userspace tools.  The
       event emitted to signify a change of runlevel is the runlevel(7) event.	For more information see its manual page.

OPTIONS

       Options are passed to init(8) by placing them on the kernel command-line.

       --confdir directory
	      Read job configuration files from a directory other than /etc/init.

       --no-sessions
	      Disable user and chroot sessions.

       --no-startup-event
	      Suppress emission of the initial startup event. This option should only be used for testing since it will stop  the  init(8)  daemon
	      from starting any jobs automatically.

       --session
	      Connect to the D-Bus session bus. This should only be used for testing.

       --startup-event event
	      Specify a different initial startup event from the standard startup(7).

       --verbose
	      Outputs verbose messages about job state changes and event emissions to the system console or log, useful for debugging boot.

NOTES

       init  is not normally executed by a user process, and expects to have a process id of 1.  If this is not the case, it will actually execute
       telinit(8) and pass all arguments to that.  See that manual page for further details.

FILES

       /etc/init.conf

       /etc/init/*.conf

       $HOME/.init/

AUTHOR

       Written by Scott James Remnant <scott@netsplit.com>

REPORTING BUGS

       Report bugs at <https://launchpad.net/upstart/+bugs>

COPYRIGHT

       Copyright (C) 2009-2011 Canonical Ltd.
       This is free software; see the source for copying conditions.  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
       LAR PURPOSE.

SEE ALSO

       control-alt-delete(7) init(5) initctl(8) runlevel(7) startup(7) starting(7) started(7) stopping(7) stopped(7) telinit(8) upstart-events(7)

Upstart 							    2011-04-06								   init(8)