Sponsored Content
Full Discussion: losing mail enroute
Operating Systems HP-UX losing mail enroute Post 302561160 by edstevens on Monday 3rd of October 2011 10:42:26 AM
Old 10-03-2011
losing mail enroute

system is HP-UX B.11.23 U ia64

A standard feature of almost all of our cron jobs is to redirect output to a log file, then at the end of the script to embed the contents of that log file in the body of an email sent to the IT staff. Typical code to do this is
Code:
$MAILER -s "$PROC: $SUBJECT" $MAILTO < $LOG > /dev/null 2>&1

where $MAILER = /usr/bin/mailx

the mail is forwarded to an Exchange server where we then pick it up in our individual Outlook accounts. There are several dozen, possibly in excess of 100 of these every day. Last week we quit receiving the email from one single job. All others continue to come through. I checked for the log file output of the job (set to /tmp/$PROC.$$) and it is being created and shows the job ran as expected. But the mail appears to not be reaching our Exchange server. Or if it is, it is not making it to our individual accounts. On the source, the mail is sent to a distribution list defined in our aliases file.

So, how do I begin to follow this email through the system and find where it is getting dropped? (My primary job role is Oracle DBA, but I work closely with our unix SA and consider myself a power user or SA apprentice. I have full root access to the HP system. The exchange server is managed by a different dept and I have no direct access to it, will have to work with their admin when we get to that point.

Last edited by vbe; 10-03-2011 at 01:32 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

losing time

Hi all, The server seems to be losing time, not a lot, but enough to be noticed. UNIX AIX 4.3.3 Any ideas, Kathy (9 Replies)
Discussion started by: kburrows
9 Replies

2. UNIX for Dummies Questions & Answers

Losing ownership with gzip

I'm trying to sell the use of gzip instead of compress in our department. One issue I'm having (which is a showstopper) is that I lose the ownership when gzipping and gunzipping, though it's mentioned all over the web that files are supposed to keep ownership. Example: -rwxrwxrwx 1 ms32345 ... (3 Replies)
Discussion started by: superdelic
3 Replies

3. Solaris

mail.alert: Losing ./qfm4TKt04M014942

Hi guys yesterday we made an aplication update runing over solaris10, when finish we have next message every 5 minutes :eek: sendmail: m4TKt04M014942: Losing ./qfm4TKt04M014942: savemail panic:confused: Do you now what does it mean? what can I do in order to fix it? Thanks in... (0 Replies)
Discussion started by: panylinux
0 Replies

4. Shell Programming and Scripting

Losing zero in while read

I'm using a while read statement to read in lines from a file, if a value (for example) is 1000.10 in a field, the last zero is removed leaving 1000.1 does anyone know a way to keep the field as it is in the original file? (1 Reply)
Discussion started by: gefa
1 Replies

5. Solaris

Losing my solaris virginity

So here's the scoop. I am working on a project to automate the building of spark based solaris servers. I've got a cursory amount of knowledge of how to use the os after some pretty heavy experience with Linux, and doing a similar project there. I have a few questions though... 1) how is... (5 Replies)
Discussion started by: msarro
5 Replies

6. Emergency UNIX and Linux Support

losing ESSID

Hey guys, facing a weird issue - hoping someone might be able to help. The wireless network on my laptop is configured with a static IP address. (not using nm) When i take the laptop out of the range (or i power the router down) the essid is becoming "off/any". When i'm back in range the... (6 Replies)
Discussion started by: moshe88
6 Replies

7. Programming

Losing signal problem

I'm newbie in UNIX programming, I have a problem with signals. I'm writing multithread program, where threads can die at any moment. When thread dies it generates signal SIGUSR1 to main thread and then thread dies. Main thread gets a signal and waits for thread dead. I wrote program like this: ... (5 Replies)
Discussion started by: DendyGamer
5 Replies

8. Forum Support Area for Unregistered Users & Account Problems

Losing the connection

Hi. Recently when I'm logged in to site after some seconds, for instance, I lose the connection and need sign in again. It happens on Firefox and Chrome. Or another example, when I'm logged in to site and click on my nick name (right up corner) I lose the connection to site. User: tiago ... (0 Replies)
Discussion started by: Unregistered
0 Replies

9. UNIX for Dummies Questions & Answers

Losing Time

Our Unix system is losing a considerable amount of time each day, and our support service company says our motherboard is the cause. They "upgraded" us 5 years ago to basically the same thing as what we had previously, and are looking to "upgrade" us again now for about $5,000... I think... (23 Replies)
Discussion started by: Big Z
23 Replies

10. UNIX for Advanced & Expert Users

Client was not authenticated to send anonymous mail during MAIL FROM (in reply to MAIL FROM comm

I am having trouble getting mail to work on a red hat server. At first I was getting this message. Diagnostic-Code: X-Postfix; delivery temporarily suspended: connect to :25: Connection refused Then added the port to my firewall. Then I temporarily turned off selinux. I then copied this file... (1 Reply)
Discussion started by: cokedude
1 Replies
queuedefs(4)						     Kernel Interfaces Manual						      queuedefs(4)

NAME
queuedefs - Queue description file for at, batch, and cron commands DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron or specifies other characteristics for cron. Each noncom- ment line in this file describes either one queue or a cron characteristic. Each uncommented line should be in one of the following for- mats. q.[njobj][nicen][nwaitw] max_jobs=mjobs log=lcode The fields in these lines are as follows: The name of the queue. Defined queues are as follows: The default queue for jobs started by at The default queue for jobs started by batch The default queue for jobs run from a crontab file Queues d to z are also available for local use. The maximum number of jobs that can be run simultaneously in the queue; if more than njob jobs are ready to run, only the first njob jobs will be run. The others will be initiated as currently running jobs ter- minate. The nice(1) value to give to all jobs in the queue that are not run with a user ID of superuser. The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that queue, or because the system-wide limit of jobs executing (max_jobs) has been reached. The maximum number of active jobs from all queues that may run at any one time. The default is 25 jobs. Logging level of messages sent to a log file. The default is 4. Defined levels are as follows: level-code level 0 None 1 Low 2 Medium 3 High 4 Full Lines beginning with # are comments, and are ignored. EXAMPLES
The following file specifies that the b queue, for batch jobs, can have up to 50 jobs running simultaneously; that those jobs will be run with a nice value of 20. If a job cannot be run because too many other jobs are running, cron will wait 60 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. If a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. b.50j20n60w The following file specifies that a total of 25 active jobs will be allowed by cron over all the queues at any one time, and cron will log all messages to the log file. The last two lines are comments that are ignored. max_jobs=25 log=4 # This is a comment # And so is this FILES
Main cron directory The default location for the queue description file. RELATED INFORMATION
Commands: at(1), cron(8), crontab(1), nice(1) delim off queuedefs(4)
All times are GMT -4. The time now is 10:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy