BUG create and start new job

[Itstommy10]

ciao @fccview, ho scaricato e avviato tramite portainer CronMaster con questa config:
services: cronmaster: image: ghcr.io/fccview/cronmaster:latest container_name: cronmaster user: "root" ports: - "40123:3000" environment: - NODE_ENV=production - NEXT_PUBLIC_CLOCK_UPDATE_INTERVAL=30000 - AUTH_PASSWORD=very_strong_password - HOST_CRONTAB_USER=root - DEBUGGER=true - HOST_PROJECT_DIR=/home/cronmaster volumes: - /var/run/docker.sock:/var/run/docker.sock - /home/cronmaster/scripts:/app/scripts - /home/cronmaster/data:/app/data - /home/cronmaster/snippets:/app/snippets pid: "host" privileged: true restart: always init: true

nei log con debugger attivo ottengo:
MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] [SSE] Broadcast system-stats to 1 clients (0 failed) MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] [SSE] Broadcast system-stats to 1 clients (0 failed) MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] [SSE] Broadcast system-stats to 1 clients (0 failed) MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] MIDDLEWARE - cookieName: cronmaster-session MIDDLEWARE - NODE_ENV: production MIDDLEWARE - HTTPS: undefined MIDDLEWARE - sessionId: undefined MIDDLEWARE - cookies: [] [SSE] Broadcast system-stats to 1 clients (0 failed)

il job:
copia Pages
Schedule: 0 * * * *

Command: /home/cronmaster/data/cron-log-wrapper.sh "kpk2-74ri" docker exec rclone sh -c "RCLONE_CONFIG=/config/rclone/rclone.conf rclone copy icloud:Pages folder_Francesca:Francesca/icloud/Pages"

funziona perfettamente

mentre il job:
prova
Schedule: * * * * *

Command: /home/cronmaster/data/cron-log-wrapper.sh "7805-xxd9" docker exec rclone sh -c "RCLONE_CONFIG=/config/rclone/rclone.conf rclone copy icloud:Pages folder_Francesca:Francesca/icloud/Pages"

fallisce. da dentro il container vedo che la cartella e il relativo file di log per 7805-xxd9 non vengono mai creati

[Itstommy10]

dopo alcuni minuti ho fatto un clone del job funzionante, e dopo un primo tentivo di failed, ho abilitato il logging ed ha funzionato

[fccview]

Ciao!
Vuoi provare a cambiare il comando così non sono esattamente uguali? (Anche aggiungendo un echo ridondante)

Ho il presentimento che il problema sia che sono lo stesso esatto comando.

Ho cambiato l'applicazione qualche mese fa e ora usa gli uuid parziali, ma inizialmente l'index era il comando. Mi sa che potrei aver dimenticato qualche file quando lo feci.

Se funziona lascio questa aperta e vedo di risolvere con la prossima release ♥️

[fccview]

dopo alcuni minuti ho fatto un clone del job funzionante, e dopo un primo tentivo di failed, ho abilitato il logging ed ha funzionato

Ok ora sono ufficialmente confuso 😆
Tutto é bene quel che finisce bene? Lol

[Itstommy10]

ho messo echo hello come command
primo tentativo con logging disattivato ottengo:

`
Failed to execute cron job
An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.

Details
Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.
Timestamp: 2026-03-26T14:03:54.848Z
secondo tentativo dopo aver attivato loggin ottengo: Failed (Exit: 1)`

terzo tentativo dop o qualche secondo (non so se centra cambiando la select con le righe del logging a 5000) ha funzionato (magari però in background aveva già funzionato priam che riprovassi cambiando le righe)