Sponsored Content
Top Forums UNIX for Advanced & Expert Users Enomem in Journal Retry Error Post 69190 by killerserv on Wednesday 13th of April 2005 01:10:01 AM
Old 04-13-2005
Question Enomem in Journal Retry Error

Hi,
Does anyone seen this error before..

kernel: ENOMEM in journal_alloc_journal_head, retrying.

I encounter this problem on IBM eServers where when the above error appears usually the machine is dead or hanged. Unless a hard reboot is been done. Is this something have to do with the memory ?

The machine is having 16GB Physical memory and 32GB Swap.
System utilization (looking at sar log) is at 60% before the machine gets dead/hang. No other errors can be found other then the above ENOMEM error..

Im running on Linux 7.1 (2.4.9-45lxset34enterprise)

Any similiar exprerience.. ?
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

ext3: No journal on filesystem on dm-0

Hi Linuxers, I am a newbie here and loggin this facilities regularly. Recently my PC experience a power trip, my system could not boot up after restarting. I did the following : - Boot up with "linux rescue" using installation disk FC3 - In a shell, run "lvm vgchange... (0 Replies)
Discussion started by: chowkimhan
0 Replies

2. Shell Programming and Scripting

retry process in ftp

hi #!/bin/bash SERVER=10.89.40.35 USER=xyz PASSWD=xyz ftp -in $SERVER<<EOF user $USER $PASSWD mkdir PPL cd /path of remote dir lcd /path of local dir hash bin put <file name> bye <<EOF The above ftp script i have to schedule in crontab at a particular instance of time run daily.... (2 Replies)
Discussion started by: rookie250
2 Replies

3. Shell Programming and Scripting

Retry upon FTP failure

I am using the following code in a C Shell script to transfer files to a remote server: ftp -n logxx.xxxx.xxx.xxx.com <<DO_FTP1 quote user $user_name quote pass $password ascii put $js_file_name bin put $FinalZipFile quit DO_FTP1 This code works great except on those rare occasions... (8 Replies)
Discussion started by: phudgens
8 Replies

4. Shell Programming and Scripting

Shell Script to Retry and Exit

ok, so I'm trying to add a function to my local script that runs a command on a remote host. The reason why this is needed is that, there are other scripts that run different commands on the same remote host. so the problem is that many times there are multiple scripts being run on the remote... (1 Reply)
Discussion started by: SkySmart
1 Replies

5. AIX

mprotect fails with ENOMEM in text segment

Hi guys, I use AIX version 5 on IBM Power 5+ machine. I am currently trying to experiment with sort of self-modifying code, like this: ucontext_t ut; getcontext(&ut); int iar = ut.uc_mcontext.jmp_context.iar; int pageSize = getpagesize(); int rest = iar % pageSize; void *ptr = iar -... (6 Replies)
Discussion started by: manolo123
6 Replies

6. UNIX for Advanced & Expert Users

How to manipulate the conditions between every retry in wget?

Hi , When i hit the URL using WGET command ,it is retrying according to the number of retry we mentioned along with Wget command. my expectation : 1) If 1st try is failed and iam retrying again before 2nd retry i have to check for "xxxxxxx" entry in the log file. 2) If "XXXXXXX" entry is... (4 Replies)
Discussion started by: vinothsekark
4 Replies

7. Shell Programming and Scripting

If then else - Retry operation

I need to read a file line by line, then depending on the contents of each line, type in a code that will get written to an array. The problem I have is when I ask the user to confirm the input code, if it is wrong, how do i Return to ask again? Any thing I try increments the file to the next... (6 Replies)
Discussion started by: kcpoole
6 Replies

8. UNIX for Dummies Questions & Answers

Wget retry on 500 internal error

Hello Guys, I am trying to generate static site, I have perl script that wget the url, so the problem is sometimes wget has 500 internal error, this is failing to get that page. So I am thinking of retrying that url with 500 response. system $command = 'wget ... -i inputfile -o outfile" Is... (2 Replies)
Discussion started by: neal
2 Replies

