Read-Only-Mode Issue?

Administration
1

Hi folks,

if primary cfg_dbserver terminates CME stays in Read-Only-Mode until the primary is running again AND in primary mode, as well, although the backup of cfg_dbserver is up and running in primary mode. I would have assumed that the backup in primary mode should just do the work of the original primary, so that a Read-Only-Mode therefore should not have to be activated.

Is this a volitional behaviour?

Best wishes

Phil

2

look likes this issue :
"When using redundant Configuration Servers, if the Configuration DB Server terminates while the backup Configuration Server is terminated, and is restarted after the backup Configuration Server is restarted, the primary Configuration Server remains in READ-ONLY mode. Do not attempt to:

  • Start both primary and backup Configuration Servers simultaneously.
  • Start the backup Configuration Server while the primary Configuration Server is in READ-ONLY mode because of its lost connection with the database.
    Workaround: Wait until one of the Configuration Servers is fully initialized, or its connection with the database is restored and it is no longer in READ-ONLY mode."

WBR Thaler

3

Thanks Timur,

unfortunately it’s not this issue, because both primary and backup Configuration were up and running, when the primary cfg_dbserver was terminated whereby Read-Only-Mode was activated.

Im hoping for further ideas.

Cheers

Phil

1 Like
4

I had similar problems with 7.5/early 7.6 applications. But after upgrades it was resolved.

What versions are you using?

1 Like
5

im just about to update confserv from 7.6.000.18 to the latest version 7.6.000.57

1 Like
6

OK, so the version of configserver should be OK :slight_smile:

Have you configured configserver correctly in confserv.cfg file so that it knows about the backup dbserver?

Please post you config here.

1 Like
7

Good point! I think here could be the problem. Here’s the config:

[confserv]
port=2020
management-port=2021
server=cfg_dbserver
encryption=false
encoding=utf-8
force-reconnect-reload=true

[history-log]
all=histlog
expiration=30
client-expiration=1
max-records=1000
active=true
failsafe-store-processing=true

[log]
verbose=all
standard=network
all=D:\var\log\genesys\confserv\confserv
buffering=false
expire=10
segment=50000
time_format=ISO8601

[hca]
schema = none

[soap]
port=2022
debug=true
client_lifespan=600

[cfg_dbserver]
host=test0
port=4040
dbengine=oracle
dbserver=testawd
username=genconfig
password=*****
server=cfg_dbserver_HA
reconnect-timeout=10
response-timeout=600

[dbserver_HA]
host=test1
port=4040
dbengine=oracle
dbserver=testawd
username=genconfig
password=******
server=dbserver
reconnect-timeout=10
response-timeout=60

8

Hi phil,

Database servers are not configured properly in your confserv.cfg/config file and this is cause (with high probability) of your “read-only” issue. Please change following options:

[cfg_dbserver]
server=dbserver_HA

[dbserver_HA]
server=cfg_dbserver

R.

9

i think, the section [dbserver_HA] should be named [cfg_dbserver_HA] as specified in section
[cfg_dbserver]->server=cfg_dbserver_HA

10

excactly, thanks a lot. i just figured that out myself. are the names fixed values or can i chose them on my own as long as they match?

the lab environment is a mess, i try to clear. the wrong config must persist since over a year ::slight_smile:

11

seem like the names have to be the original application names of the dbservers. everthing’s fine now.

Cheers People

1 Like