analysis.go AnalyzeSensorData:222 unable to analyze: could not find ***.find3.ai

[n4kre]

Hi everyone,

I'm trying to set up FIND3 in passive mode, but I cannot manage to get the learning phase properly working. Below is a sample of my main.stdout log file, showing the kind of error I keep having:

2018-05-17 09:49:11 [ERROR] [PID-14] analysis.go AnalyzeSensorData:222 unable to analyze: could not find '/data/data/HnyBvV9USQt.find3.ai'
2018-05-17 09:49:11 [DEBUG] [PID-14] db.go AddSensor:365 [foobar] inserted sensor data, 306.570142ms
2018-05-17 09:49:11 [DEBUG] [PID-14] server.go parseRollingData:959 [foobar] saved reverse sensor data for wifi-f4:8c:50:e0:e4:fd
2018-05-17 09:49:11 [DEBUG] [PID-14] server.go parseRollingData:948 [foobar] reverse sensor data: {Timestamp:1526550550364 Family:foobar Device:wifi-8c:f5:a3:e6:f2:ef Location: Sensors:map[wifi:map[rasp4-wifi:-84]] GPS:{Latitude:0 Longitude:0 Altitude:0}}

Regarding ai.stderr, this is what I constantly get:

2018-05-17 09:49:39,160 - [server/classify] - DEBUG - loading /data/data/HnyBvV9USQt.find3.ai
127.0.0.1 - - [17/May/2018 09:49:39] "POST /classify HTTP/1.1" 200 -

Does anyone have an idea on why the so called HnyBvV9USQt.find3.ai file is missing? I only have HnyBvV9USQt.sqlite3.db is in /opt/find3-data/data.

FYI:

• I launched the FIND3 server using docker run -p 8005:8003 -v /opt/find3-data:/data --name find3server -d -t schollz/find3. (It is behind a reverse proxy, accessible at https://find3.example.com.)

• I then launched find3-cli-scanner -i wlan1 -device rasp# -family foobar -server https://find3.example.com -scantime 40 -forever -passive -no-modify on each Raspberry Pi (# depending on the Raspberry Pi the command is launched from, and having set wlan1 in monitor mode for each Raspberry Pi beforehand).

• I finally started the learning mode with http POST https://find3.example.com/api/v1/settings/passive family=foobar device=wifi-b8:08:cf:af:f3:b6 location="desk=x.xxxxxx=y.yyyyyy". (the label weird name simply aims at providing the GPS coordinates of the location being learnt.)

[n4kre]

After a few hours, it eventually self-resolved: just be patient. :)

[sjcliffe]

I'm having the same issue. Left it running overnight but it hasn't "self-resolved" yet :-(