Could you please try following points and let us know.
i- Try to run your script manually once to make sure it is running correctly.
ii- If first option works fine then go to cron logs /var/log/cron and see there what's happening.
Thanks,
R. Singh
I see the entry in the cron system logs as above.
i- Try to run your script manually once to make sure it is running correctly. -> Done. Works fine manually.
Can yu now suggest something ?? what should i do now ?
Is there anyway to get the start time and end time / status of a crontab job which was just completed? Of course, we know the start time of the crontab job since we are scheduling. But I would like to know process start and time recorded somewhere or can be fetched from a command like 'ps'. ... (3 Replies)
Hi,
I am a beginner in shell scripting but I have a task to complete where I have to extract the time of script execution in human format so anyone can run the script and understand what script is running when in simple format. Let me illustrate what I mean:
Two scripts in crontab, for this... (4 Replies)
im puting script in crontab, script is executing every 15min, every day, every monath
but i must make time range from 0:00 - 20:00 <> 20:30 - 0:00
or if i cant make 20:30 then 0:00 - 20:00 <> 21:00- 0:00
can i make it in single line like this?
7,22,37,52 0-23 * * * test.sh >/dev/null... (3 Replies)
Hi,
I want to set cron job for different time zone from my machine. So here is what I did to set it.
I am having a file cronfile, which I use to set cron jobs by using
Crontab cronfile
Now in cronfile I set TZ variable as
Set TZ=Asia/Calcutta
But now... (3 Replies)
good day..how can I simply create a cron job that will be executed every 5mins from 12:01 to 7Pm..
is it like this
*/5 12:01-19 * * * <path> (3 Replies)
I have set up my cron job on the solaris SunOS 5.10 Generic_138888-03 sun4u sparc SUNW,UltraAX-i2 but it is not running on time as expected.
Would you please help me to find out what I did wrong?
I want to have this cron job run once every month on the 1st Wednesday of the month, but it ran... (6 Replies)
This is a new one on me. We upgraded a system from AIX 5.3 TL 7 to 6.1 TL 7 yesterday. The app people notified us that their cron jobs weren't running at the right time. So I made a test cron entry and here's what I've found:
# crontab -l
* * * * * /usr/bin/date > /tmp/test.log 2>&1
# cat... (2 Replies)
Hello All,
I have created a shell script, When i run it manually as ./<script_name> it takes 5 hours to run, but when i am scheduling it in crontab, it is taking 20 hours to run.
Please help me and advice, what can be done to reduce the time in crontab.
Thank you (6 Replies)
Hi,
I need to schedule a cronjob to kick start @ 8:30 PM server time and run every 5 mins there upon till I force stop it.
Can you please let me know how can it be achieved ? (5 Replies)
Discussion started by: mohtashims
5 Replies
LEARN ABOUT DEBIAN
epylog
epylog(8) Applications/System epylog(8)NAME
epylog - Syslog new log notifier and parser.
SYNOPSIS
epylog [-c epylog.conf] [-d LOGLEVEL] [--last PERIOD]
[--store-offsets] [--quiet] [--cron]
DESCRIPTION
Epylog is a new log notifier and parser which runs periodically out of cron, looks at your logs, processes the entries in order to present
them in a more comprehensive format, and then provides you with the output. It is written specifically with large network clusters in mind
where a lot of machines (around 50 and upwards) log to the same loghost using syslog or syslog-ng.
Alternatively, Epylog can be invoked from the command line and provide a log report based on a certain provided time period. In this case
it relies on syslog timestamps to find the offsets, as opposed to the end-of-log offsets stored during the last run, though this behavior
is not as reliable and is easily thwarted by skewed clocks.
OPTIONS -c config.file
Provide an alternative config file to Epylog. By default, it will look in /etc/epylog/epylog.conf.
-d LOGLEVEL
Logging level. The default is 1. 0 will produce no output except for critical errors (useful for cron runs). 2 and above are debug-
ging levels. 5 is the most verbose.
--last PERIOD
Will make a report on events that occurred in the last PERIOD. PERIOD can be either "hour", "day", "week", "month", or more granu-
lar: "1h", "2h", "3d", "2w", etc. When --last is specified, epylog will ignore the saved offsets and locate the entries by time-
stamps. CAUTION: this process is not to be trusted, since the timestamps are not checked for any validity when arriving to the
loghost. One reporting machine with a skewed clock may confuse Epylog enough to miss a lot of valid entries.
--store-offsets
When specified, will store the offset of the last log entry processed in offsets.xml. During the cron runs epylog relies on the off-
set information to find out what new entries to process. This is more trustworthy than relying on timestamps. The default behavior
is not to store the offsets, as this allows to run epylog both from cron and manually without the two interfering with each-other.
The location of offset.xml is specified in epylog.conf. See epylog.conf(5) for more details.
--quiet
In every way identical to -d 0.
--cron This is essentially --quiet --store-offsets, plus a lockfile will be created and consulted, preventing more than one instance of
epylog from running. You can still run epylog manually -- the lockfile is only checked when running in --cron mode.
FEATURES
The core of epylog is written in python. It handles things like timestamp lookups, unwrapping of "last message repeated" lines, han-
dling of rotated files, preparing and publishing the reports, etc.
The modules are pluggable and can be either "internal", written in python, or external. External modules can be written in any lan-
guage, but at a price of some convenience. For more info see epylog-modules(5).
INITIAL RUN
Depending on the size of your logs, you might want to initialize your offsets before letting epylog run from cron. When the off-
sets.xml file is missing, epylog will by default process the entire log, and depending on your configuration, that can be a lot of
entries. A good way to init epylog is to run:
epylog --last day --store-offsets
FILES
/etc/epylog/epylog.conf
/usr/sbin/epylog
/etc/cron.daily/epylog.cron
/etc/epylog/*
/var/lib/epylog/*
/usr/share/epylog/modules/*
EXAMPLES
The useful way to run from a command line is with --last. E.g.:
epylog --last day
epylog --last 2w
When running from cron, you want to store the offsets and not rely on timestamps. There is a mode that allows you to do this:
epylog --cron
AUTHORS
Konstantin Ryabitsev <icon@linux.duke.edu>
SEE ALSO epylog.conf(5)epylog-modules(5)Konstantin Ryabitsev 1.0 epylog(8)