Sponsored Content
Top Forums UNIX for Advanced & Expert Users Upgrading legacy packages with patch Post 303043799 by Neo on Friday 7th of February 2020 04:23:05 AM
Old 02-07-2020
Normally if we are making upgrades to mission critical applications in 100s of servers in a large organization with a risk management team we should notify them if if we plan any upgrades which may cause an outage.

You should test in a test bed, make a plan, identify the risks and notify your risk management team.

Upgrading the core "mission critical" application on 200-300 web servers requires planning and team work.

What happens if you make a mistake and bring down the application(s)? Do you want your organization to be caught off guard when customers are calling in, angry their service is down?

You have described a major infrastructure upgrade. You certainly do not want to upgrade with YUM over a manually installed configuration until you have completed tested this idea in a test bed, insure you have backups of each application and database before hand, etc. In other words, you need a plan in coordination with your IT risk management team, customer service, etc.

This is how we work as IT professionals.
 

9 More Discussions You Might Find Interesting

1. Programming

CMI Legacy

Is there anyone who still uses CMI to connect to the legacy system , my c applications do uses the binaries and libraries for using the CMI functionality but i do not have access to the original source code , and since this is a very old stuff , i just could not get any source to get to knwo the... (0 Replies)
Discussion started by: dino_leix
0 Replies

2. IP Networking

Patch-o-matic (patch for iptable) for linux2.4.08 & iptable1.2.7a

Hello friends I'm running Redhat 9.0 with linux kernel 2.4.20-8 & have iptables version 1.2.7a & encountering a problem that I narrate down. I need to apply patch to my iptable and netfilter for connection tracking and load balancing that are available in patch-o-matic distribution by netfilter.... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies

3. Red Hat

upgrading packages

Hello, I am using Redhat Linux Enterprise 4 AS. To upgrade NFS, I had to browse the internet and finally I got the latest rpm https://rhn.redhat.com/errata/RHBA-2005-727.html That was a time-consuming procedure. On Solaris, I am used to go to sunfreeware.sun.com and download the latest... (3 Replies)
Discussion started by: melanie_pfefer
3 Replies

4. Programming

VERSYS Legacy System

I need help locating the tables that hold the demograhic data in this system on an AIX box. Does anyone know the path? (0 Replies)
Discussion started by: Chelcye
0 Replies

5. Slackware

Find Slackware Packages - packages.acl.org.ua

Hi! Let me introduce a project for find and download Slackware packages and browse Slackware repositories. The site provides following features: * Large, daily updated database with RPM, DEB, TGZ, TXZ packages for well-known repositories of the Slackware, Fedora, CentOS, RHEL, Debian,... (2 Replies)
Discussion started by: lystor
2 Replies

6. Solaris

Facing problem after upgrading the kernal patch level to 142900-12

I have a Solaris 10 OS having kernal patch level 138888-03 on several servers but recenlty I upgraded it into 142900-12 on some T-Series servers & v890 server after install them my syslog is increasing at a rate of 1GB on average on all servers . I believe its a bug, can somebody help me in... (1 Reply)
Discussion started by: sb200
1 Replies

7. What is on Your Mind?

Tron Legacy

Watched it. Major disappointment. (10 Replies)
Discussion started by: ni2
10 Replies

8. Ubuntu

Encountering problem on upgrading the packages

Hi folks, Ubuntu 9.04 I have an old box not running for years. I just dig it out from the store room. On running; $ sudo aptitude update ...... ...... Err http://hk.archive.ubuntu.com jaunty/main Packages 404 Not Found Err http://hk.archive.ubuntu.com jaunty/restricted Packages ... (1 Reply)
Discussion started by: satimis
1 Replies

9. Solaris

Determine if you are in a Legacy Zone?

Hi Folks, Just a quick question here, about Legacy Zones. Well more about how to determine if you are actually in one, on logging into a legacy zone - is there a quick way of checking that? Regards Gull04 (7 Replies)
Discussion started by: gull04
7 Replies
Apache::Test(3) 					User Contributed Perl Documentation					   Apache::Test(3)

