Open amm042 opened 4 years ago
Could it be because we have multiple network controllers each writing a syslog for the same date?
The current dataframe is tied to one source file but the AP_traj are by DATE?
Here is my data directory: -rw------- 1 amm042 cs 211K Jun 18 11:44 20200604-172.30.121.21-wifitrace.csv -rw------- 1 amm042 cs 238K Jun 18 11:46 20200604-172.30.121.23-wifitrace.csv -rw------- 1 amm042 cs 300K Jun 18 11:46 20200604-172.30.121.25-wifitrace.csv
Thanks @amm042 for raising the issue. I think you are right about multiple syslog files for same date from multiple controllers.
Since a device might roam around multiple controllers for a single date, to create the entire mobility trajectory of the device I consolidated (basically concatenated) all syslog files of all APs/controllers for a single date into one large syslog file and then give that consolidated event file as the input to the tool.
So, for the correct functioning of the tool and generation of output reports I would suggest consolidating all syslogs for a single date into one file. Please let me know if any error comes up after that.
I concatenated the controllers logs to one csv for each day, but still see the error.
Do you mean, you have one single input csv file containing all days of interest?
At the beginning of get trace, I had to add this, it seems to work correctly.
for date in past_n_days:
AP_traj_list = []
AP_traj_start_list = []
AP_traj_end_list = []
AP_duration = []
I am glad to hear that it is working correctly now. Thanks for sharing the fix, in case someone else is facing a similar error.
One follow-up question. Can you share the version of HP Aruba OS? It would be something like ArubaOS_
Currently on 8.6.0.4. Waiting for 8.6.0.5.
On Thu, Jun 25, 2020 at 8:03 AM Amee Trivedi notifications@github.com wrote:
I am glad to hear that it is working correctly now. Thanks for sharing the fix, in case someone else is facing a similar error.
One follow-up question. Can you share the version of HP Aruba OS? It would be something like ArubaOS__Syslog.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/umassos/WiFiTrace/issues/1#issuecomment-649499015, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABRHBOT4226GAKWOVODD22TRYM4I3ANCNFSM4OCXPGUA .
-- Alan Marchiori | Bucknell University | Dana 327 Assistant Professor of Computer Science Calendar: https://calendar.google.com/calendar/embed?src=amm042%40bucknell.edu https://calendar.google.com/calendar/embed?src=amm042%40bucknell.edu&ctz=America%2FNew_York Appointments: https://calendar.google.com/calendar/selfsched?sstoken=UUNGd08xclV2MHphfGRlZmF1bHR8YzAzMzU2NzgwYmQ1MDBjNmFkYTgxZjQzODgwNTIzZDQ
in contact_trace.py, line 577:
I'm getting an exception that the lengths do not match the length of the index, the console output is: 705 705 705 705 705 705 705 275
This shows in the index length is only 275, but the data lengths are 705.
I'm not sure what might cause this problem. Do you have any advice?