Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ECS Ingestion failures

See original GitHub issue

Description: ECS ingestion for one AWS account fails with ValueError: not enough values to unpack (expected 2, got 0).

See full logs below.

Logs:

ERROR:cartography.sync:Unhandled exception during sync stage 'aws'
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/cartography/sync.py", line 74, in run
    stage_func(neo4j_session, config)
  File "/usr/local/lib/python3.9/site-packages/cartography/util.py", line 113, in timed
    return method(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/cartography/intel/aws/__init__.py", line 208, in start_aws_ingestion
    _sync_multiple_accounts(
  File "/usr/local/lib/python3.9/site-packages/cartography/intel/aws/__init__.py", line 145, in _sync_multiple_accounts
    _sync_one_account(
  File "/usr/local/lib/python3.9/site-packages/cartography/intel/aws/__init__.py", line 57, in _sync_one_account
    RESOURCE_FUNCTIONS[func_name](**sync_args)
  File "/usr/local/lib/python3.9/site-packages/cartography/util.py", line 113, in timed
    return method(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/cartography/intel/aws/ecs.py", line 539, in sync
    cluster_arns, clusters = get_ecs_clusters(boto3_session, region)
ValueError: not enough values to unpack (expected 2, got 0)
Traceback (most recent call last):
  File "/src/custom_sync.py", line 56, in <module>
    sys.exit(main(sys.argv[1:]))
  File "/src/custom_sync.py", line 51, in main
    return cli.CLI(build_custom_sync(), prog='cartography').main(argv)
  File "/usr/local/lib/python3.9/site-packages/cartography/cli.py", line 444, in main
    return cartography.sync.run_with_config(self.sync, config)
  File "/usr/local/lib/python3.9/site-packages/cartography/sync.py", line 151, in run_with_config
    return sync.run(neo4j_driver, config)
  File "/usr/local/lib/python3.9/site-packages/cartography/sync.py", line 74, in run
    stage_func(neo4j_session, config)
  File "/usr/local/lib/python3.9/site-packages/cartography/util.py", line 113, in timed
    return method(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/cartography/intel/aws/__init__.py", line 208, in start_aws_ingestion
    _sync_multiple_accounts(
  File "/usr/local/lib/python3.9/site-packages/cartography/intel/aws/__init__.py", line 145, in _sync_multiple_accounts
    _sync_one_account(
  File "/usr/local/lib/python3.9/site-packages/cartography/intel/aws/__init__.py", line 57, in _sync_one_account
    RESOURCE_FUNCTIONS[func_name](**sync_args)
  File "/usr/local/lib/python3.9/site-packages/cartography/util.py", line 113, in timed
    return method(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/cartography/intel/aws/ecs.py", line 539, in sync
    cluster_arns, clusters = get_ecs_clusters(boto3_session, region)
ValueError: not enough values to unpack (expected 2, got 0)

Cartography release version: 0.54.0

Issue Analytics

State:
Created a year ago
Comments:11

Top GitHub Comments

2reactions

ryan-lanecommented, Apr 8, 2022

@achantavy @ramonpetgrave64

so, my guess is that the action isn’t allowed in the account, but the exception is being raised and it’s returning a list. It’s a bit annoying that it changes the return type, especially since it makes the type checking invalid 😦

1reaction

ryan-lanecommented, Apr 11, 2022

Ah, yeah, that solution looks good!

Top Results From Across the Web

API failure reasons - Amazon Elastic Container Service

When an API action that you have triggered through the Amazon ECS API, console, or the AWS CLI exits with a failures error...

8 - ECS Troubleshooting - Harness.io Docs

General troubleshooting steps for ECS deployments. ... The following errors might occur when setting up and deploying ECS in Harness:.

Using ECS to track the source of errors or exceptions #154

I'd like to discuss the use case of tracking the source of program errors / exceptions (line numbers, function names, etc) with ECS....

Introduction | ECS Logging Reference - Elastic

Elastic Common Schema (ECS) defines a common set of fields for ingesting data into ... thus no risk of out of memory errors...

Dell EMC ECS: Technical FAQ

failures. ECS availability is 99.999 (five 9s) based on request-error-rate estimates. Question: What is Chunk? Answer: Data and system metadata are written ...