Opened 15 years ago

Closed 14 years ago

Last modified 14 years ago

#439 closed defect (obsolete)

Inconsistant seeing other users on SoaS

Reported by: CarolineM Owned by: marcopg
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: Sugar on a Stick (SoaS) Version: Unspecified
Severity: Critical Keywords:
Cc: FGrose Distribution/OS: Unspecified
Bug Status: Resolved


I have 2 SoaS running at my house. One can see other people on the schoolserver one can't. The one that can't is on wireless. However, I can browse the internet.

Change History (8)

comment:1 Changed 15 years ago by FGrose

  • Bug Status changed from Unconfimed to Needinfo
  • Cc FGrose added
  • Component changed from sugar to SoaS
  • Distribution/OS changed from Unspecified to SoaS

I see this behavior too. We should work on getting some appropriate logs to debug with.

comment:2 Changed 15 years ago by CarolineM

  • Resolution set to fixed
  • Status changed from new to closed

I haven't been seeing this lately.

comment:3 follow-up: Changed 15 years ago by CarolineM

  • Resolution fixed deleted
  • Status changed from closed to reopened

I saw this again at FOSSED.

comment:4 in reply to: ↑ 3 Changed 15 years ago by garycmartin

Replying to CarolineM:

I saw this again at FOSSED.

Thanks for the video. Next time you see this, could you blank out the jabber server on each machine (and if on VM in VirtualBox check the Network settings are not set to NAT, but bridged over the correct network interface). That should let you test locally via Salut, and likely indicate that it is jabber, or jabber server load issue related (your vid showed about 27-30 active buddies).

comment:5 Changed 15 years ago by CarolineM

Nod, when I'm at a conference its hard to stop everything and debug. We need to try to catch this in a testing session.

27 to 30 active people is not beyond what we'd expect in a school environment.

Does it make sense to assign to Martin? I suggest Martin and the testing volunteers get together and lets see if we can catch this problem in a more controlled setting.

comment:6 Changed 14 years ago by CarolineM

I suggest closing this. We have two many tickets open on collaboration issues. I'd put this as obsolete but we don't seem to have that as an option.

comment:7 Changed 14 years ago by FGrose

  • Bug Status changed from Needinfo to Resolved
  • Resolution set to obsolete
  • Status changed from reopened to closed

Obsolete is under the resolution settings.

comment:8 Changed 14 years ago by sascha_silbe

  • Distribution/OS changed from SoaS to Unspecified

Bulk change distribution=SoaS -> component=SoaS

Note: See TracTickets for help on using tickets.