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

Support: Server with several ORGS in permitted does not sync #8779

Open
1 task done
jfgobin opened this issue Nov 26, 2022 · 1 comment
Open
1 task done

Support: Server with several ORGS in permitted does not sync #8779

jfgobin opened this issue Nov 26, 2022 · 1 comment
Labels
needs triage This issue has been automatically labelled and needs further triage support

Comments

@jfgobin
Copy link

jfgobin commented Nov 26, 2022

Support Questions

I configured a server to pull events. The pull rules excluded the tag tlp:red and had a few ORGs in the permitted org field. The sync went fine and the events were downloaded.

I added several ORGs to the permitted organizations (more than 10) and after that the sync never brought any events: there was no failure but no event was brought either. The worker logs showed the upstream server' HTTP code as 305 (not modified). After a few days, I confirmed on the upstream servers that new events had been created which should have been pulled.

I deleted the server and recreated it with the same rule, no effect. I deleted all the events using the API, no effect.

Removing all the ORGs from the rule but one made the sync pull events once more.

Is there a limit on the number of orgs one can put in a pull rule?

MISP version

2.4.165

Operating System

Ubuntu

Operating System version

20.04

PHP version

7.4

Browser

Edge

Browser version

107.0.1418.56

Relevant log output

No response

Extra attachments

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@jfgobin jfgobin added needs triage This issue has been automatically labelled and needs further triage support labels Nov 26, 2022
@jfgobin
Copy link
Author

jfgobin commented Nov 26, 2022

I forgot to write: after that, when I tried to delete all the events using misp-purge, only 7 events out of 600+ were found for deletion. I deleted all the others using the API (/events/index, retrieved the event number, /events/delete/) and purged the blocklist.

By the looks of it, it seems the database of events/attributes/elements got corrupted or damaged somehow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage This issue has been automatically labelled and needs further triage support
Projects
None yet
Development

No branches or pull requests

1 participant