-
Notifications
You must be signed in to change notification settings - Fork 2
Data not showing in email #1
Comments
Are you sure that caching server actual delivers cached content to devices? The fact that it's only moving a couple 100 MBs would indicate very little usage, but is at least working. |
Have you enabled advanced logging? sudo serveradmin settings caching:LogClientIdentity Sent from my iPhone
|
I have enabled the advanced logging. I am running Server 4.1.5 on 10.10.5. Thanks for your help! Eric Hemmeter
|
Your log didn't come through... try https://www.dropbox.com/request/7MxRxC3VDpjeaIl2BOci |
Could you also run Cacher to see what it generates? I'm curious to see what difference in statistics show up as well. If not, no problem. Sent from my iPhone
|
You mean I shouldn't hard-code our Wi-Fi subnets first octet into the script? ;) |
Nice catch! I tried looking through the script and skipped right over that. Thanks,
|
Eric, Can you try the testing branch. I should have fixed your issue with the latest commit. |
I moved the old sashay.py out of the way and created a new one with the testing branch content. I then ran it manually and got this output: mini01:/usr/local/bin serveradmin$ sudo ./sashay.py The 4 most frequently seen types of devices (of 4 unique devices in total, followed by their count) were: Of the 3 different OS versions seen across all devices, the 3 most frequent were: 3 different iPhone Applications were requested 8 times, So I am getting data. Where it reports dt:86, that seems to be an iPad2,5 and dt:74 is an iPad2,1. Since attaching logs didn’t work last time, here are the relevant lines for the dt:86: and for dt:74: Thanks for the update and let me know if I can help further! Eric
|
huh, looks like 9.0 has a different longline format, thanks for the sample. This still isn't the fix because it assumes first octet is the same between client and server. Will probably just switch to a regex to catch IPs or figure out why I'm doing that field verification in the first place, I forget now. |
FWIW, Cacher isn't impacted by this, as I am looking for the values rather than explicitly calling a location in the log. Looks like get_device_stats function needs to be refactored. Time willing, I will take a stab at it. |
Eric, I noticed another interesting thing. Can you try the latest commit on the testing branch and see the following goes away?
It looks like it was always outputting a false response. |
I made the change and still get the same output. I then checked on my server with defaults and my LogClientIdentity = ‘true’ not True. mini01:~ serveradmin$ defaults read /Library/Server/Caching/Config/Config LogClientIdentity Can that check be done in a case insensitive way?
|
It isn't case sensitive. Can you ensure that you didn't set it as a string, rather than a Boolean? Sent from my iPhone
|
My output is a "1", so I'm fairly certain you have it set as a string. |
Hmm… Using the command as the tool suggests seems to set it as a string. mini01:~ serveradmin$ sudo serveradmin settings caching:LogClientIdentity = true This seems to work: As I then get: mini01:~ serveradmin$ sudo serveradmin settings caching:LogClientIdentity and sashay reports properly: The 4 most frequently seen types of devices (of 4 unique devices in total, followed by their count) were: Of the 3 different OS versions seen across all devices, the 3 most frequent were: 4 different iPhone Applications were requested 11 times,
|
Can you see what If this fixes it, I will update the readme/script. |
That works as expected. Both serveradmin and defaults report back 1 and sashay does not complain about it not being set. mini01:~ serveradmin$ sudo serveradmin settings caching:LogClientIdentity = 1 The 4 most frequently seen types of devices (of 4 unique devices in total, followed by their count) were: Of the 3 different OS versions seen across all devices, the 3 most frequent were: 4 different iPhone Applications were requested 11 times, Eric
|
Thanks for testing. I've pushed this fix to both the testing and master branch. |
You’re welcome. Thanks for a great tool!
|
Pardon the lag, should be fixed by eadd54f. Closing in anticipation that I did that right.. ;) |
I am getting emails correctly each day, but most of the data is missing.
Any advice on troubleshooting this?
Thanks!
The text was updated successfully, but these errors were encountered: