Инструкции оборудования hajdu

ТЕСТ 24 — ОЛИМПОКС

Тест 24 — Олимпокс, это каталог обучающих курсов, предназначенных для организации предэкзаменационной самоподготовки или предаттестационной подготовки с последующей проверкой собственных знаний, как у руководителей и специалистов организаций, так и у персонала организаций.

Для быстрого и успешного самообучения — самоподготовки, все обучающие курсы разбиты на разделы, которые находятся в свободном доступе на сайте «Тест 24.SU«. Каждый обучающий курс в своем составе содержит ссылки на учебно-методические материалы (нормативные правовые акты, нормативно-технические документы, справочные и учебные пособия и др.) по которым составлены вопросы Ростехнадзора из которых составлены билеты тестов Олимпокс.

Все тесты обучающего курса Олимпокс, представленные на сайте «Тест 24», разработаны по обучающим материалам 2016, 2017, 2020 и 2020 годов и могут реализовать потребности при подготовке к аттестации руководителей и специалистов по промышленной безопасности в Ростехнадзоре. Прохождение онлайн тестирования по системе Олимпокс проводится без предварительной регистрации пользователей на сайте «Тест 24» и не требует дополнительных настроек. Все представленные материалы и обучающие курсы не являются официальным источником и предназначены для ознакомления и личного использования в целях самоподготовки.

Each node on a separate machine

Each Jira node (two in this example) runs on its own machine (physical or virtual), with a third machine for the shared services. In production, the shared services will most likely run on separate machines from each other. 

Jira setup

1. On the third machine, set up a shared home directory that is writable by both servers.
2. Set up the two Jira servers on different machines. These servers should:
   • Have a  in the local Jira home directory (see example below).
   • Be configured to use the same context path.
   • Be configured to use the same database. The  files on each should probably be identical.
   • Have their Apache node name set, by appending the following setting to the same variable (replacing 

     -DjvmRoute=node1

      with the node name used in the Apache load balancer configuration):

3. Ensure the Base URL configured in Jira is the URL of the front end proxy / load balancer.

Example cluster.properties file

1
2
3
4

httpd configuration (no context path)

We need to configure  similarly to a standard reverse proxy, but with the addition of the  configuration.

To run Jira at , add a configuration block similar to this at the end of 

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

httpd configuration (with a context path)

Some slight changes to the above configuration are required if Jira is deployed under a context path. To run Jira at , add a configuration block similar to this at the end of 

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

High level guide

1. Install and configure the latest Jira as normal, ie. without the cluster-specific settings mentioned further below.
   1. Startup this instance and load it with your Jira test plan data.
   2. Shutdown this instance.

   The default HSQL database will not work with the Jira Cluster.

2. Install a second node without launching it yet.
3. Set the cluster settings on both instances as mentioned below:
   1. Point to the same database(the dbconfig.xml files on each should probably be identical) and an empty shared home.
   2. Create the cluster.properties file for each node
4. Copy the following directories from the local home of the first node to the shared home (some may be empty) :
   • data
   • plugins
   • logos
   • import
   • export
5. Start the already-configured instance.
6. Install your plugin and add the license if needed.
7. Start the second instance. It will attach itself to the DB, and then fill in its local home and attach itself to the shared home. It will also then copy across your plugin.

For the clustering general release we aim to have the ability to add/update a plugin on a live cluster. This is not available yet for plugins that require upgrade tasks.

Trouble shooting

To test if caches are being replicated correctly between the two nodes in the cluster.

1. 1. Log in to one node in the cluster. Going directly to the node is easiest, bypassing any load balancer.
   2. Go to Administration / Issue Types and edit the name of an issue type
   3. Log in to the other node(s) in the cluster
   4. Go to Administration / Issue Types and check that the edited name from step-b appears correctly.

If the new value is no seen on the other nodes then the cluster is not communicating properly.

• You may need to disable your firewall, or at least allow the ports configured above to pass through. Some systems, especially later versions of linux block these even on the internal localhost network.
• You need to ensure multicast is supported.  For Linux you may need to turn it on.  Multicast is often not enabled for the local host.

1
2
3
4
5
6
7
8
9
10

Each server needs to be able to resolve its own host name correctly. This is not as obvious as it seems and errors here can be difficult to detect

Some linux distributions will add entries to /etc/hosts such as

1
2

This may cause ehcache to announce itself to other nodes in the cluster as being located at 127.0.1.1. This is not helpful and will result in cache inconsistency across the cluster.  You can set the logging level to ehcache in log4j.properties to trace to try and diagnose this sort of error.

1

Try removing the line refering to 127.0.1.1 from /etc/hosts or specify the hostName property for the cacheManagerPeerListenerFactory in the cluster.properties

1

Список источников

• tests24.su
• developer.atlassian.com