Readonlyrest 7.17 for Kibana

Hello,

I want to download kibana ROR plugin version 7.17.17 but latest available is 7.17.16, where i can download 7.17.17? My kibana wont start with 7.5.2 and 7.17.16 is not working.

Plugin installation was unsuccessful due to error “Plugin readonlyrestkbn [7.17.16] is incompatible with Kibana [7.17.17]”

We will release it soon, 1-2 days.

1 Like

it’s ready to be downloaded!

TY Guys i will try it. Also i want to ask if ROR for ES 8.0.0 will be available soon? i want to upgrade from 7.17.17 to 8.0.0 or can i go directly to 8.0.1 ? Because there is ROR plugin 8.0.0 for kibana and 8.0.1 for ES.

Also i Tried to upgrade Kibana to 7.17.17 but i wont come up.
Do you know what this mean Feb 01 15:00:55 testweb01 kibana[10165]: FATAL TypeError: Cannot read properties of undefined (reading ‘readonlyrest_kbn’) ?
Also my ES are already on 7.17.17 with 7.17.17 ror plugin without problem.

Feb 01 15:00:42 testweb01 systemd[1]: Started Kibana.
– Subject: Unit kibana.service has finished start-up
– Defined-By: systemd
– Support: Debian -- User Support

– Unit kibana.service has finished starting up.

– The start-up result is done.
Feb 01 15:00:42 testweb01 kibana[10165]: Kibana is currently running with legacy OpenSSL providers enabled! For details and instructions on how to disable see Use Kibana in a production environment | Kibana Guide [7.17] | Elastic
Feb 01 15:00:52 testweb01 systemd-timesyncd[317]: Timed out waiting for reply from 92.240.244.202:123 (1.debian.pool.ntp.org).
Feb 01 15:00:55 testweb01 kibana[10165]: FATAL TypeError: Cannot read properties of undefined (reading ‘readonlyrest_kbn’)
Feb 01 15:00:55 testweb01 systemd[1]: kibana.service: Main process exited, code=exited, status=1/FAILURE
Feb 01 15:00:55 testweb01 systemd[1]: kibana.service: Unit entered failed state.
Feb 01 15:00:55 testweb01 systemd[1]: kibana.service: Failed with result ‘exit-code’.
Feb 01 15:00:58 testweb01 systemd[1]: kibana.service: Service hold-off time over, scheduling restart.
Feb 01 15:00:58 testweb01 systemd[1]: Stopped Kibana.
– Subject: Unit kibana.service has finished shutting down
– Defined-By: systemd
– Support: Debian -- User Support

– Unit kibana.service has finished shutting down.
Feb 01 15:00:58 testweb01 systemd[1]: kibana.service: Start request repeated too quickly.
Feb 01 15:00:58 testweb01 systemd[1]: Failed to start Kibana.
– Subject: Unit kibana.service has failed
– Defined-By: systemd
– Support: Debian -- User Support

– Unit kibana.service has failed.

– The result is failed.

oh, you are right. For some reason, ROR ES 8.0.0, 7.0.0, and 6.0.0 were not published. We will fix it.

@Dzuming could you please take a look at the problem with ROR KBN 7.17.17?

Hi @miroslavkardos

The error sounds like the Kibana patching process was not running or failed. Did you patch a Kibana after the ROR Kibana plugin upgrade? For Kibana - ReadonlyREST

Hi Mateusz,

Thanks for fixing it. Now I am able to download version 8.0.0 for both ES and Kibana.

1 Like

Hi Dawin,

Yes, indeed it was problem i did not patch Kibana. Now it is working with some warnings/errors in my configuration. I will try fix it and contact you later if problem persists.

Hello All,

Could you please help me fix this issue :

Feb 06 13:54:18 testweb01 kibana[10857]: [13:54:18:873] [error][plugins][ReadonlyREST][csrf] invalid csrf token
Feb 06 13:54:22 testweb01 kibana[10857]: [13:54:22:975] [error][plugins][ReadonlyREST][csrf] invalid csrf token
Feb 06 13:54:32 testweb01 kibana[10857]: [13:54:32:423] [error][plugins][ReadonlyREST][csrf] invalid csrf token
Feb 06 13:54:36 testweb01 kibana[10857]: [13:54:36:778] [error][plugins][ReadonlyREST][csrf] invalid csrf token
Feb 06 13:55:18 testweb01 kibana[10857]: [13:55:18:498] [error][plugins][ReadonlyREST][csrf] invalid csrf token
Feb 06 13:55:46 testweb01 kibana[10857]: [13:55:46:776] [error][plugins][ReadonlyREST][csrf] invalid csrf token
Feb 06 13:55:49 testweb01 kibana[10857]: [13:55:49:805] [error][plugins][ReadonlyREST][csrf] invalid csrf token

Hi,

Could you kindly provide me with the version of Kibana/ES and ROR, along with the kibana.yml configuration? We have identified an issue related to CSRF that occurs when the machine goes to sleep and wakes up after some time. Restarting the Kibana server is the only solution to this problem.

Hi Dawid,

I am using ROR readonlyrest_kbn_universal-1.55.0_es7.17.17.zip for Kibana and for ES readonlyrest-1.55.0_es7.17.17.zip , and ES,KIbana are on version 7.17.17 also i noticed another error :

