Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: Browsers stop after 8~9 hours of continouos working

  1. #1

    Default Browsers stop after 8~9 hours of continouos working

    Hi all!

    I have a very strange problem.
    I use OpenSUSE 12.3 (but it happened on SUSE 11.3 and 11.4, too) and the symptom is after about 8 hours google becomes unavailable (gmail, and the search engine, too), and after that all other sites become unavailable. It seems like browser cannot load all the items of the site. I can see it on the end of the address bar (Items loaded n-1/n), so the last item cannot be loaded. Skype works properly of course... If I reboot the machine -> net works properly for the next eight hours.

    I use it in the traditional ifup way, IPv6 disabled.
    All the following commands gives the same output before/after the crash as you can see:

    Code:
    #/sbin/route -n :
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
    127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
    169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
    192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
    192.168.31.0    0.0.0.0         255.255.255.0   U     0      0        0 vmnet1
    192.168.73.0    0.0.0.0         255.255.255.0   U     0      0        0 vmnet8
    
    #nslookup forums.opensuse.org :
    Server:        208.67.222.222
    Address:    208.67.222.222#53
    Non-authoritative answer:
    Name:    forums.opensuse.org
    Address: 130.57.66.6
    
    #host forums.opensuse.org :
    forums.opensuse.org has address 130.57.66.6
    forums.opensuse.org has IPv6 address 2600:806:310::100
    forums.opensuse.org mail is handled by 42 mx2.suse.de.
    
    #ethtool eth0 :
    Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Half 1000baseT/Full 
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Half 1000baseT/Full 
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Link partner advertised link modes:  10baseT/Half 10baseT/Full 
                                             100baseT/Half 100baseT/Full 
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: d
        Current message level: 0x00000033 (51)
                       drv probe ifdown ifup
        Link detected: yes
    I set address reservation in my TP-Link router (TL-R402M).
    I have done a test : with the cable connected i made an ifdown eth0, and I had been waiting for 4 hours. After that I made an ifup and the behavior was the same : it becomes unusable after about eight hours from boot. It doesn't care about online time. I thought if it is some power management problem, but how can skype work in this case?

    I hope someone can help, because i took a lot of effort on googling, but without any goal.
    Thanks,

    Zivatar

  2. #2

    Default Re: Browsers stop after 8~9 hours of continouos working

    Any other machines on the network? Do they work?

    Try other tests:

    Code:
    --------------------
    ip addr
    ip route
    ip -s link #run a couple of times while trying your tests
    grep -v '^#' /etc/resolv.conf
    ping -c 6 forums.opensuse.org
    curl -v http://forums.opensuse.org/
    curl -v http://www.google.com/
    sudo tail --lines=100 /var/log/firewall
    --------------------

    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below...

  3. #3
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,236

    Default Re: Browsers stop after 8~9 hours of continouos working

    On 02/19/2014 10:36 PM, ab wrote:
    > Any other machines on the network? Do they work?
    >
    > Try other tests:
    >
    > Code:
    > --------------------
    > ip addr
    > ip route
    > ip -s link #run a couple of times while trying your tests
    > grep -v '^#' /etc/resolv.conf
    > ping -c 6 forums.opensuse.org
    > curl -v http://forums.opensuse.org/
    > curl -v http://www.google.com/
    > sudo tail --lines=100 /var/log/firewall
    > --------------------


    Are you running some program that is leaking memory? Run the command 'free' and
    save the output. When the condition happens, run it again and compare the results.



  4. #4
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,818

    Default Re: Browsers stop after 8~9 hours of continouos working

    I am wondering a bit. Is it just me or does nobody of us know which browser this is about?
    Henk van Velden

  5. #5

    Default Re: Browsers stop after 8~9 hours of continouos working

    hcvv wrote:
    > I am wondering a bit. Is it just me or does nobody of us know which
    > browser this is about?


    Well, is it about a browser at all?

    We haven't been shown any evidence that every other kind of network
    access is working but the browser is not. People have asked for more
    info that may clarify.

  6. #6

    Default Re: Browsers stop after 8~9 hours of continouos working

    Hi all!

    Thank you for all your answers!
    First I answer your questions:
    All the other computers on the LAN are able to browse without mishap, but these computers run Windows on themselves. I tried it with two kind of browsers, Firefox, and Opera, too, but the behavior is the same.
    I will do the offered tests. I will make a summary as soon as I can.
    Meanwhile I have found an other topic, where turned out that the router caused a malfunction that looks like this.
    https://forums.opensuse.org/showthre...-(even-google)

    Best Regards
    Zivatar

  7. #7
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Browsers stop after 8~9 hours of continouos working

    On 2014-02-20 12:10, Dave Howorth wrote:
    > hcvv wrote:
    >> I am wondering a bit. Is it just me or does nobody of us know which
    >> browser this is about?

    >
    > Well, is it about a browser at all?


    Probably not. :-)

    > We haven't been shown any evidence that every other kind of network
    > access is working but the browser is not. People have asked for more
    > info that may clarify.


    He did say that skype kept working.

    I would suspect the router...

    --
    Cheers / Saludos,

    Carlos E. R.

    (from 13.1 x86_64 "Bottle" (Minas Tirith))

  8. #8
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,818

    Default Re: Browsers stop after 8~9 hours of continouos working

    You may all be correct, but when someone reporting a problem syas that he uses "a browser", my first reaction then is "which browser?". And this lack of information does not prevents me trying to read and understand the rest of a post, it at least stops me for a while, trying to re-read to see if I skipped something, wondering if I am getting that old, etc. In other words it does hamper the whole interpretation process.
    Henk van Velden

  9. #9
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Browsers stop after 8~9 hours of continouos working

    On 2014-02-20 15:46, hcvv wrote:
    >
    > You may all be correct, but when someone reporting a problem syas that
    > he uses "a browser", my first reaction then is "which browser?". And
    > this lack of information does not prevents me trying to read and
    > understand the rest of a post, it at least stops me for a while, trying
    > to re-read to see if I skipped something, wondering if I am getting that
    > old, etc. In other words it does hamper the whole interpretation
    > process.


    Oh, absolutely :-)

    --
    Cheers / Saludos,

    Carlos E. R.

    (from 13.1 x86_64 "Bottle" (Minas Tirith))

  10. #10

    Default Re: Browsers stop after 8~9 hours of continouos working

    Quote Originally Posted by robin_listas View Post
    On 2014-02-20 15:46, hcvv wrote:
    >
    > You may all be correct, but when someone reporting a problem syas that
    > he uses "a browser", my first reaction then is "which browser?". And
    > this lack of information does not prevents me trying to read and
    > understand the rest of a post, it at least stops me for a while, trying
    > to re-read to see if I skipped something, wondering if I am getting that
    > old, etc. In other words it does hamper the whole interpretation
    > process.


    Oh, absolutely :-)

    --
    Cheers / Saludos,

    Carlos E. R.

    (from 13.1 x86_64 "Bottle" (Minas Tirith))
    Yes, of course!

    But I have written "browsers" so I would had made you to think about browsers generally, because I have tried a few kind and the result was same. Execuse me, if I was not understandable! Please notice that I am new in problem solving on Linux systems.
    I did the tests, and the results are here:

    Code:
    #ip addr
    #ip route
    #ip -s link #run a couple of times while trying your tests
    #grep -v '^#' /etc/resolv.conf
    #ping -c 6 forums.opensuse.org
    #curl -v http://forums.opensuse.org/
    #curl -v http://www.google.com/
    #sudo tail --lines=100 /var/log/firewall
    
    results:
    zivatar-laptop:~ # ip addr
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
        link/ether 00:03:0d:5d:1c:96 brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.100/24 brd 192.168.1.255 scope global eth0
    3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
        link/ether 00:19:d2:47:9e:c9 brd ff:ff:ff:ff:ff:ff
    4: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
        link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
        inet 192.168.31.1/24 brd 192.168.31.255 scope global vmnet1
    5: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
        link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff
        inet 192.168.73.1/24 brd 192.168.73.255 scope global vmnet8
    
    zivatar-laptop:~ # ip route
    default via 192.168.1.1 dev eth0 
    127.0.0.0/8 dev lo  scope link 
    169.254.0.0/16 dev eth0  scope link 
    192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.100 
    192.168.31.0/24 dev vmnet1  proto kernel  scope link  src 192.168.31.1 
    192.168.73.0/24 dev vmnet8  proto kernel  scope link  src 192.168.73.1
    
    zivatar-laptop:~ # ip -s link
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        RX: bytes  packets  errors  dropped overrun mcast   
        25812      271      0       0       0       0      
        TX: bytes  packets  errors  dropped carrier collsns 
        25812      271      0       0       0       0      
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
        link/ether 00:03:0d:5d:1c:96 brd ff:ff:ff:ff:ff:ff
        RX: bytes  packets  errors  dropped overrun mcast   
        1508101274 1106944  0       0       0       0      
        TX: bytes  packets  errors  dropped carrier collsns 
        66490376   658202   0       0       0       0      
    3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DORMANT qlen 1000
        link/ether 00:19:d2:47:9e:c9 brd ff:ff:ff:ff:ff:ff
        RX: bytes  packets  errors  dropped overrun mcast   
        0          0        0       0       0       0      
        TX: bytes  packets  errors  dropped carrier collsns 
        0          0        0       0       0       0      
    4: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT qlen 1000
        link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff
        RX: bytes  packets  errors  dropped overrun mcast   
        0          0        0       0       0       0      
        TX: bytes  packets  errors  dropped carrier collsns 
        0          11       0       0       0       0      
    5: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT qlen 1000
        link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff
        RX: bytes  packets  errors  dropped overrun mcast   
        0          0        0       0       0       0      
        TX: bytes  packets  errors  dropped carrier collsns 
        0          11       0       0       0       0
    
    zivatar-laptop:~ # grep -v '^#' /etc/resolv.conf
    search domain
    nameserver 208.67.222.222
    nameserver 208.67.220.220      
    
    zivatar-laptop:~ # ping -c 6 forums.opensuse.org
    PING forums.opensuse.org (130.57.66.6) 56(84) bytes of data.
    64 bytes from forums.opensuse.org (130.57.66.6): icmp_seq=1 ttl=51 time=208 ms
    64 bytes from forums.opensuse.org (130.57.66.6): icmp_seq=2 ttl=51 time=208 ms
    64 bytes from forums.opensuse.org (130.57.66.6): icmp_seq=3 ttl=51 time=208 ms
    64 bytes from forums.opensuse.org (130.57.66.6): icmp_seq=4 ttl=51 time=208 ms
    64 bytes from forums.opensuse.org (130.57.66.6): icmp_seq=5 ttl=51 time=207 ms
    64 bytes from forums.opensuse.org (130.57.66.6): icmp_seq=6 ttl=51 time=208 ms
    
    --- forums.opensuse.org ping statistics ---
    6 packets transmitted, 6 received, 0% packet loss, time 5005ms
    rtt min/avg/max/mdev = 207.620/208.368/208.852/0.423 ms
    
    zivatar-laptop:~ # curl -v http://forums.opensuse.org/
    * About to connect() to forums.opensuse.org port 80 (#0)
    *   Trying 130.57.66.6...
    * connected
    * Connected to forums.opensuse.org (130.57.66.6) port 80 (#0)
    > GET / HTTP/1.1
    > User-Agent: curl/7.28.1
    > Host: forums.opensuse.org
    > Accept: */*
    > 
    < HTTP/1.1 302 Found
    < Date: Thu, 20 Feb 2014 20:48:14 GMT
    < Server: Apache/2.2.12 (Linux/SUSE)
    < Location: http://forums.opensuse.org/forum.php
    < Content-Type: text/html; charset=iso-8859-1
    < X-Mag: 6EAD06E4F4FE6B09;5a386713;47012454;usrLkup->0;usrBase->0;getPRBefFind->0;getPRBefFind->0;PRAfterFind->0;openforums_public;publicURL->0;openforums;RwDis;FF1End->0;SendSoapStart->0;SendSoapExit->2;EvalII->2;CHd;FP2->2;WS=1f7a716d;FP4->5;C014;
    < Set-Cookie: ZNPCQ003-32323600=1f7a716d; Path=/; Domain=.opensuse.org
    < Via: 1.1 forums.opensuse.org (Access Gateway-ag-6EAD06E4F4FE6B09-47012454)
    < Keep-Alive: timeout=300, max=80
    < Connection: Keep-Alive
    < Transfer-Encoding: chunked
    < Set-Cookie: lb_opensuse=NEODEBIJ; Domain=.opensuse.org; Path=/
    < 
    <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
    <html><head>
    <title>302 Found</title>
    </head><body>
    <h1>Found</h1>
    <p>The document has moved <a href="http://forums.opensuse.org/forum.php">here</a>.</p>
    <hr>
    <address>Apache/2.2.12 (Linux/SUSE) Server at forums.opensuse.org Port 80</address>
    </body></html>
    * Connection #0 to host forums.opensuse.org left intact
    * Closing connection #0
    
    zivatar-laptop:~ # curl -v http://www.google.com/
    * About to connect() to www.google.com port 80 (#0)
    *   Trying 173.194.39.176...
    ^C
    
    zivatar-laptop:~ # sudo tail --lines=100 /var/log/firewall
    2014-02-20T21:16:40.757950+01:00 zivatar-laptop kernel: [32860.025532] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:03:0d:5d:1c:96:90:f6:52:24:17:4a:08:00 SRC=145.236.45.84 DST=192.168.1.100 LEN=33 TOS=0x00 PREC=0x00 TTL=248 ID=28262 DF PROTO=UDP SPT=5060 DPT=59773 LEN=13 
    2014-02-20T21:16:57.142948+01:00 zivatar-laptop kernel: [32876.410437] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:03:0d:5d:1c:96:90:f6:52:24:17:4a:08:00 SRC=145.236.45.84 DST=192.168.1.100 LEN=33 TOS=0x00 PREC=0x00 TTL=248 ID=63600 DF PROTO=UDP SPT=5060 DPT=59773 LEN=13 
    2014-02-20T21:17:13.527975+01:00 zivatar-laptop kernel: [32892.795378] SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:03:0d:5d:1c:96:90:f6:52:24:17:4a:08:00 SRC=145.236.45.84 DST=192.168.1.100 LEN=33 TOS=0x00 PREC=0x00 TTL=248 ID=48059 DF PROTO=UDP SPT=5060 DPT=59773 LEN=13
    .
    .
    .
    and so on
    Thanks for the Help!

    Best Regards
    Zivatar

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •