App & web server stop working after ~24hrs
Hi there,
As the title says, the app stops being able to connect after about 24 hours with the error “Connection Failed/Unable to connect to the server”. The web server becomes inaccessible at the same time. But recording, triggers and even iOS notifications work fine throughout.
Logging in via remote desktop and clicking around in Securityspy resolves the issue for another 24 hours or so. I don’t have to restart the app to fix it.
This is an installation that’s been working fine for years with the latest securityspy running on an older OS version. The problem started about the time I enabled the feature for uploading public webcam images to S3 and I’ve not had chance to try disabling that yet.
Any ideas please?
As the title says, the app stops being able to connect after about 24 hours with the error “Connection Failed/Unable to connect to the server”. The web server becomes inaccessible at the same time. But recording, triggers and even iOS notifications work fine throughout.
Logging in via remote desktop and clicking around in Securityspy resolves the issue for another 24 hours or so. I don’t have to restart the app to fix it.
This is an installation that’s been working fine for years with the latest securityspy running on an older OS version. The problem started about the time I enabled the feature for uploading public webcam images to S3 and I’ve not had chance to try disabling that yet.
Any ideas please?
Comments
-
It's difficult to diagnose what might be going wrong here, and it's strange that simply clicking around in SecuritySpy resolves the issue temporarily.
The first thing to check is if the Mac in question is sleeping. Have you enabled the option to "Allow automatic computer sleep" under Preferences - General perhaps? Or, could someone be sleeping this Mac manually?
You mentioned that this problem started when you set up S3 uploads. This shouldn't be related, but this should be investigated by turning off these uploads temporarily to see if this resolves the issue. Please try this and report back. -
Not sure it's the same problem but the SecuritySpy web server now stops working every couple of days (no web/app access). It's an actual crash as below. This is version 5.3.4.
Thread 16 Crashed:
0 libsystem_kernel.dylib 0x00007fff6a06796e os_fault_with_payload + 10
1 libsystem_kernel.dylib 0x00007fff6a068451 __darwin_check_fd_set_overflow.cold.2 + 31
2 libsystem_kernel.dylib 0x00007fff6a05367c __darwin_check_fd_set_overflow + 68
3 com.bensoftware.SecuritySpy 0x00000001036c7c72 SEWorkerThread + 370
4 libsystem_pthread.dylib 0x00007fff6a10e109 _pthread_start + 148
5 libsystem_pthread.dylib 0x00007fff6a109b8b thread_start + 15 -
The crash appears to be related to network socket communication, and is happening in some Apple code deep within macOS that appears to do some checking of network packets. It is something we have seen before, but since this is not in our code, I don't think there is anything in SecuritySpy we can do about this. One possible explanation is some kind of bad network packet being received.
You said you are on an older OS version - what version are you running?
Can you correlate these crashes with the web server going offline? I would be surprised if this were the case; as long as you have enabled the option in SecuritySpy under Preferences > General to restart after a crash (which is on by default), SecuritySpy should automatically come right back up again and continue to function. -
It's Catalina 10.15.7. Restart after a crash is enabled, but SecuritySpy as a whole doesn't terminate when the crash occurs, just the process that faulted. Recording and triggers continue working as normal, just without web/app access until the app is restarted.
I'm using the Reolink cameras with the "bad data received" problem on reconnection. Is line 370 of SEWorkerThread connecting to cameras, or is it on the web server side?
