<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic cron issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/cron-issue/m-p/5092026#M442533</link>
    <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I am investigating an issue where several defunc progs are being produced between 1600 - 2200 on evry hour and half hour:&lt;BR /&gt;&lt;BR /&gt;output from my last failure:&lt;BR /&gt;&lt;BR /&gt;imx018&amp;gt; # ps -ef |grep 17417&lt;BR /&gt;root      13232  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      14125  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      14375  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      15199  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      15294  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      15953  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      16369  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      16633  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      16713  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      17236  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      17417    789  0.0 17:30:00 ??           0:00.04 /usr/sbin/cron&lt;BR /&gt;root      17693  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      17804  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      18679  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;imx018&amp;gt; # ps -ef |grep cron&lt;BR /&gt;root        789      1  0.0   Jan 21 ??           1:43.60 /usr/sbin/cron&lt;BR /&gt;root      17417    789  0.0 17:30:00 ??           0:00.04 /usr/sbin/cron&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;as you can see 789 is the original cron process however when the defunc procs are produced another cron daemon is left hanging around.&lt;BR /&gt;&lt;BR /&gt;Investigations I have done so far are:&lt;BR /&gt;&lt;BR /&gt;checked all cron jobs that start between 00, 30 from the /var/spool/cron/crontabs directory.&lt;BR /&gt;&lt;BR /&gt; - commented out all jobs that start at this time and the defunc still appear&lt;BR /&gt;&lt;BR /&gt;- added two lines to each cron script scheduled to obtain the PID and COMMAND and sent this to a file, no pids match any of the defunc pids.&lt;BR /&gt;&lt;BR /&gt;all I can think is maybe there is a job that is started by the original program that initiates another script which is failing however as I mentioned I have commented out all jobs ( one at a time ) and the defun procs still come .....&lt;BR /&gt;&lt;BR /&gt;The final thing i performed was to restart the cron daemon.&lt;BR /&gt;&lt;BR /&gt;Does anyone have any idea how I can trouble shoot this further?&lt;BR /&gt;&lt;BR /&gt;there is no indication of the issue in mail or syslog.&lt;BR /&gt;&lt;BR /&gt;thanks for any help.&lt;BR /&gt;&lt;BR /&gt;Chris.&lt;BR /&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;</description>
    <pubDate>Mon, 11 Feb 2008 16:44:49 GMT</pubDate>
    <dc:creator>lawrenzo_1</dc:creator>
    <dc:date>2008-02-11T16:44:49Z</dc:date>
    <item>
      <title>cron issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cron-issue/m-p/5092026#M442533</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I am investigating an issue where several defunc progs are being produced between 1600 - 2200 on evry hour and half hour:&lt;BR /&gt;&lt;BR /&gt;output from my last failure:&lt;BR /&gt;&lt;BR /&gt;imx018&amp;gt; # ps -ef |grep 17417&lt;BR /&gt;root      13232  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      14125  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      14375  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      15199  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      15294  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      15953  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      16369  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      16633  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      16713  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      17236  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      17417    789  0.0 17:30:00 ??           0:00.04 /usr/sbin/cron&lt;BR /&gt;root      17693  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      17804  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;root      18679  17417  0.0 -        ??           0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;imx018&amp;gt; # ps -ef |grep cron&lt;BR /&gt;root        789      1  0.0   Jan 21 ??           1:43.60 /usr/sbin/cron&lt;BR /&gt;root      17417    789  0.0 17:30:00 ??           0:00.04 /usr/sbin/cron&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;as you can see 789 is the original cron process however when the defunc procs are produced another cron daemon is left hanging around.&lt;BR /&gt;&lt;BR /&gt;Investigations I have done so far are:&lt;BR /&gt;&lt;BR /&gt;checked all cron jobs that start between 00, 30 from the /var/spool/cron/crontabs directory.&lt;BR /&gt;&lt;BR /&gt; - commented out all jobs that start at this time and the defunc still appear&lt;BR /&gt;&lt;BR /&gt;- added two lines to each cron script scheduled to obtain the PID and COMMAND and sent this to a file, no pids match any of the defunc pids.&lt;BR /&gt;&lt;BR /&gt;all I can think is maybe there is a job that is started by the original program that initiates another script which is failing however as I mentioned I have commented out all jobs ( one at a time ) and the defun procs still come .....&lt;BR /&gt;&lt;BR /&gt;The final thing i performed was to restart the cron daemon.&lt;BR /&gt;&lt;BR /&gt;Does anyone have any idea how I can trouble shoot this further?&lt;BR /&gt;&lt;BR /&gt;there is no indication of the issue in mail or syslog.&lt;BR /&gt;&lt;BR /&gt;thanks for any help.&lt;BR /&gt;&lt;BR /&gt;Chris.&lt;BR /&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;&lt;/DEFUNCT&gt;</description>
      <pubDate>Mon, 11 Feb 2008 16:44:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cron-issue/m-p/5092026#M442533</guid>
      <dc:creator>lawrenzo_1</dc:creator>
      <dc:date>2008-02-11T16:44:49Z</dc:date>
    </item>
    <item>
      <title>Re: cron issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cron-issue/m-p/5092027#M442534</link>
      <description>This shouldn't be happening.  cron shouldn't be creating zombies (zombie master).  If it is, then it is a bug in cron.  Have you looked for any cron patches?&lt;BR /&gt;&lt;BR /&gt;root 13232 17417 0.0 - ?? 0:00.00 &lt;DEFUNCT&gt;&lt;BR /&gt;I assume something like "ps -fp 13232" doesn't give you the name of the process?&lt;BR /&gt;It is root, does that tell you anything?&lt;BR /&gt;&lt;BR /&gt;&amp;gt;The final thing i performed was to restart the cron daemon.&lt;BR /&gt;&lt;BR /&gt;Did the restart create another zombie master?&lt;BR /&gt;Have you tried killing the zombie master 17417?&lt;BR /&gt;&lt;/DEFUNCT&gt;</description>
      <pubDate>Mon, 11 Feb 2008 17:12:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cron-issue/m-p/5092027#M442534</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2008-02-11T17:12:16Z</dc:date>
    </item>
    <item>
      <title>Re: cron issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cron-issue/m-p/5092028#M442535</link>
      <description>thanks Dennis,&lt;BR /&gt;&lt;BR /&gt;I have checked the ps -fp and nothing exept the defunc proc being displayed.&lt;BR /&gt;&lt;BR /&gt;running ./cron stop from init.d directory didnt kill the second cron master so killed manually&lt;BR /&gt;&lt;BR /&gt;I restarted cron and have also removed a cron file for a user that had the home area removed / not present and didnt see any errors appear at 1700&lt;BR /&gt;&lt;BR /&gt;offending user:&lt;BR /&gt;&lt;BR /&gt;riviera:Nologin:xxx:xxx:Riviera transfer:/usr/users/tx/riviera:/bin/ksh&lt;BR /&gt;&lt;BR /&gt;the directory /usr/users/tx/riviera is not present and although the cron jobs associated with this were not relevant - hopefully this will fix my issue ...&lt;BR /&gt;&lt;BR /&gt;Thanks for the advise</description>
      <pubDate>Mon, 11 Feb 2008 17:25:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cron-issue/m-p/5092028#M442535</guid>
      <dc:creator>lawrenzo_1</dc:creator>
      <dc:date>2008-02-11T17:25:06Z</dc:date>
    </item>
    <item>
      <title>Re: cron issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/cron-issue/m-p/5092029#M442536</link>
      <description>identifying the reviera user and removing the cron file has resolved my issue.</description>
      <pubDate>Tue, 12 Feb 2008 10:25:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/cron-issue/m-p/5092029#M442536</guid>
      <dc:creator>lawrenzo_1</dc:creator>
      <dc:date>2008-02-12T10:25:55Z</dc:date>
    </item>
  </channel>
</rss>

