I don't run the latest version. Tomorrow I will try to update the server
side. I will keep you updated.
On the server side after the server bring up we forgot to update crontab
to run the mtt cron. Is it ok to start the cron jobs now ?
I afraid the the late cron start up will cause problem to DB.
Ethan Mallove wrote:
> Hi Pasha,
> I thought this issue was solved in r1119 (see below). Do you
> have the latest mtt/server scripts?
> On Tue, May/06/2008 03:26:43PM, Pavel Shamis (Pasha) wrote:
>> About the issue:
>> 1. On client side I see ""*** WARNING: MTTDatabase client did not get a
>> As result of the error some of MTT results is not visible via the web
>> 2. On server side I found follow error message:
>> [client 10.4.3.214] PHP Fatal error: Allowed memory size of 33554432
>> bytes exhausted (tried to allocate 23592960
>> bytes) in /.autodirect/swgwork/MTT/mtt/submit/index.php(79) : eval()'d
>> code on line 77515
>> [Mon May 05 19:26:05 2008] [notice] caught SIGTERM, shutting down
>> [Mon May 05 19:30:54 2008] [notice] suEXEC mechanism enabled (wrapper:
>> [Mon May 05 19:30:54 2008] [notice] Digest: generating secret for digest
>> authentication ...
>> [Mon May 05 19:30:54 2008] [notice] Digest: done
>> [Mon May 05 19:30:54 2008] [notice] LDAP: Built with OpenLDAP LDAP SDK
>> [Mon May 05 19:30:54 2008] [notice] LDAP: SSL support unavailable
>> My memory limit in php.ini file was set on 256MB !
>> Any ideas ?
>> Pavel Shamis (Pasha)
>> Mellanox Technologies
>> mtt-users mailing list
Pavel Shamis (Pasha)