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
When running a script manually (clicking "run") script executes correctly, but when run on a schedule it throws a connection error:
Traceback (most recent call last):
File "/home/hamish/Documents/Code/scrape-officehq-linux/.venv/lib/python3.11/site-packages/urllib3/connection.py", line 199, in _new_conn
sock = connection.create_connection(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/hamish/Documents/Code/scrape-officehq-linux/.venv/lib/python3.11/site-packages/urllib3/util/connection.py", line 60, in create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/hamish/.pyenv/versions/3.11.9/lib/python3.11/socket.py", line 962, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
socket.gaierror: [Errno -3] Temporary failure in name resolution
google.auth.exceptions.TransportError: HTTPSConnectionPool(host='oauth2.googleapis.com', port=443): Max retries exceeded with url: /token (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x779471b8e850>: Failed to resolve 'oauth2.googleapis.com' ([Errno -3] Temporary failure in name resolution)"))
Is there any difference when running using manual execution - "run" - vs. on a schedule?
Steps to reproduce the problem
This is a complex setup:
Using cronicle-edge
Add shell script to call python script
Python script has it's own enviromnent:
#!/bin/bash
export DISPLAY=:0
# Navigate to the project directory (replace with your actual project path)
cd /home/hamish/Documents/Code/scrape-officehq-linux/
# Run the Python script using Poetry
poetry run python selenium.py
Inside python script use gspread to make a connection to Google.
Your Setup
cronicle-edge 1.11.0
running native (no docker)
Operating system and version?
Manjaro Linux
Node.js version?
Node.js v22.9.0
Cronicle software version?
cronicle-edge 1.11.0
Are you using a multi-server setup, or just a single server?
Single server setup
Are you using the filesystem as back-end storage, or S3/Couchbase?
filesystem
Can you reproduce the crash consistently?
yes
The text was updated successfully, but these errors were encountered:
No difference that I know of, but note that you are using cronicle-edge which is not an official build, and I don't know how it handles launching jobs. You may want to cross-post this issue over at https://github.com/cronicle-edge/cronicle-edge/issues
No difference that I know of, but note that you are using cronicle-edge which is not an official build, and I don't know how it handles launching jobs. You may want to cross-post this issue over at https://github.com/cronicle-edge/cronicle-edge/issues
Summary
When running a script manually (clicking "run") script executes correctly, but when run on a schedule it throws a connection error:
Is there any difference when running using manual execution - "run" - vs. on a schedule?
Steps to reproduce the problem
This is a complex setup:
Using cronicle-edge
Add shell script to call python script
Python script has it's own enviromnent:
Inside python script use gspread to make a connection to Google.
Your Setup
cronicle-edge 1.11.0
running native (no docker)
Operating system and version?
Manjaro Linux
Node.js version?
Node.js v22.9.0
Cronicle software version?
cronicle-edge 1.11.0
Are you using a multi-server setup, or just a single server?
Single server setup
Are you using the filesystem as back-end storage, or S3/Couchbase?
filesystem
Can you reproduce the crash consistently?
yes
The text was updated successfully, but these errors were encountered: