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.

Sign up for GitHub

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

The correlation id was not found (probably evicted due to inactivity #3462

Closed
0xPugal opened this issue Mar 23, 2023 · 35 comments · Fixed by #3621 or #3680
Closed

The correlation id was not found (probably evicted due to inactivity #3462

0xPugal opened this issue Mar 23, 2023 · 35 comments · Fixed by #3621 or #3680
Assignees
@Mzack9999 @tarunKoyalwar
Labels
Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Milestone
nuclei v2.9.5

Comments

@0xPugal
Copy link

0xPugal commented Mar 23, 2023 

root@ubuntu:~/prgms# nuclei -l alive.txt -t ~/nuclei-templates/cves/2022/ -o out.txt

                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   v2.9.0

                projectdiscovery.io

[INF] Using Nuclei Engine 2.9.0 (latest)
[INF] Using Nuclei Templates 9.4.0 (latest)
[INF] Templates added in last update: 65
[INF] Templates loaded for scan: 312
[INF] Targets loaded for scan: 78794
[INF] Templates clustered: 5 (Reduced 236382 Requests)
[INF] Using Interactsh Server: oast.me
2023/03/23 06:54:56 Unsolicited response received on idle HTTP channel starting with "[1,\"ping\",{}]\n"; err=<nil>
2023/03/23 06:55:20 Unsolicited response received on idle HTTP channel starting with "[1,\"ping\",{}]\n"; err=<nil>
2023/03/23 08:15:57 Unsolicited response received on idle HTTP channel starting with "[1,\"ping\",{}]\n"; err=<nil>
2023/03/23 08:15:57 Unsolicited response received on idle HTTP channel starting with "[1,\"ping\",{}]\n"; err=<nil>
2023/03/23 08:15:57 Unsolicited response received on idle HTTP channel starting with "[1,\"ping\",{}]\n"; err=<nil>
2023/03/23 08:15:57 Unsolicited response received on idle HTTP channel starting with "[1,\"ping\",{}]\n"; err=<nil>
2023/03/23 08:22:24 Unsolicited response received on idle HTTP channel starting with "[1,\"ping\",{}]\n"; err=<nil>
2023/03/23 08:22:24 Unsolicited response received on idle HTTP channel starting with "[1,\"ping\",{}]\n"; err=<nil>
2023/03/23 08:38:12 Unsolicited response received on idle HTTP channel starting with "[1,\"ping\",{}]\n"; err=<nil>
2023/03/23 08:38:12 Unsolicited response received on idle HTTP channel starting with "[1,\"ping\",{}]\n"; err=<nil>
2023/03/23 08:38:13 Unsolicited response received on idle HTTP channel starting with "[1,\"ping\",{}]\n"; err=<nil>
[FTL] The correlation id was not found (probably evicted due to inactivity)
@0xPugal 0xPugal added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Mar 23, 2023
@0xPugal
Copy link
Author

0xPugal commented Mar 25, 2023 

[FTL] The correlation id was not found (probably evicted due to inactivity)

@ehsandeep ehsandeep added the Investigation Something to Investigate label Mar 28, 2023
@demon1k
Copy link

demon1k commented Mar 28, 2023

facing same issue on 3 different servers scanning different targets. started happening only after latest update of nuclei+templates.

@ehsandeep ehsandeep mentioned this issue Apr 3, 2023
Closed
@demon1k
Copy link

demon1k commented Apr 6, 2023

any update on this guys?

@0xPugal
Copy link
Author

0xPugal commented Apr 7, 2023

Still facing the Same issue.

@tarunKoyalwar
Copy link
Member

@0xpugazh , Unsolicited response received is not a error but more of a warning/best practice which we can ignore and has no impact golang/go#19895. . we will hide that msg in next release .

Correlation ID not found is also a warning and it has to do with interactsh-server note this has been resolved in dev branch and the core issue is being tracked here projectdiscovery/interactsh#525

@tarunKoyalwar
Copy link
Member

tarunKoyalwar commented Apr 7, 2023 •
edited by DhiyaneshGeek
Loading

@demon1k @0xpugazh this error is fixed in dev branch and you can install nuclei from dev branch with below command

$ go install github.com/projectdiscovery/nuclei/v2/cmd/nuclei@dev

Ref:

#3506 (comment) .

@tarunKoyalwar tarunKoyalwar removed the Investigation Something to Investigate label Apr 7, 2023
@tarunKoyalwar tarunKoyalwar self-assigned this Apr 7, 2023
@mastercho
Copy link

@demon1k @0xpugazh this error is fixed in dev branch and you can install nuclei from dev branch with below command

$ go install github.com/projectdiscovery/nuclei/v2/cmd/nuclei@dev

Ref:

#3506 (comment) .

Is this was included in 2.9.1 ? because using latest 2.9.1 and getting

[FTL] The correlation id was not found (probably evicted due to inactivity)

Which cause Nuclei abort the scan

@tarunKoyalwar
Copy link
Member

tarunKoyalwar commented Apr 13, 2023 •
edited
Loading

Installing from dev branch will show that nuclei is running in development

$ nuclei

                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   v2.9.2-dev

		projectdiscovery.io

[INF] Using Nuclei Engine 2.9.2-dev (development)
[INF] Using Nuclei Templates 9.4.2 (latest)
[INF] Templates added in last update: 78
[INF] Templates loaded for scan: 5845
[INF] No results found. Better luck next time!

@mastercho can you try uninstalling and then reinstalling with above command most likely it is using old version (due to PATH) or you can also install by cloning the repo and building from dev branch

@Mzack9999 Mzack9999 mentioned this issue Apr 13, 2023
Closed
4 tasks
@Mzack9999 Mzack9999 linked a pull request Apr 13, 2023 that will close this issue
Bugfix interact random eviction #3543
Closed
4 tasks
@0xPugal
Copy link
Author

0xPugal commented Apr 14, 2023

Thanks you guys <3 @tarunKoyalwar @mastercho

@0xPugal 0xPugal closed this as completed Apr 14, 2023
@tarunKoyalwar tarunKoyalwar reopened this Apr 14, 2023
@tarunKoyalwar tarunKoyalwar added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Apr 14, 2023
@demon1k
Copy link

demon1k commented Apr 14, 2023

@tarunKoyalwar is this still only in dev. or if i update nuclei normally this fix will be included?

@tarunKoyalwar
Copy link
Member

@demon1k , yes this issue is resolved in dev branch and there will be a nuclei release soon . if you installed dev version now after release of v2.9.2 you just need to update nuclei using -un flag it will be updated to v2.9.2

@mastercho
Copy link

i just test it and once i get the message its prints non stop so i tried to stop and resume checkpoint but it fails, is that normal?

Screenshot

@0xPugal
Copy link
Author

0xPugal commented Apr 15, 2023

Still facing the issue even in dev branch

...
...
[ERR] The correlation id was not found (probably evicted due to inactivity) got: could not get correlation-id from cache                                       
[ERR] The correlation id was not found (probably evicted due to inactivity) got: could not get correlation-id from cache                                       
[5:37:40] | Templates: 3162 | Hosts: 76600 | RPS: 106 | Matched: 1 | Errors: 31234 | Requests: 2149213/486869600 (0%)                                          
[ERR] The correlation id was not found (probably evicted due to inactivity) got: could not get correlation-id from cache                                       
[5:37:45] | Templates: 3162 | Hosts: 76600 | RPS: 106 | Matched: 1 | Errors: 31234 | Requests: 2149903/486869600 (0%)                                          
[ERR] The correlation id was not found (probably evicted due to inactivity) got: could not get correlation-id from cache                                       
[5:37:50] | Templates: 3162 | Hosts: 76600 | RPS: 106 | Matched: 1 | Errors: 31234 | Requests: 2150580/486869600 (0%)                                          
[5:37:55] | Templates: 3162 | Hosts: 76600 | RPS: 106 | Matched: 1 | Errors: 31234 | Requests: 2151281/486869600 (0%)                                          
[ERR] The correlation id was not found (probably evicted due to inactivity) got: could not get correlation-id from cache                                       
[5:38:00] | Templates: 3162 | Hosts: 76600 | RPS: 106 | Matched: 1 | Errors: 31234 | Requests: 2151966/486869600 (0%)                                          
[ERR] The correlation id was not found (probably evicted due to inactivity) got: could not get correlation-id from cache                                       
[5:38:05] | Templates: 3162 | Hosts: 76600 | RPS: 106 | Matched: 1 | Errors: 31234 | Requests: 2152653/486869600 (0%)                                          
[ERR] The correlation id was not found (probably evicted due to inactivity) got: could not get correlation-id from cache                                       
[5:38:10] | Templates: 3162 | Hosts: 76600 | RPS: 106 | Matched: 1 | Errors: 31234 | Requests: 2153340/486869600 (0%)                                          
[ERR] The correlation id was not found (probably evicted due to inactivity) got: could not get correlation-id from cache                                       
[ERR] The correlation id was not found (probably evicted due to inactivity) got: could not get correlation-id from cache                                       
[5:38:15] | Templates: 3162 | Hosts: 76600 | RPS: 106 | Matched: 1 | Errors: 31234 | Requests: 2154023/486869600 (0%)                                          
[5:38:20] | Templates: 3162 | Hosts: 76600 | RPS: 106 | Matched: 1 | Errors: 31234 | Requests: 2154721/486869600 (0%)                                          
[ERR] The correlation id was not found (probably evicted due to inactivity) got: could not get correlation-id from cache                                       
[5:38:25] | Templates: 3162 | Hosts: 76600 | RPS: 106 | Matched: 1 | Errors: 31234 | Requests: 2155404/486869600 (0%)                                          
[ERR] The correlation id was not found (probably evicted due to inactivity) got: could not get correlation-id from cache                                       
[5:38:30] | Templates: 3162 | Hosts: 76600 | RPS: 106 | Matched: 1 | Errors: 31234 | Requests: 2156084/486869600 (0%)                                          
[ERR] The correlation id was not found (probably evicted due to inactivity) got: could not get correlation-id from cache                                       
[ERR] The correlation id was not found (probably evicted due to inactivity) got: could not get correlation-id from cache  
...
...

@tarunKoyalwar tarunKoyalwar removed the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Apr 15, 2023
@tarunKoyalwar
Copy link
Member

@0xpugazh its WIP but should be resolved with linked PR i.e #3543

@mastercho
Copy link

@0xpugazh its WIP but should be resolved with linked PR i.e #3543

i did updated to latest version from dev to main and same issue again once i get [FTL] The correlation id was not found (probably evicted due to inactivity) its aborts the scan... I thought changes from DEV must be in main already ?

@mastercho mastercho mentioned this issue Apr 24, 2023
Closed
@ehsandeep ehsandeep changed the title Unsolicited response received The correlation id was not found (probably evicted due to inactivity Apr 25, 2023
@jaikishantulswani
Copy link

@ehsandeep facing same with new release too in v2.9.2

[FTL] The correlation id was not found (probably evicted due to inactivity)

@ehsandeep ehsandeep added the Priority: High After critical issues are fixed, these should be dealt with before any further issues. label Apr 26, 2023
@Mzack9999
Copy link
Member

@mastercho @jaikishantulswani @0xpugazh would it be possible to confirm if using the branch bugfix-interact-random-eviction fixes the issue?

# install from bugfix-interact-random-eviction branch
go install -v github.com/projectdiscovery/nuclei/v2/cmd/nuclei@bugfix-interact-random-eviction
# or checkout branch
cd projectdiscovery/nuclei
git checkout bugfix-interact-random-eviction

Unfortunately I'm facing some issues to reproduce the bug consistently. Thanks!

@ehsandeep ehsandeep linked a pull request Apr 29, 2023 that will close this issue
updated interactsh version #3621
Merged
4 tasks
@0xPugal
Copy link
Author

0xPugal commented May 8, 2023

Still i got this error..

[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                  [549/954]
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache                                           
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache

@demon1k
Copy link

demon1k commented May 9, 2023

@ehsandeep It is almost gonna be 2months on 28th May. Why this bug that which has ability to crash nuclei isn't getting fixed :(

@ehsandeep
Copy link
Member

@demon1k Unfortunately, we can not fix something we can not reproduce; we have been using current/old nuclei without any issues, so it sounds like of more of an issue that can be reproduced in a specific (unknown) environment.

We are still waiting for information that can be actually used to reproduce this on our side; feel free to dm on on Discord (pdteam) if you have a more specific/reliable way to reproduce this, otherwise, I can only suggest excluding the interactsh related template using -ni option.

@demon1k
Copy link

demon1k commented May 9, 2023

@ehsandeep i have dm'd pdteam on discord. you can also reach directly to me on discord DM my id is BlankJin #362.
I would gladly share all details that you need to reproduce this issue. because i have ran into this 30+ times.

@ehsandeep ehsandeep linked a pull request May 16, 2023 that will close this issue
Adding interact keepalive to reduce server-side id pruning #3680
Merged
4 tasks
@Darkcast
Copy link

Darkcast commented May 16, 2023 •
edited
Loading

im running the latest v2.9.4 and Im having the same issue
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache

@ehsandeep ehsandeep mentioned this issue May 18, 2023
Closed
@Mzack9999 Mzack9999 added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label May 23, 2023
@MetzinAround MetzinAround mentioned this issue May 24, 2023
Closed
@ehsandeep ehsandeep added this to the nuclei v2.9.5 milestone May 28, 2023
@marcelo321
Copy link

@ehsandeep the issue is not constant and happens randomly.

image

I noticed it tends to happen in long scans, maybe because of inactivity as stated between brackets??

@0xPugal
Copy link
Author

0xPugal commented Jun 2, 2023

@marcelo321 Did you update the nuclei to its latest version?

@marcelo321
Copy link

marcelo321 commented Jun 2, 2023 •
edited
Loading

@0xpugazh i'm pretty sure of it. the scans I run with axiom do nuclei -update and nuclei -update-templates before every scan.

[INF] Current nuclei version: v2.9.6 (latest)

specially getting it when running the last new templates:

INF] Current nuclei version: v2.9.6 (latest)
[INF] Current nuclei-templates version: v9.5.1 (latest)
[INF] New templates added in latest release: 56
[INF] Templates loaded for current scan: 10
[INF] Using Interactsh Server: oast.pro
[INF] Using Interactsh Server: oast.site
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache

@0xPugal
Copy link
Author

0xPugal commented Jun 29, 2023

Still the error occur [ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache

root@ubuntu:~# nuclei -l subs -t ~/nuclei-templates/http/cves/ -ss template-spray -o nuclei/cves | notify -silent

                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   v2.9.7

                projectdiscovery.io

[INF] Current nuclei version: v2.9.7 (latest)
[INF] Current nuclei-templates version: v9.5.3 (latest)
[INF] New templates added in latest release: 82
[INF] Templates loaded for current scan: 1832
[INF] Targets loaded for current scan: 21096
[INF] Running httpx on input host
[INF] Found 1323 URL from httpx
[INF] Templates clustered: 16 (Reduced 210960 Requests)
[INF] Using Interactsh Server: oast.site
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache
[ERR] The correlation id was not found (probably evicted due to inactivity): could not get correlation-id from cache
[INF] No results found. Better luck next time!

@dogasantos
Copy link

This happens (at least to me) when I have a list of targets with 3k+ hosts.
Not sure if you all have same scenario

Sometimes I also see a stack trace going on and I have to reduce the number of templates or hosts (using severity for example)

@c0ldbr3w
Copy link

I'm running into this same issue. 2 concurrent nuclei scans going on, both fed from different projects in bbrf. Talk about a useless error message, wow, but here's details because @dogasantos mentioned 3k+ horts:

Scan 1:
[INF] Current nuclei version: v2.9.8 (latest)
[INF] Current nuclei-templates version: v9.5.7 (latest)
[INF] New templates added in latest release: 21
[INF] Templates loaded for current scan: 3184
[INF] Targets loaded for current scan: 1243
[INF] Running httpx on input host
[INF] Found 1147 URL from httpx
[INF] Templates clustered: 222 (Reduced 259787 Requests)

Scan 2:
[INF] Current nuclei version: v2.9.8 (latest)
[INF] Current nuclei-templates version: v9.5.7 (latest)
[INF] New templates added in latest release: 21
[INF] Templates loaded for current scan: 3184
[INF] Targets loaded for current scan: 22569
[INF] Running httpx on input host
[INF] Found 18687 URL from httpx
[INF] Templates clustered: 222 (Reduced 4716921 Requests)

If someone wants the input files, let me know.

@marcelo321
Copy link

hey, just wanted to mention it keeps happening with the last version of nuclei

@0xPugal
Copy link
Author

0xPugal commented Dec 11, 2023

Hey, I too got this error even in the latest version of nuclei

@dogasantos
Copy link

dogasantos commented Jan 3, 2024 •
edited
Loading

yeap. Still seeing this very often in large scans on my end.
@ehsandeep As this still occurring, would it worth reopening this case ?

@Darkcast
Copy link

Darkcast commented Feb 8, 2024

running version 3.1.10 and the issue is still happening

@RAH88
Copy link

RAH88 commented Feb 14, 2024

I am still receiving the same error in build version 3.1.10

@AgoraSecurity
Copy link

I am receiving the same error in version 3.1.10
I scanned new targets and it's the first time I see it.

@MMquant
Copy link

MMquant commented Mar 19, 2024 •
edited
Loading

I had this error when running nuclei v3.2.2 over the http proxy. Adding -proxy-internal fixed the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Mzack9999 Mzack9999

@tarunKoyalwar tarunKoyalwar

Labels
Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Milestone
nuclei v2.9.5