[WBEL-users] network shuts down just because
Daniel Bahena
daniel@informatux.dyndns.org
Sat, 04 Sep 2004 12:07:36 -0500
Hi
I just installed a WBEL on a Pentium 3 @ 1.2 gigs and 128 ram (i'm
waiting for the 512 ram module).
It has 2 network adapters, 1 is a SIS 900 and the other is a Realtek
8139C
40 gig hard drive
and a adsl connection @ 1mb
It has been running for 4 days, and 2 times it has happened that the
network just stops. I have this from last night in /var/log/messages
Sep 4 05:17:25 secundaria named[889]: shutting down: flushing changes
Sep 4 05:17:25 secundaria named[889]: stopping command channel on
127.0.0.1#953
Sep 4 05:17:26 secundaria named: succeeded
Sep 4 05:17:26 secundaria named[889]: no longer listening on
127.0.0.1#53
Sep 4 05:17:26 secundaria named[889]: no longer listening on
192.168.0.254#53
Sep 4 05:17:26 secundaria named[889]: no longer listening on
201.135.209.74#53
Sep 4 05:17:26 secundaria named[889]: exiting
Sep 4 05:17:27 secundaria adsl-stop: Killing pppd
Sep 4 05:17:27 secundaria adsl-stop: Killing adsl-connect
Sep 4 05:17:27 secundaria network: Interrupción de la interfaz ppp0:
succeeded
Sep 4 05:17:27 secundaria pppd[1346]: Terminating on signal 15.
Sep 4 05:17:27 secundaria pppd[1346]: Connection terminated.
Sep 4 05:17:27 secundaria pppd[1346]: Connect time 867.1 minutes.
Sep 4 05:17:27 secundaria pppd[1346]: Sent 1947022 bytes, received
6318347 bytes.
Sep 4 05:17:27 secundaria pppoe[1347]: read (asyncReadFromPPP): Session
18441: Input/output error
Sep 4 05:17:27 secundaria pppoe[1347]: Sent PADT
Sep 4 05:17:27 secundaria /etc/hotplug/net.agent: NET unregister event
not supported
Sep 4 05:17:27 secundaria pppd[1346]: Exit.
Sep 4 05:17:27 secundaria network: Interrupción de la interfaz eth0:
succeeded
Sep 4 05:17:28 secundaria network: Interrupción de la interfaz eth1:
succeeded
Sep 4 05:17:28 secundaria network: Interrupción de la interfaz de
loopback: succeeded
Sep 4 05:17:28 secundaria sysctl: net.ipv4.ip_forward = 0
Sep 4 05:17:28 secundaria network: Deshabilitando el reenvio de
paquetes IPv4: succeeded
Sep 4 05:17:29 secundaria apmd[798]: System Standby
Other thing is that I see a lot of this messages also in
/var/log/messages:
Sep 3 13:45:02 secundaria named[889]: lame server resolving
'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 216.73.87.11#53
Sep 3 13:45:04 secundaria named[889]: lame server resolving
'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 65.205.8.11#53
Sep 3 13:45:05 secundaria named[889]: lame server resolving
'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 206.65.183.13#53
Sep 3 13:45:07 secundaria named[889]: lame server resolving
'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 65.205.8.12#53
Sep 3 13:45:27 secundaria named[889]: lame server resolving
'm3.3md.doubleclick.net' (in '3md.doubleclick.NET'?): 216.73.87.11#53
Sep 3 14:10:17 secundaria named[889]: lame server resolving
'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 65.205.8.12#53
Sep 3 14:10:17 secundaria named[889]: lame server resolving
'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 65.205.8.11#53
Sep 3 14:10:17 secundaria named[889]: lame server resolving
'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 206.65.183.13#53
Sep 3 14:10:18 secundaria named[889]: lame server resolving
'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 216.73.87.11#53
Sep 3 14:10:27 secundaria named[889]: lame server resolving
'85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.224.163#53
Sep 3 14:10:27 secundaria named[889]: lame server resolving
'85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.240.41#53
Sep 3 14:10:28 secundaria named[889]: lame server resolving
'85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.224.164#53
Sep 3 14:10:28 secundaria named[889]: lame server resolving
'85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.240.41#53
Sep 3 14:10:28 secundaria named[889]: lame server resolving
'85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.224.164#53
Sep 3 14:10:28 secundaria named[889]: lame server resolving
'85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.224.163#53
Sep 3 14:10:28 secundaria named[889]: lame server resolving
'85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.240.41#53
Sep 3 14:10:28 secundaria named[889]: lame server resolving
'85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.224.163#53
Sep 3 14:10:28 secundaria named[889]: lame server resolving
'85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.224.164#53
Sep 3 14:10:28 secundaria named[889]: lame server resolving
'85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.240.41#53
Sep 3 14:10:28 secundaria named[889]: lame server resolving
'85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.224.163#53
Sep 3 14:10:28 secundaria named[889]: lame server resolving
'85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.224.164#53
Sep 3 14:10:29 secundaria named[889]: lame server resolving
'55.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.240.41#53
Sep 3 14:10:29 secundaria named[889]: lame server resolving
'55.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.224.163#53
Sep 3 14:10:29 secundaria named[889]: lame server resolving
'55.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
207.248.224.164#53
Is that good or bad? If it is bad, how can I avoid that?
And to finish, what mirror for WBEL updates supports rsync? I'm from
Cuernavaca, Morelos and here we have a LUG and already have a mirror for
FC1 & FC2 base system and updates, besides dag, freshrpms, newrpms and a
extra directory. We want to set up a mirror for WBEL, any server adress
that might be useful? Our url is http://softwarelibremorelos.gob.mx
Thanks for all your time and help
Best wishes
--
Daniel Bahena <daniel@informatux.dyndns.org>
Informatux.net