Hello!

I'm running a dozen of Tcl applications inside Apache with mod_rivet for several years.

Recently I've upgraded. Now

Debian is release 8 jessie
Apache is Apache/2.4.10 (Debian)
Tcl is ActiveTcl 8.6.4
Rivet is SVN Rivet/2.3.0

Every application is running in it's own virtual host and it's own child interpreter. Theese child interpreters are created by my custom init script

RivetServerConf ChildInitScript "source /etc/apache2/rivet-childinit.tcl"

# RivetServerConf SeparateVirtualInterps no


I'm running apache with LogLevel debug.

Now two kind of error messages appear in apache's error.log.

First:

[Thu Sep 03 13:44:47.316904 2015] [:debug] [pid 6558] mod_rivet/rivet_prefork_mpm.c(49): (20014)Internal error: mod_rivet: Running prefork bridge finalize method [Thu Sep 03 13:44:47.316923 2015] [:debug] [pid 6558] mod_rivet/mod_rivet.c(464): Thread exiting after 0 requests served (18 vhosts)

Theese messages are repeated about every 20 seconds. I belive pefromance is degraded now since apache child processes die often after processing zero requests. Child processes are supposed to keep persistent database connections in my applications.

Am I wrong about perfomance degradation?

Second message kind appears only if I enable single one of my dozen of applications:

Tcl_AppendStringsToObj called with shared object
[Thu Sep 03 13:46:12.423202 2015] [core:notice] [pid 30351] AH00051: child pid 6017 exit signal Aborted (6), possible coredump in /tmp

This message goes away if I disable virtual host for this one application. When this special application is enabled "signal Aborted" hits this application AND other applications too. Confirmed it looking and PIDs of apache children processing application requests.

I've tried to identify special application features that cause the errors, but without success :( Of course, this application runs without problems with older versions of Apache, Tcl and Rivet.

How to find the reason for "signal Aborted"? Please, help!

--
Best regards, Anton.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to