Notes |
(0008027)
Teravus (administrator)
2008-12-17 14:33
|
Try 7742 or later. I added something that might help. Then again, it might not. I'm not sure. but it at least fixes a locking issue which *could* cause events to not be received. |
|
(0008578)
Chri5 Somme (reporter)
2008-12-31 01:10
|
Using 7901 same Win32 .NET environment and have same issue. Problem is not resolved. |
|
(0009151)
jfhopkin (reporter)
2009-02-04 04:35
|
Have been experiencing total loss of scripting for many revisions now. Typically, it'll work fine for a few hours, then without any error message scripts will no longer run at all. Create a new box, create the default script in it and the code in state_entry() doesn't run (no llSay()), not does anything else. The workaround is to rerun the sim, when it will work again for a while.
It's possible that this is happening on a region-by-region basis - ie scripting works in one region but not in another run by the same instance of OpenSim.exe. I don't have enough information to be able to say this with certainty.
Various revisions of OS, running on Ubuntu 8.10 Intrepid with Mono 1.9.1 and 2.0, region server only, OSGrid's UGAIM, four/five regions on single instance of region server, MySQL database, XEngine running LSL only. Various simple LSL scripts for things like poseballs, lights, "teleporters", texture animation, sound playing, single, simple HUD radar, that sort of thing. No vehicles or other scripts using control keys. |
|
(0009226)
jfhopkin (reporter)
2009-02-07 13:22
|
Upgraded to 8270, same setup as before, additional information on same problem:
It certainly is region-by-region. Immediately fter a fresh restart, I logged into region B, and scripts were not working on arrival. Relogged into region T, and scripts were working fine there. Relogged again into B and not working there.
I can think of no obvious difference between the two regions that might explain this - both have a few hundred prims and perhaps 15 or so running scripts. None of the scripts in either region is particularly exotic or complex - in B, they're mainly poseballs and "teleporters" (avatar transporters using "warp" technique). There are no listening scripts, nor any chatty ones.
Log shows XEngine starting in region B, and loading the scripts there. Also shows objects containing scripts being saved. B's scripts happen to be loaded before T's (presumably, XML file order). No entry in log indicates any kind of failure from or of XEngine.
Continuing to monitor - we'd love this one to be sorted out. |
|
(0009232)
jfhopkin (reporter)
2009-02-08 05:15
|
Now running r.8242, removed one scripted object from region B, a swing using llTargetOmega(). Scripts in that region now worked. Rezzed object again, scripts still worked. Restarted, still OK. On checking, scripts in region T found not to be working - unsure if T was working before during this testing. Upgraded to r.8270, will test all regions from now on: B, T, C, H and R.
B OK
T OK
C OK
H OK
R Not OK
Noted that while scripts don't run in R, they do compile, including checking, reporting any errors and otherwise reporting successful compilation. Also noted that a script in R that handles touch_start() events causes mouse cursor to change to a hand when floated over. Only object in R is a simple touch-to-say-something scripted box, placed there just now to test if scripting works. Regions C and H contain roughly equivalent numbers and types of objects and scripts to B and T.
Will continue monitoring and report any more findings. |
|
(0009252)
jfhopkin (reporter)
2009-02-08 17:24
|
Still on 8270, rezzed "beacon" prims with LSL scripts on all five regions - scripts use llSetText() on a 1-second timer event to flash (glow) on and off and display result of llGetTimeStamp() (date & time), with another message in state_entry(). This is designed to show the time when script running stopped in each region and, in the event of a script never having started properly, whether the state_entry() event was processed. The server was restarted, and the five beacons examined in-world soon after restart was complete:
B Never run
T OK - running
C OK - running
H OK - running
R Never run
The server was again restarted, with no changes made:
B OK - running
T OK - running
C OK - running
H OK - running
R Never run
Appears to be intermittent, at least for region B; no significant difference between the way the two tests were conducted.
At this point it was noted that even though the beacon in T continued to run, flashing and updating the time on the timer() event, if a new prim was rezzed and "New script" added to the contents, this failed to be compiled or start. Other scripts already in progress on T continued to run. This isn't as simple as a "all on or all off" situation!
Server restarted a third time, and:
B OK - running
T OK - running
C OK - running
H OK - running
R Never run
Testing continues. |
|
(0009383)
jfhopkin (reporter)
2009-02-12 08:19
|
Not had time to do formal testing, but noticed a pattern that may help. Working on something else region B last night, no objects created or rezzed from inventory had scrips that would run or compile, but objects already in-world on startup were working fine. A workround was to rez the objects I'd be needing, then restart the region server and carry on working.
Hope this helps diagnose the problem. |
|
(0010127)
jfhopkin (reporter)
2009-03-25 06:45
|
To bring this up-to-date, all but one of the regions has been working fine for the last few upgrades over several weeks. Three more regions have been added, all of which are also working well in this respect.
Scripts in the "R" region, however, still do not run. In the simplest case, rezzing a cube, and clicking "New Script", will compile the script but not run it; the llSay() command in the state_entry() event is not executed. The "beacon" script in that region (see previous notes) has not run since the 8th February, according to its floating text. |
|
(0012291)
jfhopkin (reporter)
2009-06-29 14:01
|
This is no longer an issue for me. As far as I'm concerned, it's resolved - thanks to everyone. |
|