You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While launching a scan the following error message is reported in the make logs when the message to log is larger than 300 chars.
Scan seems to crash without errors.
db_1 | 2023-09-08 09:28:44.379 UTC [22518] ERROR: value too long for type character varying(300)
db_1 | 2023-09-08 09:28:44.379 UTC [22518] STATEMENT: UPDATE "startScan_scanactivity" SET "status" = 0, "error_message" = 'HTTPSConnectionPool(host=''www.google.com'', port=443): Max retries exceeded with url: /search?q=(ext:pdf%20OR%20ext:doc%20OR%20ext:docx%20OR%20ext:xls%20OR%20ext:xlsx%20OR%20ext:ppt%20OR%20ext:pptx)+(site:*.xxxxx.com%20OR%20site:xxxxx.com)&num=50&start=0 (Caused by ProxyError(''Cannot connect to proxy.'', ConnectionResetError(104, ''Connection reset by peer'')))', "time" = '2023-09-08T09:28:44.378820+00:00'::timestamptz WHERE "startScan_scanactivity"."id" = 895
celery_1 | [2023-09-08 09:28:44,412: ERROR/ForkPoolWorker-189] Task reNgine.tasks.initiate_scan[5f80f0d3-1427-426a-94a9-ea3c95c72354] raised unexpected: DataError('value too long for type character varying(300)\n')
Full ST Scan activity
celery_1 | The above exception was the direct cause of the following exception:
celery_1 |
celery_1 | Traceback (most recent call last):
celery_1 | File "/usr/local/lib/python3.9/dist-packages/celery/app/trace.py", line 451, in trace_task
celery_1 | R = retval = fun(*args, **kwargs)
celery_1 | File "/usr/local/lib/python3.9/dist-packages/celery/app/trace.py", line 734, in __protected_call__
celery_1 | return self.run(*args, **kwargs)
celery_1 | File "/usr/src/app/reNgine/tasks.py", line 356, in initiate_scan
celery_1 | update_last_activity(activity_id, 0, error_message=str(e))
celery_1 | File "/usr/src/app/reNgine/tasks.py", line 2107, in update_last_activity
celery_1 | ScanActivity.objects.filter(
celery_1 | File "/usr/local/lib/python3.9/dist-packages/django/db/models/query.py", line 783, in update
celery_1 | rows = query.get_compiler(self.db).execute_sql(CURSOR)
celery_1 | File "/usr/local/lib/python3.9/dist-packages/django/db/models/sql/compiler.py", line 1559, in execute_sql
celery_1 | cursor = super().execute_sql(result_type)
celery_1 | File "/usr/local/lib/python3.9/dist-packages/django/db/models/sql/compiler.py", line 1175, in execute_sql
celery_1 | cursor.execute(sql, params)
celery_1 | File "/usr/local/lib/python3.9/dist-packages/django/db/backends/utils.py", line 66, in execute
celery_1 | return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
celery_1 | File "/usr/local/lib/python3.9/dist-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
celery_1 | return executor(sql, params, many, context)
celery_1 | File "/usr/local/lib/python3.9/dist-packages/django/db/backends/utils.py", line 84, in _execute
celery_1 | return self.cursor.execute(sql, params)
celery_1 | File "/usr/local/lib/python3.9/dist-packages/django/db/utils.py", line 90, in __exit__
celery_1 | raise dj_exc_value.with_traceback(traceback) from exc_value
celery_1 | File "/usr/local/lib/python3.9/dist-packages/django/db/backends/utils.py", line 84, in _execute
celery_1 | return self.cursor.execute(sql, params)
celery_1 | django.db.utils.DataError: value too long for type character varying(300)
👋 Hi @psyray,
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.
psyray
changed the title
Bug - Scan activity table - error_message column too small
Bug - Scan activity & history table - error_message column too small
Sep 8, 2023
Issue Summary
While launching a scan the following error message is reported in the
make logs
when the message to log is larger than 300 chars.Scan seems to crash without errors.
Full ST Scan activity
rengine/web/reNgine/tasks.py
Line 2102 in f5f3c22
ST History table
Steps to Reproduce
To resolve issue
Set error_message column up to 1000 chars in startScan_scanactivity & startScan_scanhistory table
The text was updated successfully, but these errors were encountered: