Stream

Join this community to post or comment

Michelle Cordova

Cloud Platform  - 
 
Cool application, you can get more information from http://www.veloxity.net
1
Add a comment...

Rif Kiamil
moderator

App Engine  - 
 
Made a small video showing why still using old App Engine Console over new Google Cloud Console https://www.youtube.com/watch?v=MNM0tlm-R10&feature=youtu.be

We hope some this feedback can be put into the new console
1
Mohammad Ashraf's profile photoBrad Abrams's profile photo
3 comments
 
Thanks! This is very helpful. I am discussing it with the team now. Keep the feedback coming.

Add a comment...

Shamir Husein

Cloud Platform  - 
 
Hi,
i like to ask about google cloud.
how to estabelish corporate partnership between google and university ?
Our vice dean want to know about this.
thanks
1
Tyler Larson's profile photo
 
Talk to their sales department.
Add a comment...
 
Asking here too
 
Has anyone tried moving an existing GAE app to "managed VM"/"Flexible Environment"? Curious to hear what you think of the "Compat Runtime", what works, what doesn't and how well.

https://cloud.google.com/appengine/docs/flexible/java/dev-jetty9-and-apis
1
Add a comment...

Sreekanth Krishnan

Cloud Platform  - 
 
Hey, check out this Primer lesson I just did (mobile-only link): https://www.yourprimer.com/app/en/lesson/appperformance/
1
Add a comment...

Atif Qureshi

Cloud Platform  - 
 
How To Host Drupal On Vultr Cloud


Drupal is a very popular PHP based Content Management system. These days cloud hosting services has just revolutionized the hosting industry. Learn how to host a Drupal App on Vultr Cloud services.
Follow this step by step guide to install your Drupal application on the Vultr Cloud in just a few minutes
1
Add a comment...

Przemek Sienkiewicz

Cloud Platform  - 
 
Hello, I'm looking for a free document viewer plugin (pdf, ms office, etc) for online service that I'm building. It needs to ensure security of viewed files. Can you suggest something?
1
Add a comment...

Scott Miller

Cloud Platform  - 
 
Let me share my experiences with trying to learn the basics of working with Google Cloud over the first 2 weeks.

First the $300 free trial option is good and appreciated, 60 days, might not be long enough.

I went through the App Engine PHP hello world, and while it worked, I didn't really understanding the need to download the SDK, especially with the "ssh console" being demonstrated. And you use appcfg.py to deploy the app? Took a few days for that to sink in completely. How does this make sense? Shouldn't it be deploy.py or something like that? Minor issues, yes, but not a smooth start.

Decided to try deploying a small snippet of a pre-built website next. Two PHP files, a couple include files, one straight HTML file and a CSS file.

The first issue was figuring out the app.yaml file. There are good app.yaml resources, but not within google's docs. Tried putting all the include files in a static folder, which worked well with the local SDK "test" option (which I also learned about outside of google's docs). But when deploying the app, there were complaints about unknown MIME types.

After adding text/html MIME type for the whole static directory, the CSS file didn't load when deployed at Google. Again, it worked fine locally. Why does it work locally but not deployed on the actual GAE? Took splitting my static folder into static and css folders, setting the proper MIME type on each, but there are no resources I found to really help understand A) what the issue actually was, and B) how to fix it, ultimately it was a guess that turned out correct.

I saw several resources that showed how to do individual file extension mime types, but trying to use that seems to want all the files to be located in your root source directory and then it "moves them" into the static directory on upload. My files were already in those directories, and once uploaded, I have no idea where those files went because the logs said the files didn't exist.

At this point I'm a week plus into the process spending a few hours each evening.

My next major issue is I wanted to do a simple database read on an already existing, hosted elsewhere MySQL database. Again, it worked just fine locally, but when deployed I got a cryptic "The Socket API will be enabled for this application once billing has been enabled in the admin console." But no clue as to what exactly was causing that message. Not remembering how, but I found a clue that it may have been caused by the DNS lookup, so I tried using the IP address. This was worse because now the app just crashed, and restarted according to the logs.

I found documentation that said I needed to enable billing for socket API calls to be allowed. But another frustration was I wasn't sure what would happen with my "free trial period" if I turned billing on, again I found the answer that the $300 credit would still apply for the remainder of the 60 days, but it took a couple google search attempts to find that. So, I "upgraded" the account, but I kept getting the crashing app. Eventually have days of searching I came across an article that showed me that although the account had been "upgraded" billing was still not active on that application. And finding the place to turn that on for the app, even when I knew what I was looking for was not easy.

Finally after more than 2 weeks I have a tiny test site working in GAE that's not very complicated. It should not have taken nearly this long.
3
Hiren Patel's profile photoMalachi de Ælfweald's profile photo
2 comments
 
Agreed. I tried the java ones. The download quickstart is missing steps to get it to work correctly ( which I eventually did ). The cloud ssh one worked from one machine but not another (icons quit becoming clickable). I created 3 projects trying to figure out why it didn't work from that machine. It definitely felt like it took more effort than it should have.
Add a comment...
 
I've successfully implemented user login in my android app with Google Identity Toolkit. I've also created an App Engine Endpoint to communicate from the Android app. Now I want to secure the endpoints with auth. Can someone help me on how to do this? How should I implement a custom Authenticator to verify the GitKit User?
1
1
Sreekanth Krishnan's profile photo
Add a comment...
 
 
This is an old post in stack overflow. It hasn't got any perfect solutions yet. Does this mean it's impossible?
Basically I want to secure Google app engine endpoints(Java) based on oath2 client IDs but without user authentication. Any Google experts?
1
Add a comment...

About this community

Share your expertise and help others be successful with Google Cloud Platform technologies, such as App Engine, Compute Engine, Big Query, and more. If you are an active developer or a cloud evangelist, share your contributions in one of the discussion areas. Join community events and share your own in the "Events" section. Meet Cloud Google Developer Experts in the GDE forum. More Google Cloud Platform developer resources:

Michelle Cordova

Cloud Platform  - 
 
Cool application, you can get more information from http://www.veloxity.net
1
Add a comment...
 
tell me how to switch back to a free trial version back? Accidentally pressed the "go to a paid" yesterday.
1
Add a comment...

Michelle Cordova

Cloud Platform  - 
 
I’m happy to announce the first release of Replicator, a CLI tool for importing entities from Wikidata. Replicator was created for importing data from Wikidata into the QueryR REST API persis…
1
Add a comment...

Michelle Cordova

Cloud Platform  - 
 
It's a lot of work to create a professional website, so if you're new to web development we encourage you to start small. You won't build another Facebook right away, but it's not hard to get your own simple website online, so we'll start there.
1
1
Jusin Dorobati's profile photo
Add a comment...

Arun Kumar

Cloud Platform  - 
 
Hi Team,

Could you please let me know if I can setup the android development environment on the google cloud platform. I'd like to setup the android SDK, eclipse and android eclipse plugin and other tools on google cloud platform..

Thanks,
Arun
1
Arun Kumar's profile photo
 
Did anyone had a chance to look into this?
Add a comment...
 
Since when FTP on App Engine is not supported any more?!
It has worked, unreliably, for at least a year and now suddenly it doesn't work any more. A simple passive FTP client with outgoing requests based on sockets.

https://cloud.google.com/appengine/docs/java/sockets/

System error: errno: 113, detail:no route to host
java.net.SocketException: System error: errno: 113, detail:no route to host
at com.google.appengine.api.socket.SocketApiHelper.translateError(SocketApiHelper.java:102)
at com.google.appengine.api.socket.AppEngineSocketImpl.processConnectError(AppEngineSocketImpl.java:396)
at com.google.appengine.api.socket.AppEngineSocketImpl.createSocket(AppEngineSocketImpl.java:498)
at com.google.appengine.api.socket.AppEngineSocketImpl.connectToAddress(AppEngineSocketImpl.java:362)
at com.google.appengine.api.socket.AppEngineSocketImpl.connect(AppEngineSocketImpl.java:352)
at java.net.Socket.connect(Socket.java:612)
at java.net.Socket.connect(Socket.java:540)
at java.net.Socket.<init>(Socket.java:437)
at java.net.Socket.<init>(Socket.java:220)
at org.apache.commons.net.ftp.FTPClient.openDataConnection(FTPClient.java:514)

See my question here:
https://groups.google.com/forum/?fromgroups#!topic/google-appengine/mVVDE4wECbY
1
Emanuele Ziglioli's profile photo
 
Given up on sockets, luckily I've found equivalent services via http
Add a comment...

Sreekanth Krishnan

Cloud Platform  - 
Simplify user authentication on your Android app with federated sign-in.
3
Add a comment...

Fatih Ustun

Cloud Platform  - 
 
I've a problem with my Google Cloud instance, I worked on a cloud server with WordPress (mbabul.com)

But after two days, I started to get database connection error. And also I can not log in PhPMyAdmin.

When I reboot the instance, problem solves for a little time. After some times, I start to database error again.

Here is MySQL logs;

160503 08:28:24 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160503 8:28:24 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
160503 8:28:24 [Note] /usr/sbin/mysqld (mysqld 5.5.49-0+deb8u1) starting as process 915 ...
160503 8:28:24 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160503 8:28:25 [Note] Plugin 'FEDERATED' is disabled.
160503 8:28:25 InnoDB: The InnoDB memory heap is disabled
160503 8:28:25 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160503 8:28:25 InnoDB: Compressed tables use zlib 1.2.8
160503 8:28:25 InnoDB: Using Linux native AIO
160503 8:28:25 InnoDB: Initializing buffer pool, size = 128.0M
160503 8:28:25 InnoDB: Completed initialization of buffer pool
160503 8:28:25 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160503 8:28:25 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160503 8:28:25 InnoDB: Waiting for the background threads to start
160503 8:28:26 InnoDB: 5.5.49 started; log sequence number 3706292
160503 8:28:26 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
160503 8:28:26 [Note] - '127.0.0.1' resolves to '127.0.0.1';
160503 8:28:26 [Note] Server socket created on IP: '127.0.0.1'.
160503 8:28:26 [Note] Event Scheduler: Loaded 0 events
160503 8:28:26 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.49-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
160503 8:28:26 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 8:28:26 [Warning] Checking table: './wpdatabase/wp_options'
160503 8:28:26 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_postmeta' is marked as crashed and should be repaired
160503 8:28:26 [Warning] Checking table: './wpdatabase/wp_postmeta'
160503 8:28:26 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_posts' is marked as crashed and should be repaired
160503 8:28:26 [Warning] Checking table: './wpdatabase/wp_posts'
160503 8:28:26 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_term_relationships' is marked as crashed and should be repaired
160503 8:28:26 [Warning] Checking table: './wpdatabase/wp_term_relationships'
160503 8:28:26 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_term_taxonomy' is marked as crashed and should be repaired
160503 8:28:26 [Warning] Checking table: './wpdatabase/wp_term_taxonomy'
160503 8:28:26 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_usermeta' is marked as crashed and should be repaired
160503 8:28:26 [Warning] Checking table: './wpdatabase/wp_usermeta'
Killed
160503 08:39:00 mysqld_safe Number of processes running now: 0
160503 08:39:00 mysqld_safe mysqld restarted
160503 8:39:00 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
160503 8:39:00 [Note] /usr/sbin/mysqld (mysqld 5.5.49-0+deb8u1) starting as process 2466 ...
160503 8:39:00 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160503 8:39:00 [Note] Plugin 'FEDERATED' is disabled.
160503 8:39:00 InnoDB: The InnoDB memory heap is disabled
160503 8:39:00 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160503 8:39:00 InnoDB: Compressed tables use zlib 1.2.8
160503 8:39:00 InnoDB: Using Linux native AIO
160503 8:39:00 InnoDB: Initializing buffer pool, size = 128.0M
160503 8:39:00 InnoDB: Completed initialization of buffer pool
160503 8:39:00 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160503 8:39:00 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160503 8:39:00 InnoDB: Waiting for the background threads to start
160503 8:39:01 InnoDB: 5.5.49 started; log sequence number 3706302
160503 8:39:01 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
160503 8:39:01 [Note] - '127.0.0.1' resolves to '127.0.0.1';
160503 8:39:01 [Note] Server socket created on IP: '127.0.0.1'.
160503 8:39:01 [Note] Event Scheduler: Loaded 0 events
160503 8:39:01 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.49-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
160503 8:39:01 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 8:39:01 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 8:39:01 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 8:39:01 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 8:39:01 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 8:39:01 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 8:39:01 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 8:39:01 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 8:39:01 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 8:39:01 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 8:39:01 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 8:39:01 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 8:39:01 [Warning] Checking table: './wpdatabase/wp_options'
Killed
mysqld_safe Number of processes running now: 0
160503 09:15:34 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160503 9:15:34 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
160503 9:15:34 [Note] /usr/sbin/mysqld (mysqld 5.5.49-0+deb8u1) starting as process 976 ...
160503 9:15:34 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160503 9:15:34 [Note] Plugin 'FEDERATED' is disabled.
160503 9:15:34 InnoDB: The InnoDB memory heap is disabled
160503 9:15:34 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160503 9:15:34 InnoDB: Compressed tables use zlib 1.2.8
160503 9:15:34 InnoDB: Using Linux native AIO
160503 9:15:34 InnoDB: Initializing buffer pool, size = 128.0M
160503 9:15:34 InnoDB: Completed initialization of buffer pool
160503 9:15:34 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160503 9:15:34 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160503 9:15:34 InnoDB: Waiting for the background threads to start
160503 9:15:35 InnoDB: 5.5.49 started; log sequence number 3706302
160503 9:15:35 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
160503 9:15:35 [Note] - '127.0.0.1' resolves to '127.0.0.1';
160503 9:15:35 [Note] Server socket created on IP: '127.0.0.1'.
160503 9:15:35 [Note] Event Scheduler: Loaded 0 events
160503 9:15:35 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.49-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
160503 9:15:35 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 9:15:35 [Warning] Checking table: './wpdatabase/wp_options'
160503 9:15:35 [ERROR] Got an error from unknown thread, /build/mysql-5.5-YS7gNe/mysql-5.5-5.5.49/storage/myisam/ha_myisam.cc:912
160503 9:15:35 [Warning] Recovering table: './wpdatabase/wp_options'
160503 9:15:35 [Note] Retrying repair of: './wpdatabase/wp_options' with keycache
160503 9:15:35 [Note] Found 1501 of 1502 rows when repairing './wpdatabase/wp_options'
Killed
160503 09:23:17 mysqld_safe Number of processes running now: 0
160503 09:23:17 mysqld_safe mysqld restarted
160503 9:23:17 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
160503 9:23:17 [Note] /usr/sbin/mysqld (mysqld 5.5.49-0+deb8u1) starting as process 2113 ...
160503 9:23:18 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160503 9:23:18 [Note] Plugin 'FEDERATED' is disabled.
160503 9:23:18 InnoDB: The InnoDB memory heap is disabled
160503 9:23:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160503 9:23:18 InnoDB: Compressed tables use zlib 1.2.8
160503 9:23:18 InnoDB: Using Linux native AIO
160503 9:23:18 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
160503 9:23:18 InnoDB: Completed initialization of buffer pool
160503 9:23:18 InnoDB: Fatal error: cannot allocate memory for the buffer pool
160503 9:23:18 [ERROR] Plugin 'InnoDB' init function returned error.
160503 9:23:18 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160503 9:23:18 [ERROR] Unknown/unsupported storage engine: InnoDB
160503 9:23:18 [ERROR] Aborting

160503 9:23:18 [Note] /usr/sbin/mysqld: Shutdown complete

160503 09:23:18 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
160503 11:25:24 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160503 11:25:24 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
160503 11:25:24 [Note] /usr/sbin/mysqld (mysqld 5.5.49-0+deb8u1) starting as process 915 ...
160503 11:25:24 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160503 11:25:24 [Note] Plugin 'FEDERATED' is disabled.
160503 11:25:24 InnoDB: The InnoDB memory heap is disabled
160503 11:25:24 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160503 11:25:24 InnoDB: Compressed tables use zlib 1.2.8
160503 11:25:24 InnoDB: Using Linux native AIO
160503 11:25:24 InnoDB: Initializing buffer pool, size = 128.0M
160503 11:25:24 InnoDB: Completed initialization of buffer pool
160503 11:25:24 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160503 11:25:24 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160503 11:25:24 InnoDB: Waiting for the background threads to start
160503 11:25:25 InnoDB: 5.5.49 started; log sequence number 3706312
160503 11:25:25 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
160503 11:25:25 [Note] - '127.0.0.1' resolves to '127.0.0.1';
160503 11:25:25 [Note] Server socket created on IP: '127.0.0.1'.
160503 11:25:25 [Note] Event Scheduler: Loaded 0 events
160503 11:25:25 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.49-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
160503 11:25:26 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 11:25:26 [Warning] Checking table: './wpdatabase/wp_options'
Killed
160503 11:29:35 mysqld_safe Number of processes running now: 0
160503 11:29:35 mysqld_safe mysqld restarted
160503 11:29:36 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
160503 11:29:36 [Note] /usr/sbin/mysqld (mysqld 5.5.49-0+deb8u1) starting as process 1788 ...
160503 11:29:36 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160503 11:29:36 [Note] Plugin 'FEDERATED' is disabled.
160503 11:29:36 InnoDB: The InnoDB memory heap is disabled
160503 11:29:36 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160503 11:29:36 InnoDB: Compressed tables use zlib 1.2.8
160503 11:29:36 InnoDB: Using Linux native AIO
160503 11:29:37 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
160503 11:29:37 InnoDB: Completed initialization of buffer pool
160503 11:29:37 InnoDB: Fatal error: cannot allocate memory for the buffer pool
160503 11:29:37 [ERROR] Plugin 'InnoDB' init function returned error.
160503 11:29:37 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160503 11:29:37 [ERROR] Unknown/unsupported storage engine: InnoDB
160503 11:29:37 [ERROR] Aborting

