RTSP streams stopped working
Completed-
Same here, latest update and a few RTSP stream based cams go offline and won't work again.
Deleting and readding not working here.
Clicking the diagnostics button yields this error:
Confirming server availability.
OKConfirming camera is accessible.
FAILED: Plugin error. The plugin could not be initialized, error code: -22Diagnostics complete
-
Hi Adam and Ryan O'Dwyer,
The described behavior isn't expected.
Could you let us know from with version to which version you updated? -
Hi Adam , Ryan O'Dwyer, and Paul Duthie,
We were able to reproduce the issue and are currently working on fix.
If you want to roll back, please follow the steps in THIS support article.
JIRA-VMS-53012
-
Can I ask why this happened? We had this same type of thing happen last upgrade where permissions got all messed up and there was going to be new procedures in place when rolling out upgrades. This doesnt look like it happened. Having entire batches of camera go offline is almost worse than the permissions issue!
-
Dear Adam,
I understand your frustration with the recent issue, especially considering the previous problems with permission issue in the mobile app.
The latest issue seems to be related to the expected response times for the RTSP streams. If a device takes too long to respond, it goes offline. To address this, we've extended the delay time to prevent such occurrences in the future.
Regarding our new procedures, these were specifically implemented for the Mobile app due to its unique deployment process. The Mobile app's updates are more impactful, and potential rollbacks can be difficult or impossible to execute. In contrast, updates for the VMS are more manageable. We can publish new builds directly and address any issues promptly. Also, people often can roll back fairly easy, by using restore points created before the update or downgrading the system manually, as mentioned in my previous response to Paul Duthie.
Unfortunately, bugs can and will occur in software development, and we are committed to minimizing them. Our testing process is a continuous (24/7/365) effort, and with each bug identified, we add new test scenarios to prevent recurrence.
We understand that these issues make nobody happy, and we are dedicated to preventing them as much as possible and resolving them quickly when they arise.
Thank you for your patience and understanding.
Best regards,
Norman - Nx -
Norman - Nx Support, appreciate the response and explanation.
-
You're welcome Adam . It is the least we can do.
-
Norman - Nx Support - this has happened AGAIN.
Latest update to 5.1.5.39242 has stopped all RTSP streams, same error as last time.
Client is pissed.
-
Update to 6.0.0.39503 in the hopes that it would fix it were not successful either.
This is becoming a major issue with updates and reluctance to perform any in future. Needless to say Im hoping for a very good explanation about why this has happened a second time after: "Our testing process is a continuous (24/7/365) effort, and with each bug identified, we add new test scenarios to prevent recurrence."
-
Hi Ryan O'Dwyer,
Thank you for reaching out! Could you please provide a bit more detail about the issue you’re experiencing?
For reference, I deliberately have RTSP streams set up in my test environment and didn’t encounter any issues when updating to version 6.0.1.
Looking forward to your response!
Best regards.
Post is closed for comments.
Comments
16 comments