Backendless Pro logging error - "xhr poll error"

Paulo_Mira · January 12, 2025, 9:40pm

Hi there.

I just managed to get backendless pro in my AWS instance.
However I can’t view the real-time logging - it gives me the error “xhr poll error”.
I saw in another ticket that it could be the rt server but I checked in Pro Manager and the process is running.
Can you please help me with this issue ?

Thanks,

Paulo

mark-piller · January 12, 2025, 9:53pm

Hi Paulo,

I am sorry you ran into this issue. Unfortunately we cannot provide free support for Backendless Pro. On order to get any support, you would need to purchase support subscription.

Regards,
Mark

Paulo_Mira · January 13, 2025, 11:26am

Hello Mark.

I’m sorry too…
I’m trying to install backendless in AWS and I ran into a few issues this one being the latest.
As you can imagine I can’t use backendless if I can’t see the logs and, unfortunately, we don’t have enough content now to be able to pay $7200.
We’re actually evaluating the platform with some small internal applications before we adopt it for our customer’s projects, when we would be able to pay this fee.
We currently have these internal apps in backendless cloud but we found that some limitations were too limiting and we wanted to try the backendless pro to see whether it was an option.
I hope you reconsider letting us try the platform, that on the other end, we like very much.

Best regards,

Paulo

mark-piller · January 13, 2025, 4:43pm

Hi Paulo,

The Cloud version is the best way to evaluate the platform. All the version’s limits can be easily extended through the marketplace.

As for Backendless Pro, unfortunately, we cannot provide both a free product and free support. That option will quickly run us down into the ground.

Regards,
Mark

Paulo_Mira · May 20, 2025, 11:31am

Hi there.
We now have bought support and I would like to reactivate this issue.
Can someone help me with setting up the logs?
Now I’ve noticed that it just gives me the message timeout after a few seconds as per image attached.
Thanks very much,
Paulo

Dima · May 20, 2025, 11:43am

Hello @Paulo_Mira

I will check it now.

Sergey_Androsov · May 20, 2025, 1:15pm

Hi @Paulo_Mira

Please provide the logs for bl-web-console and bl-rt-server.
You can find them by going to the Pro Manager, selecting the deployment for bl-web-console/bl-rt-server, and navigating to the Logs tab.

Alternatively, you can also find the logs in the following directories:

/home/bl-pro-manager/pro-manager/k8s-mount/logs/bl-rt-server
/home/bl-pro-manager/pro-manager/k8s-mount/logs/bl-web-console

Regards,
Sergey

Paulo_Mira · May 20, 2025, 5:24pm

Hi Sergey.

Please receive attached a zip file with the requested log files.

logs.zip (143.7 KB)
Thanks for your help,

Paulo

Paulo_Mira · May 20, 2025, 5:44pm

By the way, Sergey, in pro manager I couldn’t get the logs - it was empty.
In case this helps…

vladimir-upirov · May 21, 2025, 10:52am

Hi @Paulo_Mira

The Pro manager uses RT for getting logs and since it does work you can not see logs there.

First of all, let’s check the connection to the RTServer from outside, for that follow these steps:

in the Postman, create a new Socket.IO request and in the settings select v2.0

2025-05-21 13-41-391774×892 120 KB
then specify your connection URL:

ws://localhost:5003/YOUR_APP_ID?apiKey=YOUR_API_KEY

instead of localhost:5003 use your public host for RT, please let me know if you do not know where to find it
replace with your AppId and APIKey

click to the Connect button, you should see it’s connected or not

2025-05-21 13-43-561726×1320 178 KB
then need to check logs of the RT Server, here is my logs from local installation:

