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
time="2024-11-20T16:08:01Z" level=error msg="unable to update bouncer 'FirewallBouncer-1650280536' pull: unable to update machine last pull in database: context canceled: sql: transaction has already been committed or rolled back"
time="2024-11-20T16:08:11Z" level=error msg="unable to update bouncer 'FirewallBouncer-1650280536' pull: unable to update machine last pull in database: context canceled"
Since we now propagate the request context to the database call it will cancel if the request is cancelled by the client.
I am proactively opening an issue so users can report their own experience below and log statements to help us debug.
The text was updated successfully, but these errors were encountered:
LaurenceJJones
changed the title
[1.6.4] unable to update bouncer 'X'
[1.6.4] Investigate unable to update bouncer 'X'
Nov 20, 2024
Check Releases to make sure your agent is on the latest version.
Details
I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.
@LaurenceJJones: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.
/kind feature
/kind enhancement
/kind refactoring
/kind bug
/kind packaging
Details
I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.
level=error msg="unable to update bouncer 'name' pull: unable to update machine last pull in database: context canceled: sql: transaction has already been committed or rolled back"
DB backend is mariadb.
Crowdsec is crowdsec-1.6.4-1.el9.x86_64.
We need to investigate the following log calls:
Since we now propagate the request context to the database call it will cancel if the request is cancelled by the client.
I am proactively opening an issue so users can report their own experience below and log statements to help us debug.
The text was updated successfully, but these errors were encountered: