Troubleshooting OCI Functions
Find out how to troubleshoot problems with OCI Functions, and possible solutions to common issues.
This topic covers common issues related to OCI Functions and how to address them.
Use the following techniques to find out more about an error or issue:
- Use the Errors chart on the Metrics page in the Console to see error codes and messages for individual functions: If a function doesn't run or perform as expected when you invoke it, you can use the Errors chart on the Metrics page in the Console to see error codes and error messages for that function. For more information, see Function Metrics.
- Use tracing to observe function execution: If a function doesn't run or perform as expected when you invoke it, you can use tracing to debug execution and performance issues. To use tracing, you have to enable tracing for the application containing the function, and then enable tracing for one or more functions. You can then view function traces in the APM Trace Explorer. For more information, see Distributed Tracing for Functions.
- Use function logs to review function invocation information: The Oracle Cloud Infrastructure Logging service is the default and recommended option for accessing, searching, and storing function logs. Note that to store and view logs for a function, the function must include print statements. For more information, see Storing and Viewing Function Logs.
-
Use DEBUG=1 to see details about requests and responses sent to and from the OCI Functions service: If you encounter an unexpected error when using an Fn Project CLI command, you can see more details about the HTTP requests and responses sent to and from the OCI Functions service. Start the command with the string
DEBUG=1
and run the command again. For example:$ DEBUG=1 fn invoke helloworld-app helloworld-func
Note that
DEBUG=1
must appear before the command, and thatDEBUG
must be in upper case.If you engage with Oracle Support and raise a support ticket, you can attach the output to the ticket.
Note also that if you have set up a local machine as your OCI Functions development environment (specifying
--provider oracle
in the Fn Project CLI context), you must set the environment variableOCI_GO_SDK_DEBUG=v
as well as starting the command withDEBUG=1
.
The issues in this topic are organized in the following broad categories:
- Setting up and running OCI Functions
- Creating applications and functions
- Deploying applications and functions
- Invoking functions
- Miscellaneous
Setting up and running OCI Functions
Error number and message (if applicable) | Description and link |
---|---|
401: Not authenticated |
Running Fn Project CLI commands returns a 401 error |
404: Resource is not authorized or not
found |
Running Fn Project CLI commands returns a 404 error |
x509: decryption password
incorrect |
Running Fn Project CLI commands returns an X509: decryption password incorrect error |
Error response from daemon... unknown:
Unauthorized |
Performing Docker-related operations with the Fn Project CLI displays an "Error response from daemon... unknown: Unauthorized" message |
asn1:structure error: tags don't match |
Running an Fn Project CLI command displays an "Fn: asn1:structure error: tags don't match" message |
Client version: n.n.nn is not latest:
n.n.nn |
Running fn version shows that a more recent version of the Fn Project CLI is available |
Creating applications and functions
Error number and message (if applicable) | Description and link |
---|---|
Unable to create your app, please try
again. |
Creating a new application displays an error message in the New Application dialog |
Deploying applications and functions
Invoking functions
Miscellaneous
Error number and message (if applicable) | Description and link |
---|---|
error getting credentials - err: exit status
1, out: Error spawning command line 'dbus-launch
--autolaunch... |
When running OCI Functions on Ubuntu, Docker login returns an "error getting credentials - err: exit status 1..." message |