Sponsored Content
Top Forums UNIX for Advanced & Expert Users cronjob not working intermittently Post 302391922 by Neo on Wednesday 3rd of February 2010 12:52:03 AM
Old 02-03-2010
Error in perl script, perhaps writing to a file, etc.?

Review perl error logs.....
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

whois lookup from script intermittently not working

Hello, I wrote a basic script to query a whois server using the whois system command to retrieve information about IP's. I have file containing the ip addresses which I feed to the whois command via a while loop. This seems to work sometimes. Most of the time, the whois command seems not to... (0 Replies)
Discussion started by: aliberson
0 Replies

2. UNIX for Advanced & Expert Users

cronjob not working

I created a file in /u01/oradata directory as cronjb.ksh which contains following script 30 12 * * * /export/home/oracle/u01/oradata/rman.ksh '/export/home/oracle' is my root directory. I then moved cronjb.ksh file to my '/export/home/oracle' directory. i typed crontab cronjb.ksh. However my... (8 Replies)
Discussion started by: manna
8 Replies

3. Solaris

cronjob not working

I am trying to schedule a job via cronjob. Not sure what the problem is. below is my script and the error. 45 10 * * * /u01/app/oracle/jpark/sched_exp_mis.sh Error received. Your "cron" job on tama /u01/app/oracle/jpark/sched_exp_mis.sh produced the following output: ... (19 Replies)
Discussion started by: mrx1350
19 Replies

4. Solaris

cronjob not working

Hi All , I have a cron jobs that is not working while put inside cron. But on executing from manually, it works fine, Pl anyone find if there is anything wrong in the script. 30 22 * * 1-5 cd /home/ab90737/introscope/util/bin; ./batchgenerateReport.pl ../config/reps.config >... (1 Reply)
Discussion started by: jegaraman
1 Replies

5. UNIX for Dummies Questions & Answers

Cronjob for running a php script intermittently?

Hey all Found this forum googling for solutions. Great community this! Im looking for help trying to run a php script every 20 minutes. The script basically has to loop continuously forever but inexplicably hangs every 30 minutes or so. I have not been able to debug the script and find... (2 Replies)
Discussion started by: aras
2 Replies

6. Shell Programming and Scripting

while loop not working in cronjob

Hi , While loop is not working when running script as cronjob. #!/usr/bin/bash xyz sleep 30 var=0 while do xyz commands done This script is working if I run it manually. (7 Replies)
Discussion started by: ankush_mehra
7 Replies

7. UNIX for Dummies Questions & Answers

Cronjob not working

Hi, I am trying to run a script through crontab but it doesn't run. The script sends an email of the logfile created.When I reun through command line it works perfectly but doesn't send any email through cron. There are othe jobs in cron wich runs perfectly. Please let me know if I am doing... (3 Replies)
Discussion started by: Rossdba
3 Replies

8. Shell Programming and Scripting

Cronjob not working as intended

I have a shell script that I have scheduled using cron using a command: 0 10 * * * /directory/Script.sh > /directory/log/output.log The script is scheduled to run at 10 AM everyday. The script executes but produces output files only with headers, no content is there. The script produces... (11 Replies)
Discussion started by: Palak Sharma
11 Replies

9. Shell Programming and Scripting

Cronjob is NOT working

Hi; Here is the output from crontab -l: 2,7,12,17,22,27,32,37,42,47,52,57 * * * * /var/tmp/gcsw/jmap_samples/jmap_script.sh > /var/tmp/gcsw/jmap_samples/histo_`date '+%Y%m%d%H%M'`.txtWhen I manually run the line: /var/tmp/gcsw/jmap_samples/jmap_script.sh >... (2 Replies)
Discussion started by: gc_sw
2 Replies

10. Shell Programming and Scripting

PHP cronjob not working but manual working

