/[monit]/monit/web/story/index.php
ViewVC logotype

Diff of /monit/web/story/index.php

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.4 by hauk, Wed Jun 8 13:35:28 2005 UTC revision 1.5 by hauk, Thu Sep 15 15:48:35 2005 UTC
# Line 16  long, one or two paragraphs are fine. A Line 16  long, one or two paragraphs are fine. A
16    Stories:<br>    Stories:<br>
17    
18    <ul style="list-style-type: square;">    <ul style="list-style-type: square;">
19      <li><a href="#proutag">PROUT AG</a>      <li><a href="#labahn">Dietmar Labahn</a>
20      <li><a href="#sturtewagen">Tim Sturtewagen</a>      <li><a href="#sturtewagen">Tim Sturtewagen</a>
21    </ul>    </ul>
22  </p>  </p>
23    
24  <div style="background: #f0f0f0; padding: 0px 0px 2px 10px; border: 1px dotted #ccc;">  <div style="background: #f0f0f0; padding: 0px 0px 2px 10px; border: 1px dotted #ccc;">
25  <a name="proutag"></a>  <a name="labahn"></a>
 <h3>PROUT AG</h3>  
26  <p>  <p>
27  <i>Contributed by Dietmar Labahn (labahn at prout!de)</i>  <i>Contributed by Dietmar Labahn</i>
28  </p>  </p>
29  <p>  <p>
30  <a href="http://www.prout.de">PROUT AG</a> provides Printout for Experts. PROUT inForm generates electronic documents and manages the workflow of these documents.  I use Linux CUPS and LPRng Print- and workflow servers. Because these
31  </p>  servers are essential to the company (Automotive), I decided to implement a
32  <p>  Heartbeat solution. During the print process the invoices are also
33  We use Linux CUPS and LPRng Printservers with our program (112 kb executable!). Because these servers are essential to the company (Daimler/Chrysler), I decided to implement a Heartbeat solution. During the print process the invoices are also transfered to a document management system (EASY), we convert the printfiles as well to PDF and create index files for the DMS. In addition, we send certain printfiles to certain people as PDF mail attachments.  transfered to a document management system (EASY), we convert the printfiles
34  </p>  as well to PDF and create index files for the DMS. In addition, we send
35  <p>  certain printfiles to certain people as PDF mail attachments.
36  It is clear that it would cost the company a lot of money, if the system would fail. I decided to use the HA system in connection with monit. Two Intel-based servers (Raid 5) running under SUSE LINUX 8.2 with mostly redundant hardware is the platform.  </p>
37  </p>  <p>
38  <p>  It is clear that it would cost the company a lot of money, if the system
39  Heartbeat and monit are configured as suggested under the monit website, which means that monit is started by the system daemon (configured via inittab). It then starts Heartbeat, via its configuration file monitrc, by the monit option "start group local". This means, when coming up, monit starts all services marked as local. The services CUPS, postfix and Samba are started by Heartbeat, using the monit "Start Group" option. This means that the services are under control of both HA and monit. HA takes care that the services are only running on the active node, and monit takes care that they are monitored and restarted on the active node if needed. Because the main server is changed now and then (printers added, deleted, PROUT configuration files changed etc), I use CRON and scripts to update the backup server with all the relevant files once a day (at night).  would fail. I decided to use the HA system in connection with monit. Two
40  </p>  Intel-based servers (Raid 5) running under SUSE LINUX 8.2 with mostly
41  <p>  redundant hardware is the platform.
42  Until now, it has worked like a charm (even though no failures happened yet). From my point of view, I can recommend it highly. It takes some time to get to all the bits, but then ..... On the other hand -- who ever said that such a highly sofisticated system is trivial. I am now at my 4th HA installation, and it works perfectly!  </p>
43    <p>
44    Heartbeat and monit are configured as suggested under the monit website,
45    which means that monit is started by the system daemon (configured via
46    inittab). It then starts Heartbeat, via its configuration file monitrc, by
47    the monit option "start group local". This means, when coming up, monit
48    starts all services marked as local. The services CUPS, postfix and Samba
49    are started by Heartbeat, using the monit "Start Group" option. This means
50    that the services are under control of both HA and monit. HA takes care that
51    the services are only running on the active node, and monit takes care that
52    they are monitored and restarted on the active node if needed. Because the
53    main server is changed now and then (printers added, deleted, configuration
54    files changed etc), I use CRON and scripts to update the backup server with
55    all the relevant files once a day (at night).</p>
56    <p>
57    Until now, it has worked like a charm (even though no failures happened
58    yet). From my point of view, I can recommend it highly. It takes some time
59    to get to all the bits, but then ..... On the other hand -- who ever said
60    that such a highly sofisticated system is trivial. I am now at my 4th HA
61    installation, and it works perfectly!
62  </p>  </p>
63  </div>  </div>
64  <div style="background: #fff; padding: 0px 0px 2px 10px; border: 1px dotted #ccc;">  <div style="background: #fff; padding: 0px 0px 2px 10px; border: 1px dotted #ccc;">

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.5

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26