I got this error from Vercel. It pop up at random times and pages when I am navigating. There are no error raised in browser console. Vercel logs only build time error, so no info there also.
Maybe Vercel or Next.js is short in memory? These navigation works mostly, 'function invoication failed' error happens rarely. Like a ghost.
This means there's an error in either getServerSideProps or an API route, which is throwing a 500 on the server. You are correct this isn't shown in the console, because it's not happening on the client side.
Inside Vercel, you can view the Functions tab for real-time logs. Then, hit this error again and you'll be able to see the stack trace. If you can't reproduce it, set up logging with a Log Drain so you can track when it does happen.
https://vercel.com/docs/logs
Related
final step is "npm run token". Takes me to authentication page with no issues. Then I get to the next page which states "magicmirror1b.firebaseapp.com wants access to your Google Account" I then click "Continue" and then i get the following message: "Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared." Tried on Chrome and on Edge. Please help.
I tried on different browsers but the problem is the same. I did some searching but could not find solutions.
When I load my docker shiny app domain name in the browser, it crashes (greys out) and I get this "ERROR: [_parse_http_data] invalid HTTP method".
I have developed an web application that consists of a shiny app (has a login feature connected to an RMySQL database), a website and a mariadb database. I put them together in a docker-compose file and tested it on my local computer and it works fine. I then proceeded to deploy them in a Kubernetes cluster in GCE and that was also successful. I used cloudflare to install a ssl certificate for the shiny app domain (i.e. trnddaapp.com). Now when I load the shiny app domain in the browser it appends the https and loads the app successfully but after about a minute it crashes (greys out). I loaded the shiny app external ip with http and this doesn’t crash.
The closest solution I have come to is https://github.com/rstudio/shiny-server/issues/392 but there doesn't seem to be any other solution to my problem. I would be grateful if anyone help me resolve this problem.
This is the error message I get when I check with kubectl log [app pod name], I get this error:
ERROR: [_parse_http_data] invalid HTTP method
ERROR: [_parse_http_data] invalid HTTP method
ERROR: [_parse_http_data] invalid HTTP method
I expect the app not to crash when the shiny app domain (trnddaapp.com) is appended with the https.
Let's start with the analysis of the error message, it says:
[_parse_http_data]
So we know that your app is receiving something, but it doesn't understand what it is (it may be a malformed HTTP/1.0 or HTTP/1.1 or even binary data) then we have an
invalid HTTP method
Now we are sure it is not a HTTP/1.X call but a stream of (non recognized) data.
We now know is not the instance since it "deploys" and "delivers" the service, but something inside that is just breaking.
There are a few things that may be happening, since it runs in your local machine (where I am assuming it has access to more resources, especially memory) it may be an issue of resource allocation and that once ran in a container, it could be possible that it empties its allocated amount of resources and breaks (perhaps a library that is called in real time that uses a chunk of memory?) but we won't be sure unless we can debug it inside a container, so could it be possible for you to add a debug library that records your requests to see if it parses all of those and at some point in time it stops and why? I know a person from R-Studio created a httpuv that logs every request this can be done as in:
devtools::install_github('rstudio/httpuv#wch-print-req')
And after that, maybe share the output and see why the application is behaving like that and killing its own service.
I really thank you in advance, hopefully with those logs we may be able to shed more light into this matter.
Thanks once again!
-JP
I'm getting this exception in Live Metrics Stream.
When I'm debugging locally I can't see any warning or error. Checking the Failure blad also leads to nowhere.
There is no track for this error in my logs.
AI (Internal): [Microsoft-ApplicationInsights-Data]
EventSourceException while processing event "Message":
System.Reflection.TargetException:Non-static method requires a target
This is a known bug in Application Insights. The errors can safely be ignored according to the product team. If you would like to track the status of this issue, you can do so on their Github repo: https://github.com/Microsoft/ApplicationInsights-dotnet-server/issues/850
Looking in the BizTalk Admin Console under tracked service instances and I can see that the default XML Receive pipeline starts, however it never completes. It remains at status "started" with the error code set to -1061153241. In tracked message events I can see the pipeline receives the message, however i can't see a "send" event type and it looks like the message is not sent to the MessageBox for the waiting orchestration to pick it up. My orchestration never gets initiated. There are no error messages in the event log, no suspended service instances, just the tracked service instance showing starting and not completed with the error code specified above.
I managed to resolve this issue. I had previously just GAC'd a dll and didn't update it as a resource in the Admin Console. Once I updated the Admin Console with this resource and restarted host instances the error went away. Thanks.
I am facing this error since some time, it is very intermittent in nature so, unable to understand why this error and what needs t be done t fix this.
Issue:
We have a workflow 4.5 WCF service. Everything goes well, but intermittently we see suddenly that a workflow instance gets suspended with an error in the table "DurableInstancing.InstancesTable"
The error is "Keyword Not supported: 'DB Name,1433';Initial Catalog'.
Since most times this ust workd fine without any error, I do not think this problem is related to web.config entry for connectionstring. Most times the workflow completes without any error. We have verified multiple times that the connection string is proper and there is no issue with parsing the connection string.
I suspect this issue is happening while Workflow instance is being recreated from persistence storage, and because some reason it is unable to recreate , the workflow is getting suspended with this error in DB.
I really appreciate any help in getting us through this error.
Thanks,
GD
What we found was it was an issue with permission in Database. We gave "dbo" user permission to the workflow database, and after that we have not seen this problem occur again. Has the error or exception that gets logged in the table is mre informative then it would have been better.
Thanks,
GD