Anyone has an idea what can cause this?
from time to time (every 3 refreshes) the app gets this error so it prevents all the rest of things from loading in the page /app
Related
EDIT1: intershop.urlrewrite.CheckSource is turned off already
We are recently having quite big problems with URL rewrite rules not being loaded in test and production multi-node environments.
The problem started happening after introducing another organization and it's related application onto the servers.
From then on we have tried multiple changes and debugging methods to try to figure it out, but without any result.
Also the major problem is that it doesn't happen all the time and server restart can fix it but not always.
Here are the details so far how the problem manifests (this has been going on for more than a month now on our production system):
Most of the time it starts happening after the deploy of new code and starting up the server
Then multiple people from multiple computers and locations try opening the website and some open it and others get either 404 or "URL invalid" page, so its 50/50.
On the PC where someone successfully opens page, if you try again in incognito mode then you may get again 404(probably connects to another node/appserver).
Usually the problem is resolved either by server restart or by restarting a single node(no code or configuration changes) although this is no reliable way and on the last occurrence we tried multiple restarts and it didn't help. After a few days one of the team members restarted only a single node for debugging purposes and then it started working normally again.
After setting up more detailed log messages and turning on debug messages for URL rewrite classes we have come to the conclusion that the rule loading fails. We have come to this conclusion because we have added debug message on the very start of our applyExpand() method and it never gets shown. This can be observed on the image below:
All of this leads to conclusion that iterator on line 149 is empty.
Please advise on possible causes of this problem and how to resolve it.
The rule loading is implemented so that it's possible to edit/add/remove rules on-the-fly without need to restart the web server. This happens when the property intershop.urlrewrite.CheckSource is set to true. For this, the last-modified time of the file is evaluated. Maybe this doesn't work correctly.
I would recommended to set this property to false and test again if the problems still occur.
With the help of IS support, we have managed to figure out that the problem was that the URL rewrite rules were in a cartridge that wasn't part of every possible application on server which would result in undefined behavior when loading them (it would load on one appserver and on another it wouldn't).
The fix was to add a new common cartridge for all possible applications which would then hold urlrewrite rules and which would definitely be loaded on server startup.
When I turn on webpack5 and call internal api(/api/*) from page after first render, the page refreshes and logs Refreshing page data due to server-side change. after refreshing once, it works fine as webpack4.
Expected Behavior
The page should not refresh on api call after first render.
I recently updated to Next JS 12 and suddenly started encountering this issue also. I'm not sure if it's necessarily related to that as I believe Next JS 11 was also using Webpack 5 for HMR, but they certainly switched over to socket communication for hot reloading, rather than server sent events as they had with previous versions. [https://nextjs.org/docs/upgrading#nextjs-hmr-connection-now-uses-a-websocket]
I have a file /inc/paths.js where I am organizing and exporting URI path string variables for different resources in my app. There were a number of paths in that module which were also being utilized by parts of my /api scripts, namely object keys for AWS S3 bucket paths. So, this module was being imported by not only React components in the /pages directory and elsewhere, but also to the modules in the /api directory. By moving all the variables used by the /api modules into their own file and making sure that none of those variables are imported by React components or pages, the error seems to have disappeared for me.
This may be related to this quote from Vercel:
Finally, if you edit a file that's imported by files outside of the
React tree, Fast Refresh will fall back to doing a full reload. You
might have a file which renders a React component but also exports a
value that is imported by a non-React component. For example, maybe
your component also exports a constant, and a non-React utility file
imports it. In that case, consider migrating the constant to a
separate file and importing it into both files. This will re-enable
Fast Refresh to work. Other cases can usually be solved in a similar
way.
https://nextjs.org/docs/basic-features/fast-refresh
Although the logic doesn't quite match up, it leads me to believe there is something occurring along those lines.
I updated next.js due to the console warning I get whenever next.js run, telling me its using using weppack 4 instead of 5
You can still use webpack 4 by changing it from your next config as it's an update issue
On the client page, I changed to call the internal API by useEffect() hook to fetch data, instead of triggering the data-fetch function by onclick. I found the issue was gone.
I have a problem with my website. Images and some .js files do not finish loading. Honestly, I don’t know what could have happened, the day before the problem everything was perfect … I just woke up and it happened. I thought it might have been the “WP Super Rocket” plugin but I already tried disabling it.
In the Chrome console I get the error “Failed to load resource: net :: ERR_CONNECTION_CLOSED”.Even when I want to see the “preview” of my home page it gives me the error “HTTP ERROR 500”, this does not happen with other pages on the web. It is rare because in these two days, the page returns to normal after noon.
I know that my site is not the most optimized, I am missing a lot for that, but I have not had any errors of this kind and it was loading everything normal.
In case you have to see, my site is hosted on GoDaddy.
The website is: www.cepeban.edu.pe
I am working with Drupal (7) for the first time. I have installed it multiple times using both an automated Simple Scripts method, and a manual method. I am using the MERCI module to create a reservation system. Every time, over the course of several installations, a seemingly simple action - such as creating a taxonomy term (most recent trigger) or activating a standard module (Views for instance) results in a permanent 500 Server Error, interspersed with a properly loaded home page that will not allow the user to proceed to further links.
Check out the site here: www.browntv.org/mgmt
On first load - you will either get a Server Error, or a properly loaded page. If the page loads properly, clicking to ANY link should result in a blank screen, server error, or some other redirect.
I honestly don't even know where to start diagnosing this. I can't tell where an error (if there was one) would be logged, and nor can I figure out how to manually step my MySQL database backwards to try and remove whatever is causing the issue.
Any leads, suggestions, or ideas would be REALLY helpful. Until now, I've just been creating a new installation, thinking that the issue stems from installation issues. However it has happened so many times now I can't just keep starting from scratch.
I'm not seeing any errors on your site, and in fact it let me register a new account.
Having said that, as should be obvious from the error message, 500 is an internal server error, and no one is going to be able to determine the cause just by going to the public url. It's an error with a configuration file on your server. Generally a syntax error would give you a consistent, not a sporadic 500.
While I have a good deal of experience with MERCI, the way you've described the issue, that wouldn't have anything to do with it.
If the problem persists you should check your Apache error log.
I have a SharePoint site that I have added a few extra pages to in order to handle some custom AJAX requests.
Every now and then, about once a week, I get a call saying it's not working. When I look into it, the error I'm receiving is:
Could not load type 'My_Controls.Control_Name' .
Where My_Controls.Control_Name is the name of the page. An IIS restart solves the issue and gets it running again, but this is obviously of great concern to the client.
I have tried everything I could think of. In the past when I encountered this, setting compilation batch="false" usually did the trick, but this time it isn't resolving the problem.
Obviously this is a pain to troubleshoot because there isn't a way to reproduce the bug (it just pops up from time to time) and a simple IIS restart solves it.
Does anyone know what may be causing this or ideas to try and fix it?
Thanks