– The start-up result is done.
Feb 06 08:50:47 myhostname kibana[10857]: Kibana is currently running with legacy OpenSSL providers enabled! For details and instructions on how to disable see Use Kibana in a production environment | Kibana Guide [7.17] | Elastic
Feb 06 08:50:52 myhostname kibana[10857]: [ROR] - serve.js - intercepting config
Feb 06 08:50:54 myhostname kibana[10857]: [08:50:54:082] [warning][plugins][ReadonlyREST][unsupportedFeaturesNotifier] logging.silent config parameter declared in kibana.yml is not supported yet. It will be ignored
Feb 06 08:50:54 myhostname kibana[10857]: [08:50:54:083] [warning][plugins][ReadonlyREST][unsupportedFeaturesNotifier] logging.quiet config parameter declared in kibana.yml is not supported yet. It will be ignored
Feb 06 08:50:54 myhostname kibana[10857]: [08:50:54:083] [warning][plugins][ReadonlyREST][unsupportedFeaturesNotifier] logging.verbose config parameter declared in kibana.yml is not supported yet. It will be ignored
Feb 06 08:50:54 myhostname kibana[10857]: [08:50:54:084] [warning][plugins][ReadonlyREST][kibanaYamlElasticsearchConfigParser] You configured more than one Elasticsearch nodes. If you also have multiple Kibana nodes in high availability (HA), you MUST add to kibana.yml ‘readonlyrest_kbn.store_sessions_in_index: true’ or it won’t work.
Feb 06 08:50:54 myhostname kibana[10857]: [08:50:54:212] [info][plugins][ReadonlyREST][LicenseService] Cannot get the encrypted activation key from Kibana… Status code: 404
Feb 06 08:50:54 myhostname kibana[10857]: [08:50:54:219] [info][plugins][ReadonlyREST][LicenseService] No Activation Key found. That’s OK. Defaulting to Free license.You can add your own Activation Key later.
Feb 06 08:50:54 myhostname kibana[10857]: [08:50:54:220] [info][plugins][ReadonlyREST][LicenseService] Visit ReadonlyREST Customer Portal at https://readonlyrest.com to get a trial Activation Key.
Feb 06 08:50:54 myhostname kibana[10857]: [08:50:54:221] [info][plugins][ReadonlyREST][LicenseService] Found ES cluster with UUID=kw565aPWRpytGsUpTHnuPw
Feb 06 08:51:07 myhostname kibana[10857]: [08:51:07:161] [info][plugins][ReadonlyREST][LicenseService] Cannot get the encrypted activation key from Kibana… Status code: 404
Feb 06 08:51:07 myhostname kibana[10857]: [08:51:07:166] [info][plugins][ReadonlyREST][LicenseService] No Activation Key found. That’s OK. Defaulting to Free license.You can add your own Activation Key later.
Feb 06 08:51:07 myhostname kibana[10857]: [08:51:07:166] [info][plugins][ReadonlyREST][LicenseService] Visit ReadonlyREST Customer Portal at https://readonlyrest.com to get a trial Activation Key.
Feb 06 08:51:07 myhostname kibana[10857]: [ROR] - serve.js - intercepting config
Feb 06 08:51:12 myhostname kibana[10857]: [ROR COMPAT] Verifying the presence of ROR hooks on Kibana files…
Feb 06 08:51:12 myhostname kibana[10857]: [ROR COMPAT] Found patch file /usr/share/kibana/plugins/readonlyrestkbn/kibana/patchers/patches_for_kbn_distribution/http_server.js.patch
Feb 06 08:51:12 myhostname kibana[10857]: Verifying patched state…
Feb 06 08:51:12 myhostname kibana[10857]: http_server.js patched state: VERIFIED.
Feb 06 08:51:12 myhostname kibana[10857]: [ROR COMPAT] Found patch file /usr/share/kibana/plugins/readonlyrestkbn/kibana/patchers/patches_for_kbn_distribution/serve.js.patch
Feb 06 08:51:12 myhostname kibana[10857]: Verifying patched state…
Feb 06 08:51:12 myhostname kibana[10857]: serve.js patched state: VERIFIED.
Feb 06 11:44:44 myhostname kibana[10857]: [11:44:44:856] [error][plugins][ReadonlyREST][lazyUtils] Caught an error in executeWithInterval FetchError: request to http://myhostname:9200/.readonlyrest_kbn_sessions/_search failed, reason: connect ECONNREFUSED myhostname:9200
Feb 06 11:44:44 myhostname kibana[10857]: at ClientRequest. (/usr/share/kibana/plugins/readonlyrestkbn/node_modules/node-fetch/lib/index.js:1491:11)
Feb 06 11:44:44 myhostname kibana[10857]: at ClientRequest.emit (node:events:514:28)
Feb 06 11:44:44 myhostname kibana[10857]: at Socket.socketErrorListener (node:_http_client:495:9)
Feb 06 11:44:44 myhostname kibana[10857]: at Socket.emit (node:events:514:28)
Feb 06 11:44:44 myhostname kibana[10857]: at emitErrorNT (node:internal/streams/destroy:151:8)
Feb 06 11:44:44 myhostname kibana[10857]: at emitErrorCloseNT (node:internal/streams/destroy:116:3)
Feb 06 11:44:44 myhostname kibana[10857]: at processTicksAndRejections (node:internal/process/task_queues:82:21) {
Feb 06 11:44:44 myhostname kibana[10857]: type: ‘system’,
Feb 06 11:44:44 myhostname kibana[10857]: errno: ‘ECONNREFUSED’,
Feb 06 11:44:44 myhostname kibana[10857]: code: ‘ECONNREFUSED’
Feb 06 11:44:44 myhostname kibana[10857]: }

Yeah and restart it helps…

Thank you for sharing the information. It appears to be an issue with Kibana 717.17 and node 20.x. With the previous Kibana version, the ES plugin response indicates that the ES plugin is not initialized yet. I will investigate further, but I assume that it does not prevent Kibana from starting, but rather causes a poor user experience.