Hi sajolida,
Thank you for responding.
I was connected to the Internet, but with regard to answering the 2nd question there appears to be an ambiguity in the phrase "Tor was ready" when the message appeared, at least according to my understanding as described below.
The normal sequence I have recorded when Tails boots up is that I have my router turned off so that I can setup my preferences in torrc, and run macchanger.
When I turn the router on, I get the following 3 messages in a small black oval: Note: I am starting to keep a log of the 24 hour time each occurs
21:34:11 Connected to eth0 (i.e. Internet with regard to your question)
21:34:11 Syncing the system clock
21:35:50 Tor is Ready
When Vidalia (Yellow status appears) I am monitoring the Message Log, The Vidalia Control Panel, The Bandwidth and the Network Map with the results:
From the Message Log:
21:35.52 (for both) Tor software is running and Connected to Tor Network
21:45:21 Vidalia Green (just under 10 minutes)
The ambiguity mentioned above is due to the fact that two different events are reported with the same text message output:
21:35:52 Connected to the Tor Network (from the Message Log) <----- This is when Vidalia is still in Yellow Status and No websites in Connection (Network Map)
21:45:21 Connected to the Tor Network (from the Vidalia Control Panel Green Status) <---- This is the real deal when the Bandwidth starts to paint
I do not consider that "Tor is ready" until the Connection Map subpart of the Network Map window is populated which took about 10 minutes in the above sequence to occur. I consider that the above message at 21:35:50 for Tor is Ready really indicates that the system clock has been successfully synchronized, and that the message at 21:35:52 Connected to Tor Network does not fully mean that the Tor Network is actually ready or safe for a user to use at that point in time.
I probably got the message due to my use case of not being connected to the Internet while I was doing my standard setup as described with the router off. This may indicate that the launching of Tails Upgrader instead of being launched silently at the beginning of each working session should more properly be tied to the notion of being connected to Internet as you asked in your question. I'm guessing that the Tails Upgrader was already initiated during the time that my router was off, and that whatever state the Tails Upgrader was in when I turned on the router was what initiated the error message I experienced.
-- Tom
Thank you for responding.
I was connected to the Internet, but with regard to answering the 2nd question there appears to be an ambiguity in the phrase "Tor was ready" when the message appeared, at least according to my understanding as described below.
The normal sequence I have recorded when Tails boots up is that I have my router turned off so that I can setup my preferences in torrc, and run macchanger.
When I turn the router on, I get the following 3 messages in a small black oval: Note: I am starting to keep a log of the 24 hour time each occurs
21:34:11 Connected to eth0 (i.e. Internet with regard to your question)
21:34:11 Syncing the system clock
21:35:50 Tor is Ready
When Vidalia (Yellow status appears) I am monitoring the Message Log, The Vidalia Control Panel, The Bandwidth and the Network Map with the results:
From the Message Log:
21:35.52 (for both) Tor software is running and Connected to Tor Network
21:45:21 Vidalia Green (just under 10 minutes)
The ambiguity mentioned above is due to the fact that two different events are reported with the same text message output:
21:35:52 Connected to the Tor Network (from the Message Log) <----- This is when Vidalia is still in Yellow Status and No websites in Connection (Network Map)
21:45:21 Connected to the Tor Network (from the Vidalia Control Panel Green Status) <---- This is the real deal when the Bandwidth starts to paint
I do not consider that "Tor is ready" until the Connection Map subpart of the Network Map window is populated which took about 10 minutes in the above sequence to occur. I consider that the above message at 21:35:50 for Tor is Ready really indicates that the system clock has been successfully synchronized, and that the message at 21:35:52 Connected to Tor Network does not fully mean that the Tor Network is actually ready or safe for a user to use at that point in time.
I probably got the message due to my use case of not being connected to the Internet while I was doing my standard setup as described with the router off. This may indicate that the launching of Tails Upgrader instead of being launched silently at the beginning of each working session should more properly be tied to the notion of being connected to Internet as you asked in your question. I'm guessing that the Tails Upgrader was already initiated during the time that my router was off, and that whatever state the Tails Upgrader was in when I turned on the router was what initiated the error message I experienced.
-- Tom
[email protected]:
> I got the following error message window block which I term false positive due
> to the fact that Tails 0.22.1 is the latest release and should probably not be
> getting this error:
>
> Error while checking for upgrades
>
> Could not determine whether an upgrade is available from our website.
> Check your network connection, and restart Tails to try upgrading again.
> If the problem persists, go to
> file:///usr/share/doc/tails/website/doc/upgrade/error/check.en.html
> Debugging information
> exit code 29440
>
> stdout:
> stderr: cound not download
> 'https://tails.boum.org/upgrade/v1/Tails/0.22.1/i386/stable/upgrades.yml',
> request filed (couldn't connect to server): can't complete SOCKS5 connection to
> 0.0.0.0.0(6) at /usr/bin/tails-iuk-get-upgrade-description-file line 21
>
> After writing this information down (seems like this information should be
> logged somewhere for the user to reference in a report), I clicked on the OK
> button, however, Tails 0.22.1 booted up just fine which is why I termed it a
> false positive.
Tails Upgrader is launched silently at the beginning of each working
session. This is needed to be able to check *whether* they are new
versions available, and this has to be done even if you are running the
latest version (at least until some new version comes up).
But in order to understand better why you faced this error, can you tell
us whether you were connected to the Interet, and Tor was ready when
this message appeared?
_______________________________________________
Tails-support mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-support
> I got the following error message window block which I term false positive due
> to the fact that Tails 0.22.1 is the latest release and should probably not be
> getting this error:
>
> Error while checking for upgrades
>
> Could not determine whether an upgrade is available from our website.
> Check your network connection, and restart Tails to try upgrading again.
> If the problem persists, go to
> file:///usr/share/doc/tails/website/doc/upgrade/error/check.en.html
> Debugging information
> exit code 29440
>
> stdout:
> stderr: cound not download
> 'https://tails.boum.org/upgrade/v1/Tails/0.22.1/i386/stable/upgrades.yml',
> request filed (couldn't connect to server): can't complete SOCKS5 connection to
> 0.0.0.0.0(6) at /usr/bin/tails-iuk-get-upgrade-description-file line 21
>
> After writing this information down (seems like this information should be
> logged somewhere for the user to reference in a report), I clicked on the OK
> button, however, Tails 0.22.1 booted up just fine which is why I termed it a
> false positive.
Tails Upgrader is launched silently at the beginning of each working
session. This is needed to be able to check *whether* they are new
versions available, and this has to be done even if you are running the
latest version (at least until some new version comes up).
But in order to understand better why you faced this error, can you tell
us whether you were connected to the Interet, and Tor was ready when
this message appeared?
_______________________________________________
Tails-support mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-support
_______________________________________________ Tails-support mailing list [email protected] https://mailman.boum.org/listinfo/tails-support
