I believe i have found why all the messages for missing gestures or at least an anomoly in the viewer since update.

1)Open the active gestures floater showing gestures with missing triggers.
2)Edit one of these gestures to see trigger is still there but is not active.
3)Opening inventory shows the gesture to be active.

This is on 1.14.x viewers as well as originally reported on the FirstLook Viewer 1.13.4 (59558).

I looked into this bug further and found this one as well, I'm sure there are others.

1)Opened active gestures floater to find gesture without trigger.
2)Edit this gesture to find all info on this gesture is missing, but gesture shows active.
3)Open inventory to confirm gesture in inventory and showing active.

Again, this has only started to happen with the 1.13.4 (59558) viewer and continues with the 1.14.x viewers.

I have tried to clear my cache but it does not remedy this bug. Thanks for your help in resolving this issue.

Sorry about the file attach, I attached as a screen shot so you can see better.

Funny thing is on the third time I logged off and back on, all my active gestures loaded correctly.

1)Upon initial rez in world, I opened active gesture floater
2)You can watch as the gestures load in bunches
3)Upon failure to load active gesture I receive the following message

[9:15] Gesture is missing from database.
[9:15] Gesture is missing from database.
[9:15] Gesture is missing from database.

It doesn't happen on every logon, as it did in the first days of reporting, but seems to exacerbate when clearing cache and logging back in immediately. I cleared my cache, as the music stream on my land was intermittent. The stream works outside of Second Life on a variety of players and clearing the cache seems to help this problem.

running OSX 10.4.9 BTW

Had this issue since before 1.14, it started immediatley I downloaded the First Look viewer.
Can not be sure of which version, it could be 1.13.4 (59558), it was either the second or third last First Look before 1.14

I get at least one "Gesture is missing from database" on every login.

If I clear cache or there is a lot of lag present I then get 5 - 10 messages saying "Gesture is missing from database"

I only have about 20 gestures active so its not a number of gestures thing.
Its not a particular common distributed gesture causing the problem either, it happens to simple one line chat gestures I have made

I have a hard repeatable fault.

hopefully fixed with tommorows update

Still a hard repeatable fault.

Wonder how many others have this fault, took me nearly a month to find this thread, think title should have been "Unable to load gesture"" or "Gesture is missing from database."

http://forums.secondlife.com/showthread.php?p=1490467#post1490467

[QUOTE=Phineas Flanagan]Mostly I've noticed that it does this for Gestures that were activated during your last login. And considering I reactivate them after logging in and getting this message, they are usually the ones I activated during my last login Basically I can be guaranteed that any Gestures I created and activated during my last login will be deactivated the next time I log in.[/QUOTE]

:\ confirm that - i modified some gestures since last update - precisely because i was getting those 'gesture missing' notices to begin with. (note that i did a clean install of the new client as i usually do, trashing the entire 'application support/second life' folder, cache and all.)

while i managed to get up and rather stable thru the weekend, last night i felt time for a cache cleaning, and upon trying to relog encountered crashing every single time upon the 'missing' notice.

i just now filtered out gestures in my inventory (before it would have a chance to fully load) and deactivated/deleted all my own saved ones ;\ ... it's too early to say, but looks like that helped get me at least logged back in a stabler fashion. i still get a 'gesture missing' notice though - if it is an accurate notice, then it must be flagging one of the linden library gestures.

(corrupt gesture in their db? and then maybe my own now-corrupt gestures were compounding probs to a hard crash?)

i don't seem to see anything hear listing any kind of resolution.

If anyone wants ot talk to me about it and how to fix it i would love to hear it

I am so sick of this

1. Gestures that were active upon last login are now inactive.

Makes for a real pain when you have to go through your inventory and reactivate all the gestures again. I'm not missing any gestures, just somehow they are being deactivated. Not too handy when you make and sell gestures, lol.

Screenshot 1 from 07-02-2007

In both the gesture edit floater and inventory floaters the gesture looks active
In the gesture edit floater, the gesture shows active and there is a trigger
In the active gestures floater, there is no trigger for this gesture

Screenshot 2 from 07-02-2007

In inventory floater shows the gesture shows active
In gesture edit floter, the gesture shows not active but has a trigger
In active gestures floater, there is no trigger for the gesture

It seems very random, not always the same gestures, all though the mot recent made ones are most likely to be deactivated upon relog. But it also takes some random ones as well. Always differrent ones, please fix this. Thanks!

I WILL NOT GO THROUGH MY SECOND LIFE WITHOUT GESTURES CAUSE THE GAME DOES NOT WANT ME CHANGING THE SHORTCUTS AND HAVING TO DEAL WITH CONFLICTING SHORTCUTS, NOW IT DISABLES ALL MY GESTURES EVERYTIME I LOG IN!

AND I KNOW THIS BUG WILL NOT BE FIXED UNTIL VOICE IS IN THE GRID. AND YES I WILL COMPLAIN UNTIL THIS IS FIXED, ALONG WITH GROUP CHAT ISSUES!

LINDEN WILL NOT SHUT ME UP BY CONSTANTLY KICKING ME OFF THE GAME!

GO AHEAD AND BAN MY ACCOUNT FOR SPEAKING OUT BUT I WILL!

I DONT CARE IF YOU DELETE THIS OR NOT! I WILL BE ABLE TO USE MY GESTURES LIKE A NORMAL PERSON ONE DAY!

--A VERY DISGRUNTLED RESIDENT THAT SEEMS TO BE GETTING TOLD BY LINDEN TO LEAVE SECOND LIFE FOREVER!--

these are the three areas that should be looked at first when analising and fixing bugs with no repro's, How are we supposed to repro this? not every bug that rears it's ugly face can be reproduced.

Just becuase a bug can not be reproduced or a repro can not be found does NOT mean it shouldn't be fixed. there are ways to find these bugs with out a resedent trying to repro it.

This bug appears to be on the asset server side, Perhaps you should start there Torlay.

Most of these bugs are either in the viewer coding, or how the viewer communicates with the servers or how the viewer processes the incoming data.
These are the three areas that should be looked at first when fixing bugs that can't be repro'ed or have no known repro.
This is why most of SL's bugs remains unfixed and unresolved because LL refuses to fix bugs that can't be reproduced by a resident.

With all due respect to LL, Second life is the only online service I know of that requires a resident to reproduce a bug before it actualy gets fixed.

So if no resident is able to reproduce this bug we the SL residents are going to have to just suck it up and live with it?

Using an AV that didn't have this error, I did the following.

Pick a gesture in inventory, I chose dance8, right click and activate (I had to do this twice, it didn't activate
the first time)

Check the gestures list (ctrl-g) and see that it's in there. Log off.

Log in, open the same gesture, add a trigger /dance8, the original didn't have a command line trigger.

Log off again.

Log on, Gesture Missing from Database. Also, missing from Gestures listing (ctrl-g). Shows in Inventory as active.

Right click and deactivate doesn't work.
Right click and open, the Active check box is unmarked, still shows active in Inventory.

Toggling checkbox changes state in inventory but save button remains greyed out.
Toggling checkbox also makes it reappear in the Gestures listing (ctrl-g)

Logging out and back in results in the error message disappearing. As long as it's in the Gestures listing, it seems to be ok.

I repeated a variation on this with dance7, I activated it by right clicking in inventory (had to do it twice), I then
edited it and changed/added a trigger /dance7, then logged off. Upon logging back in I got the error and the gesture does not show in the ctrl-g gestures listing. In this instance, it showed as not activated in Inventory. Activated and logged off again.

This problem is somewhere in the updating of this listing, I should think. It's not picking up changes to gestures and/or deletions.

Hmmm, I think I better retrieve these gestures and put them back, or my accounts going to drag trying to load non-existent gestures forever. Luckily, I saved copies of everything.

I'm assuming the active gestures are saved elsewhere and are somewhat disassociated with the ones that are actually in Inventory?

Any other steps I need to do? "I had to do this twice, it didn't activate the first time" thing is definitely a bug too.

You might try deleting an active gesture from inventory without deactivating it (empty trash too), unless somethings changed in the client or server software lately, that should result in the message as well as give you an orphan gesture in your active gestures list.

When I get a chance, I'll try to reproduce it again.

I noticed this in your steps to reproduce....

• In your Inventory > Library > Gestures > Common Gestures folder, drag "dance8" to your My Inventory > Gestures folder.

If you are doing this to try and reproduce this problem here, then try it one more time EXCEPT don't drag "dance8" to the gestures folder. In my case, I started with "Common Gestures" already as a sub-folder under my main Gestures folder with the dance gestures already in it and I activated "dance8" in place, in the sub-folder, not in the main gestures folder. Not sure how I got the entire "Common Gestures" folder as a sub-folder of Gestures, but that's the state it was in when I did the test.

It's the one difference in what I did vs what you did to reproduce this problem.

Alternately, I can confirm that if you delete an active gesture that's showing in the active gesture listing from the inventory completely, emptying trash to get rid of it, the next time you log in you should get this error plus be stuck with the gesture forever "loading...."

Have you tried the second method I outlined? Basically, deleting an active gesture from Inventory without deactivating it? Now that should definitely get you this error and there'll be nothing you can do to get rid of it at that point short of going directly into the db where the active gestures are stored and wiping it out. I certainly haven't been able to do anything about my string of active gestures that I went and did that to.

If I were to theorize about what the problem is, I'd say that you store the active gesture information separately from the actual gesture in Inventory, basically when it's activated in Inventory it writes all the gesture info to another table for active gestures. And when the active gestures table is loaded, it's cross-checking against the gestures in inventory as a validation. This error occurs then, when it for some reason (incomplete data?) it can't find or see the original gesture in inventory.

I think that in certain instances when you're activating this info either doesn't get completely written or updated in the active gestures table and in the case where an active gesture is deleted, it's not getting deleted from the active gestures table. So when it goes to validate, it's not finding the gesture.

Maybe as simple as it not writing the UUID correctly in the active gestures table.

That's my theory, anyhow.

