Professional Web Applications Themes

At job not executing - SCO

Hello, I'm having the following problem, maybe someone will be able to help me: I have a SCO Openserver 5.05 machine which stopped executing at jobs. When I use the at command: at now + 2 minutes ls -la Ctrl-D it says that the job will be executed, but after half an hour the job is still in the /usr/spool/cron/atjobs folder and never gets executed. At the same time, cron is working correctly (apparently) since crontab job get executed without any problems. I don't know what to check to find a soluzione to the problem. Any idea ? Thank you ...

  1. #1

    Default At job not executing

    Hello,

    I'm having the following problem, maybe someone will be able to help
    me:

    I have a SCO Openserver 5.05 machine which stopped executing at jobs.

    When I use the at command:
    at now + 2 minutes
    ls -la
    Ctrl-D
    it says that the job will be executed, but after half an hour the job
    is still in the /usr/spool/cron/atjobs folder and never gets executed.
    At the same time, cron is working correctly (apparently) since crontab
    job get executed without any problems.

    I don't know what to check to find a soluzione to the problem.

    Any idea ?

    Thank you in advance.

    Paolo Asioli
    Paolo Guest

  2. #2

    Default Re: At job not executing

    Paolo Asioli typed (on Thu, Nov 06, 2003 at 07:34:18AM -0800):
    | Hello,
    |
    | I'm having the following problem, maybe someone will be able to help
    | me:
    |
    | I have a SCO Openserver 5.05 machine which stopped executing at jobs.
    |
    | When I use the at command:
    | at now + 2 minutes
    | ls -la
    | Ctrl-D
    | it says that the job will be executed, but after half an hour the job
    | is still in the /usr/spool/cron/atjobs folder and never gets executed.
    | At the same time, cron is working correctly (apparently) since crontab
    | job get executed without any problems.
    |
    | I don't know what to check to find a soluzione to the problem.
    |
    | Any idea ?

    Is oss642a installed? Maybe it fixes the problem.

    As you show it, that cron job would only result in sending
    you some email with the output of 'l -a'.

    --
    JP
    Jean-Pierre Guest

  3. #3

    Default Re: At job not executing

    On 6 Nov 2003 07:34:18 -0800, it (Paolo Asioli) wrote:
     

    Wrong. cron needs to have a "controlling terminal" in which it can
    send its output. The default is to either eat the output or send it
    gift wrapped via email. Check your root email.

    Try it this way:

    at now +2 minutes
    date > /tmp/date.out
    <ctrl>D

    The contents of the /tmp/date.out file will be when cron executed the
    at command. If you wanna see output on a terminal, try it this way:

    at now +2 minutes
    ls -al | /usr/lib/lponlcr > /dev/tty01
    <ctrl>D

    Whatever you do, don't run anything from the "at" command that
    requires a keyboard command or keyboard input to terminate. It will
    run forever until you kill the job.


    --
    # Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
    # 831.336.2558 voice http://www.LearnByDestroying.com
    # santa-cruz.ca.us
    # 831.421.6491 digital_pager com AE6KS
    Jeff Guest

  4. #4

    Default Re: At job not executing

    Jeff Liebermann <santa-cruz.ca.us> wrote in message news:<com>...
     

    Sorry, I dodn't explain myself. With that command I know that the
    output of that command will go in the user's email.

    But the problem is that, while crontab jobs are correctly executed on
    that machine, "at" jobs aren't executed anyore. We have a number of
    5.05 installations and lately two or three of them showed the problem:
    basically after a time, we don't know why, the "at" command stops
    working.
    And to test this malfunctioning, if you schedule a simple command like
    "ls -la", which reads the current directory and send the output to the
    user's email, the job stays in the queue without ever getting
    executed.

    This is becoming a really big problem, since the nightly batch
    transfers don't get executed anyore and it seems to be difficult to
    convert everything to crontab.

    Any ideas ?

    Suppose that a number of jobs result still in the queue: is it
    possible that cron keeps subsequent at jobs in the queue if the limit
    in queuedefs has already been reached ?

    I'll investigate, but if anyone has idea to help be troubleshoot is
    very welcome !

    Thank you very much.

    Paolo
    Paolo Guest

  5. #5

    Default Re: At job not executing

    In article <google.com>,
    Paolo Asioli <it> wrote: 
    >
    >Sorry, I dodn't explain myself. With that command I know that the
    >output of that command will go in the user's email.
    >
    >But the problem is that, while crontab jobs are correctly executed on
    >that machine, "at" jobs aren't executed anyore. We have a number of
    >5.05 installations and lately two or three of them showed the problem:
    >basically after a time, we don't know why, the "at" command stops
    >working.
    >And to test this malfunctioning, if you schedule a simple command like
    >"ls -la", which reads the current directory and send the output to the
    >user's email, the job stays in the queue without ever getting
    >executed.
    >
    >This is becoming a really big problem, since the nightly batch
    >transfers don't get executed anyore and it seems to be difficult to
    >convert everything to crontab.[/ref]
     
     

    Do these jobs show up in at's queue - or are they simply gone and
    not just not executing. That wasn't clear.



    --
    Bill Vermillion - bv wjv . com
    Bill Guest

  6. #6

    Default Re: At job not executing

    PROBLEM SOLVED !!!!

    Thank you all, with your help I got a better understanding of the
    internals of the "at" command.

    The stuck jobs DID show in the at -l queue list, but they never got
    executed.

    This was caused by older jobs that were still executing but in effect
    stuck (the process hung and was never killed) that filled up the 4
    places allowed by default in the at queue. In that case the at simply
    stopped executing new jobs, since it was waiting for the older ones to
    finish.

    Thank you again for the help !

    Best regards,
    Paolo
    Paolo Guest

Similar Threads

  1. Executing EXE
    By Yoshitha in forum ASP.NET Security
    Replies: 5
    Last Post: July 6th, 07:24 PM
  2. Executing a file .exe or .bat
    By FhErC webforumsuser@macromedia.com in forum Macromedia Flash Actionscript
    Replies: 1
    Last Post: February 6th, 02:07 PM
  3. Error when executing UDF
    By Bill in forum Microsoft SQL / MS SQL Server
    Replies: 2
    Last Post: August 8th, 09:37 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139