I have an RDS instance that I stopped a few days ago. Everytime I start it back up, it will be stuck at starting state for a while until it goes back to stopped state.
What could be the reason?
If you operate on AWS console. You can check "logs & events" tab of specific RDS instance.
Logs section, to be more specific. Name of files depends on your DB engine version.
I would sort with "last written" column and check what in the logs.
In official Docs there is more details, also for AWS CLI.
Related
I'm making a simple TODO app and want to upload it to HEROKU.
But after I updated the code on Github, heroku code remained the same.
I've tried this and this and the other answers but nothing changed.
Site Code
Code on github here. As you can see console.log() on site has not disappeared
Heroku site
I even tried to re-create the app on Heroku but it didn't work.
Heroku's GitHub integration has been disabled for over a month as part of a security response. It appears that it will remain disabled for another week or so:
Based on current progress, we plan to complete our investigation by May 30, 2022
…
We know you are waiting for us to re-enable our integration with GitHub, and we've committed to you that we will only do so following a security review. We will post more information to status.heroku.com when it is available.
You should have received emails about this from Salesforce (Heroku's parent company) on or around April 15 and May 4, 2022.
At the moment, your only option is to deploy using some other method. See this question for more details. The answers there suggest some alternative ways to deploy your code.
(Your Heroku password was also forcefully reset; if you have not yet changed it you'll need to do that when you log back in.)
I like that I can use the Logs API (described here: https://cloud.google.com/appengine/docs/java/logs/) to programatically access and display app & request logs as I see fit--it's great.
Now that I'm using Managed VMs on AppEngine you can see on the Admin Console Logs Viewer that there are a ton of additional logs--including in my case a custom log which I found I could include in the viewer (decribed here: https://cloud.google.com/appengine/docs/managed-vms/custom-runtimes#logging).
My question is: Is there any way I can use the Logs API (or other pipelines already built?) to access these logs? My Managed VM module includes several components which could produce logs that I want to view:
App logs -- I can get these! No problem here.
Custom log files created by background processes I kick off in _ah/start (like "my_custom_1.log" in the screenshot)
STDERR & STDOUT from my background processes
Relevant Managed VM logs (e.g. for when an instance was restarted due to bad health... other system events like normal restarts?)
Basically I want "the total picture" at the instance level. Anyone tried to tame Managed VMs in this way with success? I'm not looking forward to rolling my own solution. And I wouldn't even know where to start on the problem of capturing STDERR and STDOUT. Any help appreciated.
There is a difference between App Engine logging and Google Cloud logging. Some of the Managed VM logs go to both, but much of it only goes to cloud logging.
Until recently there was not an API to read Cloud logs, only to write them. However, there is a new v2 beta API: https://cloud.google.com/logging/docs/api/introduction_v2
To do things at an instance level, entries in Cloud logging should have metadata set to denote which VM they came from. Both of these values seem to vary on logs from my VMs:
compute.googleapis.com/resource_name
compute.googleapis.com/resource_id
I tried to set up WordPress under Google App Engine earlier tonight (following the instructions here: https://developers.google.com/appengine/articles/wordpress).
It runs fine locally, but when I push to remote I get a database error (visible at https://wp-dot-frontiermediag.appspot.com/). If we throw on a /wp_admin/install.php you get:
This either means that the username and password information in your
wp-config.php file is incorrect or we can't contact the database server
at :/cloudsql/frontiermediag:fmwp. This could mean your host's database
server is down.
Here's the relevant code in wp-config:
/** MySQL hostname */
if(isset($_SERVER['SERVER_SOFTWARE']) && strpos($_SERVER['SERVER_SOFTWARE'],'Google App Engine') !== false) {
define('DB_HOST', ':/cloudsql/frontiermediag:fmwp');
}else{
define('DB_HOST', 'localhost');
}
frontiermediag:fmwp is showing "Status Runnable" in Developers Console > Cloud SQL.
I did this once before and it worked so I'm not sure what I'm missing here. I thought it might have been because I'm using WP 3.8.1. but rolled back to 3.5.1 and same thing's happening.
Any ideas? frontiermediag is listed as an authorized application on the :fmwp ACL.
This situation happened to me earlier.However, I edited my Cloud SQL instance , and set "Preferred Location" as "Follow App Engine App" from Google Developers Console. This database connection problem was solved in my case.
I tried the instructions with wordpress 3.5.1 and the instructions seem to work for me. The code snippet you have above seems right and I am not sure what could be wrong without looking at rest of your code. Can you try the instructions from the beginning one more time with 3.5.1?
I had this issue, because "Follow App Engine App" doesn't seem to be an option for second generation instances in my case, and so the instance connection name includes the region setting.
Look at the instance details, and under properties, find "Instance connection name". That is the text that should follow :cloudsql/.
I am using CapeDwarf JBoss AS7 to host classic GAE+GWT application. On server side, I am logging directly to java.util.Logger framework.
The application works fine, the logs print nice to the console and files.
However, all my logs, together with some http request logs, are also stored in the datastore. Yes, every log line becomes one datastore entity. This should not surprise me, because it is stated in the docs (http://www.jboss.org/capedwarf/docs) and it is needed in order to display logs in gae-like admin console of CapeDwarf.
I was looking for a way to disable this useful but expensive feature. I cannot find any docs that would tell me what to do if I do not need/want my logs in the datastore (e.g. right now 98.3% of my datastore are __org.jboss.capedwarf.LogRequest__ and __org.jboss.capedwarf.LogLine__ entities!). Does anyone happen to know how to do it?
Already answered on our forum: https://community.jboss.org/message/810735#810735
I've developed a DNN5 site for customer locally on my laptop and I am having problem moving it to a production server. Server is running Windows 2008 R2 (IIS 7.5). I've copied all the files, copied db, modified web.config to see the new db, checked to make sure dnn can see the db via connection string, made sure the directory permissions are correct (appdomain user has RW access to whole virtual directory) .. and it's failing me with following error message taken out of the portals/_default/logs directory:
<log LogGUID="a3f8aab9-36b6-4d95-a605-53b4b0b02c34" LogFileID="" LogTypeKey="APPLICATION_SHUTTING_DOWN" LogUserID="-1" LogUserName="" LogPortalID="-1" LogPortalName="" LogCreateDate="2/4/2011 11:52:57 AM" LogCreateDateNum="0" BypassBuffering="True" LogServerName="SERVER01" LogConfigID="">
<LogProperties>
<LogProperty>
<PropertyName>Shutdown Details</PropertyName>
<PropertyValue>The AppDomain shut down because of a change to the application level configuration.</PropertyValue>
</LogProperty>
</LogProperties>
</log>
I've been stuck on this for the last 3h .. so any hint's or advice is very appreciated.
Thanks!
Filip
Can you look in the EventLog table? I don't think that the log file there is going to be an accurate place to get all of your error messages. In particular, this isn't even an error, just a notification that a few days ago your application was restarted because of a change to the web.config file.
There may be multiple events logged at the same time, so try to take a look at the LogCreateDate attribute, and see if there are other events logged around the same time that might give more information.
Does the process running the website have access to the web.config? Can you double/triple-check, since it seems like the web.config file is being touched every time you try to hit the website? Could an upgrade routine be trying to update that on first run of the site?