Since 2 days.. when trying to load the home page at http://achhabachhadev.appspot.com/ I am receiving the following error .. need to know If I can do something to fix it.
Error: Server Error The server encountered an error and could not complete your request. If the problem persists, please report your problem and mention this error message and the query that caused it.
At the logs level all I see is that the request could not be completed in 1 min. Please tell me is there something else which could be the problem. Any help is welcome.. as it was all working till 2 days ago..
The logs are as given below:
53 / 500 62976ms 0kb Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.79 Safari/535.11 I 2012-03-15 04:41:49.013 javax.servlet.ServletContext log: Initializing Spring root WebApplicationContext I 2012-03-15 04:42:19.717 javax.servlet.ServletContext log: Initializing Spring FrameworkServlet 'ICCFinal02' W 2012-03-15 04:42:42.245 Error for / com.google.apphosting.runtime.HardDeadlineExceededError: This request (80d56e654b79f25b) started at 2012/03/15 11:41:41.284 UTC and was st W 2012-03-15 04:42:42.245 at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthentic C 2012-03-15 04:42:42.293 Uncaught exception from servlet com.google.apphosting.runtime.HardDeadlineExceededError: This request (80d56e654b79f25b) started at 2012/03/15 11:41:4 I 2012-03-15 04:42:42.315 This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This requ W 2012-03-15 04:42:42.315 A problem was encountered with the process that handled this request, causing it to exit.
Did you try re-deploying? I've noticed that every once in a while the appservers get hung up and a redeploy is required to fix it.
Related
We are facing this below error in Vespa, after restarting the cluster we got this below issue.
1600455444.680758 10.10.000.00 1030/1 container Container.com.yahoo.filedistribution.fileacquirer.FileAcquirerImpl info Retrying waitFor for file 'e0ce64d459828eb0': 103 -- Request timed out after 60.0 seconds.
1600455446.819853 10.10.000.00 32752/146 configproxy configproxy.com.yahoo.vespa.filedistribution.FileReferenceDownloader info Request failed. Req: request filedistribution.serveFile(e0ce64d459828eb0,0)\nSpec: tcp/10.10.000.00:19070, error code: 103, set error for connection and use another for next request
We faced this issue second time, earlier we kept it ideal and it was resolved automatically, but this time it is persistent.
Looks like the configproxy is unable to talk to the config server (which is listening to port 19070 on the same host: Spec: tcp/10.10.000.00:19070). Is the config server really runnning and listening on port 19070 on this host? Try running the vespa-config-status script to see if all is well with the config system
Anyone seen the below error message from PHP7 on Google App Engine standard environment?
Error: Server Error
The server encountered an error and could not complete your request.
Please try again in 30 seconds.
Example log from GCP:
xx.xxx.xxx.xx - - [01/Jul/2019:09:16:11 +0100] "GET /api/courses HTTP/1.1" 500 - - "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36" "example.com" ms=12009 cpu_ms=3303 cpm_usd=0 loading_request=0 instance=00c61b117c915eddeba77b2a4f20a2ae2b81fc81a941138beb270170b47b91aedffd87f2 app_engine_release=1.9.71 trace_id=1f2cdcf1c2ea56bc5ebf7cf12577b057
I don't see any logs in my PHP application so don't think the issue is there, but I also can't see any details of the error in GCP.
Where do I need to look? Any help appreciated!
Thanks
EDIT
Using gcloud app logs tail reveals the following errors, no idea how to fix these or if they're the cause of the issue!
2019-07-01 19:21:29 default[20190701t094939] nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /tmp/google-config/nginx.conf:3
2019-07-01 19:21:27 default[20190701t094939] [01-Jul-2019 19:21:27] ERROR: unable to read what child say: Bad file descriptor (9)
2019-07-01 19:21:18 default[20190701t094939] [01-Jul-2019 19:21:18] WARNING: [pool app] child 25 exited on signal 7 (SIGBUS) after 0.718745 seconds from start
EDIT 2
I've added caching to a pretty heavy API end point that has stopped these errors from happening, as you can see after I deployed the change on July 1st in the evening. Looking at the 500 logs they seem to correlate with spikes in traffic so if I had to guess maybe the instance was hitting a Memory/CPU limit?!
Am using digitalocean VPS I installed solr-5.5.0
sudo service solr status
Found 1 Solr nodes:
Solr process 1072 running on port 8983
{
"solr_home":"/var/solr/data/",
"version":"5.2.1 1684708 - shalin - 2015-06-10 23:20:13",
"startTime":"2016-02-25T17:14:47.47Z",
"uptime":"0 days, 8 hours, 39 minutes, 54 seconds",
"memory":"92.1 MB (%18.8) of 490.7 MB"}
http://myip:8983/solr/
am getting this error on my screen.
HTTP ERROR 404
Problem accessing /solr/. Reason:
Not Found
Powered by Jetty://
how to fix this error
As the exception says, you are missing the solrconfig.xml file in the conf folder of your core.
To get this file and all others, go to {SOLR_DIST}/server/solr/configsets/basic_configs and copy over the conf folder to /var/solr/data/gettingstarted1 and restart solr.
This will fix the error.
I've installed a CakePHP application onto App Engine, and I'm redirecting URLs into it using a wildcard URL in my app.yaml:
url: /.*
script: app/webroot/index.php
The documentation states that /_ah/* URLs will be ignored (I don't know what these are for yet), but they are being caught by my CakePHP app and throwing errors into the error log. I also suspect this is the cause of 500 errors with an appengine error of 204 that keep happening randomly.
Does anyone have a solution for this? How do I ensure that the /_ah/ urls pass through to the app engine and not my specific application code?
Example error:
E 08:51:48.957 2015-03-17 404 841 B 304ms /_ah/start
0.1.0.3 - - [17/Mar/2015:01:51:48 -0700] "GET /_ah/start HTTP/1.1" 404 841 - - "****.appspot.com" ms=304 cpu_ms=416 cpm_usd=0.000094 loading_request=1 instance=0 app_engine_release=1.9.18
E 08:51:48.854 error: [MissingControllerException] Controller class AhController could not be found.
MissingControllerException is thrown by my app.
Request to /_ah/start is an initial request from Appengine itself, to initialize your app. I think you can ignore it, if you don't need to do anything special. Or return empty response.
See docs: https://cloud.google.com/appengine/docs/php/modules/#PHP_Instance_states
while deplying app in google app engine i always got following errors...
2014-08-10 03:30:58 Running command: "['C:\\Python27\\python.exe', '-u', u'C:\\Program Files (x86)\\Google\\google_appengine\\appcfg.py', '--no_cookies', u'--email=rjt.rjtshrm94#gmail.com', '--passin', 'update', u'C:\\Users\\Rjt\\Desktop\\New folder (3)']"
03:31 AM Application: my-app-chat; version: 1
03:31 AM Host: appengine.google.com
03:31 AM
Starting update of app: my-app-chat, version: 1
03:31 AM Getting current resource limits.
Password for rjt.rjtshrm94#gmail.com: Invalid username or password.
2014-08-10 03:31:08,612 ERROR appcfg.py:2415 An error occurred processing file '': HTTP Error 401: Unauthorized. Aborting.
Error 401: --- begin server output ---
Must authenticate first.
--- end server output ---
2014-08-10 03:31:08 (Process exited with code 1)
but my emailid and password are correct....
You can close this window now.
I had the same problem and it was driving me mad. I wasn't typing the password wrong.
For me, changing a security setting, not in the app but in my Google account solved it. Go here: https://www.google.com/settings/security/lesssecureapps and "Enable" less secure devices and apps to access your data. For me, that fixed it.
Otherwise I've come accross time settings being the problem (mentioned above).
But more importantly, double-check that the name of your app, that you registered on GoogleDev, is the name that you put in the app.yaml. If it is, then hitting the dashboard in the Launcher should take you to the dashboard of your app.
See my question and answer for more information, if none of this works.