Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Command line scripts do not allow an unlimited runtime causing timeouts #3631

Closed
TheWitness opened this issue Jun 20, 2020 · 0 comments
Closed

Command line scripts do not allow an unlimited runtime causing timeouts #3631

TheWitness opened this issue Jun 20, 2020 · 0 comments
Labels
bug Undesired behaviour resolved A fixed issue
Milestone
1.2.13

Comments

@TheWitness
Copy link
Member

Describe the bug

Some CLI scripts need to become daemonized, and currently, the cli_check.php script will not allow them to set a max_execution_time of -1.

To Reproduce

Steps to reproduce the behavior:

  1. Create a script that is intended to be daemonized

  2. Set the max_execution_time to -1

  3. Start the script. It will time-out at 300 seconds.

  4. See error

Expected behavior

Daemonization should work.
@TheWitness TheWitness added the bug Undesired behaviour label Jun 20, 2020
@TheWitness TheWitness changed the title cli scripts are not allowed to have unlimited runtime Cacti cli scripts are not allowed to have unlimited runtime Jun 20, 2020
TheWitness added a commit that referenced this issue Jun 20, 2020
@TheWitness
Fixing Issue #3631
b03cb7e 
Cacti cli scripts are not allowed to have unlimited runtime
@TheWitness TheWitness added the resolved A fixed issue label Jun 20, 2020
@TheWitness TheWitness added this to the 1.2.13 milestone Jun 20, 2020
@netniV netniV changed the title Cacti cli scripts are not allowed to have unlimited runtime Command line scripts do not allow an unlimited runtime causing timeouts Jul 12, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Oct 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Undesired behaviour resolved A fixed issue
Projects
None yet
Milestone
1.2.13
Development

No branches or pull requests
1 participant
@TheWitness