Here's a solid repo for a dual core wintel box using 1.18.0.134
Create a new gesture or Activate one
Activate it (by right clicking on it in Inventory and clicking the Activate menu
Double click to open gesture preview
Edit anything (don't click the activate checkbox yet)
Click Save button

Log off
Log back on

Note new gesture missing alert.

Technical details:
BS alert - I'm guessing when it comes to what exactly happens on the asset servers. Only LL can tell us this for sure. However, the rest I'm fairly sure that I got right.

When you click the save button a temporary asset id is created and inserted into the local inventory file, then if you have the http capability a new update message through http post is sent asynch back to asset server. Meanwhile while the post is doing its thing, if the current gesture is activated then the code tries to update the list of active gestures with the temporary asset id through an "ActivateGestures" message. This makes a call to the asset server (separate from the http post) with the temporary asset id. When the http post eventually ("eventually" depends on lag) returns it updates the local inventory item with yet another asset id.

Once the inventory file is updated then all observers are updated with the new asset id. So my guess is that the inventory database has inventory item that is pointing to an asset with the temp id because when you log back on it tries to retrieve based on that id and gets an missing from database response. It might be possible that the asset server now has 3 copies (at least) of the same asset. I do know there are at least 2 copies for every edit you make. One with the temp asset id and one with the new asset generated from the http post. I'm hoping this gets cleaned out periodically...who knows?

Workarounds until this is patched:
Stop creating more missing gestures by not editing activated gestures. Do not edit an activated gesture (deactivate from inventory, edit, save, close floater and right click and activate from inventory)

For missing gesture messages they will be shown as activated in inventory but not in the Active Gestures floater (See VWR-1944) (that's for activated ones, deativated ones you will just have to guess). Deactivate/Activate for each one (be sure that you do no other edits) and then Log off and back on.

For gestures that are not in your inventory anywhere and you are getting missing gestures messages, there is nothing you can do. Also clearing cache will not help because it is a mismatch on the asset/inventory database. LL has to clean up the asset server. I looked for a way to do this client side but could not. Note that the patch does not clean up the asset server. This patch keeps new ones from being created.

Patch is in final testing before I upload to jira.

Hopefully LL will be willing and able to clean up the database to take care of the mismatch of the deleted gestures which is plaguing me.

This implementation is similar to how notecards and scripts work when saving to the database using the LLHTTPClient to upload assets. I'm not breaking new ground here, just extending what's already been done elsewhere for notecards and scripts.

BIG NOTE: This patch does not clean up the database. Linden help is needed for that from what I can tell. If LL can provide the info to clean up mismatched assets, I will gladly code a solution.

Also have verified in testing that VWR-1944 is a dup of VWR-333.

Patch file is VWR333.patch. Tested ReleaseForDownload/ReleaseNoOpt running Vista, VS2005 (express). ReleaseForDownload was compiled and tested on production grid, ReleaseNoOpt was run in debug mode on beta grid.

Let me know if you run into any problems and I will attempt to fix.

I can't get Missing Gesture Alerts at all with any of these repro steps.. not sure why.

I am seeing that if I activate a gesture, then edit pretty much anything, although it immediately shows up in my gestures floater (ctrl G) if I log off, then log back on, it's marked as Active in the inventory window, but doesn't show up in the gestures floater. I have to open it up, activate it, then deactivate it for it to be correctly updated in the inventory.

I'm going to look into that and then ask QA here to bang on this to see if they can get more solid repro steps on this in terms of the Missing Gesture Alerts problem.

Jake

Also can you explain your comment about "all updates to everything don't get reflected in the active gesture box at all" Did you just read the patch changes or actually run a modified viewer to come to this conclusion?

Thanks

When I patch the code according to what is in the patch, I basically don't ever see any updates that I make in the Preview Gesture Window show up in the Gestures floater. They don't go away (as they do now), but they also don't update. Hence me not using this code.

I'm gonna fix WR-1944 and have QA bash on this specific bug attempting to repro. If they can't, I'm gonna close this. Fair enough?

If the asset server is not changing the asset id anymore, then I agree that my patch is certainly not needed for this SPR. From an engineering perspective I'm curious why the asset id isn't changing when before on 1.18.0.6 it clearly was and the steps listed in 1944 did in fact cause missing gesture. As far as no updates to the floater with the patched code, patching 1.18.0.6 did cause updates to floater and inventory because that was one of my test cases. Oh well, since it looks like it is fixed I'm not spending anymore time thinking about it. - Cheers.

Something has changed on the production grid since my tests last week.
Here are the results of my testing in aditi approximately 9:00 PDT Aug 10
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Loaded SL aditi using viewer 1.18.1(2)
While in Sandbox Cordova
Right clicked on FTLOG gesture in my inventory and did Copy Asset UUID (99e4df01-1f12-f0f9-af66-ce939bb8c32c)
Turned on Debug Console
Double Clicked FTLOG to load Gesture preview (Gesture preview loaded)
Changed trigger from /ftlog /ftlol
Clicked Save button
Watched Debug Console and saw this:
INFO: LLUpdateAgentInventoryResponder::uploadComplete LLUpdateAgentInventoryResponder::result from capabilities
INFO: LLUpdateAgentInventoryResponder::uploadComplete: Inventory item FLTOG saved into 96885a75-35f8-3a85-89d9-a4c103432879
Right click on FTLOG and Choose Copy Asset UUID (96885a75-35f8-3a85-89d9-a4c103442879)
Press Cntl-Q to close
Logged on again
In the Debug Console observe new gesture missing sequence:
WARNING: LLGestureManager::processTransferInfo:8b33c37f-64d6-aafb-bb92-4c86c58a2917: Non-ok status, cleaning up
WARNING: LLTransferTargetVFile:completionCallback: Aborting vfile transfer for a69b1041-0e76-6c78-7b9e-d5fa448c862f
WARNING: LLGestureManager::onLoadComplete: Problem loading gesture: -4

From my testing that I did last week I think I remember that a69b1041-0e76-6c78-7b9e-d5fa448c862f would be the id that was inserted into the local vfile.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

I've provided the UUIDs so that you can look them up to verify what I'm seeing. Note again that the production grid is working correctly and you cannot generate missing gesture using these steps. Also I noticed that if you activate a gesture you can load a new inventory window and it will show up correctly..seems to be a problem with refresh/redraw but I'll refrain from speculating further.

So the end game of this is that I would check the backend code specifically the Gesture insertion code and then provide a clean up for residents

Also while merging the source code, I noticed that someone added my name to this SPR in contributions.txt. This needs to be removed because I cannot take credit for fixing this issue regardless of prior effort.

No, not fair I think, I'm still getting the bloody message. Has anyone tried to delete an active gesture without deactivating it? Maybe the problem is fixed so it won't happen any more, I don't know and may try to do it again tp see, but what about the load of missing gestures I have that are continuously "loading" in my active gestures list? They don't exist in my inventory any more, so I can't do anything about them. I try to re-add them and I get two gestures listed with the same trigger, only one is loading forever and the other isn't.

I'll try to see if I can do my repro steps and see the cause is really fixed, but in any case the effect is still there and needs to be addressed before this is closed, IMO.

I was able to reproduce this problem on the Main Grid using the most current version of the viewer software. I also spoke to Hamncheese in world and I believe he was able to reproduce the problem too, though with an interesting twist, it took up to 2 minutes later for him to get the Missing Gesture message after relogging. So when you try to do this repro, wait for a bit.

I did the following.....

I right clicked and activated a gesture, it did not highlight (this in inconsistent now, it only happens sometimes).

I opened the gesture, the Active checkbox was checked though it did not show active in Inventory (was not highlighted nor did it say Active).

I edited the trigger and saved. It then showed as active in Inventory.

Logged off.

Logged back on, got Gesture Missing From Database, also gesture was not showing in Active Gestures. Was showing active in inventory.

So, the bug is still present, at least for us laggy folks out in the real world.

I do think this may be caused by lag or something like that interrupting the update process on the activation of the the gesture in inventory. I think the code may be "correct" for what it's trying to do, but it's not handling failure correctly. This is why this problem is being so elusive.

There are three code paths in LLPreviewGesture::saveIfNeeded;
1) Save using HTTPClient
2) Save using object inventory
3) Save using AssetStorage