2025-05-21T10:48:46.598Z e[90minfoe[39m: [Global] logger was created
2025-05-21T10:48:46.599Z e[90minfoe[39m: [EventsRedis] logger was created
2025-05-21T10:48:46.642Z e[34mdebuge[39m: [EventsRedis] [events:subscriber] subscribe on [CHANNEL - backendless-events::USER_PERMISSION_CHANGED_EVENT]
2025-05-21T10:48:46.643Z e[34mdebuge[39m: [EventsRedis] [events:subscriber] subscribe on [CHANNEL - backendless-events::USER_PERMISSION_REMOVED_EVENT]
2025-05-21T10:48:46.643Z e[34mdebuge[39m: [EventsRedis] [events:subscriber] subscribe on [CHANNEL - backendless-events::ROLE_PERMISSION_CHANGED_EVENT]
2025-05-21T10:48:46.643Z e[34mdebuge[39m: [EventsRedis] [events:subscriber] subscribe on [CHANNEL - backendless-events::ROLE_PERMISSION_REMOVED_EVENT]
2025-05-21T10:48:46.643Z e[34mdebuge[39m: [EventsRedis] [events:subscriber] subscribe on [CHANNEL - backendless-events::GLOBAL_ROLE_PERMISSION_CHANGED_EVENT]
2025-05-21T10:48:46.643Z e[34mdebuge[39m: [EventsRedis] [events:subscriber] subscribe on [CHANNEL - backendless-events::BILLING_PLAN_UPGRADE]
2025-05-21T10:48:46.643Z e[34mdebuge[39m: [EventsRedis] [events:subscriber] subscribe on [CHANNEL - backendless-events::FUNCTION_PACK_INSTALL]
2025-05-21T10:48:46.643Z e[34mdebuge[39m: [EventsRedis] [events:subscriber] subscribe on [CHANNEL - backendless-events::API_CALLS_BLOCKED]
2025-05-21T10:48:46.643Z e[34mdebuge[39m: [EventsRedis] [events:subscriber] subscribe on [CHANNEL - backendless-events::USER_LOGGED_OUT]
2025-05-21T10:48:46.643Z e[34mdebuge[39m: [EventsRedis] [events:subscriber] subscribe on [CHANNEL - backendless-events::BUSINESS_LOGIC_CHANGED]
2025-05-21T10:48:46.599Z e[90minfoe[39m: [AnalyticsRedis] logger was created
2025-05-21T10:48:46.600Z e[90minfoe[39m: [RTRedis] logger was created
2025-05-21T10:48:46.738Z e[90minfoe[39m: [RTRedis] add the server into list of RT servers
2025-05-21T10:48:46.601Z e[90minfoe[39m: [UserSessionRedis] logger was created
2025-05-21T10:48:46.601Z e[90minfoe[39m: [Server] logger was created
2025-05-21T10:48:46.737Z e[90minfoe[39m: [Server] The server is listening on 0.0.0.0:5003
2025-05-21T10:48:46.738Z e[90minfoe[39m: [Server] Management Server is listening on http://0.0.0.0:2992
2025-05-21T10:48:46.603Z e[90minfoe[39m: [Request] logger was created
2025-05-21T10:48:46.603Z e[90minfoe[39m: [Notifications] logger was created
2025-05-21T10:48:46.604Z e[90minfoe[39m: [Status] logger was created
2025-05-21T10:48:46.742Z e[90minfoe[39m: [AnalyticsRedis] new client [analytics:subscriber] was connected in 98ms
2025-05-21T10:48:46.742Z e[90minfoe[39m: [EventsRedis] new client [events] was connected in 100ms
2025-05-21T10:48:46.742Z e[90minfoe[39m: [RTRedis] new client [rt:subscriber] was connected in 98ms
2025-05-21T10:48:46.742Z e[90minfoe[39m: [UserSessionRedis] new client [user-session:subscriber] was connected in 99ms
2025-05-21T10:48:46.742Z e[90minfoe[39m: [AnalyticsRedis] new client [analytics] was connected in 98ms
2025-05-21T10:48:46.743Z e[90minfoe[39m: [EventsRedis] new client [events:subscriber] was connected in 101ms
2025-05-21T10:48:46.742Z e[90minfoe[39m: [RTRedis] new client [rt] was connected in 98ms
2025-05-21T10:48:46.743Z e[90minfoe[39m: [UserSessionRedis] new client [user-session] was connected in 100ms
2025-05-21T10:48:46.743Z e[90minfoe[39m: [RTRedis] remove old server registration
2025-05-21T10:48:46.744Z e[90minfoe[39m: [RTRedis] add a new server registration
2025-05-21T10:48:46.744Z e[34mdebuge[39m: [RTRedis] renew the service registration [D0A1CD38-F4DA-D3BD-D158-8BACC1DC5695] in tne redis, expired in 20 seconds
2025-05-21T10:48:46.746Z e[33mwarne[39m: [Status] The Service Status can not be running because it is not configured {
  serviceName: 'rtServer',
  hostname: '',
  nodeName: undefined,
  internalHost: 'localhost',
  internalPort: 2992
}
2025-05-21T10:48:50.741Z e[34mdebuge[39m: [EventsRedis] add App - 48EDB07C-3089-48FE-BEFD-16D806CC73AA Event - backendless-events::USER_PERMISSION_CHANGED_EVENT Listener
2025-05-21T10:48:50.745Z e[34mdebuge[39m: [Request] Request POST: http://localhost:9000/48EDB07C-3089-48FE-BEFD-16D806CC73AA/internal/servercode/events/RT_beforeClientConnected { connectionId: 'm8JYNvNgLkAHw_7pAAAA', clientId: undefined }
2025-05-21T10:48:50.741Z e[34mdebuge[39m: [EventsRedis] add App - 48EDB07C-3089-48FE-BEFD-16D806CC73AA Event - backendless-events::USER_PERMISSION_REMOVED_EVENT Listener
2025-05-21T10:48:50.741Z e[34mdebuge[39m: [EventsRedis] add App - 48EDB07C-3089-48FE-BEFD-16D806CC73AA Event - backendless-events::ROLE_PERMISSION_CHANGED_EVENT Listener
2025-05-21T10:48:50.741Z e[34mdebuge[39m: [EventsRedis] add App - 48EDB07C-3089-48FE-BEFD-16D806CC73AA Event - backendless-events::ROLE_PERMISSION_REMOVED_EVENT Listener
2025-05-21T10:48:50.741Z e[34mdebuge[39m: [EventsRedis] add App - 48EDB07C-3089-48FE-BEFD-16D806CC73AA Event - backendless-events::GLOBAL_ROLE_PERMISSION_CHANGED_EVENT Listener
2025-05-21T10:48:50.742Z e[34mdebuge[39m: [EventsRedis] add App - 48EDB07C-3089-48FE-BEFD-16D806CC73AA Event - backendless-events::BUSINESS_LOGIC_CHANGED Listener
2025-05-21T10:48:50.738Z e[90minfoe[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA] logger was created
2025-05-21T10:48:50.738Z e[90minfoe[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA] App Socket has been created.
2025-05-21T10:48:50.743Z e[90minfoe[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA] App Socket is initialized
2025-05-21T10:48:50.740Z e[90minfoe[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - PERMISSIONS_EVENTS] logger was created
2025-05-21T10:48:50.741Z e[34mdebuge[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - PERMISSIONS_EVENTS] create MESSAGING Change Emitter
2025-05-21T10:48:50.741Z e[34mdebuge[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - PERMISSIONS_EVENTS] create PERSISTENCE Change Emitter
2025-05-21T10:48:50.741Z e[34mdebuge[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - PERMISSIONS_EVENTS] add app event - backendless-events::USER_PERMISSION_CHANGED_EVENT listener
2025-05-21T10:48:50.741Z e[34mdebuge[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - PERMISSIONS_EVENTS] add app event - backendless-events::USER_PERMISSION_REMOVED_EVENT listener
2025-05-21T10:48:50.741Z e[34mdebuge[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - PERMISSIONS_EVENTS] add app event - backendless-events::ROLE_PERMISSION_CHANGED_EVENT listener
2025-05-21T10:48:50.741Z e[34mdebuge[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - PERMISSIONS_EVENTS] add app event - backendless-events::ROLE_PERMISSION_REMOVED_EVENT listener
2025-05-21T10:48:50.741Z e[34mdebuge[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - PERMISSIONS_EVENTS] add app event - backendless-events::GLOBAL_ROLE_PERMISSION_CHANGED_EVENT listener
2025-05-21T10:48:50.739Z e[90minfoe[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - PERMISSIONS] logger was created
2025-05-21T10:48:50.742Z e[90minfoe[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - PERMISSIONS] initialized
2025-05-21T10:48:50.742Z e[90minfoe[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - EVENT HANDLERS] logger was created
2025-05-21T10:48:50.745Z e[34mdebuge[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - EVENT HANDLERS] [Request] Event: [beforeClientConnected], requestData: {"connectionId":"m8JYNvNgLkAHw_7pAAAA"}
2025-05-21T10:48:50.743Z e[90minfoe[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - API CONNECTION - m8JYNvNgLkAHw_7pAAAA] logger was created
2025-05-21T10:48:50.744Z e[90minfoe[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - API CONNECTION - m8JYNvNgLkAHw_7pAAAA - TRANSFER] logger was created
2025-05-21T10:48:50.745Z e[90minfoe[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - API CONNECTION - m8JYNvNgLkAHw_7pAAAA - PUBLICATION] logger was created
2025-05-21T10:48:50.744Z e[90minfoe[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - API CONNECTION - m8JYNvNgLkAHw_7pAAAA - METHOD] logger was created
2025-05-21T10:48:50.863Z e[34mdebuge[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - EVENT HANDLERS] Event: [beforeClientConnected] is not exist in BL, remember it.
2025-05-21T10:48:50.863Z e[34mdebuge[39m: [Request] Request POST: http://localhost:9000/48EDB07C-3089-48FE-BEFD-16D806CC73AA/internal/servercode/events/RT_afterClientConnected { connectionId: 'm8JYNvNgLkAHw_7pAAAA', clientId: undefined }
2025-05-21T10:48:50.867Z e[90minfoe[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - API CONNECTION - m8JYNvNgLkAHw_7pAAAA] Client has been connected: {"userId":null,"userToken":null}
2025-05-21T10:48:50.867Z e[34mdebuge[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA] connected sockets: 1
2025-05-21T10:48:50.863Z e[34mdebuge[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - EVENT HANDLERS] [Request] Event: [afterClientConnected], requestData: {"connectionId":"m8JYNvNgLkAHw_7pAAAA"}
2025-05-21T10:48:50.903Z e[34mdebuge[39m: [APP] - [48EDB07C-3089-48FE-BEFD-16D806CC73AA - EVENT HANDLERS] Event: [afterClientConnected] is not exist in BL, remember it.

in case you do not see such logs please check the server logs configs in your Consul,
by default the log level is info but you can change it in the Consul to “debug” by the following path config/rt-server/loggers/levels/default and it requires restarting the RTServer service

Regards,
Vlad

Paulo_Mira · May 21, 2025, 12:12pm

Hi Vladimir.
After connect in Postman it takes a few seconds and then says disconnected (image included).
Also in consul there are no keys for config/rt-server/loggers/levels.
It has only config/rt-server/loggers/file/…
Thanks,
Paulo

vladimir-upirov · May 21, 2025, 12:14pm

I assume you need to use 5000 port instead of 5003

Paulo_Mira · May 21, 2025, 12:23pm

Using port 5000 gives the same result as per image.
Could the missing keys in consul be the problem?

vladimir-upirov · May 21, 2025, 12:49pm

try to run

http://API_HOST:API_PORT/APP_ID/API_KEY/info

it should respond with information about api hosts including rtURL

Paulo_Mira · May 21, 2025, 2:10pm

Here is the result in the image below.
I can see that the rtURL is “https://bec.swstudio.es:32700”.
However, bec.swstudio.es is a subdomain configured in AWS pointing to loadBalancer/targetGroup which is pointing to port 32400.
I’ve checked in ProManager and under Domains/General/Real-Time is has as host bec.swstudio.es and port 32700.
I think this may be the problem.
Shall I create a new subdomain for 32700 and set it in ProManager ?
Thanks again,
Paulo

vladimir-upirov · May 21, 2025, 2:26pm

just to clarify

the url https://bec.swstudio.es:32700 points to port 32400 in your internal network, right?
is your RTServer running on the 32400 port?

Paulo_Mira · May 21, 2025, 2:43pm

bec.swstudio.es is a subdomain that points directly to port 32400 in my internal network through loadbalancer/targetgroup (points to console); putting bec.swstudio.es:32700 probably doesn’t work because of it.
In ProManager RTServer is set to port 32700
So, I think this is the problem as it would sort of be host:32400:3270

mark-piller · May 21, 2025, 2:48pm

It is important for you to understand that RT server and the API server are two separate things.

The API server processes requests via HTTPS.

RT server provides real-time functionality via web sockets.

Both RT server and APi server need their own port.

So, what is your configuration like now? What ports are being used by console? API server? RT server?

Paulo_Mira · May 21, 2025, 3:23pm

Hello Mark, Vladimir.
Definetly I’m not explaining myself.
I fully understand what you mentioned.
What I meant was that I had a problem of configuration for the rtserver - going to the wrong port.
Now, I’ve corrected and tested and it no longer gives me timeout.
However it is back to the initial error (“xhr poll error”) as per the image below.
Thanks both for your help,
Paulo

mark-piller · May 21, 2025, 4:00pm

Hi Paulo,

Could you please share the configuration details? What does the RT server configuration look like now?

Regards,
Mark