Server Bugs

Bug reports on new double region crossing fixes by Pepper Linden

Before any of you who are not great with reading comprehension skills want to merge this into one of the poorly reported issues, read this carefully and ask your supervisor to read it as well. Others have reported conference chat issues recently and they got some of the symptoms in those reports, but they hadn't recognized the problem itself, so those bug reports are incorrect. One is focusing on blocked people still being able to send invitations, others focus on busy venues or regions and there are some really poorly written reports, too. Here is the issue very simply put: If someone invites hundreds of people to a conference chat at the same time, no matter the participants leave the chat, the server doesn't recognize that they had left and it keeps sending them new messages from the conference chat session. In more detail, this goes like this: 1: A well-known troll (for example Hillary Davi) collects hundreds (or thousands, I suppose) of names on their contact sets over time 2: They select all these names at once and select Send IM 3: This will attempt to open a conference chat with every target that is online at the time. Those who are online and are not in unavailable mode will be added to the conference chat participants. 4: Many people start replying to the random chat and it gets chaotic with multiple replies per second. 5: Many people leave the conference chat by closing it or automatically if they enabled Firestorm's "Automatically ignore and leave all conference (ad-hoc) chats" option 6: The issue: Due to the unusually high numbers of participants, the IM server doesn't disconnect the participants that had left the conference chat and it keeps sending them new messages. 7: This results in entirely new conference chat sessions for those who don't use the "Automatically ignore and leave all conference (ad-hoc) chats" option, starting with any new random message from a participant that keeps replying, and with a notification from the viewer for those who enabled this feature, which looks like this: You've been invited to a conference (ad-hoc) chat by Hillary Davi , but viewer automatically ignored it because of your settings. 8: This keeps going on as long as the conference chat session dies on its own or if you log out. Want to reproduce this? 1: Hang out with Hillary Davi - the best bet where to find them is Blake Sea - Sirens Isle 2: Use an account that has access to LL's internal logging tools but one that is NOT named Linden or Mole or Tester - Hillary isn't that dumb. 3: Repeat step 1 a few times. You will be added to the conference chat target contact list sooner or later. 4: Keep that account online a lot. Eventually you will receive the conference chat. 5: Close the conference chat. 6: You will receive a new one right away, showing as if the first new message's sender invited you to it. OTHERWISE you can try to reproduce this issue only using LL and test accounts, but you'll need more than 200 of them or even more, so unless you can have a huge test party at the Lab, go with the first option. I know your first question will be if I can give you chat logs, where and when exactly I received the conference messages, etcetc. The ones I have are quite outdated right now and I use the conference auto-block feature lately, but if you reply to this ticket and would like to receive such info, I'll be happy to disable it and collect some of the data for you. :)

The API to convert coordinates to region name and reverse doesn't work anymore. The server's answer always is "Invalid Capability ID." Try these example URLs from the wiki: https://cap.secondlife.com/cap/0/b713fe80-283b-4585-af4d-a3b7d9a32492?var=region&grid_x=1000&grid_y=1000 https://cap.secondlife.com/cap/0/d661249b-2b5a-4436-966a-3d3b8d7a574f?var=coords&sim_name=Da%20Boom If the API runs with PHP, maybe this malfunction began with yesterday's PHP update, or the PHP version had been changed? Since yesterday in the early morning it still worked.

The new "Post links in chat" group permission is enabled for the Everyone role in SL Baddies, but regular members' links are still being automatically removed with the message "(Link removed by group moderators)". Group owners can post links successfully. The issue persists after resetting the permission and relogging using the official Second Life viewer.

When resizing, and possible other changes, the server weight of an object gets recalculated incorrectly. Making an object smaller can increase the server weight. It seems that each script counts for 0.25 except the first. After resizing the first script counts for 0.25. At hand I have a mesh object consisting of 2 prims, and 2 scripts. Server weight is initiatially 1.2(5), but this jumps to 1.5 after a change such a resize. The land impact goes from 1 to 2 .

Sending an IM right as a user goes offline fires back an OnlineNotification right after the offline notification. I assume this is a racing condition on the server side. The issue comes from the fact this then leaves the user in a permanent online state on your end unless you relog / send another IM. Example: [11:34:14] Kalimaru: Gotta dash [11:34:19] Willow (kalimaru) is offline. [11:34:20] TrishAce: ok [11:34:21] Willow (kalimaru) is online. [11:45:35] TrishAce: <testing> [11:45:35] Willow (kalimaru) is offline. [11:45:35] User not online - message will be stored and delivered later. In this example, the notice at 11:34:11 is wrong, the user went offline. Sending an IM later (while they are offline) then correctly syncs the status as you see here

Many of the groups I am in are getting hit with people spamming in chat with scam links, slurs, harassment, etc. but you can't ban the user because they make their comment and then leave the group. They re-join later and do it all over again. You can only ban people from a group while they are in the group. Not only that, but often this constant leaving and re-joining seems to confuse the group member list so they don't come up even when they are in the group chat making comments again, so you still can't ban them. Please make a way to ban people from a group regardless of if they are in it or not. We've also had incidents where we do ban people and the exact same account is somehow still coming back in chat after being banned. This is getting ridiculous. It's happening every day, multiple times a day, in groups all over SL. We need a way to get rid of them from our groups quickly and permanently. Yes, there is an option to ban members from the group by lookup. Is is not working. They are still getting in group chat.

We did 11 races in January with all together 96 racers and have about 7-12 racers per race. A race takes normally max 40min. But there was not a single race in January all sailors finished without disconnects or thrown off the sail boat on crossing sim boarders The region "Depace" is the worst sim in the last weeks. We crash there most of the times either on the crossing into Depace or out of Depace. It happens as well when someone sails alone there. There is not much underwater stuff that needs to be rezzed long. So there is no actual reason for these crashes there. Check the sim Depace first and seriously and don't just look at some general parameters or values. Do a serious check including server address changes and all those things. The other sims start getting the same issues more and more. So the whole area is worth to be seriously checked. and i talk about all these sims: Stodierski, Mautte, Paltiete, Mon Bayete, Degrand, Sarante, Petaccio, Rexach, Betacourt, Feraco, Repaci, Castrum, Palmerston, Rafeiraga, Valdivian, Couse, Gerache, Collhaytah, Port Pawtee, Maris, Conwy, Port Gonnornertnert, Quimadra, Depace, Lavaca, Val Encia, Benach, Coull, Oprince, Getachew, Wyrldmaker, Corpening, Geffers, Costagliola, Cottier

This happens intermittently, in any region, where an object won't rez and the attached message appears. Most of the time rezzing in a different spot in that region ends up working, but on one occasion a whole region was giving this error when trying to rez. Multiple people affected.

This is an old issue that happens both with and without the changes deployed on Blake Sea (Breeze channel)