The Laravel latest app crashed once we hit Waterondoor APIs multiple times and then restart while running perfectly on local. On server side it is handled by Nginx.
Server side directory: it is residing in /wms-web
What we have tried:
On local it is running fine
When we are using only APIs call from the postman, it is running fine
We cleared the cache, and config on the production side
We tried to change many things on Nginx as well but didn’t workout
here is the complete demo of this error: https://www.loom.com/share/e2139fad9a6248d4a96126dd335ef4c2?focus_title=1&muted=1&from_recorder=1
Related
as the title suggests I've used the react native expo quick start guide and managed to setup a basic project. Everything worked just fine until it came to making fetch requests to my local server by laravel 8. It seems both android and ios don't allow making http calls unless you change some config in your android folder which I don't have for using expo. Tried googling for my answer but I keep running into dead ends. Is there any way to enable this or should I try migrating my back-end temporarily to heroku or something similar? Thank you for reading.
Edit: Forgot to mention each time i make a call to the wrong route I immediately get Network error while hitting the right routes throws an unresolved promise
I have deployed an Elixir/Phoenix web app on Heroku 2x instance, the backend is in Postgres. The app works fine most of the time but every now and then it returns no such app I am not able to figure out, why is it happening. I have checked the logs and metrics but nothing is helping. In fact, no logging happens when such errors are happening. It feels as if temporarily the DNS resolver on their side has crashed. I haven't added any custom domain and using the default domain name provided by Heroku.
I'm running JMeter 3.0 on a laptop (Lenovo y700) with win10. I'm trying to get a response from a website and getting a 404 response. when I try other web sites everything works fine. tried running it from my desktop PC (win 8.1) but got the same 404 , and with another website, everything runs fine. now here's the tricky part. I've tried it again on a mac laptop (not sure the version of the os) and there everything was running fine (including the website who didn't work on the other machines).
1
3
Try using SOAP/XML-RPC Request with Send SOAPAction enabled and one HTTP Header Manager in the request.
Apache Jmeter - Samplers - SOAP/XML-RPC_Request
Look at your website logs. It is unfortunately common for developers to leave a reference on a web page which is not built out, leaving an orphaned reference. if you see the 404 in the HTTP request logs and in your results then you can be objectively certain that the reference is missing.
Should have been caught by development but was not
Should have been caught by functional testing but was not
Test blamed for being faulty because it reported something no one else caught
Common scenario....
I have three mvc 3 web applications in a single web role on Azure Cloud Services. All of a sudden this morning both the single instance in production and in staging give "HTTP Error 503. The service is unavailable." when navigated to in a browser.
I rebooted the production instance but nothing changed. Then I deployed a remote desktop enabled version to the staging instance and logged in. However, strangely when I navigate to the web applications in a browser inside the remoted staging instance everything works.
Looking at IIS server logs it seems there are some issues starting the roles (warning level about the appPoolId being incorrect) but obviously the roles are starting as they are accessible from inside the staging server.
The World Wide Web Publishing service is also running and even after restarting this service the web application is not accessible externally.
Does anyone have an explaination for why the sites are accessible locally but not remotely that would help me debug this issue?
I found out where the issue came from, the bindings that were configured in IIS7 did not include bindings for the actual [abc].cloudapp.net host headers.
I assume that for some reason since some time last night or this weekend the requests seem to come with those headers instead of the original headers for the website. This is really strange but adding these bindings fixed both the staging and production instances and they were available again after this change.
tl;dr:
my web api service is running slow, added logging
logging is giving me errors about not being able to find timeouts
didn't see the ravendb database for the webapi project on the server, but dev machines have it
raven is running and running on 8080
tried reinstalling nservicebus via platform installer(downloaded from nservicebus yesterday)
still have the same issue
i think i either messed up the deployment or I need to do a clean install somehow
What do I need to do in order for the webapi project to read the timeouts?
I'm trying to get our application working on a production machine in preparation for an alpha.
Our application has multiple web api sites and many service hosts.
The errors I'm seeing are currently in the web api host on production only:
2014-08-06 01:55:24,789 [52] DEBUG NServiceBus.Timeout.Hosting.Windows.TimeoutPersisterReceiver [(null)] - Polling for timeouts at 08/06/2014 01:55:24.
2014-08-06 01:55:24,793 [46] WARN NServiceBus.Timeout.Hosting.Windows.TimeoutPersisterReceiver [(null)] - Failed to fetch timeouts from the timeout storage
This gets repeated awhile. Eventually (about 2 minutes) the endpoint gives up and just dies
2014-08-06 01:57:03,645 [17] WARN NServiceBus.CircuitBreakers.RepeatedFailuresOverTimeCircuitBreaker [(null)] - The circuit breaker for TimeoutStorageConnectivity will now be triggered
2014-08-06 01:57:03,645 [17] FATAL NServiceBus [(null)] - Repeated failures when fetching timeouts from storage, endpoint will be terminated.
System.InvalidOperationException: There is no index named: dynamic/TimeoutData
I'm getting these logs by enabling log4net file appender for nservicebus to figure out whats going on with the web api services.
The host services work fine on our dev machines, but for some reason they're really slow on the production machines. We don't see the errors on our dev machines. We have the licenses installed on the production machines so its not like we're being throttled by an expired license.
The weird thing is that on our dev machines we see the database for our web api projects, but on the production machines, only the installed service hosts have database entries.
We've been in dev for this particular application for about 18 months. It could be that when we installed nservicebus, the timeouts were not set to be installed. However, I have tried running the platform installer (downloaded yesterday) and the timeouts are still not present. I'm assuming that when I install the service host, the timeouts are stupposed to be installed then, but they're not showing up for some reason.
At this point I'm contemplating uninstaling nservicebus and ravendb, but i'm not sure how to go about getting a clean reinstall.
Here's some relevant lines from my global.asax
IContainer container = IoC.Initialize();
DependencyResolver.SetResolver(new StructureMapDependencyResolver(container));
GlobalConfiguration.Configuration.DependencyResolver = new StructureMapDependencyResolver(container);
Configure.Transactions.Enable();
Configure.Serialization.Json();
Configure.With()
.DefiningEventsAs(t => t.Namespace != null && t.Namespace.Contains(".Events"))
.DefiningCommandsAs(t => t.Namespace != null && t.Namespace.Contains(".Commands"))
.StructureMapBuilder(container)
.Log4Net()
.UseTransport<Msmq>()
.UnicastBus()
.CreateBus()
.Start(() => Configure.Instance.ForInstallationOn<NServiceBus.Installation.Environments.Windows>().Install());
To fix this, perform the following steps
Open the the RavenDB control panel, usually located at http://RAVEN_DB_SERVER:8080
Select the database of your endpoint
Go to Indexes tab
Click at Delete All Indexes
The indexes will be recreated as soon as the service endpoint is started.
It looks like Raven is not installed in your production environment.
For install instructions please take a look here
HTH