Skip to main content

1E 8.1 (on-premises)

Verifying

Verify Patch Success installation

To run the following tests you need:

  1. Tachyon Server installed.

  2. The name and password for the server installation account, the account must also be enabled.

Ref

Test

Expected

Remediation

TCNI01

  • Logon to the Tachyon Server using the server installation account

  • Confirm 1E Tachyon Server is listed in Apps/Programs and Features

  • Confirm Tachyon's Windows services are running.

Programs and Features (appwiz.cpl) displays 1E Tachyon Server with correct version number.

If an MSP update has been installed, the Installed Updates displays 1E Tachyon Server Update (Qnnnnn).

The following Windows services exist and are running.

  • 1E Catalog Update Service (Automatic) (Service account)

  • 1E SLA Platform Engine (Automatic Delayed start) (Network Service)

  • 1E SLA Platform Integrate Agent (Automatic Delayed start) (Network Service)

  • 1E SLA Platform Integrate Manager (Automatic Delayed start) (Network Service)

  • 1E Tachyon Coordinator (Automatic Delayed start) (Network Service)

  • 1E Tachyon Switch Host(Automatic Delayed start) (Local System)

If you did not install Nomad, you may also have 1E ActiveEfficiency (Automatic) (Network Service) remaining after an upgrade.

If any of the services are not running, then check the corresponding log(s).

The Switch Host service will stop after several seconds if it is unable to start any Switches.

The ConsumerAPI log is not created until a user (the server installation account) successfully connects to the Tachyon Portal.

The BackgroundAPI log is not created until a 1E Client attempts to download content. The 1E-TachyonPlatform product pack can be used to trigger this.

TCNI02

  • Check the Tachyon Server logs.

Click here to expand...

The default location for all Tachyon logs is the folder %ALLUSERSPROFILE%\1E

Subsystem

Component

Tachyon Master

Tachyon Portal UI and applications (Tachyon)

1E\Tachyon\

Tachyon.Portal.log

Consumer API

1E\Tachyon\

Tachyon.ConsumerAPI.log

Coordinator service

1E\Tachyon\

Tachyon.Coordinator.log

Tachyon.Instrumentation.log

Experience web application

1E\Tachyon\

Tachyon.Experience.log

Catalog

Catalog UI (CatalogWeb - Admin sync)

1E\Catalog\

Catalog.Integration.UI.log

Catalog API

Catalog Update Service

1E\Catalog\

Catalog.UpdateService.log

Content Distribution

Content Distribution web application

1E\ContentDistribution

ContentDistribution.log

SLA

SLA/Platform APIs (Admin, Core External)

1E\Tachyon\

Tachyon.AdminAPI.log

SLA Platform UI (Platform)

1E\SLA Platform\

Web.log

SLA Engine

1E\SLA Platform\

Engine.log

SLA Integrate Services (Connector Manager)

1E\SLA Platform\

1E.SLAPlatformIntegrateAgent.log

1E.SLAPlatformIntegrateManager.log

1E.SLAConnector.<type>_sync.log

SLA Inventory

n/a

n/a

SLA Operations Provider (not currently used)

1E\Platform Consumer\

n/a

SLA databases (Data, Integrate, Shared)

n/a

n/a

BI

MDX API

SQL database

[SLA-BI].[BI].[Event Log]

Tachyon Response

Core

1E\Tachyon\

Tachyon.CoreAPI.log

Background Channel (Background)

1E\Tachyon\

Tachyon.BackgroundAPI.log

Switch(es) (also includes a single Switch Host service)

1E\Tachyon\

Tachyon.Switch.4000.SW1.log

Tachyon.Switch.Host.log

Please refer to Services and NTFS Security if changing the location of log files.

In this version of Tachyon Server, some installers do not support the LOGPATH property and the logs folder is not configurable during installation.

Each component has a configuration file in the Tachyon Server installation folder structure, which contains log configuration details. Defaults are:

  • Filepath %ALLUSERSPROFILE%\1E\<product>\ where product is Tachyon, SLA Platform, and Catalog

  • Filename as shown in the table above.

  • Maximum size 10MB (2MB for Switch logs).

  • 2 rollover files numbered 1 to 2 with the rollover number included as n.log (5 rollover files for Switch logs).

  • Date and timestamps are UTC to help troubleshooters synchronize logs on systems in different timezones.

Switch logs have the following names:

  • The first Switch installed will typically have a log filename Tachyon.Switch.4000.SW1.log (where 4000 is the port it is listening on and SW1 is the config name in the SwitchConfiguration table in the TachyonMaster database).

  • Other Switches on the same server will have different config names appended.

  • The log filename will be unique on a server, but there may be the same named log on a different server.

  • A Switch will continue to use the same log, unless the SwitchConfiguration table is modified so that a different ID is used.

  • If you see a Tachyon.Switch.log without a config name appended, this is a special case where a Switch cannot find its correct configuration, and has fallen back to using the template * row which has ID=1. In which case you will need to troubleshoot how that happened.

  • Rollover logs have numbers appended, for example Tachyon.Switch_A.1.log, up to a default maximum of 5.

Tachyon server components use the log4net RollingFileAppender class. Details can be found in http://logging.apache.org/log4net.

PSC01

  • Check the configuration of the Tachyon connector

In this section: