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

When running automation, scans do not always respond to being cancelled #3041

Closed
bmfmancini opened this issue Oct 18, 2019 · 2 comments
Closed
Labels
bug Undesired behaviour resolved A fixed issue

Comments

@bmfmancini
Copy link
Member

Hey Guys on 1.2.7

If you click discover and the process is running if you want to cancel it in the middle the network stop scanning you will not see any AUTOM8 processes running but the status still shows running this is different than my other report here #3040

@cigamit
Copy link
Member

cigamit commented Nov 9, 2019

It's working perfectly in my setup. Just tested with a brand new install. Make sure you have good bidirectional mysql communications. From the main data collector, goto Console > Data Collection > Data Collectors and edit the remote data collector. Go down to the Database Settings and click 'Test Connection'. Please ensure that this works.

@cigamit cigamit added unverified Some days we don't have a clue bug Undesired behaviour resolved A fixed issue and removed unverified Some days we don't have a clue labels Nov 9, 2019
@cigamit
Copy link
Member

cigamit commented Nov 9, 2019

Found the issue. Should be committed shortly.

cigamit added a commit that referenced this issue Nov 9, 2019
* AUTOM8 discovery starts even if you click cancel
* AUTOM8 network scan continues to run infinetly even when cancelled
* AUTOM8 Scan hangs when selecting remote poller
@cigamit cigamit closed this as completed Nov 9, 2019
@netniV netniV changed the title AUTOM8 network scan continues to run infinetly even when cancelled When running automation, scans do not always respond to being cancelled Dec 7, 2019
@github-actions github-actions bot locked and limited conversation to collaborators Jun 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Undesired behaviour resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

2 participants