Cron will not run on its own

That link at google for the sleepy server ....fixed it   THANKS!!!

On Thu, 17 Apr 2003 09:32:42 -0400, "Jerry" <glspen @bright.net>
wrote:



----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---

 (Jerry)  17.04.03 in /comp/unix/sco/misc:

SMP?

root>> ps -ef |grep cron

Ok.. you asked for any ...

I had a (far) similar problem, when OSR5.0.6 decided one 1,3Ghz Xeon is
fast enough so the second CPU is not required and should be deactivated...

The wierd thing:
some "cron" jobs were run, but not all.
(backup works, reboot did not)

cause:
init seems to hang somewhere/died(?).
Obviously it was not respawning getty's for example,
which makes the login on serial console imposible.

(my)solution:
apply of all available patches that contains the words "fast" and "cpu",
not only rs506a, meaning oss648a so the second CPU is not turned off
anymore.

Sorry, I have moved the job all over the place to try and make it work.

On Thu, 17 Apr 2003 16:38:03 -0400, "Jerry" <glspen @bright.net>
wrote:



Accessed system at 6 am .....10 PM backup cron did not run .....idle
time  was around 5 hours.....changed cron  crontab -e for backup to
run at 6 05 am......watched log file .....backup started just fine.

/usr/lib/cron/log

<  (null) 8322 a Thu Apr 24 06:05:00 2003
 rc=1

/usr/lib/cron/log     from  10 PM

 CMD: /usr/lib/uucp/uudemon.poll > /dev/null

<  uucp 8261 c Wed Apr 23 17:10:00 2003

<  uucp 8269 c Thu Apr 24 01:00:00 2003

22:00 ....no cron even attempted to run ......this only works if the
cron is edited and then watched......

other crons are as follows:

root:
17 5 * * 0 /etc/cleanup > /dev/null
2 3 * * 0,4 /usr/lib/cron/logchecker
0 1 * * * /usr/bin/calendar -
3 3 * * * /usr/lib/cleantmp > /dev/null
1 3 * * * /etc/setclk -rd1800 > /dev/null 2>&1
#5 18 * * 1-5 /usr/lib/sa/sa2 -s 8:00 -e 18:01 -i 1200 -A
0 4 * * 0 /etc/custom -V symlinks;# CUSTOM_SYMLINK_REPORT
0 0 * * 1-5 scosh cronsched -r
0 0 * * 1   scosh cronsched -wr
5 6 * * 1-5 exec /usr/lone-tar/ltar.M.cron    <- set to run at 6:05 AM

uucp :

39,9 * * * * /usr/lib/uucp/uudemon.hour > /dev/null
10 * * * * /usr/lib/uucp/uudemon.poll > /dev/null
45 23 * * * ulimit 5000; /usr/lib/uucp/uudemon.clean > /dev/null
48 10,14 * * 1-5 /usr/lib/uucp/uudemon.admin > /dev/null

I don't know if this sheds any light on this or not.

----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---

On Wed, 16 Apr 2003 12:02:09 -0400, "Jerry" <glspen @bright.net>
wrote:

Has the system been idle for awhile at 10:00pm?  Do other cron jobs
run, or is it just your backup entry that fails?

I don't know what the Acer G700 is, but you may have a system that has
what was not-so-affectionately referred to as the 'sleepy server'
issue.  Take a look through

Also Google for 'sleepy server' in the comp.unix.sco.* groups - You'll
find others with similar stories, but not necessarily the same
solution.

Scott McMillan

Here is one additional item :
root> ps -ef |grep cron
          root 21391 18976  3 09:29:33 tty1A00    00:00:00 grep cron
          root 15815     1  0   Apr-07       ?    00:00:01 /etc/cron
root> uptime
  9:29am  up 5 days, 20:10,  16 users,  load average: 0.02, 0.01, 0.00
root> date
Thu Apr 17 09:29:51 EDT 2003

System rebooted on April 12 th.    the cron has been running since April 7
th.....

Any thoughts?

Jerry

results of
root> crontab -l |cat -v
#       @(#) root 90.1 00/05/01
#
#       Copyright (C) 1989-2000 The Santa Cruz Operation, Inc.
#               All Rights Reserved.
#       The information in this file is provided for the exclusive use of
#       the licensees of The Santa Cruz Operation, Inc.  Such users have the
#       right to use, modify, and incorporate this code into other products
#       for purposes authorized by the license agreement provided they
include
#       this notice and the associated copyright notice with any such
product.
#       The information in this file is provided "AS IS" without warranty.
#
17 5 * * 0 /etc/cleanup > /dev/null
2 3 * * 0,4 /usr/lib/cron/logchecker
0 1 * * * /usr/bin/calendar -
3 3 * * * /usr/lib/cleantmp > /dev/null
1 3 * * * /etc/setclk -rd1800 > /dev/null 2>&1
#5 18 * * 1-5 /usr/lib/sa/sa2 -s 8:00 -e 18:01 -i 1200 -A
0 4 * * 0 /etc/custom -V symlinks;# CUSTOM_SYMLINK_REPORT
0 0 * * 1-5 scosh cronsched -r
0 0 * * 1   scosh cronsched -wr
30 23 * * 1-5   exec /usr/lone-tar/tar_test

Scott,

First thanks for the quick reply,  By 10 PM the system has normally been
idle for 4 hours,  I started the cron log to see if other jobs were
running....they are running fine....these were the standard SCO crons from
install. Near as I can tell it is only the backup entry that fails ....I
also put just a plain  tar entry in the cron ....tat also did not run.....

Dazed and confused...

Jerry

225%40mammoth.ca.caldera.com

<stuff about a cron task not running>

Thought #1: Have you already checked root email for any messages about
problems with the cron entry?

Thought #2: What exactly is the output of
$ su - root
# crontab -l | cat -v

--
Ian Wilson