When gestures are saved the unpatched code for normal users they follow path 1. Gestures in an objects inventory go through path 2. My guess is that on site (Lindens) go through path 3. The issue does not exist through path 2 or 3. Only through path 1.

My patch is bad code because while I tested path 1 and path 2, I bailed on path 3. The problem is that my patch should have left the existing code for the path 3. I will be updating this patch with a new one.

A larger question is why is the asset id changing when you go through path 1 (save using HTTPClient)? I can't answer that. Perhaps by design, but it is clear that the original code never takes into consideration that an asset id will change as part of the upload.

To fix outstanding messages that you get on log on, - once this patch hits the released client,- re activate and then edit your gestures that don't show up in the Active Gestures box (but that do show up in the inventory list as active) then log out. You shouldn't see those messages again.

Torley can tell you when this hits release

I want to also say thanks to Hamncheese and everyone working on this problem, it's great to know we can work together in getting these little bugs fixed

I wondered this as well but I let the comment stand because I could not duplicate how to get missing gesture from doing a delete. I'm still convinced that a clean up on the asset side is needed in this case. And I'm sure that this bug will be re opened many times because residents will still have the messages However I don't know enough about the back end to be able to say beyond a shadow of doubt "You need to do this"

What we have so far is a first important step which is this stops new ones. Cleaning up is a side issue that can be managed separately from this bug.

Make sense?

Cheers,

Ham

Even a screen shot up there on it.

I wouldn't even care if they just flushed all my active gestures, good and bad, I'd rather have to set them all back up than keep getting 20 missing gesture messages.

With any luck the change will check for them in inventory upon getting an error and remove them from the active gestures list if they aren't found, thereby cleaning up the problem automatically.

[22:50] Gesture is missing from database.
[22:50] Gesture is missing from database.
[22:50] Gesture is missing from database.
[22:51] Gesture is missing from database.
[22:51] Gesture is missing from database.
[22:51] Gesture is missing from database.
[22:51] Gesture is missing from database.
[22:51] Gesture is missing from database.

WARNING: LLGestureManager::onLoadComplete: Problem loading gesture: -4
WARNING: LLTransferManager::processTransferInfo: bf32b65b-beb1-ff73-221e-5d583c2
949eb: Non-ok status, cleaning up
WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for
248902cb-052b-0469-e937-1edb4015e14a
WARNING: LLGestureManager::onLoadComplete: Problem loading gesture: -4
WARNING: LLTransferManager::processTransferInfo: 37ea3544-3f6a-52f6-ef88-747c4c4
fc37a: Non-ok status, cleaning up
WARNING: LLTransferTargetVFile::completionCallback: Aborting vfile transfer for
54febe8e-6efc-e983-79ed-69c587ea57f6
WARNING: LLGestureManager::onLoadComplete: Problem loading gesture: -4
INFO: LLAgent::sendAgentSetAppearance: TAT: Sent AgentSetAppearance: HEAD UPPER
LOWER EYES

Hope this helps out.

This hasn't been fixed in a RC yet – but is targeted for 1.18.4 Viewer.

Also see the text beneath every comment field:

NOTE: The "Fixed Internally" resolution status means that the fix has been applied to a Linden Lab internal version, but is NOT in a public release of Second Life yet. "Fixed" means that the fix is confirmed public. Please do not reopen an issue unless you are sure what you are doing.

Thanks for your understanding and patience.

Second Life 1.18.4 (0) Oct 18 2007 14:36:02 (Second Life Release Candidate)

You are at 278651.6, 251524.5, 24.7 in Rlyeh located at sim1084.agni.lindenlab.com (72.5.12.234:12035)
Second Life Server 1.18.3.71877

CPU: Dual i386 (Unknown) (2160 MHz)
Memory: 2048 MB
OS Version: Darwin 8.10.1 Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386 i386
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: ATI Radeon X1600 OpenGL Engine
OpenGL Version: 2.0 ATI-1.4.56
LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000)
Packets Lost: 1004/41234 (2.4%)
Viewer Digest: dd91dc2d-99ad-49fc-86a5-9b19afacedfb

[20:48] Unable to load gesture.
Please try again.
[20:48] Unable to load gesture.
Please try again.
[20:48] Unable to load gesture.
Please try again.
[20:48] Unable to load gesture.
Please try again.
[20:48] Unable to load gesture.
Please try again.

Second Life 1.18.4 (0) Oct 18 2007 14:40:16 (Second Life Release Candidate)

You are at 282681.8, 279096.4, 35.5 in Ghloogums located at sim3393.agni.lindenlab.com (64.129.45.158:13006)
Second Life Server 1.18.3.71877

CPU: PowerPC 7450 (1249 MHz)
Memory: 768 MB
OS Version: Darwin 8.10.0 Darwin Kernel Version 8.10.0: Wed May 23 16:50:59 PDT 2007; root:xnu-792.21.3~1/RELEASE_PPC Power Macintosh
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: NVIDIA NV34MAP OpenGL Engine
OpenGL Version: 1.5 NVIDIA-1.4.18
LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_000

2007-10-20T04:57:22Z WARNING: completionCallback: Aborting vfile transfer for 387b0104-dec5-1d14-862a-316627b39704
2007-10-20T04:57:22Z WARNING: onLoadComplete: Problem loading gesture: -4
[...]
2007-10-20T05:02:11Z WARNING: _cleanupRequests: Asset download request timed out
for cc6fb816-d661-4b7a-b9b8-efdf9b88fa1b.gesture
2007-10-20T05:02:11Z WARNING: _cleanupRequests: Asset download request timed out for f7fb3790-bf6a-4834-8b1f-eaf754e4b4c9.gesture
2007-10-20T05:02:11Z WARNING: _cleanupRequests: Asset download request timed out for a49237d9-bd7f-605f-4218-4ff5042ac882.gesture
2007-10-20T05:02:11Z WARNING: _cleanupRequests: Asset download request timed out for 05effb96-2a08-47ed-9483-19273c257c66.gesture
2007-10-20T05:02:11Z WARNING: _cleanupRequests: Asset download request timed out for 1eae2ffe-6453-e668-2609-592a2a40cc2d.gesture
2007-10-20T05:02:11Z WARNING: _cleanupRequests: Asset download request timed out for 59ea72b2-57c1-4a9b-911e-e523bdc5d368.gesture
2007-10-20T05:02:11Z WARNING: _cleanupRequests: Asset download request timed out for cb3fec93-3e05-34c3-6ff1-d9119739c82d.gesture
2007-10-20T05:02:11Z WARNING: onLoadComplete: Problem loading gesture: -23016
2007-10-20T05:02:11Z WARNING: onLoadComplete: Problem loading gesture: -23016
2007-10-20T05:02:11Z WARNING: onLoadComplete: Problem loading gesture: -23016
2007-10-20T05:02:11Z WARNING: onLoadComplete: Problem loading gesture: -23016
2007-10-20T05:02:11Z WARNING: onLoadComplete: Problem loading gesture: -23016
2007-10-20T05:02:11Z WARNING: onLoadComplete: Problem loading gesture: -23016
2007-10-20T05:02:11Z WARNING: onLoadComplete: Problem loading gesture: -23016

SL crashed a minute or two later.

Interesting what SecondLife.log says about my iMac:

// CPU General Information
//////////////////////////
Processor name: Dual i386 (Unknown)
Frequency: 2000.00 MHz

Vendor:
Family:
Extended family: 0
Model:
Extended model: 0
Type:
Brand ID: Dual i386 (Unknown)
Processor Serial: Disabled

debug_info.log is a bit better:

Second Life version 1.18.4 build 0
Dual i386 (Unknown) (2000 MHz)
RAM: 1048576 KB
OS: Darwin 8.10.1 Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; ro
ot:xnu-792.22.5~1/RELEASE_I386 i386
GL_VENDOR ATI Technologies Inc.
GL_RENDERER ATI Radeon X1600 OpenGL Engine
GL_VERSION 2.0 ATI-1.4.56

Second Life 1.18.4 (2) Nov 1 2007 14:52:58 (Second Life Release Candidate)

You are at 256322.0, 262767.6, 46.7 in Diloba located at sim4357.agni.lindenlab.com (63.210.158.7:13004)
Second Life Server 1.18.3.72843

CPU: Intel Pentium 4 (Unknown model) (3013 MHz)
Memory: 2048 MB
OS Version: Microsoft Windows XP Service Pack 2 (Build 2600)
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: Radeon X1300/X1550 Series x86/SSE2
OpenGL Version: 2.0.6847 WinXP Release
LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000)
Packets Lost: 3354/941095 (0.4%)
Viewer Digest: 4d0d62ca-e703-b5e9-0b05-e8e2645e8ab5

» http://blog.secondlife.com/2007/11/07/new-viewer-second-life-1184-viewer-now-available/

For Release Notes, see:

» https://wiki.secondlife.com/wiki/Release_Notes

If still a problem (ugh, I know how annoying this is), please reopen and include log info like previous comments, and any other details we should know that'd help.

[15:13] Unable to load gesture.
Please try again.
[15:13] Unable to load gesture.
Please try again.
[15:13] Unable to load gesture.
Please try again.
[15:13] Unable to load gesture.
Please try again.
[15:13] Unable to load gesture.
Please try again.

2007-11-08T23:11:26Z INFO: updateDynamicThrottle: Easing network throttle to 702464
2007-11-08T23:11:31Z INFO: sendToSim: Sending throttle settings, total BW 735
2007-11-08T23:11:31Z INFO: updateDynamicThrottle: Easing network throttle to 752640
2007-11-08T23:11:40Z WARNING: LLCircuitData::checkCircuitTimeout for 63.210.158.39:12035 last ping 102.941 seconds ago.
2007-11-08T23:11:40Z WARNING: LLCircuitData::checkCircuitTimeout for 63.210.158.39:12035 still dead, dropping.
2007-11-08T23:11:40Z INFO: LLCircuit::removeCircuitData for 63.210.158.39:12035
2007-11-08T23:13:05Z WARNING: _cleanupRequests: Asset download request timed out for a5ed365a-d076-8db0-4aa6-d038a5f97d5d.gesture
2007-11-08T23:13:05Z WARNING: onLoadComplete: Problem loading gesture: -23016
2007-11-08T23:13:06Z WARNING: _cleanupRequests: Asset download request timed out for a1118875-a7e7-d8dc-433c-bd056ebba70e.gesture
2007-11-08T23:13:06Z WARNING: onLoadComplete: Problem loading gesture: -23016
2007-11-08T23:13:07Z WARNING: _cleanupRequests: Asset download request timed out for 2cc263c8-50c8-dd74-a24f-2773f830b3d4.gesture
2007-11-08T23:13:07Z WARNING: onLoadComplete: Problem loading gesture: -23016
2007-11-08T23:13:07Z WARNING: _cleanupRequests: Asset download request timed out for d28f4796-5390-c33f-8bd6-bbea9726c0eb.gesture
2007-11-08T23:13:07Z WARNING: onLoadComplete: Problem loading gesture: -23016
2007-11-08T23:13:08Z WARNING: _cleanupRequests: Asset download request timed out for 8ee97073-f4d7-55a4-5d7d-a9d85c397fd4.gesture
2007-11-08T23:13:08Z WARNING: onLoadComplete: Problem loading gesture: -23016
2007-11-08T23:13:09Z INFO: idle: Transmitting sessions stats
2007-11-08T23:13:09Z INFO: addToMessage: STAT: Version: 0
2007-11-08T23:13:09Z INFO: addToMessage: STAT: Vertex Buffers Enabled: 0
2007-11-08T23:13:11Z INFO: dumpReceiveCounts: Dump: 1 messages processed in 1.04877 seconds
2007-11-08T23:13:11Z INFO: ViewerStatsResponder::result
2007-11-08T23:13:19Z INFO: LLIMMgr::createFloater: from 09122cec-95e0-414e-8bdc-5691ba60079b in session 900f1316-985b-9467-3906-659a5dbe5813
2007-11-08T23:13:19Z WARNING: getCtrlByNameAndType: Widget mute_btn has improper type in panel active_speakers_panel
Is: 6
Should be: 3
2007-11-08T23:14:27Z INFO: dumpReceiveCounts: Dump: 5 messages processed in 1.17967 seconds
2007-11-08T23:16:01Z INFO: dumpReceiveCounts: Dump: 3 messages processed in 1.09843 seconds
2007-11-08T23:16:23Z INFO: dumpReceiveCounts: Dump: 5 messages processed in 1.05726 seconds
2007-11-08T23:16:46Z INFO: process_improved_im: Received IM_GROUP_NOTICE message.
2007-11-08T23:17:28Z INFO: dumpReceiveCounts: Dump: 3 messages processed in 0.569486 seconds
2007-11-08T23:17:39Z INFO: process_improved_im: Received IM_GROUP_NOTICE message.
2007-11-08T23:18:09Z INFO: idle: Transmitting sessions stats
2007-11-08T23:18:10Z INFO: addToMessage: STAT: Version: 0
2007-11-08T23:18:10Z INFO: addToMessage: STAT: Vertex Buffers Enabled: 0
2007-11-08T23:18:11Z INFO: ViewerStatsResponder::result
2007-11-08T23:20:34Z INFO: dumpReceiveCounts: Dump: 16 messages processed in 2.14734 seconds
2007-11-08T23:22:44Z INFO: dumpReceiveCounts: Dump: 4 messages processed in 1.22546 seconds
2007-11-08T23:23:09Z INFO: idle: Transmitting sessions stats
2007-11-08T23:23:10Z INFO: addToMessage: STAT: Version: 0
2007-11-08T23:23:10Z INFO: addToMessage: STAT: Vertex Buffers Enabled: 0
2007-11-08T23:23:11Z INFO: ViewerStatsResponder::result
2007-11-08T23:23:32Z INFO: dumpReceiveCounts: Dump: 8 messages processed in 0.533057 seconds
2007-11-08T23:23:37Z INFO: dumpReceiveCounts: Dump: 3 messages processed in 1.74082 seconds
2007-11-08T23:24:40Z INFO: dumpReceiveCounts: Dump: 3 messages processed in 1.19338 seconds
2007-11-08T23:25:19Z INFO: dumpReceiveCounts: Dump: 1 messages processed in 1.36325 seconds
2007-11-08T23:26:17Z INFO: dumpReceiveCounts: Dump: 5 messages processed in 1.03002 seconds
2007-11-08T23:26:30Z INFO: dumpReceiveCounts: Dump: 4 messages processed in 1.10791 seconds
2007-11-08T23:28:09Z INFO: idle: Transmitting sessions stats
2007-11-08T23:28:10Z INFO: addToMessage: STAT: Version: 0
2007-11-08T23:28:10Z INFO: addToMessage: STAT: Vertex Buffers Enabled: 0
2007-11-08T23:28:11Z INFO: ViewerStatsResponder::result
2007-11-08T23:29:02Z INFO: dumpReceiveCounts: Dump: 1 messages processed in 1.21915 seconds
2007-11-08T23:30:03Z INFO: dumpReceiveCounts: Dump: 5 messages processed in 0.578735 seconds
2007-11-08T23:30:56Z INFO: dumpReceiveCounts: Dump: 1 messages processed in 0.506905 seconds
2007-11-08T23:31:14Z INFO: dumpReceiveCounts: Dump: 7 messages processed in 0.537425 seconds
2007-11-08T23:32:07Z INFO: dumpReceiveCounts: Dump: 7 messages processed in 0.738521 seconds
2007-11-08T23:33:05Z INFO: dumpReceiveCounts: Dump: 1 messages processed in 0.584681 seconds
2007-11-08T23:33:10Z INFO: idle: Transmitting sessions stats
2007-11-08T23:33:10Z INFO: addToMessage: STAT: Version: 0
2007-11-08T23:33:10Z INFO: addToMessage: STAT: Vertex Buffers Enabled: 0
2007-11-08T23:33:11Z INFO: ViewerStatsResponder::result
2007-11-08T23:35:36Z INFO: dumpReceiveCounts: Dump: 11 messages processed in 0.74743 seconds
2007-11-08T23:35:51Z INFO: dumpReceiveCounts: Dump: 2 messages processed in 0.94211 seconds
2007-11-08T23:36:46Z INFO: dumpReceiveCounts: Dump: 5 messages processed in 0.537179 seconds
2007-11-08T23:37:33Z INFO: dumpReceiveCounts: Dump: 3 messages processed in 0.535505 seconds
2007-11-08T23:37:43Z INFO: dumpReceiveCounts: Dump: 8 messages processed in 0.532405 seconds
2007-11-08T23:37:44Z WARNING: processAvatarAppearance: AvatarAppearance msg received without any parameters, object: 839295b5-30ca-4dd9-82a1-d4508db3166e

