Page MenuHomePhabricator

Lots of pings in logs
Open, Incoming QueuePublic

Description

In my ~/.xsession-errors logs I have lines like:

E_SYSTEM_ERR: l2ping: Can't connect socket to [F4:4E:FD:68:2C:0A]
@@@ ping timer F4:4E:FD:68:2C:0A
@@@ run new ping F4:4E:FD:68:2C:0A 5000
E_SYSTEM_ERR: l2ping: Can't connect socket to [F4:4E:FD:68:2C:0A]
@@@ ping timer F4:4E:FD:68:2C:0A
@@@ run new ping F4:4E:FD:68:2C:0A 5000

Happening each 1-2 seconds. I suspect is a configured Bluetooth device

These lines should be moved to a different debug level instead of printing by default all the time? this can make also huges log files over time

ProhtMeyhet removed ProhtMeyhet as the assignee of this task.Wed, Oct 14, 12:19 PM
ProhtMeyhet added subscribers: raster, ProhtMeyhet.

Why on Earth assign this to me? I do not know a thing about bluetooth internals and nothing really about efl.

Am I that good at moderating/administrating? :-)

Anyways, does your Bluetooth device work, because it actually it seems to look like a problem with your bluetooth device/driver/connection.

The error report is from f57572b678f20d269cd1ea474a42c2eb4c727221 from @raster

src/bin/system/e_system_l2ping.c
42 static void
43 _cb_l2ping(void *data EINA_UNUSED, Ecore_Thread *th EINA_UNUSED)
44 {

(...)

73    // connect to remote device
74    _l2ping_l2addr_init(&ad);
75    str2ba(a->dev, &ad.l2_bdaddr);
76    if (connect(fd, (struct sockaddr *)&ad, sizeof(ad)) < 0)
77      {
78         ERR("l2ping: Can't connect socket to [%s]\n", a->dev);
79         goto err;
80      }

those pings are the same thing you see when you run ping on the cmdline. if you enable some device as a lock device (blueze5/bluetooth) then e will ping that device to see it's around (it's the only reliable way i've found to know this). it will also do it if you enabled "force connect". these pings are debug so you know e is actually doing this. the device you set to a lock device is obviously not around... :)

these logs exist to help people debug these features. as there has not been a lot of feedback one way or the other the logs are there to help when that feedback is needed... :)