[mapserver-users] Mapserver fastcgi process errors / crash

[Wim Vanbelle]

This is the full configuration:

MapServer version 6.4.1 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PROJ
SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=ICONV SUPPORTS=WMS_SERVER
SUPPORTS=FASTCGI INPUT=JPEG INPUT=POSTGIS INPUT=SHAPEFILE

On 22 June 2015 at 17:55, Wim Vanbelle <wimvanbelle at gmail.com> wrote:

> Sorry, 6.4.1
>
> Do you need the spawn-fastcgi script too?
>
> On 22 June 2015 at 17:51, Lime, Steve D (MNIT) <Steve.Lime at state.mn.us>
> wrote:
>
>>  What version?
>>
>>
>>
>> *From:* mapserver-users-bounces at lists.osgeo.org [mailto:
>> mapserver-users-bounces at lists.osgeo.org] *On Behalf Of *Wim Vanbelle
>> *Sent:* Monday, June 22, 2015 10:46 AM
>> *To:* mapserver-users at lists.osgeo.org
>> *Subject:* [mapserver-users] Mapserver fastcgi process errors / crash
>>
>>
>>
>> Hi all,
>>
>>
>>
>> Rather urgent production question. If we have some errors with our
>> shapefiles, our fastcgi processes get killed very rapidly. (we believe this
>> is some rapid error protection?)
>>
>>
>>
>> Is there a way to prevent this? We're running nginx + fastcgi mapserver
>> over unix sockets.
>>
>>
>>
>> I'm aware that we need to look into our shapefiles/dbf's but that's not a
>> simple thing because they need to be updated often.
>>
>>
>>
>> Migration to postgres is also not an option.
>>
>>
>>
>> Please let me know if we can tune this somehow. Anyone experience with
>> this?
>>
>>
>>
>> Thanks in advance!
>>
>>
>>
>> best regards,
>>
>> Wim
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-users/attachments/20150622/bb58b4ff/attachment.htm>