Second Life 1.18.4 (3) Nov 7 2007 11:19:15 (Second Life Release)

You are at 282700.6, 279081.9, 25.3 in Ghloogums located at sim2880.agni.lindenlab.com (64.129.43.122:13006)
Second Life Server 1.18.3.72843

CPU: PowerPC 7450 (1249 MHz)
Memory: 768 MB
OS Version: Darwin 8.10.0 Darwin Kernel Version 8.10.0: Wed May 23 16:50:59 PDT 2007; root:xnu-792.21.3~1/RELEASE_PPC Power Macintosh
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: NVIDIA NV34MAP OpenGL Engine
OpenGL Version: 1.5 NVIDIA-1.4.18
LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000)
Packets Lost: 203/41814 (0.5%)

Me, I'd be happy if they just wiped out my entries in the Active Gestures and let me re-add them.....tired of the missing gestures and the constant "loading..."

• A friend give me a gesture (in a very lagy place).
• I have use the gesture in the moment at the same place
• i have edit her (deleting some line)
• i tp me in a other sim
• log off sometime after do that.

Since this day each time i log, i have the error message (2 years i'm here, i no use gesture, was the first time.). I will post the log (need to know where i can find it)

Second Life 1.18.4 (3) Nov 7 2007 11:13:48 (Second Life Release)

You are at 222855.4, 292932.2, 301.3 in Ganesha located at sim2379.agni.lindenlab.com (64.129.41.129:13006)
Second Life Server 1.18.5.73200

CPU: Intel Core 2 Series Processor (2394 MHz)
Memory: 2046 MB
OS Version: Microsoft Windows XP Service Pack 2 (Build 2600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 7900 GS/PCI/SSE2
OpenGL Version: 2.0.3
LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000)
Packets Lost: 1/35548 (0.0%)
Viewer Digest: 5d704dc5-72dc-f8ab-0dcc-dc1497bebe16

Tip: In inventory window search for (active) to see the gestures listed as active there and compare them to your gestures window.

Could this be related to Animations, Scripts and Textures folders under Library being empty?

On EVERY login, I receive several - from 1-10 - of these messages, and looking through my gestures folder, I find that a corresponding random number have been deactivated.

I do have a LOT of gestures active, I wonder if this is a major component of the problem?

Anecdotal evidence suggests the deactivated gestures may be those recently used but I have not been able to verify this. (It could just be that one only notices a missing gesture when it is commonly played.)

Don't suppose it's got any way to notify the server side that the thing no longer exists and to go ahead and delete it from active gestures?

If anyone at LL wants a dump of the log showing the failures and associated asset id's, let me know and I'll be happy to supply the information.

if you want to save yourself the hassle of building, it's in my Windows viewer.

(Probably the viewer could to an activate on the inventory item again, but I did not go as far as trying that)

What I'd need would be to have the viewer deactivate the gesture because they don't exist in inventory under the active asset id and so fail the check when being loaded in the active gestures.

At least that's what I believe from what I've been able to deduce (really would love to see the database schema of all the stuff on the other end, just out of curiosity).

What I think has happened in my case is that when I deleted the gestures in inventory while they were still active and emptied them from the trash, it killed them in the main inventory but did not clean up the active gestures so that now, when it loads, it checks for them in inventory and basically gets a data integrity error because there's no entry there under the uuid it has. The proper behavior would be to remove the bad data in the active gestures table or tables.

Now, I don't know if the viewer can do this, and if it can I'm unsure whether it ought to because if there were some sort of communication delay or error in the check it could conceivably deactivate gestures automatically that shouldn't be deactivated (though it does seem to still do that now, or at least in some instances it seems like gestures I've activated don't "take" and are not active when I expect them to be.

From a personal standpoint, I'd like to see my active gestures wiped out so I start over and not have these error. Also, I notice that in active gestures, they all show as "loading..." and I wonder if this is just a message or if it's still attempting to load the gesture over the entire time I'm online? I'm assuming they are not because I don't think I'm seeing any indication of it in the console log.

It happend, when i was deleting the gesture the server pinged it back on the list, then I deleted it again and yes ... later there was it the whole time. "Gesture is missing from database". Ya what gesture? From where the request comes can i not see. in the "public" gesture list is "nothing" It means it's something on my log on db, which i cannot see and that requests it over and over .

Or at least i think I know why... Here is what i did:

I created some gestures for a friend.
I moved them to a folder to be easier to pack them later.
Of course I tested them, so they were active.
I did a package with the textures.
and finally I deleted them...

And there is what i think i did wrong:

• • • I deleted the gestures while they were still active ***
      Since then, I'm getting over and over the "gesture missing from database"

I see them in the gestures edit window (they looks "loading..."), but I can't edit them.
What is funny is that if I play them they still works.

If I click the "inventory" button it don't highlight the gesture (because it doesn't exists anymore).

So I think my problem began when I deleted the gestures while they were activated.

My actual viewer is WindLight 1.18.6 (76453), but it happens the same with the normal one.
I don't remember what version I was using when I created and deleted the gestures, maybe 1.18.4, don't know for sure.

Hope this will bring some light to the fix of this annoyance.
Bye!

I've been experiencing this for about 6-7 months now, it wouldn't be so bad if it wasn't for the fact that the gestures that won't load are the speech gestures, so now I'm stuck waving my arms around everytime I speak. I don't get the "Gesture missing from database." error though, but the symptoms look the same. (i.e. gestures showing up in active gestures list with "Loading..." as a description.)

The problem seems to lie in the fact that the activated gestures are no longer in my inventory, so I have no way to deactivate them.

• • Print the name of the missing gesture in the error message

In Second Life 1.19.0 (80044) Feb 15 2008 16:44:16 (Second Life WindLight) (and some versions prior) I'm getting missing from database errors from gestures I've deleted. I deleted several after I was getting the missing from database error – even though I could click on them, open them and see that all the gesture data was in fact not missing, and even preview/play them – and I still get the message. They don't show up in the gestures window, so I can't disable them. They're in the trash.

Weird thing is that some of the gestures that are supposedly missing are from the library (copied into my inv after I activated them). Like Male Laugh, etc.

I figured deleting them would kill the message, but it hasn't. Still says they're missing from database even though:
1. They clearly aren't missing if I can click on them and open the gesture window and see all the actions and preview/play and save them.
2. They're in the trash, so it shouldn't even matter!
3. Are deactivated because they're in the trash
4. Don't show up in the gestures window (because they're in the trash)

One of the ways you can get this missing gesture message is by deleting active gestures without deactivating them, in my case I deleted them and emptied the trash so I'm stuck with missing gestures until the database is cleaned up (though recently I've not been getting them so that may have happened, or it's just not reporting them any longer).

If you believe the gestures you have deleted are the ones causing the messages, I'd urge you to restore them from the trash and do an activate/deactivate on them to see if the missing gesture error goes away because if they are the gestures linked to the gestures in the active gestures window, you don't want to delete them completely until that message goes away.

At least that's what my experience with this problem indicates should be done.

This shows gestures that don't show up in the gesture window even and those usually are the culprits. Deactivate them there (yes, doing this from inventory is buggy but usually on the second try it works) and you should be rid of these messages. In my case the gestures ended up being various system gestures.

Changes on the server or viewer side of things as to how it handles these and other gestures problems had never actually fixed it which left me with the above approach as a means for resolving my own problem with it.

Ignoring this persisting symptom of a possibly deeper problem doesn't seem like a good fix to me. Did someone at least put code in to identify the gestures by name that the system was finding exception to?

Gesture Clap is missing from database.

I've gotten that for OVER 6 months now, every single login, not just intermittent, but every single time I login, still happening today, and I finally put in a ticket on the issue today cause I'm tired of seeing it, and they referred me here, to a closed JIRA entry.

If it's fixed, why do I still get it?