New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 918206 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 912801



Sign in to add a comment

shill: rate limit DNS error

Project Member Reported by gwendal@chromium.org, Dec 28

Issue description

Looking at crbug.com/912801 , where kiosk eMMC seems to have run out of spare blocks, I notice a lot of DNS related error in messages and net.log:

Form log in crbug.com/912801: the errors are:
2018-11-17T14:36:45.404433-06:00 ERR shill[898]: [ERROR:error.cc(138)] [dns_client.cc(149)]: ARES set DNS servers error code: 17
2018-11-17T14:36:45.404464-06:00 ERR shill[898]: [ERROR:http_request.cc(125)] Failed to start DNS client: ARES set DNS servers error code: 17

They happen every around 5s.




 
err_17_extract.txt
3.2 KB View Download
Cc: briannorris@chromium.org kirtika@chromium.org
It looks like the portal detector is attempting to start the DNS client with malformed DNS server strings, resulting in ARES_EBADSTR (error code 17).

In crbug/912801, I see this in the net.log:

2018-11-18T16:02:09.982478-06:00 INFO shill[898]: [INFO:dhcpv4_config.cc(123)] Event reason: BOUND
2018-11-18T16:02:09.982749-06:00 INFO shill[898]: [INFO:connection.cc(281)] UpdateFromIPConfig: Installing with parameters: local=<IPv4: 1> broadcast=<IPv4: 4> peer=<unknown> gateway=<IPv4: 5>
2018-11-18T16:02:09.983393-06:00 INFO shill[898]: [INFO:service.cc(399)] Service 5: state Configuring -> Connected
2018-11-18T16:02:12.517807-06:00 INFO shill[898]: [INFO:manager.cc(1500)] Service 5 updated; state: Connected failure Unknown
2018-11-18T16:02:12.548983-06:00 WARNING shill[898]: [WARNING:resolver.cc(72)] Malformed nameserver IP: 
2018-11-18T16:02:12.549444-06:00 WARNING shill[898]: message repeated 3 times: [ [WARNING:resolver.cc(72)] Malformed nameserver IP: ]

From the log, we can see that the IP config has somehow been botched (the nameserver IP is empty), resulting in the DNS failures. I'm guessing that this is a symptom of the bug as opposed to the cause.
Labels: Enterprise-Triaged

Sign in to add a comment