log entree
This i found in the log of my sdr..
Thu Jun 13 17:56:20 7d:16:03:41.221 012. child_task WARNING: child returned without WIFEXITED status=0x0000008b WIFEXITED=0 WEXITSTATUS=0 Thu Jun 13 17:56:20 7d:16:03:41.221 012. 2 L GEOLOC: 109.107.180.245 sent no geoloc info, we got "Moscow, " from geo host #0 Thu Jun 13 17:56:20 7d:16:03:41.225 012. task geoloc_task:P2:T008((1000.000 msec) TaskSleep) exited by returning Thu Jun 13 17:56:21 7d:16:03:42.015 012. 2 PWD entry timeout Thu Jun 13 17:56:53 7d:16:04:14.654 012. 2 L PWD new connection -------------------------------------------------------- Thu Jun 13 17:57:05 7d:16:04:26.217 012. 2 L GEOLOC: 109.107.180.245 sent no geoloc info, we got "Moscow, Russia" from geo host #2 Thu Jun 13 17:57:05 7d:16:04:26.220 012. task geoloc_task:P2:T008((1000.000 msec) TaskSleep) exited by returning Thu Jun 13 17:57:14 7d:16:04:35.073 012. 2 PWD entry timeout Thu Jun 13 17:57:46 7d:16:05:07.670 012. 2 L PWD new connection --------------------------------------------------------
can anyone tel e what the thing wit russia means
Comments
A bit of a long story. But the Kiwi server displays and logs the geolocation lookup of the user's connecting IP address. Because the geolocation servers have a limit on the number of lookups they will do for free per day the lookup is done from the browser of the connecting user (by the Kiwi Javascript code). This "spreads out" the IP addresses from which the lookups are performed.
But if the user connecting is not from the Kiwi Javascript (e.g. some code like a bot using the Kiwi API or something like kiwirecorder) they don't have to supply the geolocation information. In that case the lookup is performed on the server side (i.e. your Kiwi). That's why you see the message "sent no geoloc".
Note that the geolocation is shown in the "arrived" and "leaving" log messages no matter which method was used to obtain it.
Also note for your two log messages the connections were never actually completed and no data was sent ("PWD entry timeout"). Also, the information returned was different between geolocation hosts "#0" and "#2".