Hi, Can anyone help me on my PHP cron not working, but when i do the manual it work. # manual run working /usr/local/bin/php /root/dev/test.php # crontab not working 55 8 * * * /usr/local/bin/php /root/dev/test.php Thank in advances Regards, FSPalero Please use CODE tags as... (2 Replies)
Discussion started by: fspalero
2 Replies
Error(3)						User Contributed Perl Documentation						  Error(3)

NAME
Tk::Error - Method invoked to process background errors SYNOPSIS
Customization: require Tk::ErrorDialog; or sub Tk::Error { my ($widget,$error,@locations) = @_; ... } DESCRIPTION
The Tk::Error method is invoked by perl/Tk when a background error occurs. Two possible implementations are provided in the distribution and individual applications or users can (re)define a Tk::Error method (e.g. as a perl sub) if they wish to handle background errors in some other manner. A background error is one that occurs in a command that didn't originate with the application. For example, if an error occurs while executing a callback specified with a bind or a after command, then it is a background error. For a non-background error, the error can simply be returned up through nested subroutines until it reaches the top-level code in the application; then the application can report the error in whatever way it wishes. When a background error occurs, the unwinding ends in the Tk library and there is no obvious way for Tk to report the error. When Tk detects a background error, it saves information about the error and invokes the Tk::Error method later when Tk is idle. Tk::Error is invoked by perl/Tk as if by the perl code: $mainwindow->Tk::Error("error message", location ...); $mainwindow is the MainWindow associated with widget which detected the error, "error message" is a string describing the error that has been detected, location is a list of one or more "locations" which describe the call sequence at the point the error was detected. The locations are a typically a mixture of perl location reports giving script name and line number, and simple strings describing locations in core Tk or perl/Tk C code. Tk will ignore any result returned by the Tk::Error method. If another error occurs within the Tk::Error method (for example if it calls die) then Tk reports this error itself by writing a message to stderr (this is to avoid infinite loops due to any bugs in Tk::Error). If several background errors accumulate before Tk::Error is invoked to process them, Tk::Error will be invoked once for each error, in the order they occurred. However, if Tk::Error calls Tk->break, then any remaining errors are skipped without calling Tk::Error. The Tk module includes a default Tk::Error subroutine that simply reports the error on stderr. Tk::ErrorDialog An alternate definition is provided via: "require Tk::ErrorDialog;" that posts a dialog box containing the error message and offers the user a chance to see a stack trace showing where the error occurred. This is an OO implementation of the Tcl/Tk command bgerror, with a twist: since there is only one ErrorDialog widget, you aren't required to invoke the constructor to create it; it will be created automatically when the first background error occurs. However, in order to configure the -cleanupcode and -appendtraceback ErrorDialog options you must call the constructor and create it manually. The ErrorDialog object essentially consists of two subwidgets: a Dialog widget to display the background error and a Text widget for the traceback information. If required, you can invoke various widget methods to customize these subwidgets - their advertised names are described below. $mw->ErrorDialog(-cleanupcode => code, -appendtraceback => bool); $mw is a window reference. code is a CODE reference if special post-background error processing is required (default is undefined). The callback subroutine is called with @_ having the same arguments that Tk::Error was invoked with. bool is a boolean indicating whether or not to append successive tracebacks (default is 1, do append). Advertised ErrorDialog widgets error_dialog is the Dialog widget reference. text is the Text widget reference containing the traceback information. BUGS
If after or fileevent are not invoked as methods of a widget then perl/Tk is unable to provide a $mainwindow argument. To support such code from earlier versions of perl/Tk perl/Tk therefore calls Tk::Error with string 'Tk' instead: Tk->Tk::Error(...). In this case the Tk::Error in Tk::ErrorDialog and similar implementations cannot "popup" a window as they don't know which display to use. A mechanism to supply the MainWindow in applications which only have one (a very common case) should be provided. SEE ALSO
Tk::bind Tk::after Tk::fileevent KEYWORDS
background error, reporting perl v5.16.3 2014-06-10 Error(3)
All times are GMT -4. The time now is 06:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy