[SOLVED] daemon hangs; doesn't run without -f

[wereHamster]

I'm running the daemon on OpenSolaris (SunOS opensolaris 5.11 snv_101b). It seems as event ports don't work very well in libevent, so I have to set EVENT_NOEVPORT=1 before I start the daemon, otherwise it would abort with: Assertion failed: session->events, file trevent.c, line 377. Try setting that environment variable, maybe it will help in your situation as well.

[qwerty0987654321]

I'm running the daemon on OpenSolaris (SunOS opensolaris 5.11 snv_101b). It seems as event ports don't work very well in libevent, so I have to set EVENT_NOEVPORT=1 before I start the daemon, otherwise it would abort with: Assertion failed: session->events, file trevent.c, line 377. Try setting that environment variable, maybe it will help in your situation as well.

In my case there wasn't any assertion, just only one main thread waiting a close signal.

Thanks, Setting EVENT_NOEVPORT=1 did the thing, but daemon must be run in the foreground mode.

If we run it without -f option then we have the same problem.

[WickedWesley]

I'm running the daemon on OpenSolaris (SunOS opensolaris 5.11 snv_101b). It seems as event ports don't work very well in libevent, so I have to set EVENT_NOEVPORT=1 before I start the daemon, otherwise it would abort with: Assertion failed: session->events, file trevent.c, line 377. Try setting that environment variable, maybe it will help in your situation as well.

In my case there wasn't any assertion, just only one main thread waiting a close signal.

Thanks, Setting EVENT_NOEVPORT=1 did the thing, but daemon must be run in the foreground mode.

If we run it without -f option then we have the same problem.

Well gosh darn it! I've been running the latest transmission on opensolaris for a few days now. The web ui usually worked, unless there was some load on the box. It often took a while for a request to get through (like pausing a torrent) The most annoying thing was that the daemon sometimes becomes unresponsive. Not responding to transmission-remote or the web interface. Very annoying, because this means killing the process and having to verify each torrent again (which takes a long time, especially with 20+ 10-50GB torrents). According to top the transmission-daemon only used a 1-5% CPU.

Adding EVENT_NOEVPORT=1 and running in foreground seems to have fixed the problem. I've been running it for about an hour now and seems to have no problems. The web ui is very responsive now, the CPU usuage is now ~40% (old cpu ) So that's all good! Thank you, wereHamster and qwerty0987654321!

Wesley