Autor: Adrian Chapela Data: Dla: Magnus Holmgren CC: exim-users Temat: Re: [exim] Segment fault
Magnus Holmgren escribió: > On Wednesday 28 February 2007 19:42, Adrian Chapela wrote:
>
>> Hello,
>>
>> I compile the exim server (version 4.66 and 4.65) and then when I run
>> ./exim -bd or ./exim -bd -q15m the exim say: Segment Fault..
>>
>> You know how ??
>>
>
> No. You need to troubleshoot and provide more information.
>
> Does it crash if you run ./exim -bV ?
> Fot this command the output is:
Exim version 4.65 #1 built 28-Feb-2007 18:46:33
Copyright (c) University of Cambridge 2006
Berkeley DB: Berkeley DB 4.5.20: (September 20, 2006)
Support for: iconv()
Lookups: lsearch wildlsearch nwildlsearch iplsearch dbm dbmnz
Authenticators:
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir autoreply pipe smtp
Fixed never_users: 0
Size of off_t: 8
Configuration file is /usr/exim/configure > If you run ./exim -bd -d+all, is there any output?
> For this command the output is:
08:56:05 10209 Exim version 4.65 uid=0 gid=0 pid=10209 D=fffdffff
Berkeley DB: Berkeley DB 4.5.20: (September 20, 2006)
Support for: iconv()
Lookups: lsearch wildlsearch nwildlsearch iplsearch dbm dbmnz
Authenticators:
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir autoreply pipe smtp
Fixed never_users: 0
Size of off_t: 8
08:56:05 10209 changed uid/gid: forcing real = effective
08:56:05 10209 uid=0 gid=0 pid=10209
08:56:05 10209 auxiliary group list: <none>
08:56:05 10209 seeking password data for user "root": cache not available
08:56:05 10209 getpwnam() succeeded uid=0 gid=0
08:56:05 10209 configuration file is /usr/exim/configure
08:56:05 10209 log selectors = 00000ffc 00089001
08:56:05 10209 cwd=/usr/exim/bin 3 args: ./exim -bd -d+all
08:56:05 10209 trusted user
08:56:05 10209 admin user
08:56:05 10209 originator: uid=0 gid=0 login=root name=root
Violación de segmento --> (Segmentation Fault in spanish ;) ) > Can you try running Exim in a debugger?
>
> It's possible that the crash is caused by bad dynamic linking.
>
>