<?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 Re: Restarts in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/restarts/m-p/2470231#M716652</link>
    <description>The manner in which HP recommends complex application startups in a package is to launch the application from the customer_defined_run_cmds section of the script, and then launch yet another script (re-entry the startup script with a "monitor" option) to do the monitoring.  This technique is employed in the HP toolkit for Oracle databases for instance.&lt;BR /&gt;&lt;BR /&gt;The trouble comes, as you noted in the restarts area, where when a service fails, the restart is not performed by the standard package control script because the SERVICE_CMD would only launch yet another iteration of the monitor script, and not the start-up processes.&lt;BR /&gt;&lt;BR /&gt;Perhaps it is necessary to have the monitor script handle the restart issue, and not configure it in standard package control script SERVICE_RESTARTS variable.</description>
    <pubDate>Tue, 12 Dec 2000 19:54:44 GMT</pubDate>
    <dc:creator>Stephen Doud</dc:creator>
    <dc:date>2000-12-12T19:54:44Z</dc:date>
    <item>
      <title>Restarts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restarts/m-p/2470229#M716650</link>
      <description>I have recently installed ServiceGuard OPS r=A.11.09.&lt;BR /&gt;If I configure the package with SERVICE_CMD = a command that starts the application, the SERVICE_RESTARTS work like I would expect.&lt;BR /&gt;&lt;BR /&gt;In class it was suggested that a monitor script be &lt;BR /&gt;used for the SERVICE_CMD and the application startup&lt;BR /&gt;be done in the customer defined run commands.  When I configure in this fashion, I can see that restarts were attempted in the log, but it looks like the customer defined run commands were not executed on restart.&lt;BR /&gt;&lt;BR /&gt;I have search docs.hp.com/ha and have yet to find a answer to this problem/feature.&lt;BR /&gt;&lt;BR /&gt;Thanks for listening.</description>
      <pubDate>Mon, 04 Dec 2000 18:36:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restarts/m-p/2470229#M716650</guid>
      <dc:creator>Rod Wesselman</dc:creator>
      <dc:date>2000-12-04T18:36:00Z</dc:date>
    </item>
    <item>
      <title>Re: Restarts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restarts/m-p/2470230#M716651</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;There might be an error the script that starts up the processes. Maybe you tested it using a different PATH, a slightly modified environment, ...&lt;BR /&gt;&lt;BR /&gt;I'd try to put a 'set -x' and a 'set -v' in the script and check the output. It should be in the MC/SG log scripts for that package. Check that output for errors, especially the part starting the processes.&lt;BR /&gt;&lt;BR /&gt;Don' forget to remove the set -x and set -v after you solved the problem to avoid filling up the logfiles too quickly.&lt;BR /&gt;&lt;BR /&gt;Bye,&lt;BR /&gt;Rik</description>
      <pubDate>Tue, 05 Dec 2000 06:21:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restarts/m-p/2470230#M716651</guid>
      <dc:creator>RikTytgat</dc:creator>
      <dc:date>2000-12-05T06:21:26Z</dc:date>
    </item>
    <item>
      <title>Re: Restarts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restarts/m-p/2470231#M716652</link>
      <description>The manner in which HP recommends complex application startups in a package is to launch the application from the customer_defined_run_cmds section of the script, and then launch yet another script (re-entry the startup script with a "monitor" option) to do the monitoring.  This technique is employed in the HP toolkit for Oracle databases for instance.&lt;BR /&gt;&lt;BR /&gt;The trouble comes, as you noted in the restarts area, where when a service fails, the restart is not performed by the standard package control script because the SERVICE_CMD would only launch yet another iteration of the monitor script, and not the start-up processes.&lt;BR /&gt;&lt;BR /&gt;Perhaps it is necessary to have the monitor script handle the restart issue, and not configure it in standard package control script SERVICE_RESTARTS variable.</description>
      <pubDate>Tue, 12 Dec 2000 19:54:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restarts/m-p/2470231#M716652</guid>
      <dc:creator>Stephen Doud</dc:creator>
      <dc:date>2000-12-12T19:54:44Z</dc:date>
    </item>
  </channel>
</rss>

