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

bug: startScan_command table grows enormous sizes #1324

Open
1 task done
Vos68 opened this issue Jul 23, 2024 · 2 comments
Open
1 task done

bug: startScan_command table grows enormous sizes #1324

Vos68 opened this issue Jul 23, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@Vos68
Copy link

Vos68 commented Jul 23, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Table startScan_command becomes 200Gb + after few scans, and contains result of commands output.
Sometimes it looks like

        +|                               |             |                 |
      |                                                                                                                                                                                 |             | /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc00011dfe8 sp=0xc00011dfe0 pc=0x473461

             +|                               |             |                 |
      |                                                                                                                                                                                 |             | github.com/projectdiscovery/nuclei/v3/pkg/templates.(*Parser).LoadTemplate(0x0?, {0xc0012d2e60, 0x44}, {0x25fc7c0?, 0xc000c8ac00}, {0x0, 0x0, 0x0}, {0x3663e50, 0xc000c89660})                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        

Expected Behavior

To keep data organized and store only valuable data.

Steps To Reproduce

I recognized that as problem after upgrading to 2.1.0
I have few hundreds targets and i run scans as usual, but seem all output of commands being recorded and start to be very heavy.

Environment

- reNgine: 2.1.1
- OS: Debian 11
- Python: 3.11
- Docker Engine:  27.0.1
- Docker Compose: v2.28.1
- Browser: Firefox MacOs 128.0 (64-bit)

Anything else?

No response

@Vos68 Vos68 added the bug Something isn't working label Jul 23, 2024
Copy link
Contributor

👋 Hi @Vos68,
Issues is only for reporting a bug/feature request. Please read documentation before raising an issue https://rengine.wiki
For very limited support, questions, and discussions, please join reNgine Discord channel: https://discord.gg/azv6fzhNCE
Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.

@Vos68
Copy link
Author

Vos68 commented Jul 23, 2024

Also in logs

db-1           |        django.db.utils.IntegrityError: insert or update on table "startScan_command" violates foreign key constraint "startScan_command_activity_id_457a4aaa_fk_startScan"
db-1           |        DETAIL:  Key (activity_id)=(1393) is not present in table "startScan_scanactivity".
db-1           |
db-1           |        ', '4f8834d0-ceb6-45c4-bf35-df1c0cc96876') RETURNING "startScan_scanactivity"."id"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant