Some Members/Peers not showing up

[Murugan]

I have installed what I think you are referring to as a Superpeer -- an instance of Collanos running 24/7 on a machine with a publicly available IP who is a member of all  work spaces and thus serves to keep everyone in sync....-- the only thing is: sometimes some remote users on the team to not see the Superpeer as being online? If I do a run time check I can see, yes, it is online. shows "green for connected" in my Collanos, but not theirs.  Do we need to turn on a "switch" to tell the Superpeer to "broadcast"  his online status periodically? It is  running on a headless server and I access the UI via Remote Desktop on Mac OS X. I only drop in to make  sure he accepts the invitation to a newly created work space, but otherwise he just sits there doing nothing but "silent sync service."

[Peter Helfenstein]

Hi Murugan, the update of the presence service is not immediate. If you wait for 10-15 minutes, do the peers still not see the "server" peer as online?
Are all your peers on the newest release of Collanos Workplace (Anna will know why I ask this question :-)
Cheers
Peter

[Murugan]

I will ask those who complain that "Agni" (The Super Peer member/machine) is not showing as live... 10=15 minutes seems a Loooong time. Everyone is used to SKYPE where presence status changes are almost immediate. But, if the Superpeer is always up and on, why would it not show from the moment the other members boot Collanos... does it really take 10-15 minutes before all members on the work space who are actually online, to actually *appear* (go green) ?

[Anna Evpak]

Hello,

When space member go on line or change password it send to all space members its status with request  about other space members status.  Status check that happens each 15 minutes is made for extra sure.

Can you please clarify a bit and answer on several questions:
1. What Super-peer configuration do you have? Is it set on your local server just simple Collanos app that is always on line or it is something else?
2. Does all space members are in one local network?
3. Do you have direct connection to Internet or through your local server?
4. Do you use firewall on your PC or on your local server?
5. Can you please write in one sentence your problem? You cant communicate to space members through IV, cant send file or?

[Franco Dal Molin]

Let's be clear... Murugan simply installed a normal Collanos Workplace and leaves it running permanently on a server machine. Like this, he created a "permanently online peer" which he invites as a "member" in all his Workspaces. This helps synchronize the content with all other member peers in an almost guaranteed manner.

Small note for clarification: Only Collanos runs a small number or "super peers" (these are special Relay and Rendezvous services) on Collanos servers. So the term "super peer" should not be used for a normal Workplace that runs non-stop. ;-) We got you point anyway!

Please let us know if you continue to have presence problems. The best would be a replicable situation, so that we can try to reproduce the issue. Look for repeating patterns, and other clues that could help in narrowing down the issue. Thanks.

[Murugan]

OK I'll stop using the term SuperPeer. but you need to make up a new cool name for the "permanently online peer"  :-)
Better if Collanos team take charge of the nomenclature/lexicon.  How about "Steward Peer" or "Sleepless Peer" or "RoboPeer" (since there is no human there and all he does is try to reflect changes across from member A to member C where he is just B in the middle always away and always listening and broadcasting, hopefully but...

Meanwhile RoboPeer is not syncing  harumph...  So, not so guaranteed.

He's online, he's seen as green by other member's, when I log in via Remote Desktop, he is seeing other members as green for online... and yet, workspaces  are not being updated on RoboPeer

[admin]

I like all your terms . Ok, we'll think about a good term to use, but since this is not a separate product or even configuration, we should be careful with new names and rather try to find a good describing attribute to attach to Workplace, such as "Workplace running in unattended mode", or Sleepless Peer/Workplace is also cool.

Back to your problem: Sorry to hear you are still having issues. One good way to narrow it down could be the following tests:
1. Can the peers A, B, C chat with each other using the Workplace Instant Messenger?
2. If you create a new space and invite A, B, C without problems?
3. If 2. works, can you check if simple business objects (Task, Note, Link) work? How about Files?
4. If you have replication issues only in certain workspaces, does nothing work, or just Files?

These are just some hints or starting points. Try such a systematic approach, which will help to isolate the problem. Anna from support will get in touch with you directly via Email and assist you with this. See also the questions that she had posted here on June 11. We'll resolve this soon, I am sure.

[Murugan]

"we should be careful with new names..." agreed. it would only introduce more confusion

 Sleepless Peer/Workplace works for me. On to problems  where A is one member  C is another member and B =
 
Sleepless Peer/Workplace

Answers to your tests:

1. Can the peers A, B, C chat with each other using the Workplace Instant Messenger?
YES
2. If you create a new space and invite A, B, C without problems?
YES
3. If 2. works, can you check if simple business objects (Task, Note, Link) work? How about Files?
YES They do
4. If you have replication issues only in certain workspaces, does nothing work, or just Files?

Bingo! this is it... I create a new work space just three days called Saivite Songs. It replicated in the Sleepless Peer/Work Place.. I have the latter open via Remote desk top... I added a discussion to that Saivite Songs Work place.. and it immediate appeared  in B 


5. the workspace  "Web Server Admin" on my machine (A) has two folders:
   PCI Compliance
   Remote Database Access

on members (C and others) they see both folders  but on Sleepless Workplace (B)  only PCI  Compliance appears... If I add a task at A to PCI Compliance, it appears immediately in the PCI Compliance folder at Sleepless Workplace (B).

I have 3 other works spaces where I have added folder in work place A, where the work place appears in B but not the new folders.

So, we chasing it down to non-replication of new folders at this point. Sleepless Workplace (B) has been assign manager permissions to any work place  we invite him to, so I believe he should get everything.

OK. so now I go back to the new work place I mad three days ago and create a new folder in Saivite Songs and add a note... viola... it appears in Sleepless Workplace (B)

So, further narrowing it down to: some folders in some work places created at an earlier time are not replicating to Sleepless Workplace (B) -- whether this is a glitch that might occur again in the future we don't know but new work places create as of today are replicating as expected.

Next test:  On work place A (my machine) I go to Web Server Admin and add a new folder "Sync Test with Sleepless" and a note "Test Sync"  The new folder is replicated 

last test: go to the folder on A "Remote Database Access" that is not replicated on Sleepless Workplace (B) and enter a new note (thinking this might force an update, and replicate the missing enclosing folder as well.)

I add not to folder "Remote Database Access on A... blink: nothing happens at Sleepless Workplace (B

ergo: narrowing it down even further... possible corruption with some folders that is prevent them from replicating? I will need to check with other peers if they are see the folder "Remote database access"  I'm pretty sure they are..