NAME
Apache::Test - Test.pm wrapper with helpers for testing Apache SYNOPSIS
use Apache::Test; DESCRIPTION
Apache::Test is a wrapper around the standard "Test.pm" with helpers for testing an Apache server. FUNCTIONS
plan This function is a wrapper around "Test::plan": plan tests => 3; just like using Test.pm, plan 3 tests. If the first argument is an object, such as an "Apache::RequestRec" object, "STDOUT" will be tied to it. The "Test.pm" global state will also be refreshed by calling "Apache::Test::test_pm_refresh". For example: plan $r, tests => 7; ties STDOUT to the request object $r. If there is a last argument that doesn't belong to "Test::plan" (which expects a balanced hash), it's used to decide whether to con- tinue with the test or to skip it all-together. This last argument can be: o a "SCALAR" the test is skipped if the scalar has a false value. For example: plan tests => 5, 0; But this won't hint the reason for skipping therefore it's better to use have(): plan tests => 5, have 'LWP', { "perl >= 5.7.3 is required" => sub { $] >= 5.007003 } }; see have() for more info. o an "ARRAY" reference have_module() is called for each value in this array. The test is skipped if have_module() returns false (which happens when at least one C or Perl module from the list cannot be found). o a "CODE" reference the tests will be skipped if the function returns a false value. For example: plan tests => 5, &have_lwp; the test will be skipped if LWP is not available All other arguments are passed through to Test::plan as is. ok Same as Test::ok, see Test.pm documentation. sok Allows to skip a sub-test, controlled from the command line. The argument to sok() is a CODE reference or a BLOCK whose return value will be passed to ok(). By default behaves like ok(). If all sub-tests of the same test are written using sok(), and a test is executed as: % ./t/TEST -v skip_subtest 1 3 only sub-tests 1 and 3 will be run, the rest will be skipped. skip Same as Test::skip, see Test.pm documentation. test_pm_refresh Normally called by Apache::Test::plan, this function will refresh the global state maintained by Test.pm, allowing "plan" and friends to be called more than once per-process. This function is not exported. Functions that can be used as a last argument to the extended plan(): plan tests => 5, &have_http11; Require HTTP/1.1 support. have_ssl plan tests => 5, &have_ssl; Require SSL support. Not exported by default. have_lwp plan tests => 5, &have_lwp; Require LWP support. have_cgi plan tests => 5, &have_cgi; Requires mod_cgi or mod_cgid to be installed. have_apache plan tests => 5, have_apache 2; Requires httpd-2.x (apache-2.x). plan tests => 5, have_apache 1; Requires apache-1.3.x. have_perl plan tests => 5, have_perl 'iolayers'; plan tests => 5, have_perl 'ithreads'; Requires a perl extension to be present, or perl compiled with certain capabilities. The first example tests whether "PerlIO" is available, the second whether: $Config{useithread} eq 'define'; have_module plan tests => 5, have_module 'CGI'; plan tests => 5, have_module qw(CGI Find::File); plan tests => 5, have_module ['CGI', 'Find::File', 'cgid']; Requires Apache C and Perl modules. The function accept a list of arguments or a reference to a list. In case of C modules, depending on how the module name was passed it may pass through the following completions: 1 have_module 'proxy_http.c' If there is the .c extension, the module name will be looked up as is, i.e. 'proxy_http.c'. 2 have_module 'mod_cgi' The .c extension will be appended before the lookup, turning it into 'mod_cgi.c'. 3 have_module 'cgi' The .c extension and mod_ prefix will be added before the lookup, turning it into 'mod_cgi.c'. have plan tests => 5, have 'LWP', { "perl >= 5.7.3 is required" => sub { $] >= 5.007003 } }, { "not Win32" => sub { $^O eq 'MSWin32' } }, 'cgid'; have() is more generic function which can impose multiple requirements at once. All requirements must be satisfied. have()'s argument is a list of things to test. The list can include scalars, which are passed to have_module(), and hash references. The hash references have a condition code reference as a value and a reason for failure as a key. The condition code is run and if it fails the provided reason is used to tell user why the test was skipped. In the presented example, we require the presense of the "LWP" Perl module, "mod_cgid", that we run under perl >= 5.7.3 on Win32. It's possible to put more than one requirement into a single hash reference, but be careful that the keys will be different: have 'LWP', { "perl >= 5.7.3 is required" => sub { $] >= 5.007003 }, "not Win32" => sub { $^O eq 'MSWin32' }, }, 'cgid'; Also see plan(). Apache::TestToString Class The Apache::TestToString class is used to capture Test.pm output into a string. Example: Apache::TestToString->start; plan tests => 4; ok $data eq 'foo'; ... # $tests will contain the Test.pm output: 1..4 ok 1 ... my $tests = Apache::TestToString->finish; perl v5.8.0 2002-09-10 Apache::Test(3)
All times are GMT -4. The time now is 07:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy