Yes, it's for authorized users and worked for standard env, handler part doesn't work for flex and I added routes file.
As the log, it should come from App Engine. Do I need remove cron config part in app.yaml or even delete the whole handler setting? 03:20:40.199 GET 403 162 B 0 ms AppEngine-Google; (+http://code.google.com/appengine) /Cron/checkDeliveredBatch2 130.211.1.37 - "GET /Cron/checkDeliveredBatch2" 403 162 "-" "AppEngine-Google; (+http://code.google.com/appengine)" { insertId: "9.......l" jsonPayload: { trace: "$traceId" latencySeconds: "0.000" time: null } httpRequest: { requestMethod: "GET" requestUrl: "/Cron/checkDeliveredBatch2" status: 403 responseSize: "162" userAgent: "AppEngine-Google; (+http://code.google.com/appengine)" remoteIp: "1...2...1...37" referer: "-" } resource: { type: "gae_app" labels: {…} } timestamp: "2017-05-04T10:20:40.199761605Z" labels: { compute.googleapis.com/zone: "us-central1-b" appengine.googleapis.com/trace_id: "5.......a" compute.googleapis.com/resource_name: "5......7" compute.googleapis.com/resource_id: "7.......4" } logName: "projects/f-s/logs/appengine.googleapis.com%2Fnginx.request" } On Thursday, May 4, 2017 at 12:35:39 PM UTC-7, Takashi Matsuo (Google) wrote: > > > Hi Yao, > > I think your handlers are protected only for authorized users, right? > > > https://cloud.google.com/appengine/docs/flexible/nodejs/scheduling-jobs-with-cron-yaml#securing_urls_for_cron > On App Engine flex, it changed how to secure your cron handlers. > Check $_SERVER['HTTP_X_APPENGINE_CRON'] and if it's true, the requests are > coming from App Engine cron service. > > On Thu, May 4, 2017 at 12:13 PM Yao Li <[email protected] <javascript:>> > wrote: > >> cron.yaml >> >> cron: >> - description: check USPS Scanned every 4 hours >> url: /Cron/checkUSPSScanned >> schedule: every 4 hours >> retry_parameters: >> min_backoff_seconds: 5 >> max_doublings: 5 >> >> - description: check USPS Scanned every 4 hours (batch 2) >> url: /Cron/checkUSPSScannedBatch2 >> schedule: every 4 hours >> retry_parameters: >> min_backoff_seconds: 5 >> max_doublings: 5 >> >> - description: check Delivered every 4 hours >> url: /Cron/checkDelivered >> schedule: every 4 hours >> retry_parameters: >> min_backoff_seconds: 5 >> max_doublings: 5 >> >> - description: check Delivered every 4 hours (batch 2) >> url: /Cron/checkDeliveredBatch2 >> schedule: every 4 hours >> retry_parameters: >> min_backoff_seconds: 5 >> max_doublings: >> >> >> app.yaml >> >> runtime: custom >> env: flex >> >> >> >> handlers: >> - url: /v\d+/.* >> script: api/index.php >> secure: always >> >> - url: /.* >> script: index.php >> secure: always >> >> - url: /Cron/.* >> script: index.php >> secure: always >> login: admin >> >> resources: >> cpu: 0.5 >> memory_gb: 1.0 >> disk_size_gb: 10 >> >> env_variables: >> WHITELIST_FUNCTIONS: phpinfo >> >> beta_settings: >> cloud_sql_instances: "f-s:us-central1:flex-prod-usc-sql-2" >> >> >> \classes\cron\Routes.php >> >> namespace classes\cron; >> >> class Routes { >> public static $default = array( >> '~^/Cron/checkUSPSScanned?(\?.*)?$~' => >> array('\classes\controllers\Cron', 'checkUSPSScanned'), >> '~^/Cron/checkUSPSScannedBatch2?(\?.*)?$~' => >> array('\classes\controllers\Cron', 'checkUSPSScannedBatch2'), >> '~^/Cron/checkDelivered?(\?.*)?$~' => >> array('\classes\controllers\Cron', 'checkDelivered'), >> '~^/Cron/checkDeliveredBatch2?(\?.*)?$~' => >> array('\classes\controllers\Cron', 'checkDeliveredBatch2') >> ); >> } >> >> On Thursday, May 4, 2017 at 10:25:21 AM UTC-7, Takashi Matsuo (Google) >> wrote: >> >>> >>> Hi Yao, >>> >>> Cron works for me on my Flex app. >>> >>> Can you show your cron.yaml, and app.yaml? >>> >> On Thu, May 4, 2017 at 8:03 AM Yao Li <[email protected]> wrote: >>> >> btw, I did add cron job routing when initializing app in flex env, the >>>> cron routes are defined in app.yaml (handler part) for standard env. >>>> >>>> >>>> On Thursday, May 4, 2017 at 7:57:49 AM UTC-7, Yao Li wrote: >>>>> >>>>> I add New Relic install script in Dockerfile of app level and it >>>>> works, thanks. >>>>> >>>>> The cron job has 403 issue after I deploy the app in GAE flex env as >>>>> default service, it works well (200) previously with app in GAE standard >>>>> env. >>>>> Do I need do some configuration for flex one? >>>>> >>>>> On Monday, May 1, 2017 at 12:47:45 PM UTC-7, Takashi Matsuo (Google) >>>>> wrote: >>>>>> >>>>>> >>>>>> Hi Yao, >>>>>> >>>>>> FYI, we released a new Runtime image >>>>>> <https://github.com/GoogleCloudPlatform/php-docker/releases/tag/2017-05-01-10-25> >>>>>> >>>>>> which should capture the logs on stderr by default. >>>>>> >>>>>> On Mon, May 1, 2017 at 10:28 AM Yao Li <[email protected]> wrote: >>>>>> >>>>>>> 1. I have to install New Relic agent on instance manually with >>>>>>> script currently after ssh, is there a way (API, script or something >>>>>>> else) >>>>>>> to install the following script automatically? >>>>>>> >>>>>> >>>>>> Use runtime:custom and add required piece in your Dockerfile, except >>>>>> for the `/usr/bin/newrelic-daemon start` line. >>>>>> >>>>>> Then have a file named `additional-supervisord.conf` with the >>>>>> following: >>>>>> >>>>>> ``` >>>>>> [program:newrelic-daemon] >>>>>> command = /usr/bin/newrelic-daemon -f >>>>>> stdout_logfile = /dev/stdout >>>>>> stdout_logfile_maxbytes=0 >>>>>> stderr_logfile = /dev/stderr >>>>>> stderr_logfile_maxbytes=0 >>>>>> user = root >>>>>> autostart = true >>>>>> autorestart = true >>>>>> priority = 5 >>>>>> stopwaitsecs = 20 >>>>>> ``` >>>>>> >>>>>> I don't know if the newrelic daemon requires root, so this >>>>>> configuration runs as root in this example, but please use another >>>>>> account >>>>>> if possible. >>>>>> >>>>>> I haven't tested it myself, but technically it should work. >>>>>> >>>>>> -- Takashi >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> ``` >>>>>>> wget -r -l1 -nd -A"linux.tar.gz" >>>>>>> https://download.newrelic.com/php_agent/release/ >>>>>>> gzip -dc newrelic*.tar.gz | tar xf - >>>>>>> cd newrelic-php5* >>>>>>> rm -f >>>>>>> /opt/php56/lib/x86_64-linux-gnu/extensions/no-debug-non-zts-20131226/newrelic.so >>>>>>> cp ./agent/x64/newrelic-20131226.so >>>>>>> /opt/php56/lib/x86_64-linux-gnu/extensions/no-debug-non-zts-20131226/newrelic.so >>>>>>> cp ./daemon/newrelic-daemon.x64 /usr/bin/newrelic-daemon >>>>>>> >>>>>>> sed -i -e 's/"REPLACE_WITH_REAL_KEY"/*yourLicenseKey*/g' >>>>>>> ./scripts/newrelic.ini.template >>>>>>> sed -i -e 's/PHP Application/*yourApplicationName*/g' >>>>>>> ./scripts/newrelic.ini.template >>>>>>> cp ./scripts/newrelic.ini.template >>>>>>> /opt/php56/lib/ext.enabled:/opt/php56/lib/conf.d:/app/newrelic.ini >>>>>>> >>>>>>> /usr/bin/newrelic-daemon start >>>>>>> ``` >>>>>>> 2. I saw there are 2 or 3 instances in flex env, it seems I have to >>>>>>> install New Relic (NR) agent on each one, right? (because every >>>>>>> instance is >>>>>>> independent to hold the app, I didn't see NR agent on the 1st instance >>>>>>> if I >>>>>>> only installed on 2nd or 3rd) >>>>>>> >>>>>>> On Monday, May 1, 2017 at 9:46:20 AM UTC-7, Takashi Matsuo (Google) >>>>>>> wrote: >>>>>>> >>>>>>>> >>>>>>>> Hi Yao, >>>>>>>> >>>>>>>> > 1. flex env doesn't support handlers for routing? >>>>>>>> >>>>>>>> No Flex doesn't support handlers. Instead you can put a partial >>>>>>>> config file for nginx. Put a file named nginx-app.conf. The default >>>>>>>> configuration is as follows: >>>>>>>> >>>>>>>> ``` >>>>>>>> location / { >>>>>>>> # try to serve files directly, fallback to the front controller >>>>>>>> try_files $uri /index.php$is_args$args; >>>>>>>> } >>>>>>>> ``` >>>>>>>> >>>>>>>> > Can I migrate traffic from default service (on standard >>>>>>>> environment) to monitor one (on flex)? Or update monitor to default >>>>>>>> service? >>>>>>>> >>>>>>>> AFAIK, there's no way to do that, but instead you can use versions. >>>>>>>> >>>>>>>> Remove `service` from the app.yaml (so it's default service), and >>>>>>>> deploy with `--version` option as follows: >>>>>>>> >>>>>>>> ``` >>>>>>>> $ gcloud app deploy --version=api-flex --no-promote >>>>>>>> --no-stop-previous-version >>>>>>>> ``` >>>>>>>> >>>>>>>> You can migrate traffic between versions. >>>>>>>> >>>>>>>> On Mon, May 1, 2017 at 8:46 AM Yao Li <[email protected]> wrote: >>>>>>>> >>>>>>> How about deploying without specifying service name in app.yaml? It >>>>>>>>> will replace the current default service, right? >>>>>>>>> >>>>>>>>> >>>>>>>>> On Friday, April 28, 2017 at 4:51:26 PM UTC-7, Yao Li wrote: >>>>>>>>>> >>>>>>>>>> Two questions: >>>>>>>>>> 1. flex env doesn't support handlers for routing? >>>>>>>>>> 2. Can I migrate traffic from default service (on standard >>>>>>>>>> environment) to monitor one (on flex)? Or update monitor to default >>>>>>>>>> service? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Friday, April 28, 2017 at 3:50:41 PM UTC-7, Yao Li wrote: >>>>>>>>>>> >>>>>>>>>>> I found the possible reason: >>>>>>>>>>> >>>>>>>>>>> I defined routing in app.yaml and it works for standard >>>>>>>>>>> environment but flex env, it seems flex env doesn't support >>>>>>>>>>> handlers for >>>>>>>>>>> routing. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> handlers: >>>>>>>>>>> - url: /v\d+/.* >>>>>>>>>>> script: api/index.php >>>>>>>>>>> secure: always >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Friday, April 28, 2017 at 1:52:22 PM UTC-7, Takashi Matsuo >>>>>>>>>>> (Google) wrote: >>>>>>>>>>>> >>>>>>>>>>>> Hi Yao, >>>>>>>>>>>> >>>>>>>>>>>> On Fri, Apr 28, 2017 at 9:10 AM Yao Li <[email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Takashi, >>>>>>>>>>>>> >>>>>>>>>>>>> I did get New Relic installed successfully, thanks! >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Great :) >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> The current issue is 404 for API request from mobile app or >>>>>>>>>>>>> Postman software. >>>>>>>>>>>>> >>>>>>>>>>>>> I have the default service (f-s.appspot.com) in standard >>>>>>>>>>>>> environment and its API service works well, I copied code to >>>>>>>>>>>>> monitor >>>>>>>>>>>>> service (monitor-dot-f-s.appspot.com) which is deployed to >>>>>>>>>>>>> flex env and it doesn't work now. >>>>>>>>>>>>> >>>>>>>>>>>>> I wonder there are 2 reasons: >>>>>>>>>>>>> 1. security certificate >>>>>>>>>>>>> 2. memcache for session handler (used when initialize basic >>>>>>>>>>>>> API controller, it can pass the initialization but session >>>>>>>>>>>>> doesn't work, >>>>>>>>>>>>> actually REST api doesn't need session) >>>>>>>>>>>>> >>>>>>>>>>>>> API in default service works and reason 1 should not be the >>>>>>>>>>>>> problem, how do you think about the 2nd reason or some other >>>>>>>>>>>>> reasons? >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Sorry, but I can not tell without knowing your code. >>>>>>>>>>>> >>>>>>>>>>>> Re: session, I wrote the datastore session handler: >>>>>>>>>>>> >>>>>>>>>>>> https://github.com/GoogleCloudPlatform/google-cloud-php/blob/master/src/Datastore/DatastoreSessionHandler.php >>>>>>>>>>>> >>>>>>>>>>>> It will add some more latency, but only you have to do is to >>>>>>>>>>>> enable the datastore API. Please consider using this if it's ok to >>>>>>>>>>>> add some >>>>>>>>>>>> latency. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> BTW, I still have not received the alpha version for memcache >>>>>>>>>>>>> from the PM as you mentioned, maybe I have to upgrade to PHP 7+ >>>>>>>>>>>>> and use >>>>>>>>>>>>> memcached. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> I talked with the PM again today, I can not promise anything >>>>>>>>>>>> though. >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Wednesday, April 26, 2017 at 8:33:55 PM UTC-7, Takashi >>>>>>>>>>>>> Matsuo (Google) wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> I often do: >>>>>>>>>>>>>> ``` >>>>>>>>>>>>>> apt-get update && apt-get install -y vim less >>>>>>>>>>>>>> ``` >>>>>>>>>>>>>> If you're using runtime:custom, maybe you can install them >>>>>>>>>>>>>> during development phase >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Wed, Apr 26, 2017 at 8:28 PM Yao Li <[email protected]> >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>> I want to check the log file in the docker container, but none >>>>>>>>>>>>>>> of vi, vim, nano works. Do I need to install text editor in the >>>>>>>>>>>>>>> docker >>>>>>>>>>>>>>> image or some other way to view the content? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Or use scp to copy to my mac? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wednesday, April 26, 2017 at 2:44:11 PM UTC-7, Takashi >>>>>>>>>>>>>>> Matsuo (Google) wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi Yao, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> According to their docs, I think you need to use this >>>>>>>>>>>>>>>> method: >>>>>>>>>>>>>>>> PHP agent installation: Non-standard PHP (advanced) >>>>>>>>>>>>>>>> <https://docs.newrelic.com/docs/agents/php-agent/advanced-installation/php-agent-installation-non-standard-php-advanced> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Unfortunately we're not using the debian's official apt >>>>>>>>>>>>>>>> package. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Apr 26, 2017 at 2:31 PM Yao Li <[email protected]> >>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi Takashi, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I'm installing New Relic PHP agent based on php-nginx >>>>>>>>>>>>>>>>> docker image, it does finish all commands in Dockerfile but >>>>>>>>>>>>>>>>> not show New >>>>>>>>>>>>>>>>> Relic in phpinfo() page (phpinfo() will show New Relic module >>>>>>>>>>>>>>>>> if installed >>>>>>>>>>>>>>>>> successfully), how to ensure run the installation command >>>>>>>>>>>>>>>>> with root user in >>>>>>>>>>>>>>>>> bash shell or Dockerfile? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I tried both of following cases, but neither of them work. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Code 0: >>>>>>>>>>>>>>>>> Dockerfile >>>>>>>>>>>>>>>>> ``` >>>>>>>>>>>>>>>>> RUN su www-data -c "newrelic-install install" >>>>>>>>>>>>>>>>> ``` >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Code 1: >>>>>>>>>>>>>>>>> install_new_relic.sh (it complains error if add sudo or su >>>>>>>>>>>>>>>>> before newrelic-install) >>>>>>>>>>>>>>>>> ``` >>>>>>>>>>>>>>>>> newrelic-install install >>>>>>>>>>>>>>>>> ``` >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Logs: >>>>>>>>>>>>>>>>> + apt-get install -yq newrelic-php5 >>>>>>>>>>>>>>>>> Reading package lists... >>>>>>>>>>>>>>>>> Building dependency tree... >>>>>>>>>>>>>>>>> Reading state information... >>>>>>>>>>>>>>>>> The following extra packages will be installed: >>>>>>>>>>>>>>>>> newrelic-daemon newrelic-php5-common >>>>>>>>>>>>>>>>> The following NEW packages will be installed: >>>>>>>>>>>>>>>>> newrelic-daemon newrelic-php5 newrelic-php5-common >>>>>>>>>>>>>>>>> 0 upgraded, 3 newly installed, 0 to remove and 0 not >>>>>>>>>>>>>>>>> upgraded. >>>>>>>>>>>>>>>>> Need to get 8634 kB of archives. >>>>>>>>>>>>>>>>> After this operation, 25.9 MB of additional disk space >>>>>>>>>>>>>>>>> will be used. >>>>>>>>>>>>>>>>> Get:1 http://apt.newrelic.com/debian/ newrelic/non-free >>>>>>>>>>>>>>>>> newrelic-php5-common all 7.2.0.191 [26.2 kB] >>>>>>>>>>>>>>>>> Get:2 http://apt.newrelic.com/debian/ newrelic/non-free >>>>>>>>>>>>>>>>> newrelic-daemon amd64 7.2.0.191 [2810 kB] >>>>>>>>>>>>>>>>> Get:3 http://apt.newrelic.com/debian/ newrelic/non-free >>>>>>>>>>>>>>>>> newrelic-php5 amd64 7.2.0.191 [5798 kB] >>>>>>>>>>>>>>>>> Preconfiguring packages ... >>>>>>>>>>>>>>>>> Fetched 8634 kB in 1s (5053 kB/s) >>>>>>>>>>>>>>>>> Selecting previously unselected package >>>>>>>>>>>>>>>>> newrelic-php5-common. >>>>>>>>>>>>>>>>> (Reading database ... 14536 files and directories >>>>>>>>>>>>>>>>> currently installed.) >>>>>>>>>>>>>>>>> Preparing to unpack >>>>>>>>>>>>>>>>> .../newrelic-php5-common_7.2.0.191_all.deb ... >>>>>>>>>>>>>>>>> Unpacking newrelic-php5-common (7.2.0.191) ... >>>>>>>>>>>>>>>>> Setting up newrelic-php5-common (7.2.0.191) ... >>>>>>>>>>>>>>>>> Selecting previously unselected package newrelic-daemon. >>>>>>>>>>>>>>>>> (Reading database ... 14549 files and directories >>>>>>>>>>>>>>>>> currently installed.) >>>>>>>>>>>>>>>>> Preparing to unpack >>>>>>>>>>>>>>>>> .../newrelic-daemon_7.2.0.191_amd64.deb ... >>>>>>>>>>>>>>>>> Unpacking newrelic-daemon (7.2.0.191) ... >>>>>>>>>>>>>>>>> Processing triggers for systemd (215-17+deb8u6) ... >>>>>>>>>>>>>>>>> Setting up newrelic-daemon (7.2.0.191) ... >>>>>>>>>>>>>>>>> Processing triggers for systemd (215-17+deb8u6) ... >>>>>>>>>>>>>>>>> Selecting previously unselected package newrelic-php5. >>>>>>>>>>>>>>>>> (Reading database ... 14557 files and directories >>>>>>>>>>>>>>>>> currently installed.) >>>>>>>>>>>>>>>>> Preparing to unpack .../newrelic-php5_7.2.0.191_amd64.deb >>>>>>>>>>>>>>>>> ... >>>>>>>>>>>>>>>>> Unpacking newrelic-php5 (7.2.0.191) ... >>>>>>>>>>>>>>>>> Setting up newrelic-php5 (7.2.0.191) ... >>>>>>>>>>>>>>>>> Please run newrelic-install as root to complete >>>>>>>>>>>>>>>>> installation. >>>>>>>>>>>>>>>>> + newrelic-install install >>>>>>>>>>>>>>>>> ---> 1fef98f9ee82 >>>>>>>>>>>>>>>>> Removing intermediate container 42cf882e3357 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Wednesday, April 26, 2017 at 11:37:11 AM UTC-7, Yao Li >>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Ok, we can talk with Hangout. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Wednesday, April 26, 2017 at 11:26:36 AM UTC-7, >>>>>>>>>>>>>>>>>> Takashi Matsuo (Google) wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hi Yao, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> According to "Availability: dynamic", it looks to me >>>>>>>>>>>>>>>>>>> that you look at the App Engine Standard instance. Make >>>>>>>>>>>>>>>>>>> sure you choose the >>>>>>>>>>>>>>>>>>> Flex version. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> The VM runs a container named `gaeapp` for your >>>>>>>>>>>>>>>>>>> application. Did you do `docker ps` in the application >>>>>>>>>>>>>>>>>>> container? >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I'm happy to explain this process on a video call or >>>>>>>>>>>>>>>>>>> something if it does make sense to you. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- Takashi >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Wed, Apr 26, 2017 at 8:53 AM Yao Li <[email protected]> >>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I can see ssh button in Firefox but Chrome, it should be >>>>>>>>>>>>>>>>>>>> a Chrome issue. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I went to docker container gaeapp, but I didn't see any >>>>>>>>>>>>>>>>>>>> docker container is running (empty after docker ps), no >>>>>>>>>>>>>>>>>>>> images >>>>>>>>>>>>>>>>>>>> neither (empty after docker images). But I tried kill -HUP >>>>>>>>>>>>>>>>>>>> 1 and it does >>>>>>>>>>>>>>>>>>>> affect the application (shut down). >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> ``` >>>>>>>>>>>>>>>>>>>> sudo docker exec -t -i gaeapp /bin/bash >>>>>>>>>>>>>>>>>>>> ``` >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Do I need replace 'gaeapp' to my project id or service >>>>>>>>>>>>>>>>>>>> name? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On Tuesday, April 25, 2017 at 4:41:01 PM UTC-7, Yao Li >>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> I cannot find ssh button (as top right corner in >>>>>>>>>>>>>>>>>>>>> screenshot), is it because of permission or some other >>>>>>>>>>>>>>>>>>>>> reason? >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> <https://lh3.googleusercontent.com/-hXjjn3iAxi8/WP_ee3pYtLI/AAAAAAAAAaE/vdf1qcgtTsMTUD7QrLY3jtl6u4zEM4RtACLcB/s1600/Screen%2BShot%2B2017-04-25%2Bat%2B4.38.59%2BPM.png> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> On Tuesday, April 25, 2017 at 4:10:59 PM UTC-7, >>>>>>>>>>>>>>>>>>>>> Takashi Matsuo (Google) wrote: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Hi Yao, >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> You can ssh into the VM; Go to the Cloud Console, and >>>>>>>>>>>>>>>>>>>>>> App Engine -> instances -> ssh. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Once ssh into it, you can go into the docker >>>>>>>>>>>>>>>>>>>>>> container: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> ``` >>>>>>>>>>>>>>>>>>>>>> sudo docker exec -t -i gaeapp /bin/bash >>>>>>>>>>>>>>>>>>>>>> ``` >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Then you can restart everything in the Docker >>>>>>>>>>>>>>>>>>>>>> container by: >>>>>>>>>>>>>>>>>>>>>> ``` >>>>>>>>>>>>>>>>>>>>>> kill -HUP 1 >>>>>>>>>>>>>>>>>>>>>> ``` >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> On Tue, Apr 25, 2017 at 1:11 PM Yao Li < >>>>>>>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Hi Takashi, >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> I installed New Relic Agent in custom php-nginx >>>>>>>>>>>>>>>>>>>>>>> docker image but it doesn't show any data and I'm >>>>>>>>>>>>>>>>>>>>>>> investigating it. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Is there a way to do restart (nginx, php-fpm, httpd, >>>>>>>>>>>>>>>>>>>>>>> etc.) and ls (look up new relic extension in specific >>>>>>>>>>>>>>>>>>>>>>> directory) in GAE >>>>>>>>>>>>>>>>>>>>>>> Flex env? >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Right now I make a new image and re-deploy to >>>>>>>>>>>>>>>>>>>>>>> restart but seems not working. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> On Tuesday, April 25, 2017 at 9:47:14 AM UTC-7, >>>>>>>>>>>>>>>>>>>>>>> Takashi Matsuo (Google) wrote: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Hi Yao, >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> I asked a PM who is responsible for it (it turned >>>>>>>>>>>>>>>>>>>>>>>> out it's not Justin). I will reply you off-thread. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> On Tue, Apr 25, 2017 at 9:25 AM Yao Li < >>>>>>>>>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Hi Takashi, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Could you ask Justin to send me a test (alpha) >>>>>>>>>>>>>>>>>>>>>>>>> version including memcache? >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> As the doc, Redis Lab Memcache supports memcached, >>>>>>>>>>>>>>>>>>>>>>>>> not memcache. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> https://cloud.google.com/appengine/docs/flexible/php/using-redislabs-memcache >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> On Tuesday, April 25, 2017 at 8:42:17 AM UTC-7, >>>>>>>>>>>>>>>>>>>>>>>>> Takashi Matsuo (Google) wrote: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> Hi Yao, >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> Yes, you are right. >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Apr 25, 2017, 8:39 AM Yao Li < >>>>>>>>>>>>>>>>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Hi Takashi, >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> This instruction is only about Logging, doesn't >>>>>>>>>>>>>>>>>>>>>>>>>>> include memcache, right? >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> On Monday, April 24, 2017 at 9:31:54 PM UTC-7, >>>>>>>>>>>>>>>>>>>>>>>>>>> Takashi Matsuo (Google) wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi Yao, >>>>>>>>>>>>>>>>>>>>>>>>>>>> </ >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/c3de845f-5b4f-4d72-a161-30ca42e8c5c1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
