login about faq

What is wrong with the install. I get the following errors:
tectia-server-<version>-aix-5-6-powerpc-comm.tar ---- went fine... tectia-server-<version>-aix-5-6-powerpc-upgrd-eval.tar ---- went fine...

$ uncompress ssh-tectia-common-<version>-aix-5-6-powerpc.bff.Z --- went fine $ uncompress ssh-tectia-server-<version>-aix-5-6-powerpc.bff.Z --- went fine

installp -d ssh-tectia-common-<version>-aix-5-6-powerpc.bff SSHTectia.Common --- Bummer..see errors below.

installp -d ssh-tectia-server-<version>-aix-5-6-powerpc.bff SSHTectia.Server --- Bummer...

Any suggestions?????

root@unixtest2:/workarea/tectia-server- .1.118-aix-5-6-powerpc.bff SSHTectia.common < installp: No action was indicated. The -a (apply) flag is being assumed. +-----------------------------------------------------------------------------+ Pre-installation Verification... +-----------------------------------------------------------------------------+ Verifying selections...done Verifying requisites...done Results...


Filesets listed in this section failed pre-installation verification and will not be installed.

Missing Filesets

The following filesets could not be found on the installation media. If you feel these filesets really are on the media, check for typographical errors in the name specified or, if installing from directory, check for discrepancies between the Table of Contents file (.toc) and the images that reside in the directory.


<< End of Failure Section >>

+-----------------------------------------------------------------------------+ BUILDDATE Verification ... +-----------------------------------------------------------------------------+ Verifying build dates...done FILESET STATISTICS

1  Selected to be installed, of which:
    1  FAILED pre-installation verification

0  Total to be installed

asked Sep 20 '12 at 23:24

ronjag's gravatar image


edited Sep 20 '12 at 23:27

Hello, when installing Tectia Client/Server packages for Linux/Unix operating systems, you MUST install the COMMON package first, before the Client and Server packages.

For instance like this:

  1. ssh-tectia-common
  2. ssh-tectia-client
  3. ssh-tectia-server

You can then also change the port that Tectia Server is listening by modifying Tectia Server's XML configuration file:

  • /etc/ssh2/ssh-server-config.xml

Regs, SamiM

ps. after installation, you can check Tectia Client's/Server's status information by using our CLI control tools:


Each Tectia Client/ConnectSecure user will have his/her own personal Tectia Client daemon. Users can use CLI control tool to query information and to control the client daemon. Users can start the permanent daemon process by running command: ssh-broker-g3 (by default the daemon is started run-by-need basis)

-bash-3.1$ ssh-broker-ctl
Usage: ssh-broker-ctl command [options]
Generic options:
    -q, --quiet            Define that little or no output is to be
    -s, --short            Shorter, more machine readable output.
    -v, --verbose          Display more information, if available.
    -w, --wide             Do not truncate long output lines.
    -e, --charset=CS       Defines the output character set. See -e help for
                           a list.
        --time-format=FMT  Time format to be used in the output. The default
                           depends on system locale settings.
    -a, --broker-address=ADDR
                           Connect to separate Connection Broker process
                           using the given address.
    -h, --help             Display a context-sensitive help text.
    -D, --debug=STR        Define the debug level.
    -V, --version          Display the version string.

   Available commands:
   status                 Display status of the running Connection Broker.
   list-connections       List of open connections.
   list-channels          List of open connection channels.
   list-keys              List of user private keys.
   list-clients           List of connected client processes.
   list-profiles          List of connection profiles.
   list-tunnel-listeners  List of open tunnel listeners (port forwards).
   connection-status      Display a detailed connection status.
   close-connection       Close a connection.
   close-channel          Close a channel.
   disconnect-client      Disconnect a Connection Broker client.
   open-tunnel-listener   Open a new tunnel listener.
   close-tunnel-listener  Close tunnel listener.
   view-key               Display detailed key information.
   add-key                Add a new private key.
   key-passphrase         Prompt the user private key passphrase.
   add-provider           Add a key provider to the Connection Broker.
   list-providers         List key providers in the Connection Broker.
   remove-provider        Remove a key provider from Connection Broker.
   key-upload             Upload a public key to a remote server.
   keylog                 View and operate on the key upload log.
   pkcs10-sign            Generate a PKCS#10 certificate signing request.
   generate-key           Generate a new private key.
   probe-key              Fetch a SecSh server host key.
   remove-key             Remove a private key.
   auth-handler           Default authentication handler.
   config-value           Display configuration values.
   validate-certificate   Validate a X.509 certificate.
   add-certificate        Add a X.509 certificate to the cache.
   add-crl                Add a X.509 CRL to the cache.
   debug                  Define the Connection Broker debug settings.
   start-gui              Start the Connection Broker GUI.
   connector              Enable the Connector in the Connection Broker.
   reload                 Reload the Connection Broker configuration file.
   start                  Start a new Connection Broker.
   stop                   Stop the Connection Broker.

   Additional per command usage is available with 'ssh-broker-ctl cmd --help'.



[root@linuxserver ~]# ssh-server-ctl
Usage: ssh-server-ctl [OPTION]... command
Mandatory arguments to long options are mandatory for short options too.

Options common for all commands:

--debug=LEVEL, -D Set debug level string to LEVEL.
--help, -h        Display this help and exit.
--listen=PORT, -l
--port=PORT, -p   Port where ssh-server-g3 resides.
--server-address  The path to the server control socket.
--current, -C     Connect to current server.
--old, -O         Connect to backup listener.
--pid=PID, -P     Process id of the server.
--quiet, -q       Print little or no output, depending on command.
--short, -s       Shorter more machine readable output.
--verbose, -v     Print more information if available.

Supported commands are:

 add-servant          Instruct the server to start (/a) servant(s/).
 continue             Continue paused service.
 help                 Give help.
 pause                Pause the service.
 pid                  Print the server process ID.
 reload               Instruct the server to reload configuration.
 start                Start the server.
 status               Print server status.
 stop                 Stop the server.
 stop-servant         Instruct the server to stop the servant(s) specified.

 Additional per command usage is available with 'ssh-server-ctl help cmd' or
 'ssh-server-ctl cmd --help'.

 [root@linuxserver ~]#

answered Oct 04 '12 at 04:50

Sami%20Marttinen's gravatar image

Sami Marttinen ♦

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Sep 20 '12 at 23:24

Seen: 6,123 times

Last updated: Oct 04 '12 at 04:50

All user contributed content licensed under the cc-by-sa license.
Powered by OSQA.