Outils pour utilisateurs
fr:using:issues:known_using_issues
====== Différences ====== Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentes Révision précédente | Prochaine révision Les deux révisions suivantes | ||
|
fr:using:issues:known_using_issues [2014/05/21 22:59] myleneb |
fr:using:issues:known_using_issues [2014/05/21 23:00] myleneb |
||
|---|---|---|---|
| Ligne 17: | Ligne 17: | ||
| * **Les messages privés sont enregistrés dans le fichier user_data**. Comme les messages que tu envoies sont chiffrés avec la clef du destinataire, tu ne les verras pas sur les autres ordinateurs partageant le compte. Sauf, évidement, si tu copies le fichier user_data sur ces autres ordinateurs. | * **Les messages privés sont enregistrés dans le fichier user_data**. Comme les messages que tu envoies sont chiffrés avec la clef du destinataire, tu ne les verras pas sur les autres ordinateurs partageant le compte. Sauf, évidement, si tu copies le fichier user_data sur ces autres ordinateurs. | ||
| - | * Si le fichier user_data est **perdu ou écrasé**, les messages privés envoyés et reçus disparaîtront de l'interface html. Vous pouvez forcer twisterd à les récupérer pour en faire un fichier texte (non chiffré) grâce à la commande: | + | * Si le fichier user_data est **perdu ou écrasé**, les messages privés envoyés et reçus disparaîtront de l'interface html. Tu peux forcer twisterd à les récupérer pour en faire un fichier texte (non chiffré) grâce à la commande: |
| <code>./twisterd rescandirectmsgs my_user_name</code> | <code>./twisterd rescandirectmsgs my_user_name</code> | ||
| * **La page "Network Status" est ton amie**. Utilise-la pour tenter de résoudre les problèmes de connexion. twister needs both registration (blockchain) and DHT networks to have reachable nodes and will try to populate IP address from one to the other. The bootstrap is provided by three DNS servers. Alternatively, known peers (other computers running twister) may also be used for bootstrapping purposes. | * **La page "Network Status" est ton amie**. Utilise-la pour tenter de résoudre les problèmes de connexion. twister needs both registration (blockchain) and DHT networks to have reachable nodes and will try to populate IP address from one to the other. The bootstrap is provided by three DNS servers. Alternatively, known peers (other computers running twister) may also be used for bootstrapping purposes. | ||
| + | |||
| * In case Network status page still reports “Connections: 0″ after a while try manually re-adding DNS seeds “seed.twister.net.co”, “seed2.twister.net.co” or “seed3.twister.net.co”. | * In case Network status page still reports “Connections: 0″ after a while try manually re-adding DNS seeds “seed.twister.net.co”, “seed2.twister.net.co” or “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). | ||
| + | |||
| * A 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 size. During initialization twisterd should shrink debug.log whenever it gets larger than 10MB. | * A 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 size. During initialization twisterd should shrink debug.log whenever it gets larger than 10MB. | ||
| + | |||
| * Followers numbers are unreliable/not working. Actually there is no easy of figuring out who follow you except by checking all users. It 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 wrong. This is still an open issue. | * Followers numbers are unreliable/not working. Actually there is no easy of figuring out who follow you except by checking all users. It 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 wrong. This is still an open issue. | ||
| + | |||
| * 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. | ||
| + | |||
| + | \o/ | ||
fr/using/issues/known_using_issues.txt · Dernière modification: 2014/05/21 23:21 par myleneb
Outils de la page
Sauf mention contraire, le contenu de ce wiki est placé sous les termes de la licence suivante : CC0 1.0 Universal