9. Solaris

Unrecovered read error No retry

We encountered these error 2 times(e.g. Solaris 10 with NetWorker installed) with in the month of August, but we couldn't pin point the root cause, it might be bad sector, bad cable or software incompatibility? Do you experience these issue or please share your understanding about this? Thanks... (0 Replies)
Discussion started by: B@S
0 Replies
audit_warn(1M)						  System Administration Commands					    audit_warn(1M)

NAME
audit_warn - audit daemon warning script SYNOPSIS
/etc/security/audit_warn [option [arguments]] DESCRIPTION
The audit_warn utility processes warning or error messages from the audit daemon. When a problem is encountered, the audit daemon, auditd(1M) calls audit_warn with the appropriate arguments. The option argument specifies the error type. The system administrator can specify a list of mail recipients to be notified when an audit_warn situation arises by defining a mail alias called audit_warn in aliases(4). The users that make up the audit_warn alias are typically the audit and root users. OPTIONS
The following options are supported: allhard count Indicates that the hard limit for all filesystems has been exceeded count times. The default action for this option is to send mail to the audit_warn alias only if the count is 1, and to write a message to the machine console every time. It is recommended that mail not be sent every time as this could result in a the saturation of the file system that contains the mail spool directory. allsoft Indicates that the soft limit for all filesystems has been exceeded. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. auditoff Indicates that someone other than the audit daemon changed the system audit state to something other than AUC_AUDITING. The audit dae- mon will have exited in this case. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. ebusy Indicates that the audit daemon is already running. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. getacdir count Indicates that there is a problem getting the directory list or plugin list jjjjkj from audit_control(4). The audit daemon will hang in a sleep loop until the file is fixed. The default action for this option is to send mail to the audit_warn alias only if count is 1, and to write a message to the machine console every time. It is recommended that mail not be sent every time as this could result in a the saturation of the file system that contains the mail spool directory. hard filename Indicates that the hard limit for the file has been exceeded. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. nostart Indicates that auditing could not be started. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. Some administrators may prefer to modify audit_warn to reboot the system when this error occurs. plugin name error count text Indicates that an error occurred during execution of the auditd plugin name. The default action for this option is to send mail to the audit_warn alias only if count is 1, and to write a message to the machine console every time. (Separate counts are kept for each error type.) It is recommended that mail not be sent every time as this could result in the saturation of the file system that contains the mail spool directory. The text field provides the detailed error message passed from the plugin. The error field is one of the follow- ing strings: load_error Unable to load the plugin name. sys_error The plugin name is not executing due to a system error such as a lack of resources. config_error No plugins loaded (including the binary file plugin, audit_binfile(5)) due to configuration errors in audit_control(4). The name string is -- to indicate that no plugin name applies. retry The plugin name reports it has encountered a temporary failure. For example, the audit_binfree.so plugin uses retry to indicate that all directories are full. no_memory The plugin name reports a failure due to lack of memory. invalid The plugin name reports it received an invalid input. failure The plugin name has reported an error as described in text. postsigterm Indicates that an error occurred during the orderly shutdown of the audit daemon. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. soft filename Indicates that the soft limit for filename has been exceeded. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. tmpfile Indicates that the temporary audit file already exists indicating a fatal error. The default action for this option is to send mail to the audit_warn alias and to write a message to the machine console. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsr | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ The interface stability is evolving. The file content is unstable. SEE ALSO
audit(1M), auditd(1M), bsmconv(1M), aliases(4), audit.log(4), audit_control(4), attributes(5) NOTES
This functionality is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for more information. If the audit policy perzone is set, the /etc/security/audit_warn script for the local zone is used for notifications from the local zone's instance of auditd. If the perzone policy is not set, all auditd errors are generated by the global zone's copy of /etc/secu- rity/audit_warn. SunOS 5.10 26 May 2004 audit_warn(1M)
All times are GMT -4. The time now is 02:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy