crontab problems

[Dennis Handly]

>do you have any idea about the error code ts=11????

As I mentioned above. A child of cron(1m) died with signal 11. The ones with ts=139 got a core file. Find it.

[Safir Safir]

hello

Ok may you tell me what is sending the sig kill to the child cron process?

i find the core under /var/spool/cron/atjobs/core

please find it attached

thank you

[OldSchool]

Do files / permissions / owners in /var/adm/cron look like this?

-r--r--r-- 1 bin bin .proto
prw------- 1 root root FIFO
-rw-r--r-- 1 root root OLDlog
-r--r--r-- 1 bin bin at.allow
-r--r--r-- 1 bin bin cron.allow
-rw-r--r-- 1 root root log
-r--r--r-- 1 bin bin queuedefs

the "default" contents of queuedefs should be something like this:

a.4j1n
b.2j2n90w

[Dennis Handly]

>may you tell me what is sending the sig kill to the child cron process?

It would be root. Or the owner of the crontab sh process. Unless this is SEGSEGV.
Do you have the latest cron patches?

>i find the core under /var/spool/cron/atjobs/core

Does this match the date of your first ts=139?

>please find it attached

This is useless. It seems this is a "strings core" output.

To debug this, I would need you to do:
# file core
# gdb /usr/sbin/cron core
packcore
q

Basically this will package up cron and libc.2.

>TZ=Africa/Monrovia

This isn't valid on HP-UX unless you are in UTC?

[Yogeeraj_1]

hi BR,

can you also verify if there are any "conflicting" at jobs?

e.g.
at -l


revert.

kind regards
yogeeraj

[Safir Safir]

Hello,

this core that i sent it is not for the first one.

I have adb not gdb on my server could you advice about adb.

please fins attached the core ,not the strings,

yes we are in utc for the time

Best regards and thx

[Dennis Handly]

>I have adb not gdb on my server could you advice about adb.

adb is useless. You can download the latest gdb from:
http://www.hp.com/go/wdb

>please find attached the core

From that I was able to tell you are aborting in /usr/lib/libdld.sl.
I need a copy of that and these files:
/usr/lib/dld.sl
/usr/lib/libsec.2
/usr/lib/libc.2
/usr/sbin/cron

>yes we are in UTC for the time

Not really, it says you have this bogus TZ setting:
TZ=Africa/Monrovia
It seems you are depending on bogus TZ settings defaulting to UTC.

[Safir Safir]

Dear ALL,

The problem was resolved i rpelaced the timezone from AFRICA/MONROVIA to GMT and all the crons works fine with no problem at all

I would like to thank you all

Regards

[Safir Safir]

The problem was resolved