Request failures continuous in web log

[simonbcn]

I have received this request failures continuously in the Log tab of webUI:

[Ultima]

Heh, that'll probably cause WebUI to show a big error message asking for a refresh after a minute or so. The problem is that whatever version of µTorrent you're using doesn't support those requests.

action=getxferhist works in µTorrent v3.0 (Windows)

action=getversion doesn't

If it's µTorrent Linux v3.0 that's causing this, then that's certainly an odd oversight for them to have left it in there.

[simonbcn]

It's the utserver (Linux) version.

[Ultima]

Does it happen always?

[simonbcn]

I think that it occurs when I restart the daemon. I have to test it more.

[Ultima]

Well, if you restart it, then naturally it'll have problems connecting until the daemon finishes starting up and is reachable again.

[simonbcn]

Well, if you restart it, then naturally it'll have problems connecting until the daemon finishes starting up and is reachable again.

Well, when utserver starts, webUI starts. If utserver is down, the webUI is down too.

[Ultima]

Yeah... is that unexpected? I'm really curious as to what you're expecting to happen -- or not happen -- here when the server is brought down.

[simonbcn]

Well, if you restart it, then naturally it'll have problems connecting until the daemon finishes starting up and is reachable again.

I haven't talked about connecting problems. I have talked about errors in Log tab of webUI.

Yes, I know that if the daemon is down, I can't connect to webUI. It's normal!

When I said:

I think that it occurs when I restart the daemon. I have to test it more.

I meant that I think this happens every time I start the daemon.

[Ultima]

I haven't talked about connecting problems.

Indeed, you didn't, but the only reason I keep bringing it up is because the logger displays that error message when the request fails, whether because the backend can't be reached, or because the backend rejected the request (and I find rejection of the request only at startup to be highly unlikely). That's why it is a connection error, and that's why I keep talking about an unreachable backend while the daemon restarts.

Maybe I'm misunderstanding the point of this thread. If you're writing here just to document the behavior, fine then. It's just that it was in the Troubleshooting forum (albeit without any question), so I thought I'd explain it.

[simonbcn]

The utserver starts the webUI. If when webUI asks something to utserver and this isn't prepared to answer, there is a problem! Don't you think?

And now I verify that the problem happens always, every certain amount of time:

[Ultima]

It isn't really a problem if WebUI recovers from the error -- that's what the error recovery through request retrying was implemented for. I'm not sure what happens here, but if the server is opening the browser, then the only fix would be for it to delay when it launches the browser, which isn't exactly "better".

[simonbcn]

The server isn't opening anything.

The utserver starts (in the same manner that µTorrent Windows) the webUI server.

When I open the webUI in my browser, the webUi starts correctly but, in Log tab, I see that messages.

[Ultima]

I guess the server is lazy-loading services. Alrighty then, I suppose that's perfectly fixable from the server's side -- just don't serve up the webui.zip files until the backend is ready to take requests, or something.

[simonbcn]

No, your conclusion is incorrect:

The server was started at 20:26hs but the errors continues.

[Ultima]

Your screenshots don't make it easy to tell whether or not the problem persists beyond session start (page load).

[simonbcn]

Or my english is very bad or I don't understand nothing!

Are you saying that this error is produced by loading the webUI? And this is correct for you?

[Ultima]

I'm not saying or implying trying to imply anything. I'm just trying to determine whether the problem happens only on page load after a daemon restart, at the beginning of every page reload (WebUI session start -- inter-session), or continuously as you use WebUI without reloading the page (intra-session).

[simonbcn]

I'm not saying or implying anything. I'm just trying to determine whether the problem happens only on page load after a daemon restart, at the beginning of every page reload (WebUI session start), or if it happens continuously as you use WebUI.

Well, I can confirm that it occurs at the beginning of every page reload.

[Znarkus]

Everytime I click the "Logger" tab, there is a message "[21:53:09] Request failure #1 (will retry in 2 seconds): action=getxferhist". It never seems to retry.

There is just this single message. The timestamp is changed to current time everytime I hit refresh.

I am using the Linux alpha version

[Ultima]

If it doesn't add another entry to the logger, then it did retry, and it successfully received the response.