8 More Discussions You Might Find Interesting
1. AIX
Hello,
I did offline HACMP(PowerHA) upgrade 5.4.1 to 5.5 - basically stopped HACMP services and upgraded cluster.* filesets.
Tried to start services again - topsvcs refused to start on second node complaining that node instance numbers are different - and indeed they are different.
This is... (2 Replies)
Discussion started by: vilius
2 Replies
2. AIX
hi,
when I do a failover, hacmp always starts db2 but recently it fails to start db2..noticed the issue is db2nodes.cfg is not modified by hacmp and is still showing primary node..manually changed the node name to secondary after which db2 started immediately..unable to figure out why hacmp is... (4 Replies)
Discussion started by: gkr747
4 Replies
3. AIX
Hi
What is the procedure to upgrade the MQ from 6 to 7 in aix hacmp cluster. Do i need to bring down the cluster
services running in both the nodes and then give #smitty installp in both the nodes separately. Please assist... (0 Replies)
Discussion started by: samsungsamsung
0 Replies
4. AIX
Hi,
I need to upgrade one of my clusters from HACMP 5.41 to HACMP 6.1.
Is there an easy + clean way to do it ? Any hurdles I have to anticipate? What should I read - anything I found so far seems to talk only about HACMP 5.x - and looks pretty straight forward.
Thanks and regards
zxmaus (1 Reply)
Discussion started by: zxmaus
1 Replies
5. AIX
hi
can anyone explain the concepts of HACMP and configuration (step by step) (2 Replies)
Discussion started by: udtyuvaraj
2 Replies
6. AIX
Hi,
Can we use network for heartbeat, I mean can we use different network card for heartbeat. (6 Replies)
Discussion started by: vjm
6 Replies
7. AIX
Hi All,
My company is going to upgrade the db2 on the one node hacmp, I think there's one backup.
After the upgrade of the db2. Do I need to restart cluster and server? I mean, do a graceful shutdown of the cluster, reboot the server and do a cluster start. Is that it? Do I need to reboot... (1 Reply)
Discussion started by: itik
1 Replies
8. AIX
(0 Replies)
Discussion started by: mhenryj
0 Replies
LEARN ABOUT SUSE
innupgrade
INNUPGRADE(8) InterNetNews Documentation INNUPGRADE(8)
NAME
innupgrade - Upgrade INN configuration files
SYNOPSIS
innupgrade directory
innupgrade [-t type] -f file
DESCRIPTION
innupgrade is intended to be run during a major upgrade of INN to fix the configuration files with any required changes. If given a
directory, it will scan that directory for any files that it has updates defined for, try to perform those updates, and replace the files
with updated versions if applying the updates resulted in any changes. The old versions of the files will be saved with a ".OLD"
extension.
If the -f flag is used, only that file will be updated. If the file name doesn't match the standard file name of an INN configuration
file, the optional -t flag may be given to specify the type. See "EXAMPLES" for an example of this.
Currently, innupgrade knows how to apply the following updates:
inn.conf
o Quote values with whitespace and comment out keys with no values, required for the change in configuration parsers introduced in
INN 2.4. The new format is not backward compatible with the previous parser, since the previous parser will include the double-quotes
in the value of the parameter.
o Add the hismethod parameter if not found (introduced in INN 2.4, with the default value "hisv6") and rename nntpactsync to
incominglogfrequency (since INN 2.5).
o If the overview.fmt file exists, its content is merged in the extraoverviewadvertised and extraoverviewhidden parameters introduced in
INN 2.5. The file is then renamed to overview.fmt.OLD.
o If the sasl.conf file exists, its content is merged in the tlscapath, tlscafile, tlscertfile and tlskeyfile parameters introduced in
INN 2.5. The file is then renamed to sasl.conf.OLD.
newsfeeds
o Replace the use of startinnfeed with the appropriate direct invocation of innfeed or imapfeed.
A few obsolete programs or configuration files are renamed with a ".OLD" extension by innupgrade. Obsolete man pages are directly removed.
Normally, innupgrade should be run at least on the pathetc directory after any upgrade of INN other than a patch release (any upgrade that
changes the first or second version numbers). This may occur automatically during the upgrade process.
OPTIONS
-f file
Only act on file rather than working on an entire directory.
-t type
For a file specified with -f, parse it and upgrade it as if it were named type. Used for upgrading files with the same syntax as
normal INN configuration files but with different names. Only makes sense in combination with -f.
EXAMPLES
Upgrade any configuration files found in pathetc and append a ".OLD" extension to obsolete files in pathetc:
innupgrade <pathetc in inn.conf>
Upgrade only /news/etc/inn.conf:
innupgrade -f /news/etc/inn.conf
Upgrade a file named inn-special.conf that should have the same syntax as inn.conf:
innupgrade -t inn.conf -f inn-special.conf
Any upgrade rules that apply to inn.conf will be applied to the alternate file.
HISTORY
Written by Russ Allbery <rra@stanford.edu> for InterNetNews.
$Id: innupgrade.pod 8415 2009-04-12 20:19:35Z iulius $
INN 2.5.2 2009-05-21 INNUPGRADE(8)