It is possible that it's Mono that's glitching here, and not OpenSim. I
ran into wapi error a long time ago. I don't remember specifics at this
point, and I don't know if what worked for me will solve your problem,
but you can give it a whirl.
Mono's wapi uses actual files to keep track of the file handles. These
are typically stored in $HOME/.wapi and on rare occasions a file in
there can misbehave. So long as you make sure you're not currently
running any Mono applications that may be using that .wapi directory, it
is safe to go in there and simply delete all of the contents. Taking
that action cleared up the wapi errors I encountered.
Marcus
On 5/7/2012 6:26 PM, Gudule Lapointe wrote:
Well of course I googled too. What I don't understand is where is the
difference between both configs, the one where it works and the one
where it doesn't.
Giving scripts always worked on the good ones (one of the "twin"
debian, one freebsd and one ubuntu), and always didn't in the bad one
(the other twin debian).
Now I have another clue: could this happen when system memory is
overloaded?
Actually my two "twin" servers do not have same charge:
- the good twin is loaded with a lighter region.
- the "bad" twin seems to work fine when only loaded with a light region.
- the "heavy" region works fine on the other systems, and these have
more RAM.
--
http://www.speculoos.net/
secondlife://speculoos.net:8002/
Speculoos, the belgian cookie-flavored metaverse
Le 7 mai 2012 à 19:48, Justin Clark-Casey a écrit :
A quick google [1] seems to indicate that these are due to attempts
to close the same (file?) handle twice.
In theory, this shouldn't cause any problem, but maybe there is
another cause of this error that is less benign.
One thing to try is cleaning out existing *.dll files in
ScriptEngines (or deleting the whole directory if you don't mind
losing script state) and see if that makes any difference.
If there's a script that persistently does not work then you could
post it on the mantis (though this is less helpful if it works in an
identical build, which I think is what you're saying?)
If this has only suddenly started happening then the most helpful
thing to do would be to git bisect the code to identify the exact
commit which triggered this.
[1]
http://mono.1490590.n4.nabble.com/wapi-handle-unref-what-does-it-mean-td1521963.html
On 07/05/12 15:29, Gudule Lapointe wrote:
When installing a new server, I get these new obscure messages in
the log:
** (OpenSim.exe:13445): WARNING **: _wapi_handle_unref: Attempting
to unref unused handle 0xe
I don't understand well, as this server is the exact replication of
another one, same OS version, same packages
installed, same opensim build... And even same region.
It seems related to some scripts, and the ones I identified were not
launching. I have no clue of the other ones, I
can't see for now what they could have in common. The two I
identified were an NPC script, and hyper gate gateway (less
in common).
I tried to launch these scripts in an empty region too, same result.
Anyone has a clue on where to look?
--
http://www.speculoos.net/
secondlife://speculoos.net:8002/
Speculoos, the belgian cookie-flavored metaverse
_______________________________________________
Opensim-users mailing list
[email protected] <mailto:[email protected]>
https://lists.berlios.de/mailman/listinfo/opensim-users
--
Justin Clark-Casey (justincc)
http://justincc.org/blog
http://twitter.com/justincc
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users
