Cinder do you by chance know what the heck goes in the [AssetService]
section (and in Services for that matter) when you're configuring to run
the AssetService on a seperate port? I have things working for local
region access because they can get to the private asset specific port
but the HGAssetService doesn't know where to find it so suitcase
operations are failing. And all of this is just not documented as far
as I can tell.
Otherwise the Go based AssetService looks like an awesome solution!
Mike
On 2018-11-16 06:01, Cinder Roxley wrote:
Yes, it’s meant to run as a drop-in replacement for fsassets service to
avoid hellish migration times. I have a version utilizing ceph for
distributed storage, but the version on GitHub is just meant as an
fsasset
replacement for precisely these issues.
On November 16, 2018 at 9:54:34 AM, mike.dick...@rivendellnh.com (
mike.dick...@rivendellnh.com) wrote:
I'm running fsassets yes. And yes thats the behavior I think I'm
seeing. Though its not exhausting physical memory. Just virtual.
Cinder I pulled down your repo and built it. Checked the help text. It
looks like it should work over the top of the fsassets data I already
have? I may set up a test environment first but if thats the case I'm
happy to give it a go (pun intended).
Mike
On 2018-11-16 02:45, Cinder Roxley wrote:
On November 15, 2018 at 10:52:02 AM, Mike Dickson (
mike.dick...@rivendellnh.com) wrote:
Seems based on load. They'll run overnight and late morning one will
crash
w/the other usually a minute or 2 behind it. I've investigated lots of
possibilities. Plenty of file handles available. It's not ephemeral
port
exhaustion. I have systemd set up to auto restart the processes.
Systemd
reports an exit status of 1. But the pid file isn't cleaned up and
there
are no crashes. Happens regardless of the mono version I run.
Which asset service are you running? There are three, iirc. FSAssets
has
particularly nasty resource leaks. These lead to memory exhaustion and
eventually the OOM killer puts a bullet in its head. Check if this is
the
case via /var/log/messages. This is also why I had suggested trying my
alternative asset service written in Go which uses a fraction of the
memory
and scales out quite nicely.
_______________________________________________
Opensim-dev mailing list
Opensim-dev@opensimulator.org
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
Opensim-dev@opensimulator.org
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
Opensim-dev@opensimulator.org
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
_______________________________________________
Opensim-dev mailing list
Opensim-dev@opensimulator.org
http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
