twister

Peer-to-peer microblogging

Outils pour utilisateurs

Outils du site


fr:using:issues:known_using_issues

Différences

Ci-dessous, les différences entre deux révisions de la page.

Lien vers cette vue comparative

Les deux révisions précédentes Révision précédente
Prochaine révision
Révision précédente
fr:using:issues:known_using_issues [2014/05/21 23:04]
myleneb
fr:using:issues:known_using_issues [2014/05/21 23:21] (Version actuelle)
myleneb
Ligne 24: Ligne 24:
   * Dans le cas où la page "​Network Config"​ continue de montrer un terrifiant "​Connexions : 0" après un certain temps, essaye d'​ajouter des DNS manuellement:​ "​seed.twister.net.co",​ "​seed2.twister.net.co"​ ou "​seed3.twister.net.co"​.   * Dans le cas où la page "​Network Config"​ continue de montrer un terrifiant "​Connexions : 0" après un certain temps, essaye d'​ajouter des DNS manuellement:​ "​seed.twister.net.co",​ "​seed2.twister.net.co"​ ou "​seed3.twister.net.co"​.
    
- * Besides block synchronization which may be checked at Network page, torrent download of posts may prevent your timeline from displaying correctly. You may check posts download status at the Following page.+  ​* Besides block synchronization which may be checked at Network page, torrent download of posts may prevent your timeline from displaying correctly. You may check posts download status at the Following page.
  
   * While best efforts have been made trying to fix torrent bugs caused by twister’s modifications (basically we have a “growing torrent” file now) it seems that some corner case might still be problematic,​ preventing proper synchronization. Symptom: you compare two computers running twister and they report different number of pieces for a given user in the “Following” page. Then you make sure you have good network connectivity but your posts still don’t propagate. Ok, please be patient because sooner or later we will fix this! Restarting the deamon may help (or you may also try to debug this if you are a programmer).   * While best efforts have been made trying to fix torrent bugs caused by twister’s modifications (basically we have a “growing torrent” file now) it seems that some corner case might still be problematic,​ preventing proper synchronization. Symptom: you compare two computers running twister and they report different number of pieces for a given user in the “Following” page. Then you make sure you have good network connectivity but your posts still don’t propagate. Ok, please be patient because sooner or later we will fix this! Restarting the deamon may help (or you may also try to debug this if you are a programmer).
  
-  * bug has been seen (and hopefully fixed) which caused ​~/​.twister/​debug.log ​to grow ridiculously large (like 20GB). ​If you miss your free space you may want to check this file sizeDuring initialization ​twisterd ​should shrink ​debug.log ​whenever it gets larger than 10MB.+  * On a repéré à temps un bug qui remplissait dangereusement le fichier ​~/​.twister/​debug.log (genre 20GB). ​Si jamais tu manques d'​espace,​ regardes du coté de la taille de ce fichierÀ chaque lancement, normalement ​twisterd ​réduit ​debug.log ​s'il dépasse les 10MB.
  
-  * Followers numbers are unreliable/​not workingActually there is no easy of figuring out who follow you except by checking all usersIt should be possible, however, to find how many users are connected to your swarm (a sort of “online followers”). ​I tried using certain internal variable of libtorrent ​expecting to obtain this information ​but unfortunately I was wrongThis is still an open issue.+  * **Le nombre de followers n'est pas exact** (on peut même dire, ça me fonctionne pas du tout)En fait, ce n'est pas facile de déterminer qui te suis sans vérifier chaque utilisateurIl serait ​possible ​de connaitre le nombre d'​utilisateurs connectés à ton "swarm" ​(un genre de “online followers”). ​J'ai essayé d'​utiliser certaines variables internes de libtorrent ​dans le but d'​obternir cette information,​ mais malheureusement je me trompaisC'est une question ouverte.
  
   * Sometimes the block chain database may get corrupt, preventing twisterd from starting. You should first try the -reindex flag to see if it recovers. If it still refused to start, the solution is to completely erase the block database. So, unless you feel attached to it by some reason, erase the directories ~/​.twister/​blocks and ~/​.twister/​chainstate and let twisterd download it all over again from other peers.   * Sometimes the block chain database may get corrupt, preventing twisterd from starting. You should first try the -reindex flag to see if it recovers. If it still refused to start, the solution is to completely erase the block database. So, unless you feel attached to it by some reason, erase the directories ~/​.twister/​blocks and ~/​.twister/​chainstate and let twisterd download it all over again from other peers.
fr/using/issues/known_using_issues.1400706296.txt.gz · Dernière modification: 2014/05/21 23:04 par myleneb