Full-text search no function after update to 12.1.0.1760

Do you want to: Suggest a feature / Report a bug / Ask a how-to question
For feature suggestions, describe the result you would like to achieve in detail:
For bug reports, provide the steps to reproduce and if possible a minimal demo of the problem:
Community Server/Control Panel version: 12.1.0.1760
Type of installation of Workspace (docker, deb/rpm, exe) docker
OS: ubuntu 20.00
Browser version: Edge version 111.0.1661.44

Go to the control panel, pick up the Full-text search from menu then shows “error while fetching data” please wait…

Hello @kmkevin
I have checked my test Workspace portal (docker, all portal components have the latest versions), all things are OK. Let’s focus on your installation. Please point me to the guide which you used for installation and update process. Also please go to the host and run docker ps command, please show us the result.
After that please reproduce the issue > make screenshot of the error (entire page) > provide us with whole Community server and Control Panel logs folders. They are located here:
/app/onlyoffice/CommunityServer/logs/
/app/onlyoffice/ControlPanel/logs

Alex, @Alexandre

I use the control panel upgrade menu to upgrade the community server and control panel.

Here is the docker ps result:
ab98ea6bfde9 onlyoffice/communityserver:12.1.0.1760 “/app/run-community-…” 38 hours ago Up 26 hours 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 3306/tcp, 5280/tcp, 9865-9866/tcp, 9871/tcp, 9882/tcp, 0.0.0.0:5222->5222/tcp, :::5222->5222/tcp, 9888/tcp onlyoffice-community-server
42df0b8f9df2 onlyoffice/elasticsearch:7.16.3 “/bin/tini – /usr/l…” 38 hours ago Up 26 hours 9200/tcp, 9300/tcp onlyoffice-elasticsearch
c0b1c7f6fe1e onlyoffice/controlpanel:3.1.1.467 “/var/www/onlyoffice…” 38 hours ago Up 26 hours 80/tcp, 443/tcp onlyoffice-control-panel
e5919a7bd8e3 onlyoffice/documentserver:7.1.1.23 “/app/ds/run-documen…” 9 months ago Up 26 hours 80/tcp, 443/tcp onlyoffice-document-server
62b0c9542fee mysql:8.0 “docker-entrypoint.s…” 23 months ago Up 26 hours 0.0.0.0:3306->3306/tcp, :::3306->3306/tcp, 33060/tcp onlyoffice-mysql-server

======================================
here is the screen shoot error page.

I check the log folders, and that’s quite big, as I used them for many years, if you need a particular date log? like the date, I process the upgrade?

Pls advise how can I send the logs to you? by email?

Thanks

I believe we have to take a closer look at entire folders (Control Panel\Community server - all logs). I’ve increased your forum level, so you can contact me via PM (private message) now. Please place logs to any external storage and provide us with download link.
Also please reproduce the issue one more time and check out browser console (F12 in Google Chrome) > make screenshots of any error entries in ‘Console’ and ‘Network’ tabs.

Hello @Alexandre and @kmkevin

I have the same exact issue, it was reported earlier today from one of my users (a simple resaerch was taking way too long) .
I updated Control Panel to 3.1.1.467 and Community server to 12.1.0.1760 two days ago (28th march) however, Document server still on 7.0.1.37, mail Server uninstalled.

So at first glance, when researching for a Folder or a Document it is either not working or taking way too long and we get a timeout.
A Javascript Error is prompted :

image
image

I was wandering if an indexation (dunno if this is the english correct term) was occuring or was faulty, and took a closer look at the control panel to see if full-text search was activated.
Then i got the same error as @kmkevin

On elasticsearch’s logs (elasticsearch_deprecation.log to be precise), the last entry is this
"The default behavior of disabling security on basic licenses is deprecated. In a later version of Elasticsearch, the value of [xpack.security.enabled] will default to “true” , regardless of the license level. See Set up minimal security for Elasticsearch | Elasticsearch Guide [7.16] | Elastic to enable security, or explicitly disable security by setting [xpack.security.enabled] to false in elasticsearch.yml
"
by the way date/time in this log is exactly when the server was restarded due updates two days ago.

In elasticsearch.log , a huge list of errors " almost every type like this pattern : [o.e.d.PeerFinder ] [id(will provide in pm)] address [127.0.0.1:9301], node [null], requesting [false] connection failed: [][127.0.0.1:9301] connect_exception: Connection refused: /127.0.0.1:9301: Connection refused

Trying to connect from port 9301 to 9305 with no results.

I hope we can fix this and thoses additionnal informations help you.

Take Care :slight_smile:

Hello @GabrielHuyard
I believe we need to take a look at your Community server and Control Panel logs. Please provide us with them.
By the way, I’ve noticed that you have commercial license. It’s better to contact us via Zendesk to get prompt replies.