Troubleshooting Cloud Functions
    • PDF

    Troubleshooting Cloud Functions

    • PDF

    Article Summary

    Available in Classic and VPC

    This document details problematic situations users may face while using Cloud Functions, as well as their causes and solutions. However, some problems may be difficult for users to handle themselves, even with the following information at hand. To efficiently address these user difficulties, NAVER Cloud Platform also provides various channels to resolve them.

    Note

    For various troubleshooting channels, see Portal and Console > Portal > Customer Support > Support center.

    Troubleshooting Cloud Functions covers the following topics.

    Restricted specifications

    The following describes the causes and solutions for problems related to restricted specifications.

    The action execution resulted in the response, "Too many concurrent requests in flight()."

    • Cause: the default concurrent value is exceeded.
    • Solution: see Prerequisites for using Cloud Functions to edit the number of concurrent actions that can be executed. If you need to increase the default concurrent value, contact NAVER Cloud Platform.

    Network

    The following describes causes and resolutions for problems related to networks.

    VPC VM communications failed in a VPC action.

    • Cause: if the VM has multiple NICs (more than 1 public subnet) set up, the packet may be kernel dropped by rp_filter (Reverse Path Filter).
    • Set the static routes in the VM as follows.
      # Add static route
      ip route add <range of subnet connected to the action> via <VM's Private NIC Gateway IP>
      
      # Example
      The subnetA range associated with the VPC subnet (private) linked to the action 10.0.10.0/24
      Subnets connected to the VM:
        Subnet(Public) subnetB (10.0.20.0/24)
        Subnet(Private) subnetC (10.0.30.0/24)
      VM NIC
        eth0 ip 10.0.20.3 mask 255.255.255.0 g/w 10.0.20.1
        eth1 ip 10.0.30.5 mask 255.255.255.0 g/w 10.0.30.1
      
      ip route add 10.0.10.0/24 via 10.0.30.1
      

    Logs

    The following describes causes and solutions for each problem related to logs.

    Unable to check the execution history in the dashboard/ monitoring.

    • Cause: all the execution histories of Cloud Functions are stored in Cloud Log Analytics, and the monitoring/dashboard displays the execution history stored in Cloud Log Analytics. If a log loading delay occurs in Cloud Log Analytics, the execution history may not be visible temporarily.
    • Solution: check if logs exist in Cloud Log Analytics. If logs exist in Cloud Log Analytics, but you're unable to check them in Cloud Functions monitoring/dashboard or the delay continues, contact NAVER Cloud Platform.

    Resource

    The following describes the causes and solutions for each problems related to actions, triggers, and packages.

    An error in the format of "cannot import name ..." occurs when running a Python action.

    • Cause: the error is caused due to omission of libraries in the compressed code file, or omission of the system library.
    • Solution: check the following:
      • Missing compressed code file library: see Cloud Functions examples > Create and utilize actions by runtime > Create actions by packaging with Python dependency files of this guide.
      • Missing system library: mostly occurs when Python libraries are dependent on the OS that references system libraries (e.g., *.so, *.dll), or when Windows or macOS system libraries are included in a compressed file, or when the system library to reference for CF runtime image does not exist, so resolve the issues accordingly.

    Connected services

    The following describes causes and resolutions for each problems related to connected services.

    An HTTP status code other than 200 is returned.

    • Cause: 202 (Accepted) returns when making an asynchronous execution call (blocking=false query param). It only checks whether the action is run, and is not involved with whether activities within the action code are successful or not. In case of synchronous calls, 200 (OK) is returned if the execution was successful. If the action runs for 1 minute or more, it's switched to an asynchronous execution and returns 202 (accepted).

    Was this article helpful?

    Changing your password will log you out immediately. Use the new password to log back in.
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.