Sponsored Content
Operating Systems Linux Red Hat Logs & Lists to Save before httpd restart when web server freezes? Post 302858827 by joeyg on Tuesday 1st of October 2013 01:21:41 PM
Old 10-01-2013
Your Sys Admin is fine with you doing this? He/she should be working to resolve, or at least be directing you to what to look for before simply power-down/power-up.
So many things to think about...
# users connected
memory space in-use/free
disk space free
last user connected; last program run
cron jobs

and so on.
As you look through, probably several will be quickly ruled out. However, a system should not freeze without a reason.
 

10 More Discussions You Might Find Interesting

1. Solaris

Solaris 7 & 9, Iplannet 4.1 and Sun One Web Server 6.1

Hey all, I was wondering whether anyone could give me any tips. I'm a total newcomer when it comes to Solaris and i need to dothe following: Current System: Solaris 7 running IPlannet 4.1: Upgrade (Preserving current data) to: Solaris 9 running Sun ONE Web Server 6.1 Has anyone... (0 Replies)
Discussion started by: AJD
0 Replies

2. UNIX for Dummies Questions & Answers

Solaris 7 & 9, Iplannet 4.1 and Sun ONE web server 6.1

Hey all, I was wondering whether anyone could give me any tips. I'm a total newcomer when it comes to Solaris and i need to dothe following: Current System: Solaris 7 running IPlannet 4.1: Upgrade (Preserving current data) to: Solaris 9 running Sun ONE Web Server 6.1 Has anyone... (1 Reply)
Discussion started by: AJD
1 Replies

3. Linux

Shared web server resources (CPU&RAM)

Hello, guys ! Long time no seen. I have a question about Linux web servers. I guess it is a more general question, but in my case it is a Linux web server. I want to know how much RAM memory should I put on my servers. Do you have some formula or guidelines on how should I calculate the amount... (1 Reply)
Discussion started by: Sergiu-IT
1 Replies

4. Solaris

what is the difference between http & Tomcat web server

I do not know the difference between the apache-http and the apche-Tomcat.Is they are differentiated on their version or on their features.:confused: (2 Replies)
Discussion started by: jayaprakash
2 Replies

5. Web Development

sudo httpd -k restart

hi, why do I need -k in sudo httpd -k restart ? thanks (2 Replies)
Discussion started by: aneuryzma
2 Replies

6. Solaris

Oracle Database and HTTPD Web Service

Hi, I have a Solaris 5.6 having an Oracle database.Now this server is being accessed by a web service interface.I cannot see anything other than httpd daemons running on my server. There is a frequent problem of the stopping of these httpd daemons . Now i am asked to find the root case.I talked... (1 Reply)
Discussion started by: asalman.qazi
1 Replies

7. UNIX for Advanced & Expert Users

How to Restart the web server

Hi, Unix AIX, on WebLogic How to Restart the web server Thank you. (2 Replies)
Discussion started by: big123456
2 Replies

8. Red Hat

Comprehensive Disk & Server Logs.

Hello All, I'm using a RHEL6.4 on IBM X3850 X5 server. I want to get a comprehensive report containing disk-wise health status as well as overall server status. I see there's utility "ibm_utl_dsa_dsytd3h-9.51_portable_rhel6_x86-64.bin" which is also used to do diagnostics tasks. I'm not sure of... (1 Reply)
Discussion started by: vaibhavvsk
1 Replies

9. Shell Programming and Scripting

Need Script to ZIP/SAVE & then DELETE Log file & send a mail conformation for any error

ENVIROMENT Linux: RHEL 6.4 Log Path: /usr/iplanet/servers/https-company/logs Log Format: user.log.03-15-2015 I have log4j log rotation enabled rotating files on a daily basis. The rotated logs are NOT compressed & are taking up too much space. I need a script that will run daily that... (1 Reply)
Discussion started by: admin_job_admin
1 Replies

10. Shell Programming and Scripting

Show Logs from a server location to a web browser

hey Guys, Am a newbie to Linux and have a probable requirement that might come up pretty soon. I need to understand, how log files and log location can be displayed on a web browser. So that the end user can read the log files and should be able to search for order numbers in the logs. If... (2 Replies)
Discussion started by: ashish_samarth
2 Replies
queuedefs(4)                                                       File Formats                                                       queuedefs(4)

NAME
queuedefs - queue description file for at, batch, and cron SYNOPSIS
/etc/cron.d/queuedefs DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue. The format of the lines are as follows: q.[njobj][nicen][nwaitw] The fields in this line are: q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see at(1)); c is the default queue for jobs run from a crontab(1) file. njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100. nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2. nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's queue, or because the system-wide limit of jobs executing has been reached. The default value is 60. Lines beginning with # are comments, and are ignored. EXAMPLES
Example 1: A sample file. # # a.4j1n b.2j2n90w This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron. SEE ALSO
at(1), crontab(1), nice(1), cron(1M) SunOS 5.10 1 Mar 1994 queuedefs(4)
All times are GMT -4. The time now is 02:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy