You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In computeengine.py and cloudsql.py (will soon be merged with PR #164 ) need to hardcode the thread config to 1, otherwise, we get SSL errors.
Repro steps:
Have more than one resource (eg. 2 vms, or 2 cloud SQL instances)
Start a scan
You should see errors in the console, or sometimes it hangs indefinitely
Here's different errors I got:
[SSL: BLOCK_CIPHER_PAD_IS_WRONG] block cipher pad is wrong (_ssl.c:2217)Failed to fetch backups for SQL instance xxxxxxxx: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:2217)
python SSL: WRONG_VERSION_NUMBER
The text was updated successfully, but these errors were encountered:
Yep, this is an odd one. Will either require diving into the API's implementation or maybe wait until Google does a decent job with their own libraries...
x4v13r64
changed the title
Fix GCP multithreading problem
Fix GCP service multithreading issue
Feb 11, 2019
x4v13r64
changed the title
Fix GCP service multithreading issue
GCP CE/CloudSQL can't run with multiple threads
Mar 8, 2019
In computeengine.py and cloudsql.py (will soon be merged with PR #164 ) need to hardcode the thread config to 1, otherwise, we get SSL errors.
Repro steps:
Here's different errors I got:
[SSL: BLOCK_CIPHER_PAD_IS_WRONG] block cipher pad is wrong (_ssl.c:2217)Failed to fetch backups for SQL instance xxxxxxxx: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:2217)
python SSL: WRONG_VERSION_NUMBER
The text was updated successfully, but these errors were encountered: