FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 05-02-2012, 09:57 AM
Brian
 
Default Exim panics

On Wed 02 May 2012 at 10:17:59 +0100, Tony van der Hoff wrote:

> What would be the preferred way of overcoming this problem?

Sorting out what the problem is, I suppose. But on the odd occasion it
happens here I just delete paniclog.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120502095710.GB32481@desktop">http://lists.debian.org/20120502095710.GB32481@desktop
 
Old 05-02-2012, 10:15 AM
Jon Dowland
 
Default Exim panics

On Wed, May 02, 2012 at 11:29:19AM +0200, Jochen Spieker wrote:
> You need to find out the source of the problem. Do you regularly restart
> Exim?

In my experience, with the Debian packaging, this is usually caused by exim
conflicting with itself. I've never figured the problem out entirely, but it
is exacerbated by having exim listen on more than one port (-oX 587:465:25)


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120502101510.GJ17757@debian">http://lists.debian.org/20120502101510.GJ17757@debian
 
Old 05-02-2012, 04:40 PM
Camaleón
 
Default Exim panics

On Wed, 02 May 2012 10:17:59 +0100, Tony van der Hoff wrote:

> On my Squeeze box, I am getting occasional panics from Exim, due to port
> 25 being in use. I imagine it's occasionally clashing with Thunderbird:

With Thunderbird? :-?

> exim paniclog /var/log/exim4/paniclog on tony-lx.magpieway.net has non-
> zero size, mail system might be broken. The last 10 lines are quoted
> below.
>
> 2012-04-15 22:01:07 socket bind() to port 25 for address ::1 failed:
> Cannot assign requested address: daemon abandoned

(...)

> What would be the preferred way of overcoming this problem?

I guess you could configure Exim ("dpkg-reconfigure exim4-config") so
that listens only at the desired interfaces (i.e., only to localhost ipv4
-127.0.0.1- instead adding localhost ipv6 -::1- addresses).

Anyway, Exim shouldn't complain if your nic is configured to handle ipv6
requests (which is the default since years but "/sbin/ifconfig lo" will
confirm).

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: jnro1m$iv6$10@dough.gmane.org">http://lists.debian.org/jnro1m$iv6$10@dough.gmane.org
 
Old 05-02-2012, 05:05 PM
Tony van der Hoff
 
Default Exim panics

On 02/05/12 17:40, Camaleón wrote:


I guess you could configure Exim ("dpkg-reconfigure exim4-config") so
that listens only at the desired interfaces (i.e., only to localhost ipv4
-127.0.0.1- instead adding localhost ipv6 -::1- addresses).

Thanks, everybody, for your answers. Especially this one, which tells me
what to do, and how to do it


So, I've done that, watch this space to see whether the problem recurs.

Oh, yes, I've had Jochen's script running all day, no culprits, except
exim itself, but I guess I'd expect that, as the log entries are days apart.



Anyway, Exim shouldn't complain if your nic is configured to handle ipv6
requests (which is the default since years but "/sbin/ifconfig lo" will
confirm).


Nope:
tony@tony-lx:~$ sudo ifconfig lo
[sudo] password for tony:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:116280 errors:0 dropped:0 overruns:0 frame:0
TX packets:116280 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:21992844 (20.9 MiB) TX bytes:21992844 (20.9 MiB)



--
Tony van der Hoff | mailto:tony@vanderhoff.org
Buckinghamshire, England |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4FA16974.5040102@vanderhoff.org">http://lists.debian.org/4FA16974.5040102@vanderhoff.org
 
Old 05-03-2012, 03:52 PM
Camaleón
 
Default Exim panics

On Wed, 02 May 2012 18:05:56 +0100, Tony van der Hoff wrote:

> On 02/05/12 17:40, Camaleón wrote:
>>
>> I guess you could configure Exim ("dpkg-reconfigure exim4-config") so
>> that listens only at the desired interfaces (i.e., only to localhost
>> ipv4 -127.0.0.1- instead adding localhost ipv6 -::1- addresses).
>>
> Thanks, everybody, for your answers. Especially this one, which tells me
> what to do, and how to do it
>
> So, I've done that, watch this space to see whether the problem recurs.

Mmm, fine.

I don't use Exim very much (I have a strange relation with Exim, it's
there -and I know it is- but I barely notice its presence nor review the
logs not check what's doing), so I guessed the re-configuration routine
will ask for the interfaces to use and allows the user to manually define
them but I can't be sure :-)

