10-30-2001
Bhupal,
SIGTERM or signal-15 is a graceful way of terminating a process. this signal can also be generated the user by using "Kill" or may even be generated in your case by the kernel. That is what I can presume after seeing the log files.
I cant tell much about the actual reason for termination of the process by seeing these three lines of your file. But may be ur CPU is too busy that is what I see in logs. but in case, it should generate a signal
SIGXCPU CPU time limit exceeded.
Add a singal handler in your process for this signal and that can help you find out whether this isthe actual problem.
Good luck
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi all,
I am running 7.3 Redhat Linux, I have Oracle database running on it and I have some problem with the memory. every time I startup the database, the memory was peak up to 630M of Ram out 640M ram on the entire box and I didn't specify that much of memory on my database. Oracle advise me... (2 Replies)
Discussion started by: lapnguyen
2 Replies
2. UNIX for Dummies Questions & Answers
Received the following on the weekend.
Panic:k_trap kernel mode trap type 0X0000000e cannot dump 163739 pages to dumpdev hd (1/41):space for only 48640 pages
Dump not complete
Safe to power off or press any key to reboot
Any ideas how to fix this one? It also happen a month ago. (3 Replies)
Discussion started by: jcoleman544
3 Replies
3. Linux
Hello!
Does anyone know howto reload your kernal without rebooting the machine?
I´ve updated the "/etc/security/limits.conf " file and need to make this active without rebooting the machine. this is Red Hat Advanced Server 2.1AS
Regards...
dOzY (3 Replies)
Discussion started by: dozy
3 Replies
4. UNIX for Dummies Questions & Answers
hello all,
as we know that the kernal Schedules tasks with some time slice given to each.
how does the Kernal know that the time of a Task has been elapsed?
does it follow the syatem Clock?or how?
thanks for your time (4 Replies)
Discussion started by: compbug
4 Replies
5. UNIX for Dummies Questions & Answers
Hi friends,
i would like to know the kernal information (semaphores), which command do i use
Thanks (4 Replies)
Discussion started by: shaan_dmp
4 Replies
6. Solaris
hi,
can anybody tell me how to increase the parameters like project.max-shm-ids on solaris10.
i have used prctl, but got reset while server reboot.
thnks and regards
Ajay (1 Reply)
Discussion started by: ajaysahoo
1 Replies
7. SCO
I am trying to restore Unixware 7.1 from a backup using RestoreEdge which is from Microline version 2. The restore is on another machine using the same RAID controller and TBU. We are retiring the other machine.
Anyway, we get to disk #2 and it panics. Here is the Pic.
Can anyone tell me... (13 Replies)
Discussion started by: ccd1977
13 Replies
8. Solaris
Hi,
Can you please let me know about kernal parameters?
Where we can see that kernal parameters?
we are using System = SunOS 5.10.
Please let me know commands to see these kernal parameters file or files. (1 Reply)
Discussion started by: kancherla.sree
1 Replies
9. Shell Programming and Scripting
How can view log messages between two time frame from /var/log/message or any type of log files.
when logfiles are very big and especially many messages with in few minutes, I would like to display log messages between 5 minute interval.
Could you pls give me the command? (1 Reply)
Discussion started by: johnveslin
1 Replies
10. Linux
Please clarify on below two which one is the latest Kernal version.
Also clarify me , how to break and understand, which part meant for what?
kernel-2.6.18-348.6.1.el5.i686.rpm
kernel-2.6.18-308.11.1.el5.i686.rpm
Thanks (3 Replies)
Discussion started by: Siva SQL
3 Replies
LEARN ABOUT DEBIAN
mojo::log
Mojo::Log(3pm) User Contributed Perl Documentation Mojo::Log(3pm)
NAME
Mojo::Log - Simple logger
SYNOPSIS
use Mojo::Log;
# Log to STDERR
my $log = Mojo::Log->new;
# Customize log file location and minimum log level
my $log = Mojo::Log->new(path => '/var/log/mojo.log', level => 'warn');
# Log messages
$log->debug("Why isn't this working?");
$log->info("FYI: it happened again");
$log->warn("This might be a problem");
$log->error("Garden variety error");
$log->fatal("Boom!");
DESCRIPTION
Mojo::Log is a simple logger for Mojo projects.
EVENTS
Mojo::Log can emit the following events.
"message"
$log->on(message => sub {
my ($log, $level, @messages) = @_;
...
});
Emitted when a new message gets logged.
$log->unsubscribe('message');
$log->on(message => sub {
my ($log, $level, @messages) = @_;
say "$level: ", @messages;
});
ATTRIBUTES
Mojo::Log implements the following attributes.
"handle"
my $handle = $log->handle;
$log = $log->handle(IO::Handle->new);
Log file handle used by default "message" event, defaults to opening "path" or "STDERR".
"level"
my $level = $log->level;
$log = $log->level('debug');
Active log level, defaults to the value of the "MOJO_LOG_LEVEL" environment variable or "debug".
These levels are currently available:
"debug"
"info"
"warn"
"error"
"fatal"
"path"
my $path = $log->path
$log = $log->path('/var/log/mojo.log');
Log file path used by "handle".
METHODS
Mojo::Log inherits all methods from Mojo::EventEmitter and implements the following new ones.
"new"
my $log = Mojo::Log->new;
Construct a new Mojo::Log object and subscribe to "message" event with default logger.
"debug"
$log = $log->debug('You screwed up, but that is ok');
Log debug message.
"error"
$log = $log->error('You really screwed up this time');
Log error message.
"fatal"
$log = $log->fatal('Its over...');
Log fatal message.
"format"
my $message = $log->format('debug', 'Hi there!');
my $message = $log->format('debug', 'Hi', 'there!');
Format log message.
"info"
$log = $log->info('You are bad, but you prolly know already');
Log info message.
"is_level"
my $success = $log->is_level('debug');
Check log level.
"is_debug"
my $success = $log->is_debug;
Check for debug log level.
"is_error"
my $success = $log->is_error;
Check for error log level.
"is_fatal"
my $success = $log->is_fatal;
Check for fatal log level.
"is_info"
my $success = $log->is_info;
Check for info log level.
"is_warn"
my $success = $log->is_warn;
Check for warn log level.
"log"
$log = $log->log(debug => 'This should work');
Emit "message" event.
"warn"
$log = $log->warn('Dont do that Dave...');
Log warn message.
SEE ALSO
Mojolicious, Mojolicious::Guides, <http://mojolicio.us>.
perl v5.14.2 2012-09-05 Mojo::Log(3pm)