160503 11:29:37 [Note] /usr/sbin/mysqld: Shutdown complete

160503 11:29:37 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
160503 12:40:08 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160503 12:40:08 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
160503 12:40:08 [Note] /usr/sbin/mysqld (mysqld 5.5.49-0+deb8u1) starting as process 976 ...
160503 12:40:08 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160503 12:40:08 [Note] Plugin 'FEDERATED' is disabled.
160503 12:40:08 InnoDB: The InnoDB memory heap is disabled
160503 12:40:08 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160503 12:40:08 InnoDB: Compressed tables use zlib 1.2.8
160503 12:40:08 InnoDB: Using Linux native AIO
160503 12:40:08 InnoDB: Initializing buffer pool, size = 128.0M
160503 12:40:08 InnoDB: Completed initialization of buffer pool
160503 12:40:08 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160503 12:40:08 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
160503 12:40:08 InnoDB: Waiting for the background threads to start
160503 12:40:09 InnoDB: 5.5.49 started; log sequence number 3706322
160503 12:40:09 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
160503 12:40:09 [Note] - '127.0.0.1' resolves to '127.0.0.1';
160503 12:40:09 [Note] Server socket created on IP: '127.0.0.1'.
160503 12:40:09 [Note] Event Scheduler: Loaded 0 events
160503 12:40:09 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.49-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
160503 12:40:09 [ERROR] /usr/sbin/mysqld: Table './wpdatabase/wp_options' is marked as crashed and should be repaired
160503 12:40:09 [Warning] Checking table: './wpdatabase/wp_options'
Killed
160503 12:47:01 mysqld_safe Number of processes running now: 0
160503 12:47:01 mysqld_safe mysqld restarted
160503 12:47:02 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
160503 12:47:02 [Note] /usr/sbin/mysqld (mysqld 5.5.49-0+deb8u1) starting as process 2042 ...
160503 12:47:03 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
160503 12:47:03 [Note] Plugin 'FEDERATED' is disabled.
160503 12:47:03 InnoDB: The InnoDB memory heap is disabled
160503 12:47:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160503 12:47:03 InnoDB: Compressed tables use zlib 1.2.8
160503 12:47:03 InnoDB: Using Linux native AIO
160503 12:47:03 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(137363456 bytes) failed; errno 12
160503 12:47:03 InnoDB: Completed initialization of buffer pool
160503 12:47:03 InnoDB: Fatal error: cannot allocate memory for the buffer pool
160503 12:47:03 [ERROR] Plugin 'InnoDB' init function returned error.
160503 12:47:03 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
160503 12:47:03 [ERROR] Unknown/unsupported storage engine: InnoDB
160503 12:47:03 [ERROR] Aborting

160503 12:47:03 [Note] /usr/sbin/mysqld: Shutdown complete

160503 12:47:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended


1
Ivan Jaros's profile photo
 
Why don't you use Google Cloud SQL instance? What's the point in being in cloud if you're not using it properly?
Add a comment...

Ivan Jaros

Cloud Platform  - 
 
Hi, I want to create deployment manager configuration so that I can ensure all resources but don't want to spend time on creating configs manually. Is there a way to export all existing services from selected project into yaml configs?
1
Viva Di Hanqu's profile photo
4 comments
 
+Igor Zorzetto there may be a quicker way but quicker dose not always mean that you will be right especely if you although you have read and kooked at a subject have no actual experties in the use of the item asked about the best thing to do is to enpart what information you are more or less certain about and if you can addvise the question asker to seek ferther help from there tutors
Add a comment...