> Oh, yes, I've had Jochen's script running all day, no culprits, except
> exim itself, but I guess I'd expect that, as the log entries are days
> apart.
>
>> Anyway, Exim shouldn't complain if your nic is configured to handle
>> ipv6 requests (which is the default since years but "/sbin/ifconfig lo"
>> will confirm).
>
> Nope:
> tony@tony-lx:~$ sudo ifconfig lo
> [sudo] password for tony:
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:116280
> errors:0 dropped:0 overruns:0 frame:0 TX packets:116280
> errors:0 dropped:0 overruns:0 carrier:0 collisions:0
> txqueuelen:0
> RX bytes:21992844 (20.9 MiB) TX bytes:21992844 (20.9 MiB)

Then Exim is right but, how that can be? :-?

sm01@stt008:~$ /sbin/ifconfig lo
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)

Check you "/etc/hosts" file. You should have this line which enables the
ipv6 loopback interface:

***
::1 localhost ip6-localhost ip6-loopback
***

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: jnu9kc$78r$5@dough.gmane.org">http://lists.debian.org/jnu9kc$78r$5@dough.gmane.org
 
Old 05-03-2012, 05:07 PM
Tony van der Hoff
 
Default Exim panics

On 03/05/12 16:52, Camaleón wrote:

On Wed, 02 May 2012 18:05:56 +0100, Tony van der Hoff wrote:

tony@tony-lx:~$ sudo ifconfig lo
[sudo] password for tony:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:116280
errors:0 dropped:0 overruns:0 frame:0 TX packets:116280
errors:0 dropped:0 overruns:0 carrier:0 collisions:0
txqueuelen:0
RX bytes:21992844 (20.9 MiB) TX bytes:21992844 (20.9 MiB)


Then Exim is right but, how that can be? :-?

sm01@stt008:~$ /sbin/ifconfig lo
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)

Check you "/etc/hosts" file. You should have this line which enables the
ipv6 loopback interface:

***
::1 localhost ip6-localhost ip6-loopback
***


Yeah, it's commented out
I can't now remember why I did that; but I think it might have been a
problem with bind9...


I've uncommented it now; done ifdown/ifup, but still no inet6 addr on
lo. Still, never mind...


Cheers, Tony


--
Tony van der Hoff | mailto:tony@vanderhoff.org
Buckinghamshire, England |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4FA2BB39.5090000@vanderhoff.org">http://lists.debian.org/4FA2BB39.5090000@vanderhoff.org
 
Old 05-03-2012, 07:55 PM
Camaleón
 
Default Exim panics

On Thu, 03 May 2012 18:07:05 +0100, Tony van der Hoff wrote:

> On 03/05/12 16:52, Camaleón wrote:

(...)

>> Check you "/etc/hosts" file. You should have this line which enables
>> the ipv6 loopback interface:
>>
>> ***
>> ::1 localhost ip6-localhost ip6-loopback ***
>
> Yeah, it's commented out
> I can't now remember why I did that; but I think it might have been a
> problem with bind9...

Does bind9 have any problem with ipv6? I didn't notice, at least in my
Lenny servers :-?

> I've uncommented it now; done ifdown/ifup, but still no inet6 addr on
> lo. Still, never mind...

I'm a curious cat O:-)

Mmm, then there must be something at a lower layer, I mean, maybe is that
you have disabled the whole ipv6 support at the kernel.

I can see my two interfaces are getting an ipv6 address:

sm01@stt008:~$ cat /proc/net/if_inet6
00000000000000000000000000000001 01 80 10 80 lo
fe80000000000000023048fffed90827 02 40 20 80 eth0

And (from my Lenny):

sm01@stt008:~$ lsmod|grep ipv6
ipv6 288456 26

Now I realize there's a wiki page in Debian explaining this ipv6 thingy:

http://wiki.debian.org/DebianIPv6#How_to_turn_off_IPv6

Oh, and there's even a how-to for disabling ipv6 in Exim4. Too late, I'm
afraid :-P

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: jnunqp$78r$13@dough.gmane.org">http://lists.debian.org/jnunqp$78r$13@dough.gmane.org
 
Old 05-03-2012, 08:53 PM
Tony van der Hoff
 
Default Exim panics

On 03/05/12 20:55, Camaleón wrote:

On Thu, 03 May 2012 18:07:05 +0100, Tony van der Hoff wrote:


On 03/05/12 16:52, Camaleón wrote:


(...)


Check you "/etc/hosts" file. You should have this line which enables
the ipv6 loopback interface:

***
::1 localhost ip6-localhost ip6-loopback ***


Yeah, it's commented out
I can't now remember why I did that; but I think it might have been a
problem with bind9...


