kerberos-io/agent

Disable uploads

Hooch76 opened this issue · 8 comments

Hi,

is there a way to disable uploading mp4 files?

2023-03-15T12:47:56+01:00 INF msg=UploadS3: Upload started for .mp4
2023-03-15T12:47:56+01:00 ERR msg=UploadS3: Uploading Failed, Bucket name cannot be empty

There are is nothing configured in Settings -> Persistence: Kerberos Hub and Persistence.

I am aware of the option "Offline mode", but that also disables MQTT (which is running locally) so this does not help.

Thanks.

Icemic commented

notices this silent uploading too, which causing tranfer data up to 100GiB per day!

The target ip address is 35.187.121.96 which seems to be a proxy.

Where was it uploading to? And how you treat those data? Since I did NOT add any config of Kerberos Hub but keep it as default

We will add a disable upload option asap, (similar to offline mode), or disable it if no credentials are set. https://github.com/kerberos-io/agent/blob/master/machinery/src/cloud/Cloud.go#L53

I have added a fix, please pull latest release! ;) Thanks for opening this issue! 58c3e73. Please close if sufficient.

Hi,

I am using kerberos agent d9694ac and those lines are no longer appearing in the logs, so this seems to be fixed:

INF msg=UploadS3: Upload started for .mp4
ERR msg=UploadS3: Uploading Failed, Bucket name cannot be empty

I don't know if it is related, but now I see every 30s or so:

RR msg=HandleHeartBeat: (400) Something went wrong while sending to Kerberos Hub.

I've to wait for something moving in front of the camera to be able to tell if MQTT is still working though ;-)

Update ... this is how it looks like now:

INF msg=HandleRecordStream: Synced file: 1679313244_6-967003_xxyyzz_200-200-400-400_1082_769.mp4
INF msg=HandleRecordStream: motion detected while recording. Expanding recording.
INF msg=Received message with recording data, detected changes to save: 8999
ERR msg=UploadS3: Uploading Failed, as no credentials found
ERR msg=UploadS3: Uploading Failed, as no credentials found
ERR msg=UploadS3: Uploading Failed, as no credentials found
INF msg=HandleStream: packet size 36379
INF msg=HandleRecordStream: Synced file: 1679313244_6-967003_xxyyzz_200-200-400-400_1082_769.mp4
INF msg=HandleRecordStream: motion detected while recording. Expanding recording.
INF msg=Received message with recording data, detected changes to save: 7026
ERR msg=UploadS3: Uploading Failed, as no credentials found

@Hooch76 let me check the heartbeat. Yes this is expected! We might get rid of the uploaded recordings if no credentials are set. I believe it will now keep uploading recordings.

This has been fixed by 71cd315. Thanks @Hooch76