I have a FreeBSD 7.1-RELEASE server on which runs Apache 2.2.16 + mod_fcgid + PHP 5.2.14. After some time (less then an hour) I get the following error:
In the same time, Apache won't accept any new requests and after a few minutes dies.
Does anyone have any ideea on why I get this error message?
Hey guys, need some help. Running AIX Version 5.2 and one of our cron jobs is writing errors to a log file. Any ideas on the following error message.
Error: Internal system error: Unable to initialize standard output file
I'm guessing more info might be needed, so let me know.
Thanks (2 Replies)
hi there
i write one awk script file in shell programing
the code is related to dd/mm/yy to month, day year format
but i get an error
please can anybody help me out in this problem ??????
i give my code here including error
awk `
# date-month -- convert mm/dd/yy to month day,... (2 Replies)
I encounters a VSIFAX related error:
vfxstat: Cannot login to server on rsac3: Connect error to host 172.16.1.45: Invalid argument
It started happening last night with a core dump. Then we can't start VSIFAX again.
I am runing VSI-FAX 4.2 on AIX box (0 Replies)
--------------------------------------------------------------------------------
Hello, help me please.
I am trying to create a mksysb bakup using nim. I am geting this error, how to correct it ? :
Command : failed stdout: yes stderr: no... (9 Replies)
Hi Guys.
This is part of my filesystem structure :
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 47G 5.2G 42G 12% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% ... (2 Replies)
im kinda new to shell scripting so i need some help
i try to run this script and get the error code
> 5 ")syntax error: operand expected (error token is "
the code for the script is
#!/bin/sh
#
# script to see if the given value is correct
#
# Define errors
ER_AF=86 # Var is... (4 Replies)
I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet.
... (2 Replies)
Hello,
I have another problem with my script. Please accept my apologies, but I am really nooby in sh scripts. I am writing it for first time.
My script:
returned=`tail -50 SapLogs.log | grep -i "Error"`
echo $returned
if ; then
echo "There is no errors in the logs"
fi
And after... (10 Replies)
I am writing a shell script with 2 run time arguments. During the execution if i got any error, then it needs to redirected to a error file and in console. Also both error and output to be redirected to a log file. But i am facing the below error.
#! /bin/sh
errExit ()
{
errMsg=`cat... (1 Reply)
Discussion started by: sarathy_a35
1 Replies
LEARN ABOUT MOJAVE
apache::testtrace
Apache::TestTrace(3) User Contributed Perl Documentation Apache::TestTrace(3)NAME
Apache::TestTrace - Helper output generation functions
SYNOPSIS
use Apache::TestTrace;
debug "foo bar";
info_sub "missed it";
error_mark "something is wrong";
# test sub that exercises all the tracing functions
sub test {
print $Apache::TestTrace::LogFH
"TraceLevel: $Apache::TestTrace::Level
";
$_->($_,[1..3],$_) for qw(emerg alert crit error
warning notice info debug todo);
print $Apache::TestTrace::LogFH "
"
};
# demo the trace subs using default setting
test();
{
# override the default trace level with 'crit'
local $Apache::TestTrace::Level = 'crit';
# now only 'crit' and higher levels will do tracing lower level
test();
}
{
# set the trace level to 'debug'
local $Apache::TestTrace::Level = 'debug';
# now only 'debug' and higher levels will do tracing lower level
test();
}
{
open OUT, ">/tmp/foo" or die $!;
# override the default Log filehandle
local $Apache::TestTrace::LogFH = *OUT;
# now the traces will go into a new filehandle
test();
close OUT;
}
# override tracing level via -trace opt
% t/TEST -trace=debug
# override tracing level via env var
% env APACHE_TEST_TRACE_LEVEL=debug t/TEST
DESCRIPTION
This module exports a number of functions that make it easier generating various diagnostics messages in your programs in a consistent way
and saves some keystrokes as it handles the new lines and sends the messages to STDERR for you.
This module provides the same trace methods as syslog(3)'s log levels. Listed from low level to high level: emerg(), alert(), crit(),
error(), warning(), notice(), info(), debug(). The only different function is warning(), since warn is already taken by Perl.
The module provides another trace function called todo() which is useful for todo items. It has the same level as debug (the highest).
There are two more variants of each of these functions. If the _mark suffix is appended (e.g., error_mark) the trace will start with the
filename and the line number the function was called from. If the _sub suffix is appended (e.g., error_info) the trace will start with the
name of the subroutine the function was called from.
If you have "Term::ANSIColor" installed the diagnostic messages will be colorized, otherwise a special for each function prefix will be
used.
If "Data::Dumper" is installed and you pass a reference to a variable to any of these functions, the variable will be dumped with
"Data::Dumper::Dumper()".
Functions whose level is above the level set in $Apache::TestTrace::Level become NOPs. For example if the level is set to alert, only
alert() and emerg() functions will generate the output. The default setting of this variable is warning. Other valid values are: emerg,
alert, crit, error, warning, notice, info, debug.
Another way to affect the trace level is to set $ENV{APACHE_TEST_TRACE_LEVEL}, which takes effect if $Apache::TestTrace::Level is not set.
So an explicit setting of $Apache::TestTrace::Level always takes precedence.
By default all the output generated by these functions goes to STDERR. You can override the default filehandler by overriding
$Apache::TestTrace::LogFH with a new filehandler.
When you override this package's global variables, think about localizing your local settings, so it won't affect other modules using this
module in the same run.
TODO
o provide an option to disable the coloring altogether via some flag
or import()
AUTHOR
Stas Bekman with contributions from Doug MacEachern
perl v5.18.2 2015-06-18 Apache::TestTrace(3)