Closed anadahz closed 7 years ago
The issue is in looking up the Hidden Service address. Usually this will happen if your system clock is not accurate. Is that the case?
This is not the case. this system uses the tor client for other processes without any issues.
@anadahz hum, that's weird, are you able to reach the bouncer with torsocks curl http://nkvphnp3p6agi5qq.onion
?
Note: the tor client doesn't require such an up to date system clock to work properly when not connecting to hidden services.
@hellais yes i'm able to access the bouncer via torsocks
The following daily cronjobs seems to work as expected, after this day without any change. Adding an option in ooniprobe to retry bringing up tor again rather than failing after the first attempt could have been useful for such cases.
@anadahz I am not sure that restarting tor would fix the issue in this case. If the cause of the problem was in fact a clock with the wrong time restarting tor would have no effect.
We also make the assumption at this point that we do have a functioning Tor and from the looks of it that is indeed the case since the error message returned is returned by the SOCKS port when a hidden service is not reachable.
Adding logic for restarting tor would mean that we would also restart tor in the cases where the bouncer is really offline or tor is not configured properly so I don't think that is a satisfactory solution.
I'm getting different reason why it fails for same version of ooniprobe on Ubuntu/Debian:
test -f /var/lib/ooni/decks/debian-default/user.deck || exit 0
But the deck generated on installation for .my users is:
/var/lib/ooni/decks/deck-my/default-user.deck
@kaerumy do you have some error log output or provide more information on what the failure is?
This is the output when selecting daily configuration for debian package. Will need to look at the .deb file I guess why oonideckgen fails, I don't see any log or other output that shows what failed.
Subsequent runs of oonideckgen doesn't show any errors and generates and recommends usage of the deck-my config.
$ sudo dpkg-reconfigure ooniprobe
WARNING: Passing command line arguments is deprecated
Downloading https://github.com/TheTorProject/ooni-probe/releases/download/v1.5.1/ooni-resources.tar.gz to /var/lib/ooni
Written GeoIP files to /var/lib/ooni/GeoIP
Written resources files to /var/lib/ooni/resources
oonideckgen failed.
WARNING: ooniprobe will not be able to run daily.
Looking up your IP address via ubuntu
Found your IP via a GeoIP service
Deck written to /var/lib/ooni/decks/deck-my/default-user.deck
Run ooniprobe like so:
ooniprobe -i /var/lib/ooni/decks/deck-my/default-user.deck
A quick guess is that the failure is somewhere at the cron.daily/ooniprobe generation part, where it tries to generate it before the country default user deck is created.
Can we close this issue?
I am closing this as done.
Debian stretch ooniprobe 1.5.1-1
It seems that the ooniprobe cronjob fails:
/var/log/ooni/ooniprobe.log
output:Contents of:
/etc/cron.daily/ooniprobe
Contents of:
/var/lib/ooni/decks/debian-default/user.deck