The command I am issuing as per documentation is
endpointscfg.py get_openapi_spec cfcapi.GreetingApi cfcmelbourne.org
The error I get is
WARNING:root:An exception has been encountered when attempting to use Application Default Credentials: An error was encountered while reading json file: C:\Code\Video-Archive\requirements.txt (pointed to by GOOGLE_APPLICATION_CREDENTIALS environment variable): No JSON object could be decoded. Falling back on dummy AppIdentityServiceStub.
usage: C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\platform\google_appengine\endpointscfg.py
[-h] {get_client_lib, get_discovery_doc} ...
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\platform\google_appengine\endpointscfg.py: error: argument {get_client_lib, get_discovery_doc}: invalid choice: 'get_openapi_spec' (choose from 'get_client_lib', 'get_discovery_doc')
You need to use the endpointscfg.py that comes with the new Endpoints library. The version you're using is an old version distributed through the Cloud SDK.
Related
Im trying to start virgo server with vsphere sdk version 6.7 in my local machine and getting this error.
λ startup.bat
WARNING: jmxPermissions.vbs did not update the permissions of \vSphere Client SDK\html-client-sdk-6.7.0-8170180\vsphere-ui\server\configuration\org.eclipse.virgo.kernel.jmxremote.access.properties. Check the file has the correct permissions.
'Client' is not recognized as an internal or external command,
operable program or batch file.
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
Error: Could not find or load main class Client
The issue is that you have deployed the SDK on a Windows path with spaces - startup.bat thinks " Client SDK\html-client-sdk-6.7.0-8170180\vsphere-ui\server\" is a command line argument.
The simple fix is to move the SDK to a location without any spaces.
Kudos goes to my colleague Alex Marinov (https://www.linkedin.com/in/aleksandar-marinov/) for spotting this.
I'm trying to push my application to IBM cloud but getting the following error:
Error: Unable to read archive file at - target/DAH-APP-0.0.1.war as specified in the project's manifest.yml. Please ensure that the file exists at the specified path and is accessible. Cannot complete archive push.
Please help me resolve the issue.
I'm trying to use Spacy on the new AppEngine Standard Python 3.7 runtime.
When I try to deploy I get:
ERROR: (gcloud.app.deploy) Cannot upload file
[/my/project/path/venv/lib/python3.7/site-packages/spacy/lang/tr/lemmatizer.py],
which has size [41523943] (greater than maximum allowed size of
[33554432]). Please delete the file or add to the skip_files entry in
your application .yaml file and try again.
A few oddities:
The docs seem to indicate that I don't need to upload the virtual environment and it will be created from requirements.txt
Looking at the log file, it seems to ignore .pyc files, but not the venv directory
The error message says to add to the skip_files in your application .yaml file and try again., but the docs say the python3.7 runtime doesn't use skip files and to use a .gcloudignore file instead, but adding venv/ or venv/* doesn't work (it appears to be ignored)
To fix this, I needed up update gcloud and reauthenticate:
gcloud components update
gcloud auth login
I recently upgraded my cloud SDK, and now I can no longer deploy to app engine flexible. I deploy my app with the following command:
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\bin\gcloud.cmd preview app deploy --promote vm.yaml
I am getting get the following output and crash (abridged):
WARNING: Could not acquire lock C:\Users\Michael\AppData\Roaming\gcloud\credentials.lock in 0 seconds
WARNING: The credentials file (C:\Users\Michael\AppData\Roaming\gcloud\credentials) is not writable. Opening in read-only mode. Any refreshed credentials will only be valid for this run.
WARNING: Could not acquire lock C:\Users\Michael\AppData\Roaming\gcloud\credentials.lock in 0 seconds
WARNING: The credentials file (C:\Users\Michael\AppData\Roaming\gcloud\credentials) is not writable. Opening in read-only mode. Any refreshed credentials will only be valid for this run.
WARNING: Could not acquire lock C:\Users\Michael\AppData\Roaming\gcloud\credentials.lock in 0 seconds
WARNING: The credentials file (C:\Users\Michael\AppData\Roaming\gcloud\credentials) is not writable. Opening in read-only mode. Any refreshed credentials will only be valid for this run.
...
ERROR: gcloud crashed (OSError): [Errno 13] Permission denied: 'C:\\Users\\Michael\\AppData\\Roaming\\gcloud\\credentials.lock'
If you would like to report this issue, please run the following command:
gcloud feedback
Below is some of the output from gcloud feedback
Trace:
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\gcloud_main.py:171
gcloud_cli.Execute()
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\calliope\cli.py:719
result = args.calliope_command.Run(cli=s...
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\calliope\backend.py:1404
resources = command_instance.Run(args)
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\lib\surface\app\deploy.py:91
return deploy_util.RunDeploy(self, args,...
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\command_lib\app\deploy_util.py:206
service, code_bucket_ref)
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\api_lib\app\deploy_app_command_util.py:233
_UploadFiles(files_to_upload, bucket_ref...
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\api_lib\app\deploy_app_command_util.py:175
results = pool.map(_UploadFile, tasks)
c:\Python27\lib\multiprocessing\pool.py:251
return self.map_async(func, iterable, ch...
c:\Python27\lib\multiprocessing\pool.py:567
raise self._value
OSError: [Errno 13] Permission denied: 'C:\\Users\\Michael\\AppData\\Roaming\\gcloud\\credentials.lock'
Installation information:
Google Cloud SDK [120.0.0]
Platform: [Windows, x86_64]
Python Version: [2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015, 20:32:19) [MSC v.1500 32 bit (Intel)]]
Python Location: [c:\Python27\python.exe]
[output truncated]
Any ideas?
This is a bug with the Google SDK's parallel upload feature introduced in June 2016. Work-around the bug by turning off the feature with the following command:
gcloud config set app/num_file_upload_processes 1
The command above limits the number of parallel uploads to 1 thread/process, so they don't step on each other's feet.
I recently had the same issue. Go to the directory shown in the error message. You'd find two credientials files. Delete the one with the LOCK extension( it would be the empty one). Then redeploy your project. Worked perfectly for me.
I've also ran into this issue as well. How it happened --> I ran gcloud app deploy command, but later realised that the deployment took much longer to finish (perhaps hanging), then I killed the batch process i.e. CTRL +C. When I reissued the command thats when I got into this issue. So the SOLUTION, do what's already said above i.e. go and delete the credentials.lock file (in my case it found in C:\Users\Sam\AppData\Roaming\gcloud directory)
The better way is to solve this error is to reinstall after deleting the root directory where lock file is.
I did my reading before posting
I know there are quite a few questions on this issue.
I have read all those that I could find but non of the issues and suggestions there helped.
My environment
windows 7 64bit
GAE SDK 1.8.8
version 1.7.0_45 of the JDK
eclipse kepler 4.3.1 + google plugin.
Stuff I tried already
Here are the things I have already tried:
1) changed system variable JAVA_HOME to point to C:\Program Files\Java\jdk1.7.0_45
2) ensured the system variable PATH contains C:\Program Files\Java\jdk1.7.0_45\bin
3) when opening a command window and running both java -version and javac -version I get:
C:\Users\epeleg>java -version
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
C:\Users\epeleg>javac -version
javac 1.7.0_45
4) checked that all my JSP pages (there are only 2) are working properly when used in development server
5) modified C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin\appcfg.cmd so that the command inside it starts with #%JAVA_HOME%\bin\java ... instead of java...
6) I opened the Markers Pane (eclipse: window - show view - other... General--Markers) and fixed all the Java issues that where mentioned there no matter how trivial they seemed.
What the logs show
The Deploy process reports:
Preparing to deploy:
Created staging directory at: 'C:\Users\epeleg\AppData\Local\Temp\appcfg1552018719531070310.tmp'
Scanning for jsp files.
Compiling jsp files.
com.google.appengine.tools.admin.JspCompilationException: Failed to compile the generated JSP java files.
ינו 13, 2014 3:20:30 PM org.apache.jasper.JspC processFile
INFO: Built File: \myFirstJSP.jsp
ינו 13, 2014 3:20:30 PM org.apache.jasper.JspC processFile
INFO: Built File: \mySecondJSP.jsp
Debugging information may be found in C:\Users\epeleg\AppData\Local\Temp\appengine-deploy4888568219008828635.log
The "Staging directory" seems o.k. (but maybe there are missing libraries there ?!)
and the log file contains the following text:
Unable to update:
com.google.appengine.tools.admin.JspCompilationException: Failed to compile the generated JSP java files.
at com.google.appengine.tools.admin.Application.compileJavaFiles(Application.java:840)
at com.google.appengine.tools.admin.Application.compileJsps(Application.java:801)
at com.google.appengine.tools.admin.Application.createStagingDirectory(Application.java:615)
at com.google.appengine.tools.admin.AppAdminImpl.doUpdate(AppAdminImpl.java:418)
at com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:55)
at com.google.appengine.eclipse.core.proxy.AppEngineBridgeImpl.deploy(AppEngineBridgeImpl.java:433)
at com.google.appengine.eclipse.core.deploy.DeployProjectJob.runInWorkspace(DeployProjectJob.java:158)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
My Questions
1) looking for ideas regarding what else I can try
2) Is there a way to simulate the compile from a command window directly on the staging folder so that I might hopefully see an actual helpful error message?
3) The error says Failed to compile the generated JSP java files - where are those generated files supposed to be?
4) Is there a way to run appcfg.cmd directly from the command line (and with what parameters) so that I can see its output (assuming that the plugin is hiding some stuff from me...).
Problem solved
Here is what I did to resolve this, hopefully it will help others that have similar issues.
I decided to try and run the upload from the command line instead of using the plugin for it.
And here is what I got:
[note that I added rem to the #echo off command and also removed the # from the begining of the java command in appcfg.cmd so that all the commands would echo to the console]
C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin>appcfg.cmd update "X:\path\to\my\project\war"
C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin>rem #echo off
C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin>rem Copyright 2009 Google Inc. All Rights Reserved.
C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin>rem Launches the AppCfg utility, which allows Google App Engine
C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin>rem developers to deploy their application to the cloud.
C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin>C:\Program Files\Java\jdk1.7.0_45\bin\java -Djava.home="C:\Program Files\Java\jdk1.7.0_45\jre" -Xmx1100m -cp "C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin\\..\lib\appengine-tools-api.jar" com.google.appengine.tools.admin.AppCfg update "X:\path\to\my\project\war"
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
OK, so I edited appcfg.cmd again and changed its last line to look like this:
"%JAVA_HOME%\bin\java" -Djava.home="%JAVA_HOME%\jre" -Xmx1100m -cp "%~dp0\..\lib\appengine-tools-api.jar" com.google.appengine.tools.admin.AppCfg %*
Try again:
C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin>appcfg.cmd update "X:\path\to\my\project\war"
C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin>rem #echo off
C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin>rem Copyright 2009 Google Inc. All Rights Reserved.
C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin>rem Launches the AppCfg utility, which allows Google App Engine
C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin>rem developers to deploy their application to the cloud.
C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin>"C:\Program Files\Java\jdk1.7.0_45\bin\java" -Djava.home="C:\Program Files\Java\jdk1.7.0_45\jre" -Xmx1100m -cp "C:\Program Files\GAE\appengine-java-sdk-1.8.8\bin\\..\lib\appengine-tools-api.jar" com.google.appengine.tools.admin.AppCfg update "X:\path\to\my\project\war"
Θ≡σ 13, 2014 5:17:12 PM java.util.prefs.WindowsPreferences <init>
WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.
Reading application configuration data...
Θ≡σ 13, 2014 5:17:13 PM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
INFO: Successfully processed X:/path/to/my/project/war\WEB-INF/appengine-web.xml
Θ≡σ 13, 2014 5:17:13 PM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
INFO: Successfully processed X:/path/to/my/project/war\WEB-INF/web.xml
Θ≡σ 13, 2014 5:17:13 PM com.google.apphosting.utils.config.IndexesXmlReader readConfigXml
INFO: Successfully processed X:/path/to/my/project/war\WEB-INF\appengine-generated\datastore-indexes-auto.xml
Beginning interaction for module default...
Email: myemail#mydomain.com
Password for myemail#mydomain.com:
0% Created staging directory at: 'C:\Users\epeleg\AppData\Local\Temp\appcfg8197335956386755707.tmp'
5% Scanning for jsp files.
8% Compiling jsp files.
C:\Users\epeleg\AppData\Local\Temp\1389626267515-0\org\apache\jsp\myFirstJSP_jsp.java:6: error: package com.mycompany does not exist
import com.mycompany.*;
^
C:\Users\epeleg\AppData\Local\Temp\1389626267515-0\org\apache\jsp\mySecondJSP_jsp.java:6: error: package com.mycompany does not exist
import com.mycompany.*;
^
C:\Users\epeleg\AppData\Local\Temp\1389626267515-0\org\apache\jsp\myFirstJSP_jsp.java:6: error: package com.mycompany does not exist
import com.mycompany.*;
^
C:\Users\epeleg\AppData\Local\Temp\1389626267515-0\org\apache\jsp\mySecondJSP_jsp.java:6: error: package com.mycompany does not exist
import com.mycompany.*;
^
2 errors
Error Details:
Θ≡σ 13, 2014 5:17:48 PM org.apache.jasper.JspC processFile
INFO: Built File: \myFirstJSP.jsp
Θ≡σ 13, 2014 5:17:48 PM org.apache.jasper.JspC processFile
INFO: Built File: \mySecondJSP.jsp
com.google.appengine.tools.admin.JspCompilationException: Failed to compile the generated JSP java files.
Unable to update app: Failed to compile the generated JSP java files.
Please see the logs [C:\Users\epeleg\AppData\Local\Temp\appcfg6545644664045561868.log] for further information.
So I went to my JSP's, removed the offending import attribute from the page tag, tryed again and this time it worked.
Now, I don't know why the plugin fails to display the most important lines in appcfg.cmd's output, but to me it feels like some sort of a bug.
Two lines Summary
run <path-to-appengine-java-sdk>\bin\appcfg.cmd update <war-location> in a command window,
it will provide you with a more detailed output then the plugin does and will most likely enable you to resolve the problem in a matter of minutes.
If that fails you are welcome to follow all the steps I mentioned in the questions body, hey seem to have helped other people in the past.