Does bind9 have any problem with ipv6? I didn't notice, at least in my
Lenny servers :-?


Yes, I think it was discussed on this list.
Maybe not bind9, but my router can't handle ipv6:

May 3 21:29:53 tony-lx named[1985]: error (FORMERR) resolving
'telegraph.nestoria.co.uk/AAAA/IN': 178.250.72.132#53
May 3 21:29:53 tony-lx named[1985]: DNS format error from
178.250.74.132#53 resolving telegraph.nestoria.co.uk/AAAA for client
192.168.1.105#56959: invalid response


Commenting out the ipv6 entry in hosts fixed that.


I've uncommented it now; done ifdown/ifup, but still no inet6 addr on
lo. Still, never mind...



Re-commented now...


I'm a curious cat O:-)

Mmm, then there must be something at a lower layer, I mean, maybe is that
you have disabled the whole ipv6 support at the kernel.

I can see my two interfaces are getting an ipv6 address:

sm01@stt008:~$ cat /proc/net/if_inet6
00000000000000000000000000000001 01 80 10 80 lo
fe80000000000000023048fffed90827 02 40 20 80 eth0

And (from my Lenny):

sm01@stt008:~$ lsmod|grep ipv6
ipv6 288456 26


Neither of those provokes a response here.


Now I realize there's a wiki page in Debian explaining this ipv6 thingy:

http://wiki.debian.org/DebianIPv6#How_to_turn_off_IPv6

Oh, and there's even a how-to for disabling ipv6 in Exim4. Too late, I'm
afraid :-P

Greetings,


Cheers, tony

--
Tony van der Hoff | mailto:tony@vanderhoff.org
Buckinghamshire, England |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4FA2F046.5080706@vanderhoff.org">http://lists.debian.org/4FA2F046.5080706@vanderhoff.org
 
Old 05-04-2012, 02:44 PM
Camaleón
 
Default Exim panics

On Thu, 03 May 2012 21:53:26 +0100, Tony van der Hoff wrote:

> On 03/05/12 20:55, Camaleón wrote:

>> Does bind9 have any problem with ipv6? I didn't notice, at least in my
>> Lenny servers :-?
>>
> Yes, I think it was discussed on this list. Maybe not bind9, but my
> router can't handle ipv6:

None of my ADSL routers do. But this (the traffic between ipv4 and ipv6
backbones) has to be handled transparently by your carrier.

> May 3 21:29:53 tony-lx named[1985]: error (FORMERR) resolving 'telegraph.nestoria.co.uk/AAAA/IN': 178.250.72.132#53
> May 3 21:29:53 tony-lx named[1985]: DNS format error from 178.250.74.132#53 resolving telegraph.nestoria.co.uk/AAAA for client 192.168.1.105#56959: invalid response

Mmm, there should be no need for that, I mean, bind9 can be configured to
don't use ipv6... this is what I get in lenny when daemon starts:

syslog.1:May 4 07:18:51 stt005 named[2382]: loading configuration from '/etc/bind/named.conf'
syslog.1:May 4 07:18:51 stt005 named[2382]: using default UDP/IPv4 port range: [1024, 65535]
syslog.1:May 4 07:18:51 stt005 named[2382]: using default UDP/IPv6 port range: [1024, 65535]
syslog.1:May 4 07:18:51 stt005 named[2382]: no IPv6 interfaces found
syslog.1:May 4 07:18:51 stt005 named[2382]: listening on IPv4 interface lo, 127.0.0.1#53
syslog.1:May 4 07:18:51 stt005 named[2382]: listening on IPv4 interface eth0, 192.168.0.5#53

And I did nothing to disable ipv6 here (in fact, I can see it's enabled at
"/etc/bind/named.conf.options" → listen-on-v6 { any; };" , but still bind9
does this by its own.

> Commenting out the ipv6 entry in hosts fixed that.

And that's strange because if you are using a local dns resolver, the "hosts"
file shouldn't be queried to resolve external domains :-?

>> Mmm, then there must be something at a lower layer, I mean, maybe is
>> that you have disabled the whole ipv6 support at the kernel.
>>
>> I can see my two interfaces are getting an ipv6 address:

(...)

>> And (from my Lenny):
>>
>> sm01@stt008:~$ lsmod|grep ipv6
>> ipv6 288456 26
>>
> Neither of those provokes a response here.

That can mean you have disabled ipv6, system-wide.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: jo0q11$3du$5@dough.gmane.org">http://lists.debian.org/jo0q11$3du$5@dough.gmane.org
 

Thread Tools




All times are GMT. The time now is 08:05 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org