new machine - problems with gaim

[Mark Knecht]

On Wed, 05 Jan 2005 10:54:10 -0800, Rick Stevens
<rstevens at vitalstream.com> wrote:
> Mark Knecht wrote:
> > On Wed, 05 Jan 2005 10:13:31 -0800, Rick Stevens
> > <rstevens at vitalstream.com> wrote:
> >
> >>Mark Knecht wrote:
> >
> >
> >>>   In /var/log/messages I do see some strangeness:
> >>>
> >>> Jan  4 18:26:04 Christmas dhclient: DHCPDISCOVER on sit0 to
> >>>255.255.255.255 port 67 interval 19
> >>>Jan  4 18:26:04 Christmas dhclient: send_packet: Network is down
> >>>Jan  4 18:26:23 Christmas dhclient: DHCPDISCOVER on sit0 to
> >>>255.255.255.255 port 67 interval 4
> >>>Jan  4 18:26:23 Christmas dhclient: send_packet: Network is down
> >>>Jan  4 18:26:27 Christmas dhclient: No DHCPOFFERS received.
> >>>Jan  4 18:26:27 Christmas dhclient: No working leases in persistent
> >>>database - sleeping.
> >>>Jan  4 18:28:47 Christmas su(pam_unix)[3284]: session opened for user
> >>>root by matt(uid=500)
> >>>Jan  4 18:30:04 Christmas dhclient: DHCPDISCOVER on sit0 to
> >>>255.255.255.255 port 67 interval 8
> >>>Jan  4 18:30:04 Christmas dhclient: send_packet: Network is down
> >>>Jan  4 18:30:12 Christmas dhclient: DHCPDISCOVER on eth0 to
> >>>255.255.255.255 port 67 interval 4
> >>>Jan  4 18:30:12 Christmas dhclient: DHCPDISCOVER on sit0 to
> >>>255.255.255.255 port 67 interval 18
> >>>Jan  4 18:30:12 Christmas dhclient: send_packet: Network is down
> >>>
> >>>   This sort of stuff is repeating a lot.
> >>
> >>It sure looks like the DHCP server is cycling a lot.  Are you using
> >>your ISP's DHCP or one on your local access point/switch/router?
> >
> >
> > Is this cycling for the wired Etherenet port which I'm not using? (And
> > currently has no cable plugged in?)
> 
> It's possible.  Don't worry about the "sit0" stuff as that's for
> IPV6.  If eth0 is the wired connection (which is unused), why not
> delete the /etc/sysconfig/network-scripts/ifcfg-eth0 file or edit it
> so it says "ONBOOT=no"?  That'll shut up the eth0 stuff.

I'll be trying that after I send this message.

Can I just disable IPv6 completely? Or does that get used in the
background somewhere?

> 
> As to why GAIM is slow to start up...that's hard to say.  You say
> you have iptables turned off on the local machine.  How about your
> router/firewall?

[root at Christmas root]# ps aux | grep iptables
root      3361  0.0  0.1  3584  660 pts/0    R    11:17   0:00 grep iptables
[root at Christmas root]#

So it seems to be gone. I was refering to the local firewall, not the
one in my router. However, all other machines here (Windows and FC2
anyway - I don't chat on the Gentoo machine) can chat successfully,
and this machine can too once it starts working.

One other issue I'm seeing (maybe this in Gnome related?) is that when
I've been using the account for a while and then want to log out of
Gnome, I go the the red-hat icon and choose 'Log out' and I get
another wait of 5 minutes. It doesn't happen every time, but it
happens often. What's weird is that I can open a terminal and reboot
the machine, or kill X, or pretty much anything else, but the log out
dialog doesn't come up for maybe 4-5 minutes.

What causes this sort of stuff? Weird... I understand that it's hard
to say from your location. Just looking for ideas on debugging it. I
thought it was purely memory related since the machine had only 128MB,
but after adding an additional 256MB yesterday I don't think that's
the problem. (Or hope not....)

Thanks,
Mark