SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-06-05 15:02:27 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Cronicle install script should not copy init.d service #2079

New Issue
Closed
opened 2025-11-20 05:23:01 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:23:01 -05:00
Owner
Copy Link

Originally created by @de666 on GitHub (Oct 13, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Cronicle Primary

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/cronicle.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-3-pve)

📝 Provide a clear and concise description of the issue.

Install script should not copy cronicled service from the /opt/bin folder to /etc/init.d since Cronicle already install a service unit for systemd (cronicle.service).
This result in failing to execute one of the two services since Cronicle is already running and listening to the configured port.
I think this line should be removed from the script:
1fd132e6d3/install/cronicle-install.sh (L27)

🔄 Steps to reproduce the issue.

After boot check the status of cronicle.service and cronicled.service

❌ Paste the full error output (if available).

systemctl status cronicle
× cronicle.service - Node Cronicle
     Loaded: loaded (/etc/systemd/system/cronicle.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Mon 2025-10-13 15:56:20 CEST; 2min 6s ago
   Duration: 2.014s
 Invocation: 649230294d3d44a0ac6cda537ecf3fb7
    Process: 167 ExecStart=/opt/cronicle/bin/control.sh start (code=exited, status=0/SUCCESS)
   Main PID: 326 (code=exited, status=1/FAILURE)
   Mem peak: 55.1M
        CPU: 2.080s

Oct 13 15:56:14 cronicle systemd[1]: Starting cronicle.service - Node Cronicle...
Oct 13 15:56:14 cronicle control.sh[167]: /opt/cronicle/bin/control.sh start: Starting up Cronicle Server...
Oct 13 15:56:18 cronicle control.sh[167]: /opt/cronicle/bin/control.sh start: Cronicle Server started
Oct 13 15:56:18 cronicle systemd[1]: Started cronicle.service - Node Cronicle.
Oct 13 15:56:20 cronicle systemd[1]: cronicle.service: Main process exited, code=exited, status=1/FAILURE
Oct 13 15:56:20 cronicle systemd[1]: cronicle.service: Failed with result 'exit-code'.
Oct 13 15:56:20 cronicle systemd[1]: cronicle.service: Consumed 2.080s CPU time, 55.1M memory peak.

root@cronicle:~# systemctl status cronicled
● cronicled.service - LSB: Start/Stop Cronicle Scheduler
     Loaded: loaded (/etc/init.d/cronicled; generated)
     Active: active (running) since Mon 2025-10-13 15:56:18 CEST; 2min 11s ago
 Invocation: ca60b4ca4c144b0ca93ab978c2505062
       Docs: man:systemd-sysv-generator(8)
    Process: 168 ExecStart=/etc/init.d/cronicled start (code=exited, status=0/SUCCESS)
      Tasks: 11 (limit: 6687)
     Memory: 64.6M (peak: 66.3M)
        CPU: 3.476s
     CGroup: /system.slice/cronicled.service
             └─327 "Cronicle Server"

Oct 13 15:56:14 cronicle systemd[1]: Starting cronicled.service - LSB: Start/Stop Cronicle Scheduler...
Oct 13 15:56:14 cronicle cronicled[173]: /opt/cronicle/bin/control.sh start: Starting up Cronicle Server...
Oct 13 15:56:18 cronicle cronicled[173]: /opt/cronicle/bin/control.sh start: Cronicle Server started
Oct 13 15:56:18 cronicle systemd[1]: Started cronicled.service - LSB: Start/Stop Cronicle Scheduler.

Cronicle.log

[1760363780.57][2025-10-13 15:56:20][cronicle][327][Cronicle][debug][4][Starting UDP server on port: 3014][]
[1760363780.58][2025-10-13 15:56:20][cronicle][326][Cronicle][error][startup][Component startup error: Error: listen EADDRINUSE: address already in use :::3012][]
[1760363780.58][2025-10-13 15:56:20][cronicle][326][Cronicle][debug][1][Component startup error: Error: listen EADDRINUSE: address already in use :::3012][]
[1760363780.58][2025-10-13 15:56:20][cronicle][326][Cronicle][debug][2][Shutting down][]
[1760363780.581][2025-10-13 15:56:20][cronicle][326][Cronicle][debug][9][Deleting PID File: logs/cronicled.pid: 326][]
[1760363780.583][2025-10-13 15:56:20][cronicle][326][Cronicle][error][1][Startup process was interrupted, exiting][]

🖼️ Additional context (optional).

No response

Originally created by @de666 on GitHub (Oct 13, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Cronicle Primary ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/cronicle.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-3-pve) ### 📝 Provide a clear and concise description of the issue. Install script should not copy cronicled service from the /opt/bin folder to /etc/init.d since Cronicle already install a service unit for systemd (cronicle.service). This result in failing to execute one of the two services since Cronicle is already running and listening to the configured port. I think this line should be removed from the script: https://github.com/community-scripts/ProxmoxVE/blob/1fd132e6d371ab03cb53509873fb644ae8a6c3dc/install/cronicle-install.sh#L27 ### 🔄 Steps to reproduce the issue. After boot check the status of cronicle.service and cronicled.service ### ❌ Paste the full error output (if available). ``` systemctl status cronicle × cronicle.service - Node Cronicle Loaded: loaded (/etc/systemd/system/cronicle.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Mon 2025-10-13 15:56:20 CEST; 2min 6s ago Duration: 2.014s Invocation: 649230294d3d44a0ac6cda537ecf3fb7 Process: 167 ExecStart=/opt/cronicle/bin/control.sh start (code=exited, status=0/SUCCESS) Main PID: 326 (code=exited, status=1/FAILURE) Mem peak: 55.1M CPU: 2.080s Oct 13 15:56:14 cronicle systemd[1]: Starting cronicle.service - Node Cronicle... Oct 13 15:56:14 cronicle control.sh[167]: /opt/cronicle/bin/control.sh start: Starting up Cronicle Server... Oct 13 15:56:18 cronicle control.sh[167]: /opt/cronicle/bin/control.sh start: Cronicle Server started Oct 13 15:56:18 cronicle systemd[1]: Started cronicle.service - Node Cronicle. Oct 13 15:56:20 cronicle systemd[1]: cronicle.service: Main process exited, code=exited, status=1/FAILURE Oct 13 15:56:20 cronicle systemd[1]: cronicle.service: Failed with result 'exit-code'. Oct 13 15:56:20 cronicle systemd[1]: cronicle.service: Consumed 2.080s CPU time, 55.1M memory peak. ``` ``` root@cronicle:~# systemctl status cronicled ● cronicled.service - LSB: Start/Stop Cronicle Scheduler Loaded: loaded (/etc/init.d/cronicled; generated) Active: active (running) since Mon 2025-10-13 15:56:18 CEST; 2min 11s ago Invocation: ca60b4ca4c144b0ca93ab978c2505062 Docs: man:systemd-sysv-generator(8) Process: 168 ExecStart=/etc/init.d/cronicled start (code=exited, status=0/SUCCESS) Tasks: 11 (limit: 6687) Memory: 64.6M (peak: 66.3M) CPU: 3.476s CGroup: /system.slice/cronicled.service └─327 "Cronicle Server" Oct 13 15:56:14 cronicle systemd[1]: Starting cronicled.service - LSB: Start/Stop Cronicle Scheduler... Oct 13 15:56:14 cronicle cronicled[173]: /opt/cronicle/bin/control.sh start: Starting up Cronicle Server... Oct 13 15:56:18 cronicle cronicled[173]: /opt/cronicle/bin/control.sh start: Cronicle Server started Oct 13 15:56:18 cronicle systemd[1]: Started cronicled.service - LSB: Start/Stop Cronicle Scheduler. ``` Cronicle.log ``` [1760363780.57][2025-10-13 15:56:20][cronicle][327][Cronicle][debug][4][Starting UDP server on port: 3014][] [1760363780.58][2025-10-13 15:56:20][cronicle][326][Cronicle][error][startup][Component startup error: Error: listen EADDRINUSE: address already in use :::3012][] [1760363780.58][2025-10-13 15:56:20][cronicle][326][Cronicle][debug][1][Component startup error: Error: listen EADDRINUSE: address already in use :::3012][] [1760363780.58][2025-10-13 15:56:20][cronicle][326][Cronicle][debug][2][Shutting down][] [1760363780.581][2025-10-13 15:56:20][cronicle][326][Cronicle][debug][9][Deleting PID File: logs/cronicled.pid: 326][] [1760363780.583][2025-10-13 15:56:20][cronicle][326][Cronicle][error][1][Startup process was interrupted, exiting][] ``` ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:23:01 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#2079
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?