We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When I restart or power off/on my Dahua DHI-VTO2211G-P, the log fills up with about 30GB of data in just one hour, with the following error message:
2023-09-02T17:10:55.394200831Z multipart: NextPart: read tcp 172.18.0.2:56202->192.168.5.20:80: read: connection reset by peer 2023-09-02T17:10:55.394204682Z multipart: NextPart: read tcp 172.18.0.2:56202->192.168.5.20:80: read: connection reset by peer 2023-09-02T17:10:55.394209726Z multipart: NextPart: read tcp 172.18.0.2:56202->192.168.5.20:80: read: connection reset by peer 2023-09-02T17:10:55.394213693Z multipart: NextPart: read tcp 172.18.0.2:56202->192.168.5.20:80: read: connection reset by peer 2023-09-02T17:10:55.394217678Z multipart: NextPart: read tcp 172.18.0.2:56202->192.168.5.20:80: read: connection reset by peer 2023-09-02T17:10:55.394221532Z multipart: NextPart: read tcp 172.18.0.2:56202->192.168.5.20:80: read: connection reset by peer
To solve this, I need to restart my alarmserver container.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When I restart or power off/on my Dahua DHI-VTO2211G-P, the log fills up with about 30GB of data in just one hour, with the following error message:
To solve this, I need to restart my alarmserver container.
The text was updated successfully, but these errors were encountered: