Sponsored Content
Operating Systems AIX AIX warning message: 651-812: System shutdown due to Post 302303076 by dukessd on Wednesday 1st of April 2009 07:30:51 PM
Old 04-01-2009
Diagela runs at 4:00 am from cron and is causing the message.
Diagela analyses the error report for about the last 30 days and reports permanent hardware errors.
There must be an abnormal reboot recorded in the errpt in the last 30 days caused by a reason given in the message.
HTH
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

System Error: 651-880

Hi... I have a IBM pseries with AIX 4.3... and the root user receive the next error (via e-mail) diagela A PROBLEM WAS DETECTED ON Thu Aug 18 04:01:05 AST 2005 801014 The Service Request Number(s)/Probable Cause(s) (causes are listed in descending order of probability): ... (1 Reply)
Discussion started by: mgonzal
1 Replies

2. Shell Programming and Scripting

Shutdown a system by MAC?

Ok here is the problem we have 2 v440 with same IP address running solars 9. one remains on the other remains off. They are both configured exactly the same for redundant purposes for the software we use. This was the best/worst idea. Great because down time is only a mere minutes. The bad is the... (7 Replies)
Discussion started by: deaconf19
7 Replies

3. Programming

CORE_DUMP due to PRO C on AIX !! Help me !!

Hi All , i found two core files on aix customer machine due to two pro-c executables . we dont have any debugger like dbx . even i captured the log reports reg the core dumps .. i pasted the details here belo3w .please help me out h ow to resolve the issue :-( .... THANKS IN ADVANCE ... ... (1 Reply)
Discussion started by: vparunkumar
1 Replies

4. AIX

Process crashing on AIX due to memory Leak

Hi All, I have a process running on my AIX 5.3 server box. The process runs fine for 5-6days but then crashes. The log file shows malloc failure and the svmon (Virtual memory size), ps -lef (SZ value) are also gradually increasing. But unfortunately MALLOCDEBUG and any other memory debugging... (3 Replies)
Discussion started by: SBatra
3 Replies

5. Solaris

logs for system shutdown

I am working on a SUN T2000 machine with Solaris 10 running on it. When I checked the system this morning, I found it to be turned off. The lastreboot command showed that the system had been shut down the previous night. I want to find out how the system was shut down. I have run hardware health... (2 Replies)
Discussion started by: batman727
2 Replies

6. UNIX for Advanced & Expert Users

System Shutdown Warning Using SAM

Bump to questions thread, thanks. (1 Reply)
Discussion started by: MINICooperS
1 Replies

7. Forum Support Area for Unregistered Users & Account Problems

Cannot register due to "spam" error message

Hi all, I am trying to register but it seems my IP address is being seen or black listed as a spam address. I get the following message: "Registration denied. Sorry, The UNIX and Linux Forums runs an active policy of not allowing spammers. Please contact us via by posting in this forum if... (0 Replies)
Discussion started by: codenjanod
0 Replies

8. AIX

AIX 6.1 Error - "A file, file system or message queue is no longer available."

Getting a strange error with a log file below. This is just a normal text log file that is written to by an application on the server. The applicaiton is down, however, I cannot read, remove or touch this file. The file shows on an ls listing but not an ls -al listing. The file system is JFS2... (0 Replies)
Discussion started by: troym72
0 Replies

9. Shell Programming and Scripting

how do i avoid system hang due to ssh in script?

I have a script that collects data from about 200 servers using 'ssh'. The problem is that, process sometime hangs at some point stopping the execution of the script. Please give me some idea how can I force the execution to jump to the next step if there arises any problem !! Thanks for replies if... (1 Reply)
Discussion started by: mdangol
1 Replies

10. Solaris

Shutdown system option

I am working on sunos solaris. I want to know which is good for system shut-down ? (3 Replies)
Discussion started by: Jitesh Varshney
3 Replies
FAXCRON(8)						      System Manager's Manual							FAXCRON(8)

NAME
faxcron - HylaFAX routine maintenance script SYNOPSIS
/usr/sbin/faxcron [ -n ] [ -l lastrun ] DESCRIPTION
faxcron is a command script that does routine upkeep tasks in a HylaFAX spooling directory hierarchy. This script is intended to be invoked from cron(8) on behalf of the fax user (often the ``fax'' user is uucp) once a day, with the standard output sent by mail to the HylaFAX administrator. For example, the following crontab might be set up for the fax user: 25 23 * * * sh /usr/sbin/faxcron | mail FaxMaster The faxcron script does the following work: o report statistics for facsimile transmitted since the last time faxcron was run. o report statistics for facsimile transmitted in the past week. o report statistics for facsimile received since the last time faxcron was run. o report statistics for facsimile received in the past week. o report any recent calls that failed suspiciously and return the associated trace log; o purge data that is 30 days or older from the remote machine information directory; o delete information that is 30 days or older from session trace log files; o remove files from the tmp directory that are older than 1 day; o remove files in the received facsimile queue that are 7 days or older; o report sites that are currently having jobs rejected; and o force all session log files to be owned by the fax user and kept with protection mode 644. OPTIONS
-n Forces faxcron to run without updating any files. -l lastrun Forces the notion of the last time that faxcron was run to be lastrun. The value of lastrun is a date and time string of the form ``MM/DD/YY HH:MM'' (the date(1) format string ``%D %H:%M''). -info n Set the expiration time for data in the info database to be n days. -log n Set the expiration time for session log data to be n days. -rcv n Set the expiration time for files in the received facsimile queue to be n days. -tmp n Set the expiration time for files in the tmp directory to be n days. -mode m Set the file protection mode for session logs to m (a command line argument to chmod(1)). NOTES
This script requires nawk(1) or gawk(1) and a date (1) program that supports the ``+format'' option. If session logs are to be kept private this script must be modified to filter out sensitive information such as calling card numbers. (It should also be run with ``-mode 0600'' so that session log files are not publicly readable.) FILES
/var/spool/hylafax spooling area /var/spool/hylafax/status/lastrun timestamp of last run /usr/sbin/xferfaxstats for generating transmit statistics /usr/sbin/recvstats for generating receive statistics /var/spool/hylafax/tmp/faxcronXXXX temporary file for truncating session logs /var/spool/hylafax/tmp/faxlogXXXX temporary file for logs of failed calls SEE ALSO
cron(8), faxq(8), faxgetty(8), faxsend(8), xferfaxstats(8), recvstats(8), hylafax-server(5) May 12, 1996 FAXCRON(8)
All times are GMT -4. The time now is 09:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy