Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Why SIGKILL will occur?
Top Forums Shell Programming and Scripting Why SIGKILL will occur? Post 302096770 by bdsffl on Saturday 18th of November 2006 02:11:10 AM
Old 11-18-2006
One suggestion if the the problem occurs soner than later is this.

Start a prstat and redirect to a log file. Thats why I say if
it starts immediately to avoid filling up disk space.

When the sigkill calls out the PID you can then view
the PID by looking at the log file and trace that pid
back to the PPID also by reviewing the log file.

Hopefully this will get you started in the right direction.

Also you can set up user.<severity> in the syslog.conf file
and have that directed to /var/adm/messages

This may also give you a clue to whats happening
with your process. Also look at the fuser command
I haven't used it alot my self but it allows you to tell
who's trying access the particular file *.db or whatever
file your interested in.

But as mentioned earlier since databases tend to be on the large size, physical memory and swap space maybe running out.

prstat > problem.db.log

I would run this in the foreground so you don't forget
it's running. It wiil take up some disk space but the log can rm'd as required.
Last edited by bdsffl; 11-18-2006 at 03:27 AM..
 

10 More Discussions You Might Find Interesting

1. Programming

How to implement SIGKILL and SIGTERM and print a message?

Hello, I am running a webserver that uses sockets, forks, and children. The parent process listens for connections and the child processes the information. I am trying to figure out why the code I have below SIGTERM, and SIGKILL never fire. I was messing around with the printfs and doesnt... (11 Replies)
Discussion started by: norelco55
11 Replies

2. Shell Programming and Scripting

how many times a word occur in afile

i want a shell script program for how many times a word occur in a file. i need not the line number but i want the counts of the particular word for eg:- hai how r u.. i am from andhra pradesh.. i am from tenali.i need this answer.i need it urgently.. i hope u will answer this ... ... (9 Replies)
Discussion started by: madhu.it
9 Replies

3. Solaris

SIGQUIT and SIGKILL message

Dear All, I have machine with SunOS 5.10 Generic_138888-01 sun4v sparc SUNW,SPARC-Enterprise-T5120. Yesterday there is something at dmesg command : May 25 18:09:02 cacao_launcher: Timeout occured on heartbeat channel, cleanup engaged May 25 18:09:07 cacao_launcher: watchdog : warning,... (0 Replies)
Discussion started by: mbah_jiman
0 Replies

4. Shell Programming and Scripting

How to detect SIGTERM,SIGKILL signal in UNIX

Dear All We have JBOSS server running on Linux we need to track Graceful Shutdown(SIGTERM) and Forceful Shutdown(SIGKILL) timestamp and write it into one file, I am new to UNIX Signal processing if is it possible how to detect it? We generally do $kill PID For Graceful... (5 Replies)
Discussion started by: mnmonu
5 Replies

5. Shell Programming and Scripting

To find number of char occur

To find out number of "|" symbol is available in file: Input: a|b|c|d|z Ouput: 4 I am using below set of commands,It is working... Anybody have anyother solution using sed / awk. cnt=`wc -c <1.txt` cnt1=`tr -d "|" <1.txt >c.dat` cnt2=`wc -c <c.dat` outp=`expr $cnt... (19 Replies)
Discussion started by: Jairaj
19 Replies

6. UNIX for Dummies Questions & Answers

C shell loop problem occur

Hi all, i create 2 file Config path1 5 group1 path2 6 group2 path3 10 group1 path4 15 group2 Confine group1 andrew group2 alan In my C shell script i write like this: set line_array = (`cat $app_dir/config`) set line_array_2 =... (0 Replies)
Discussion started by: proghack
0 Replies

7. Shell Programming and Scripting

Print lines where variables occur more than once using grep

Hello, I want to only print lines where variables occur more than once using grep. For eg: Input: $this is a comment int a,b,c,b; int b,c; int d,e; int f,g,f; x=y+5; For the above input, the output would be int a,b,c,b; int f,g,f; I have done grep... (3 Replies)
Discussion started by: prasanna1157
3 Replies

8. Shell Programming and Scripting

SIGSTOP and SIGKILL

Which is sent to a terminal when it closes? SIGKILL? Reason I ask is I have a script I want to run in the background, but want it to run even if the terminal window is closed. Or, I'd like it to background itself if the terminal is closed but not if its running in an open window. I will learn how... (5 Replies)
Discussion started by: DC Slick
5 Replies

9. Programming

Finding items that occur more than once in a vector

I have some vectors to evaluate and develop a list of values that occur in more than one element. This is the simplest case. I have a vector, std::vector<int> vec1; vec1=5; vec1=5; I need to know that that 5 occurs twice in the vector. If I do a double loop, std::vector<int>... (13 Replies)
Discussion started by: LMHmedchem
13 Replies

10. Cybersecurity

Where does Ciphering & Encryption occur?

Hello everyone. Upon reading the recent news about the NSA paying RSA to use a faulty cipher suite for it's default, it got me thinking... During a connection say for SSL, what is it that "knows" the rules for ciphers? Are these rules stored on the NIC? can they be edited, changed or appended? ... (3 Replies)
Discussion started by: Lost in Cyberia
3 Replies

LEARN ABOUT CENTOS

systemd-journald.service

SYSTEMD-JOURNALD.SERVICE(8)				     systemd-journald.service				       SYSTEMD-JOURNALD.SERVICE(8)

NAME

       systemd-journald.service, systemd-journald.socket, systemd-journald - Journal service

SYNOPSIS

       systemd-journald.service

       systemd-journald.socket

       /usr/lib/systemd/systemd-journald

DESCRIPTION

       systemd-journald is a system service that collects and stores logging data. It creates and maintains structured, indexed journals based on
       logging information that is received from the kernel, from user processes via the libc syslog(3) call, from STDOUT/STDERR of system
       services or via its native API. It will implicitly collect numerous meta data fields for each log messages in a secure and unfakeable way.
       See systemd.journal-fields(7) for more information about the collected meta data.

       Log data collected by the journal is primarily text-based but can also include binary data where necessary. All objects stored in the
       journal can be up to 2^64-1 bytes in size.

       By default, the journal stores log data in /run/log/journal/. Since /run/ is volatile, log data is lost at reboot. To make the data
       persistent, it is sufficient to create /var/log/journal/ where systemd-journald will then store the data.

       systemd-journald will forward all received log messages to the AF_UNIXSOCK_DGRAM socket /run/systemd/journal/syslog, if it exists, which
       may be used by Unix syslog daemons to process the data further.

       See journald.conf(5) for information about the configuration of this service.

SIGNALS

       SIGUSR1
	   Request that journal data from /run/ is flushed to /var/ in order to make it persistent (if this is enabled). This must be used after
	   /var/ is mounted, as otherwise log data from /run is never flushed to /var regardless of the configuration.

       SIGUSR2
	   Request immediate rotation of the journal files.

KERNEL COMMAND LINE

       A few configuration parameters from journald.conf may be overridden on the kernel command line:

       systemd.journald.forward_to_syslog=, systemd.journald.forward_to_kmsg=, systemd.journald.forward_to_console=
	   Enables/disables forwarding of collected log messages to syslog, the kernel log buffer or the system console.

	   See journald.conf(5) for information about these settings.

ACCESS CONTROL

       Journal files are, by default, owned and readable by the "systemd-journal" system group but are not writable. Adding a user to this group
       thus enables her/him to read the journal files.

       By default, each logged in user will get her/his own set of journal files in /var/log/journal/. These files will not be owned by the user,
       however, in order to avoid that the user can write to them directly. Instead, file system ACLs are used to ensure the user gets read access
       only.

       Additional users and groups may be granted access to journal files via file system access control lists (ACL). Distributions and
       administrators may choose to grant read access to all members of the "wheel" and "adm" system groups with a command such as the following:

	   # setfacl -Rnm g:wheel:rx,d:g:wheel:rx,g:adm:rx,d:g:adm:rx /var/log/journal/

       Note that this command will update the ACLs both for existing journal files and for future journal files created in the /var/log/journal/
       directory.

FILES

       /etc/systemd/journald.conf
	   Configure systemd-journald behaviour. See journald.conf(5).

       /run/log/journal/machine-id/*.journal, /run/log/journal/machine-id/*.journal~, /var/log/journal/machine-id/*.journal,
       /var/log/journal/machine-id/*.journal~
	   systemd-journald writes entries to files in /run/log/journal/machine-id/ or /var/log/journal/machine-id/ with the ".journal" suffix. If
	   the daemon is stopped uncleanly, or if the files are found to be corrupted, they are renamed using the ".journal~" suffix, and
	   systemd-journald starts writing to a new file.  /run is used when /var/log/journal is not available, or when Storage=volatile is set in
	   the journald.conf(5) configuration file.

SEE ALSO

       systemd(1), journalctl(1), journald.conf(5), systemd.journal-fields(7), sd-journal(3), setfacl(1), pydoc systemd.journal.

systemd 208													       SYSTEMD-JOURNALD.SERVICE(8)
All times are GMT -4. The time now is 04:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy