12-23-2011
Do those servers start to swap a lot in the evening? Are all servers hosting both webserver and database or are there dedicated boxes that run only one component? Did you investigate why tomcat / postgres / system reboot themself?
The most common reason I've seen systems reboot themself without a hardware issue was them running out of paging space.
9 More Discussions You Might Find Interesting
1. SCO
Dear sir,
I am using sco open server 5.06.How we can reboot the system without using root password? Whar are the permision need to change to do this.
Thanks,
Mostafizur Rahman (3 Replies)
Discussion started by: rahmanm
3 Replies
2. Shell Programming and Scripting
I want to get an email alert from a cronjob when a server got rebooted unexpectedly. Please help. Thanks! :confused: (2 Replies)
Discussion started by: angloi
2 Replies
3. UNIX for Advanced & Expert Users
hi all, :)
for a reboot of sun box for patch installation i would like to know where do the reboot logs apart from /var/adm/messages and patch run messages would be available,
i would like to know the sequence of messages logged in the file like
requesting the users to log out
sending a... (1 Reply)
Discussion started by: matrixmadhan
1 Replies
4. AIX
I've recently changed my gateway setting using SMIT. Everything went fine except that the gateway setting kept reverting back to the old one everytime I reboot the server.
I'm on AIX 5.2 running p-Series. Thanks for any info. (3 Replies)
Discussion started by: dereklow
3 Replies
5. Solaris
Hi All,
I want to know the procedure like if server is down, i want to reboot the server through console ($rsc or $sc prompt).Could you please help me out.
I would really appreciate your cooperation.
thanks for understanding
regards
krishna (5 Replies)
Discussion started by: murthy76
5 Replies
6. UNIX for Advanced & Expert Users
Hi,
please could someone advise the best command to shutdown and then for it to reboot back online again.
Note: I shall be doing this from a telent session.
regards
venhart (3 Replies)
Discussion started by: venhart
3 Replies
7. Red Hat
Hi All,
Our Linux server were rebooted 723 days before and now We have decided to reboot the server due to server performance.
Could someone advise us what is the optimal duration of a server reboot ?
Thanks for your time.
Best Regards,
Arun (2 Replies)
Discussion started by: arunap44
2 Replies
8. Solaris
Hi,
anyone please let us know how to write shell script to find the missing mountpoints after server reboot.
i want to take the mountpount information before server reboot, and validate the mountpoints after server reboot if any missing.please let us know the shell script from begining to end as... (24 Replies)
Discussion started by: VenkatReddy786
24 Replies
9. Red Hat
Hi,
The server got rebooted and below messages can be seen in /var/log/messages
Sep 7 10:49:12 minersville kernel: Call Trace: <IRQ> <ffffffff80167420>{__alloc_pages+796}
Sep 7 10:49:12 minersville kernel: <ffffffff80182814>{kmem_getpages+106} <ffffffff80183c16>{fallback_alloc+304}... (3 Replies)
Discussion started by: admin_db
3 Replies
reboot(1M) reboot(1M)
NAME
reboot - reboot the system
SYNOPSIS
time] message]
time] message]
DESCRIPTION
The command terminates all currently executing processes except those essential to the system, then reboots the system, or halts, or makes
the partition ready for reconfiguration. When invoked without arguments, syncs all disks before rebooting the system.
Options
The command recognizes the following options:
Shut down the system and halt.
Shut down the system and reboot automatically (default).
Shut down the system to a ready-to-reconfigure state and reboot if possible.
If the partition is unable to reboot, it will stop at a ready-to-reconfigure state. However, if the option is also
specified, the system will always stop at ready-to-reconfigure state. This option is available only on systems that
support hardware partitions.
Shut down the system to a ready-to-reconfigure state and do not reboot.
This option can be used only in combination with the option. This option is available only on systems that support
hardware partitions.
Do not sync the file systems before shutdown.
The and options are ignored with this option.
Sync the file systems before shutdown;
for file systems that were cleanly mounted, modify the flag from to (default).
Quick and quiet.
Suppress broadcast of warning messages, terminate processes by brute force (with and immediately call with arguments
as indicated by the other options (see reboot(2)). No logging is performed. The and options are ignored with this
option.
Specify what time
will bring the system down. time can be the word (indicating immediate shutdown) or a future time in one of two for-
mats: and The first form brings the system down in number minutes; the second brings the system down at the time of
day indicated (based on a 24-hour clock).
Display message at the terminals of all users on the system at decreasing intervals as reboot time approaches. The message
must not contain any embedded double quotes.
At shutdown time a message is written in the file
(if it exists), containing the time of shutdown, who ran and the reason.
Only users with appropriate privileges can execute the command.
WARNINGS
does not invoke the shutdown scripts associated with subsystems to bring them down in a cautious manner. See shutdown(1M).
If the option is used in a virtual partition environment on a partitionable system, then the requested reconfiguration will not take place
until all the virtual partitions on that hard partition are shut down and the virtual partition monitor is rebooted.
AUTHOR
was developed by HP and the University of California, Berkeley.
FILES
Shutdown log
SEE ALSO
vpartition(1), reboot(2), partition(5).
reboot(1M)