YaCy-Bugtracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000175YaCy[All Projects] Generalpublic2012-03-27 19:452014-11-21 23:32
Reporterrsandu 
Assigned ToBuBu 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionno change required 
ETAnone 
PlatformOSOS Version
Product VersionYaCy 1.0 
Target VersionFixed in Version 
Summary0000175: YaCy does not allow changing peer name to a previously-used value
DescriptionHello,

I am running YaCy 1.02 in senior mode, on Debian stable, using the provided .deb package.

After a machine reboot, I've noticed that YaCy inadvertently changed the peer name to a random one (_anonXXXXX).

Trying to get the name back (using admin rights and the proper password), under Administration -> Network Configuration, YaCy won't allow me to configure the old peer name. I *am* able to change the peer name, but only to a new, unused value.

Best regards,
Răzvan
Steps To ReproduceIt happened only once, but I'm unable to regain the old name since then (no matter what name I use).
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0000957)
BuBu (developer)
2014-11-21 23:32

In General it is possible to Change the Name to a previous used Name
(under normal circumstances)
The Situation described here is, that the config was overwritten/lost on reboot, what caused the reset the peer Name to a random Name.

One side effect of this lost config is that your peer got also a new internal peer id (hash). YaCy prevents double peernames for different Peers. Because of the new ID YaCy detects that the (old)-Name is used by a other inactive peer (the entry with the old ID).

Same would happen if you intentionally delete the config. On next start YaCy generates a new peer ID and same names for different peer ID can't be allowed. This will only recover after some days after old peer ID is not longer in passive peer list.

Long Story short,
this reported behavior can't be fixed (is not a bug),

P.S. other fixes have been issued to prevent overwrite/loss of the config (the actual root cause of it all)

- Issue History
Date Modified Username Field Change
2012-03-27 19:45 rsandu New Issue
2014-11-21 23:32 BuBu Note Added: 0000957
2014-11-21 23:32 BuBu Status new => resolved
2014-11-21 23:32 BuBu Resolution open => no change required
2014-11-21 23:32 BuBu Assigned To => BuBu


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker