The API logging... it burns us (2.5.2.3)

maybe because i’m using the SGP API guider, my logfile is enormous… 1.2GB after just 2 hours of operation. i think i’m going to have to go back to 2.5.2.1 or else my boot disk is going to fill up.

rob

1 Like

lots of stuff like this:

[10/9/2016 11:59:31 PM] [DEBUG] [Unknown] API Request:
[10/9/2016 11:59:31 PM] [DEBUG] [Unknown]  * Endpoint: (POST) - /json/reply/SgGetGuiderImage
[10/9/2016 11:59:31 PM] [DEBUG] [Unknown]  * Operation: SgGetGuiderImage
[10/9/2016 11:59:31 PM] [DEBUG] [Unknown]  * Body: {"Receipt":"f44f1322-37a9-4cbe-9334-4931261171c1"}
[10/9/2016 11:59:31 PM] [DEBUG] [Unknown] API Response:
[10/9/2016 11:59:31 PM] [DEBUG] [Unknown]  * Endpoint: (POST) - /json/reply/SgGetGuiderImage
[10/9/2016 11:59:31 PM] [DEBUG] [Unknown]  * Operation: SgGetGuiderImage
[10/9/2016 11:59:31 PM] [DEBUG] [Unknown]  * Body: {"ImageData":null,"Message":"No image found for receipt: f44f1322-37a9-4cbe-9334-4931261171c1","Success":false}
1 Like

This is on just for the PEMPro debug session and will be turned off shortly.

OK thanks, i am running on one of those compute sticks with not a lot of disk space. i’ll have to wait until the next build comes out to test the .3 fixes.

I’ll release another one tonight that is pretty much the same as 2.5.2.3, w/o the logging. Folks that want to engage in PEMPro testing can just pull 2.5.2.3.

Hopefully I’ll be able to test the PEMPro integration tomorrow night.

I found the same problem, and the log file size blow up to 14G. Hope the new version. :wink:

1 Like

Everyone keep in mind that this is a beta. Often we add additional logging to help us track down errors and remove that logging when we release an actual beta.

Thanks,
Jared

We’re gonna need a bigger drive. :fish:

In the latest beta (2.5.2.4) you can turn the API logging off. The default
is off.

1 Like

cool. the pempro thing will be great. i’ve not been able to use it due to not having maxim or an otherwise supported camera. thanks for making the logging optional.

1 Like