[mapserver-users] Mapcache segmentation faults under high load

[Pieter Callewaert]

Hi Andreas,

Using Ubuntu 16.04 instead of Ubuntu 14.04 fixed the issue, thanks for your help.

Kind regards,
Pieter Callewaert

-----Original Message-----
From: Eichner, Andreas - SID [mailto:Andreas.Eichner at sid.sachsen.de] 
Sent: Thursday, 9 March, 2017 11:23
To: Pieter Callewaert <pieter.callewaert at be-mobile.com>; mapserver-users at lists.osgeo.org
Subject: AW: [mapserver-users] Mapcache segmentation faults under high load

Hi Pieter,

have you tried it on a different OS or just on different hardware?
To me it looks as if it happens somewhere in a C library call. 
Have you a chance to try it on another OS and/or library versions?

> -----Ursprüngliche Nachricht-----
> Von: mapserver-users [mailto:mapserver-users-bounces at lists.osgeo.org] 
> Im Auftrag von Pieter Callewaert
> Gesendet: Donnerstag, 9. März 2017 09:09
> An: mapserver-users at lists.osgeo.org
> Betreff: Re: [mapserver-users] Mapcache segmentation faults under high 
> load
> 
> Hi,
> 
> I’ve been testing further, on other servers to eliminate hardware 
> failures, but I keep getting consistent this problem.
> I made now consistent the same core dumps, I think my first core dump 
> was not a correct one.
> 
> http://pastebin.com/L0Lhru4m
> 
> You can see at start:
> 1. Program terminated with signal SIGSEGV, Segmentation fault.
> 2. #0  process_socket (my_thread_num=42, my_child_num=<optimized out>, 
> cs=0x7fee0d1042b8, sock=<optimized out>, p=<optimized out>, 
> thd=<optimized
> out>)
> 3.     at event.c:1064
> 
> If you scroll down, the last thread is this thread, but I'm not sure 
> yet what the problem exactly is. Any pointers?
> 
> Kind regards,
> Pieter Callewaert
>