Getting a few errors in browser dev tools after building my own REI3 instance

lsits

I just built my own REI3 instance without making any changes to the source files and now when i start the server and login, i get errors in the dev tools console and if i click on the home tab, the entire dashboard breaks.

Heres a screenshot of the errors in console.

Heres a screenshot of the issues after clicking on the home tab

Any help would be great. Thank you.

gabriel

Welcome to the forum 🙂

If you did not make any changes, I would suspect it would work correctly. But it does not hurt to try to completely clear the browser cache. Could you please try that and report back? (if you have not done so already)

One thing that looks odd is that the error log references a chrome extension. I´ve never seen that error before. Could you please check in another browser, if you get the same error?

lsits

gabriel Ive cleared the cache a million times. When I clear the cache pages seem to work, then the minute i click the home tab again, everything breaks. And it seems to be breaking the machine its hosted on as well as once i click on the home tab, im unable to run 'systemctl restart rei3' or 'systemctl status rei3'. Im forced to restart the VM and still the issue persists.

And the chrome extension error is unrelated to the rei3 issue. Thats just wappalyzer trying to see what libraries and frameworks are running on the site but its unable to. I disabled the extension and the chrome error disappeared but rei3 remained broken

But once i click the home tab, anything i click after that brings the 'length' error in the dev console.

And Im having the same issue in MS Edge.

gabriel

That sounds wild. Even if the frontend breaks, this should not have any relevance to the r3 service. If the service itself breaks, than the communication with the frontend breaks down and you will get errors.

Given that your r3 service cannot shut down, I assume that the issue is there. Could you please elaborate on:

Did you run a 'regular' (eg. released by us) version of r3 on the same VM without these issues?
Are you running r3 clustered or single node?
What are the specs of the VM? What is the OS? Version of the Postgres service?
Are there any errors/warnings in the r3 error log in the admin panel (if you can get to it)?
Are there any errors/warnings in the r3 service log (systemctl status rei3)?

lsits

gabriel

I was able to run a regular precompiled version of rei3 on the same vm without issue.
Its a single node.
VM specs are as follows:

No errors in the admin panel logs.

No errors in systemctl status rei3

Postgresql Version as follows:

gabriel

Not much to go on without errors/warnings. But specs seem fine and your environment should be fine as well.

I will take some time and build r3 myself with the steps in the Github. While everything should work, it is possible that a newer release broke something. I´ll let you know, if I find something.

lsits

gabriel

Also, Ive put back the precompiled version of R3 and it works fine but for some reason, when i click on tickets, it loads the tickets page but has the loading overlay in front of it and if i refresh the page, the front end can no longer connect to the backend. And again, its not throwing any errors in syslog or dev console

This is the latest 3.6.1 build by the way

EDIT

After letting the page load for awhile trying to reconnect to the backend, this error appears in dev console:

And as for that "chrome extension" error, it must be something with r3 because ive uninstalled all of my chrome extensions and that error still shows.

lsits

Ive even tried recompiling the r3 instance and that still didnt work. But if i throw the precompiled version of r3 back on the machine, everything seems to work fine.

gabriel

Do you have a proxy running in front of the r3 server? If so, it might timeout your clients. r3 requires a permanent websocket connection. This has nothing to do with the backend freezing up though.

lsits

gabriel

I have an opnsense router that forwards traffic on a static wan IP to the vm hosting rei3. So rei3 is sitting on its own static public IP. No proxies in place. Just the firewall.

lsits

Apparently, whenever i click on tickets, thats when everything breaks. Back end completely loses connection with front end and I cant run systemctl restart rei3.service. Itll shut it down but wont start it back up again. I have to ctrl-c the systemctl restart and run systemctl start rei3.service for it to work again. And again, once i click on tickets, its broken again and im forced to restart the service

No errors in systemctl status rei3. No errors in /var/log/syslog. No errors anywhere

lsits

@gabriel

This is what i get when i run systemctl stop rei3.service after tickets has broken it:

PS: This is using the precompiled r3 in the official release

lsits

Yea so it seems to be an issue with tickets as i can access everything on the web ui but the minute i try to access tickets, thats when the service takes a dump.

gabriel

I´ve compiled a fresh version of r3 directly from the source, without any minifying or other changes. I´ve installed all available apps from the repository, including the Tickets app, and loaded some data. So far, I could not see any weird behaviour.

Does your OS have anything special? Is it running selinux maybe? Is the service running with a limited user account? Does your Postgres DB limit the connection pool?

Sorry, I am grasping at straws - I have no idea what might be wrong here. I´ve seen quite a few people building their own version of r3 - but issues this severe are new to me. I would love to get to the bottom of this, in case its something we can fix.

lsits

gabriel

So ive created a new VM and installed precompiled r3 on it and its working fine. Im going to spin up another VM later tonight and try installing the self built version and see what happens. I have a feeling it is either a DB issue or some weird OS issue. The OS is just ubuntu 22.04 with latest postgres. Users are not limited. Postgress pool isnt limited. So i have no idea what would have caused the issue. It only happened once i tried throwing on a self built r3. Prior to that, it was working fine with precompiled r3. So ive no clue. But when i try again later tonight, Ill keep you posted on the outcome.