Re: [opensuse] unable to access website after 10.2 install
Hi
Tom Patton <thpnalb@micro-net.com> 12/19/06 8:23 PM >>> On Tue, 2006-12-19 at 09:43 -0800, Randall R Schulz wrote:
I don't know what could be causing this and why it's (so far)
manifested
only when trying to access this particular site / address, but clearly the checksum generation is the problem. I'm by far a guru here, and still waiting on my boxed 10.2, but I wonder if any of you have tried dial-up (modem0) vs your eth0 interface...?
All I can say at this point is it workes here, and is a very interesting problem...
What I can say so far: in the company, where I have a proxy between my Suse box and this specific server, it works. So it seems to be a problem caused by two 'incompatible' tcp stacks. Very nice thing to find in the net. I'll stay a bit on it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 19 December 2006 10:34, Dominique Leuenberger wrote:
...
What I can say so far: in the company, where I have a proxy between my Suse box and this specific server, it works. So it seems to be a problem caused by two 'incompatible' tcp stacks. Very nice thing to find in the net.
The buzz-phrase is "interoperable." And yes, it really is quite surprising in 2006 such issues are still lurking. I wonder how much we can discern about the hosts on the other end when the failure occurs? We know that openSuSE 10.2 is one part of the equation, but since most peers do work, perhaps there's something instructive about the ones that do elicit the problem.
I'll stay a bit on it.
Likewise. I just know that one of these days it'll crop up for a site I really need to access. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006-12-19 12:47, Randall R Schulz wrote:
I wonder how much we can discern about the hosts on the other end when the failure occurs? We know that openSuSE 10.2 is one part of the equation, but since most peers do work, perhaps there's something instructive about the ones that do elicit the problem.
The OP has reported that reverting to the 2.6.16 kernel allows him to access the sites. Everyone reporting the problem so far has a 2.6.18 kernel, and the same problem has also been mentioned with other distros using that kernel version. The TCP stack idea seems most on track, but it is curious that it doesn't affect everyone running 10.2. 32 vs. 64 bit doesn't appear to answer it, or does SMP vs. non-SMP.
I'll stay a bit on it.
Likewise. I just know that one of these days it'll crop up for a site I really need to access.
Felix suggested it is perhaps time for bugzilla. I think I agree with him. The rabid sysclock issue is another area where reverting to an earlier kernel resolved the issue, and which is also one which affects only a few. I have been trying to keep an eye on things which could suggest a common denominator in all this, without success so far. -- The best way to accelerate a computer running Windows is at 9.81 m/s² -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Darryl, On Tuesday 19 December 2006 12:01, Darryl Gregorash wrote:
On 2006-12-19 12:47, Randall R Schulz wrote:
I wonder how much we can discern about the hosts on the other end when the failure occurs? We know that openSuSE 10.2 is one part of the equation, but since most peers do work, perhaps there's something instructive about the ones that do elicit the problem.
The OP has reported that reverting to the 2.6.16 kernel allows him to access the sites. Everyone reporting the problem so far has a 2.6.18 kernel, and the same problem has also been mentioned with other distros using that kernel version.
The TCP stack idea seems most on track, but it is curious that it doesn't affect everyone running 10.2. 32 vs. 64 bit doesn't appear to answer it, or does SMP vs. non-SMP.
I'll stay a bit on it.
Likewise. I just know that one of these days it'll crop up for a site I really need to access.
Felix suggested it is perhaps time for bugzilla.
Well, someone else can do _that_ particular bit of penance, this time. I tried to explore the possibility of a hardware ("offloaded") checksum generation bug. I found some reports of past bugs in some of the Ethernet drivers relating to this capability, and clearly it's being used on my system. So far I have not been able to find out how, if indeed it's possible, to disable the use of the hardware checksum offloading in the "skge" driver. Does anyone know how to disable hardware- (NIC-) based packet checksumming, either specifically for the skge driver or in general? However, just now I came up with another data point that pretty much refutes the erroneous hardware checksum generation hypothesis: I modified my system's configuration so as to use the other NIC, which is not the same kind of hardware and does not use the same device driver (before the system was using the skge driver for external traffic, now it's the sky2 driver). But the symptom remains unchanged. So whatever it is, its either something these two drivers have in common (they're not wholly unrelated, I don't think) or it's something that happens higher up in the protocol stack where the data paths are by all NICs.
I think I agree with him. The rabid sysclock issue is another area where reverting to an earlier kernel resolved the issue, and which is also one which affects only a few. I have been trying to keep an eye on things which could suggest a common denominator in all this, without success so far.
I don't have any real-time clock issues on this system. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006-12-19 15:17, Randall R Schulz wrote:
Darryl,
On Tuesday 19 December 2006 12:01, Darryl Gregorash wrote:
<snip> Felix suggested it is perhaps time for bugzilla.
Well, someone else can do _that_ particular bit of penance, this time.
Felix was the first one to suggest it, so maybe he should do it :-)
him. The rabid sysclock issue is another area .... I don't have any real-time clock issues on this system. Which makes that one equally as mystifying as this one. Maybe Felix will handle that bug report too :-)
-- The best way to accelerate a computer running Windows is at 9.81 m/s² -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006/12/19 17:48 (GMT-0600) Darryl Gregorash apparently typed:
Felix was the first one to suggest it, so maybe he should do it :-)
https://bugzilla.novell.com/show_bug.cgi?id=229848 Those who have bugzilla accounts should feel free to add any useful information I may have left out. -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Those who have bugzilla accounts should feel free to add any useful information I may have left out.
Thank Felix--you beat me to it. Chip -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006-12-19 18:58, Felix Miata wrote:
On 2006/12/19 17:48 (GMT-0600) Darryl Gregorash apparently typed:
Felix was the first one to suggest it, so maybe he should do it :-)
https://bugzilla.novell.com/show_bug.cgi?id=229848
Those who have bugzilla accounts should feel free to add any useful information I may have left out.
And vote for the bug too. Anyone without an account should create one, add comments where appropriate, and then vote for it :-) BTW, Felix, you created the bug as normal severity. Shouldn't it be a tad higher than that? I don't think it's quite a blocker, but it's certainly major, IMO. -- The best way to accelerate a computer running Windows is at 9.81 m/s² -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006/12/19 19:18 (GMT-0600) Darryl Gregorash apparently typed:
On 2006-12-19 18:58, Felix Miata wrote:
And vote for the bug too.
Anyone without an account should create one, add comments where appropriate, and then vote for it :-)
Comments are not prerequisite to voting, but if most who replied in thread also vote they'll probably get a better handle on how widespread the problem is among 10.2 users.
BTW, Felix, you created the bug as normal severity. Shouldn't it be a tad higher than that? I don't think it's quite a blocker, but it's certainly major, IMO.
https://bugzilla.novell.com/page.cgi?id=fields.html#bug_severity The way I read the instructions, the assignee should determine whether some deviation from normal is warranted for this particular bug. It's only major if you have to reach a particular site, which would make it a literal blocker for you. Zillions of other web sites don't produce the problem. In the overall scheme, this is more like trivial, which Mozilla's Bugzilla has, but not Novell's. -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Felix Miata <mrmazda@ij.net> [12-19-06 20:48]:
Comments are not prerequisite to voting, but if most who replied in thread also vote they'll probably get a better handle on how widespread the problem is among 10.2 users.
me thinks it not be a 10.2 problem, but a kernel problem. I have 10.1 with 2.6.18.5-jen40-default and cannot access the site. I have read the thread and, as I recall, noone with 2.6.18+ could access, but several with 2.6.16 could. I will vote and comment. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006-12-19 19:53, Patrick Shanahan wrote:
* Felix Miata <mrmazda@ij.net> [12-19-06 20:48]:
Comments are not prerequisite to voting, but if most who replied in thread also vote they'll probably get a better handle on how widespread the problem is among 10.2 users.
me thinks it not be a 10.2 problem, but a kernel problem. I have 10.1 with 2.6.18.5-jen40-default and cannot access the site. I have read the thread and, as I recall, noone with 2.6.18+ could access, but several with 2.6.16 could.
Quite correct, save one point: Felix put up a vanilla 2.6.19 kernel, and the problem went away. That and Martin Mielke's 403 error in his squid log are the only clues to what is happening. -- The best way to accelerate a computer running Windows is at 9.81 m/s² -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/20/06, Patrick Shanahan <ptilopteri@gmail.com> wrote:
me thinks it not be a 10.2 problem, but a kernel problem. I have 10.1 with 2.6.18.5-jen40-default and cannot access the site. I have read the thread and, as I recall, noone with 2.6.18+ could access, but several with 2.6.16 could.
Patrick, that's not correct. As I wrote I had no problem accessing these sites and I have 2.6.18.2-34-default kernel on 2 machines. -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 19 December 2006 21:45, Mark Goldstein wrote:
On 12/20/06, Patrick Shanahan <ptilopteri@gmail.com> wrote:
me thinks it not be a 10.2 problem, but a kernel problem. I have 10.1 with 2.6.18.5-jen40-default and cannot access the site. I have read the thread and, as I recall, noone with 2.6.18+ could access, but several with 2.6.16 could.
Patrick, that's not correct. As I wrote I had no problem accessing these sites and I have 2.6.18.2-34-default kernel on 2 machines.
Mark: did you post your particulars (processor, nics, etc) to the bugzilla report as a point of reference to the developers? -- _____________________________________ John Andersen
On 12/20/06, John Andersen <jsa@pen.homeip.net> wrote:
Mark: did you post your particulars (processor, nics, etc) to the bugzilla report as a point of reference to the developers?
Will do -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, On Wednesday 20 December 2006 07:45, Mark Goldstein wrote:
On 12/20/06, Patrick Shanahan <ptilopteri@gmail.com> wrote:
me thinks it not be a 10.2 problem, but a kernel problem. I have 10.1 with 2.6.18.5-jen40-default and cannot access the site. I have read the thread and, as I recall, noone with 2.6.18+ could access, but several with 2.6.16 could.
Patrick, that's not correct. As I wrote I had no problem accessing these sites and I have 2.6.18.2-34-default kernel on 2 machines.
Only guessing: you're accessing http through a proxy, right? Greetings from Stuhr hartmut -- Hartmut Meyer, NTS EMEA Partner Relationship Manager SUSE LINUX GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 421 3064385 - M: +49 179 2279480 F: +49 421 3064387 - hartmut.meyer@novell.com ---------------------------------------------------- SUSE® Linux Enterprise 10 - Your Linux is ready http://www.novell.com/linux
Hartmut Meyer wrote:
On Wednesday 20 December 2006 07:45, Mark Goldstein wrote:
Patrick, that's not correct. As I wrote I had no problem accessing these sites and I have 2.6.18.2-34-default kernel on 2 machines.
Only guessing: you're accessing http through a proxy, right?
Interesting idea. The 10.2 machine i386 at work that did work as well was accessing www.marymount.com through the squid proxy on our 9.3 server. It is definitely not an arch problem. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 20 December 2006 01:45, Mark Goldstein wrote:
On 12/20/06, Patrick Shanahan <ptilopteri@gmail.com> wrote:
me thinks it not be a 10.2 problem, but a kernel problem. I have 10.1 with 2.6.18.5-jen40-default and cannot access the site. I have read the thread and, as I recall, noone with 2.6.18+ could access, but several with 2.6.16 could.
Patrick, that's not correct. As I wrote I had no problem accessing these sites and I have 2.6.18.2-34-default kernel on 2 machines.
FWIW I did make oldconfig with 2.6.19.1-default. Compiled and installed the new kernel. I can now get to Mary Mount but www.keh.com is still broken. Nick -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 20 December 2006 12:29, Nick Zentena wrote:
On Wednesday 20 December 2006 01:45, Mark Goldstein wrote:
On 12/20/06, Patrick Shanahan <ptilopteri@gmail.com> wrote:
me thinks it not be a 10.2 problem, but a kernel problem. I have 10.1 with 2.6.18.5-jen40-default and cannot access the site. I have read the thread and, as I recall, noone with 2.6.18+ could access, but several with 2.6.16 could.
Patrick, that's not correct. As I wrote I had no problem accessing these sites and I have 2.6.18.2-34-default kernel on 2 machines.
FWIW I did make oldconfig with 2.6.19.1-default. Compiled and installed the new kernel. I can now get to Mary Mount but www.keh.com is still broken.
I can get to Mary Mount too, where I previously could not! Seems the site is fixed??? Comfirmed: www.keh.com is still broken. Cheers, Leen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/20/06, Leendert Meyer <leen.meyer@home.nl> wrote:
On Wednesday 20 December 2006 12:29, Nick Zentena wrote:
On Wednesday 20 December 2006 01:45, Mark Goldstein wrote:
On 12/20/06, Patrick Shanahan <ptilopteri@gmail.com> wrote:
me thinks it not be a 10.2 problem, but a kernel problem. I have 10.1 with 2.6.18.5-jen40-default and cannot access the site. I have read the thread and, as I recall, noone with 2.6.18+ could access, but several with 2.6.16 could.
Patrick, that's not correct. As I wrote I had no problem accessing these sites and I have 2.6.18.2-34-default kernel on 2 machines.
FWIW I did make oldconfig with 2.6.19.1-default. Compiled and installed the new kernel. I can now get to Mary Mount but www.keh.com is still broken.
I can get to Mary Mount too, where I previously could not! Seems the site is fixed???
Comfirmed: www.keh.com is still broken.
Cheers,
Guys, please re-check. Somebody mistyped it as marymount.com. This one is working. It was marymount.edu that still fails (on ALL my boxes, including Win XP). -- Mark Goldstein -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 20 December 2006 06:44, Mark Goldstein wrote:
Guys, please re-check. Somebody mistyped it as marymount.com. This one is working. It was marymount.edu that still fails (on ALL my boxes, including Win XP).
Okay neither are working for me after upgrading the kernal. Nick -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006/12/20 06:59 (GMT-0500) Nick Zentena apparently typed:
On Wednesday 20 December 2006 06:44, Mark Goldstein wrote:
Guys, please re-check. Somebody mistyped it as marymount.com. This one is working. It was marymount.edu that still fails (on ALL my boxes, including Win XP).
Okay neither are working for me after upgrading the kernal.
Upgrading to which kernel? I tried on 3 different boxes with about 8 different operating systems. The only failures came from using 2.6.18 kernels. XP and OS/2 reach it fine, as do 2.6.19 and <=2.6.17. -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006-12-20 08:06, Felix Miata wrote:
On 2006/12/20 06:59 (GMT-0500) Nick Zentena apparently typed:
Okay neither are working for me after upgrading the kernal.
Upgrading to which kernel? I tried on 3 different boxes with about 8 different operating systems. The only failures came from using 2.6.18 kernels. XP and OS/2 reach it fine, as do 2.6.19 and <=2.6.17.
Nick put up a 2.6.19 kernel, but with make oldconfig. A clue perhaps? -- The best way to accelerate a computer running Windows is at 9.81 m/s² -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 20 December 2006 12:44, Mark Goldstein wrote:
On 12/20/06, Leendert Meyer <leen.meyer@home.nl> wrote:
On Wednesday 20 December 2006 12:29, Nick Zentena wrote:
On Wednesday 20 December 2006 01:45, Mark Goldstein wrote:
On 12/20/06, Patrick Shanahan <ptilopteri@gmail.com> wrote:
me thinks it not be a 10.2 problem, but a kernel problem. I have 10.1 with 2.6.18.5-jen40-default and cannot access the site. I have read the thread and, as I recall, noone with 2.6.18+ could access, but several with 2.6.16 could.
Patrick, that's not correct. As I wrote I had no problem accessing these sites and I have 2.6.18.2-34-default kernel on 2 machines.
FWIW I did make oldconfig with 2.6.19.1-default. Compiled and installed the new kernel. I can now get to Mary Mount but www.keh.com is still broken.
I can get to Mary Mount too, where I previously could not! Seems the site is fixed???
Comfirmed: www.keh.com is still broken.
Cheers,
Guys, please re-check. Somebody mistyped it as marymount.com. This one is working. It was marymount.edu that still fails (on ALL my boxes, including Win XP). -- Mark Goldstein
Arg! :( I'm sorry, I got that .com address from the mail right above. I'll send that person a mail to ask him to recheck. Sorry, Leen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Dec 19, 2006 at 08:53:13PM -0500, Patrick Shanahan wrote:
me thinks it not be a 10.2 problem, but a kernel problem. I have 10.1 with 2.6.18.5-jen40-default and cannot access the site. I have read the thread and, as I recall, noone with 2.6.18+ could access, but several with 2.6.16 could.
I am running 10.1 with a self-compiled "Linux seahunt 2.6.18" kernel, and it raises the Marymount site just fine. If it's a 2.6.18 problem, it's related to something in the SUSE version of 2.6.18, because kernel.org's 2.6.18 works fine. Michael -- San Francisco, CA -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006/12/20 05:15 (GMT-0800) Michael Nelson apparently typed:
I am running 10.1 with a self-compiled "Linux seahunt 2.6.18" kernel, and it raises the Marymount site just fine. If it's a 2.6.18 problem, it's related to something in the SUSE version of 2.6.18, because kernel.org's 2.6.18 works fine.
Have you read the bug? Etch's and Fedora's 2.6.18 kernels also fail. OTOH, the vanilla 2.6.19 kernel worked for me yesterday, and still works today. -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 20 December 2006 09:02, Felix Miata wrote:
Have you read the bug? Etch's and Fedora's 2.6.18 kernels also fail. OTOH, the vanilla 2.6.19 kernel worked for me yesterday, and still works today.
How did you configure it? I downloaded it and did an make oldconfig. It still fails here. Nick -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006/12/20 09:01 (GMT+-0500) Nick Zentena apparently typed:
On Wednesday 20 December 2006 09:02, Felix Miata wrote:
Have you read the bug? Etch's and Fedora's 2.6.18 kernels also fail. OTOH, the vanilla 2.6.19 kernel worked for me yesterday, and still works today.
How did you configure it? I downloaded it and did an make oldconfig. It still fails here.
I didn't build it specifically for testing this problem, instead for cifs & smbfs testing. I stripped out a lot of useless hardware support to conserve space. http://mrmazda.no-ip.com/tmp/config -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 20 December 2006 05:15, Michael Nelson wrote:
On Tue, Dec 19, 2006 at 08:53:13PM -0500, Patrick Shanahan wrote:
me thinks it not be a 10.2 problem, but a kernel problem. I have 10.1 with 2.6.18.5-jen40-default and cannot access the site. I have read the thread and, as I recall, noone with 2.6.18+ could access, but several with 2.6.16 could.
I am running 10.1 with a self-compiled "Linux seahunt 2.6.18" kernel, and it raises the Marymount site just fine. If it's a 2.6.18 problem, it's related to something in the SUSE version of 2.6.18, because kernel.org's 2.6.18 works fine.
Funny - I couldn't reach it this morning. I can now. I then checked: Owner: Marymount University 2807 North Glebe Rd Arlington VA US 22207 IP Address: 198.100.0.3 Operating System: Solaris 8 Web Server: Apache/1.3.14 Unix tomcat/1.0 Last Updated: 9-Apr-2001 No wonder they're having problems, they need to run the web server on a REAL OS. :P -- kai www.perfectreign.com || www.4thedadz.com a turn signal is a statement, not a request -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 20 December 2006 07:43, Kai Ponte wrote:
...
Funny - I couldn't reach it this morning. I can now.
I then checked:
Owner: Marymount University 2807 North Glebe Rd Arlington VA US 22207 IP Address: 198.100.0.3 Operating System: Solaris 8 Web Server: Apache/1.3.14 Unix tomcat/1.0 Last Updated: 9-Apr-2001
Solaris 8 is a bit long in the tooth, and it's certainly not out of the question that there could be a subtle error in its TCP/IP stack, especially if the administrators at Marymount are not diligent about updates and patches, but I think it's a long shot. Where did you get that information? It's not part of the "whois" output.
... kai
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Randall R Schulz <rschulz@sonic.net> [12-20-06 11:53]:
Where did you get that information? It's not part of the "whois" output.
Don't know where *he* got it but, http://toolbar.netcraft.com/site_report?url=http://www.marymount.edu -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 20 December 2006 08:51, Randall R Schulz wrote:
On Wednesday 20 December 2006 07:43, Kai Ponte wrote:
...
Funny - I couldn't reach it this morning. I can now.
I then checked:
Owner: Marymount University 2807 North Glebe Rd Arlington VA US 22207 IP Address: 198.100.0.3 Operating System: Solaris 8 Web Server: Apache/1.3.14 Unix tomcat/1.0 Last Updated: 9-Apr-2001
Solaris 8 is a bit long in the tooth, and it's certainly not out of the question that there could be a subtle error in its TCP/IP stack, especially if the administrators at Marymount are not diligent about updates and patches, but I think it's a long shot.
Who knows. I just noticed the older software.
Where did you get that information? It's not part of the "whois" output.
http://news.netcraft.com/ Whois won't spit that information out. I could also use nmap. -- kai www.perfectreign.com || www.4thedadz.com a turn signal is a statement, not a request -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006-12-19 19:45, Felix Miata wrote:
On 2006/12/19 19:18 (GMT-0600) Darryl Gregorash apparently typed:
Not "apparently" ;-)
BTW, Felix, you created the bug as normal severity. Shouldn't it be a tad higher than that? I don't think it's quite a blocker, but it's certainly major, IMO.
https://bugzilla.novell.com/page.cgi?id=fields.html#bug_severity
The way I read the instructions, the assignee should determine whether some deviation from normal is warranted for this particular bug. It's only major if you have to reach a particular site, which would make it a literal blocker for you. Zillions of other web sites don't produce the problem. In the overall scheme, this is more like trivial, which Mozilla's Bugzilla has, but not Novell's.
That isn't how I read it, particularly since my permissions allow me to edit any bug field :-) The OP could probably bump the bug up to P0, given that it's his work site -- and for him, that is surely a major loss of function at least. -- The best way to accelerate a computer running Windows is at 9.81 m/s² -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Felix suggested it is perhaps time for bugzilla.
I'll submit a report to bugzilla. Presently running 2.6.16 on my 10.2 box and able to access all sites. So, something is up with 2.6.18, as many have noted. Will wait for the kernel upgrades, but it would be interesting to know what the culprit is in all of this.
Chip -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 19 December 2006 11:01, Darryl Gregorash wrote:
The TCP stack idea seems most on track, but it is curious that it doesn't affect everyone running 10.2. 32 vs. 64 bit doesn't appear to answer it, or does SMP vs. non-SMP.
Actually, I don't thing either 32bit vs 64 bit is definitely excluded because several of the people reporting their hardware congiguration (up thread) failed to mention whether it DID or DID NOT work for them, and I'm too lazy to go back thru the whole thread and match worked/noworked with hardware. Same is true of SMP. Same is true of gigabit vs 10/100 nic. The best thing is a bugzilla so we can all report failures in a standard place and with standard info. -- _____________________________________ John Andersen
On 2006-12-19 16:17, John Andersen wrote:
On Tuesday 19 December 2006 11:01, Darryl Gregorash wrote:
The TCP stack idea seems most on track, but it is curious that it doesn't affect everyone running 10.2. 32 vs. 64 bit doesn't appear to answer it, or does SMP vs. non-SMP.
Actually, I don't thing either 32bit vs 64 bit is definitely excluded because several of the people reporting their hardware congiguration (up thread) failed to mention whether it DID or DID NOT work for them, and I'm too lazy to go back thru the whole thread and match worked/noworked with hardware.
Same is true of SMP.
Same is true of gigabit vs 10/100 nic.
I went through most of the previous messages, and found approximately an equal number of 32 and 64 bit systems with a problem. The actual CPU model/manufacturer is similarly not an issue. No one has mentioned a SMP kernel, in fact most who did mention the kernel clearly stated they were using the default. I think only you (or Randall??) mentioned a gigabit nic, whereas most others reported 10/100's (when the nic was identified at all).
The best thing is a bugzilla so we can all report failures in a standard place and with standard info.
Quite so; I don't think we are going to get any closer to figuring it out here. All I know for sure right now is that it went away in one instance where the user reverted to a 2.6.16, and in another where the user switched to a 2.6.19 kernel. Someone will come along for sure now, and say that a 2.6.19 kernel didn't solve it for him :-) -- The best way to accelerate a computer running Windows is at 9.81 m/s² -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 19 December 2006 14:44, Darryl Gregorash wrote:
No one has mentioned a SMP kernel, in fact most who did mention the kernel clearly stated they were using the default.
Default IS a SMP. Its the same kernel. On smp hardware it runs smp, on single processor it defaults to single processor mode. But your point is taken, several have reported that they have single processor machines that can't reach it either. Currently my only 10.2 machine is smp x86_64 and has all 10/100/1000 nics. I plan to upgrade another machine 32bit with old nics, to 10.2 tonight. -- _____________________________________ John Andersen
On 2006/12/19 14:01 (GMT-0600) Darryl Gregorash apparently typed: http://www.marymount.edu/
The OP has reported that reverting to the 2.6.16 kernel allows him to access the sites. Everyone reporting the problem so far has a 2.6.18 kernel, and the same problem has also been mentioned with other distros using that kernel version.
On my Sempron/NForce2 box that fails to reach it using 10.2 with the stock kernel, booting a generic 2.6.19 kernel instead fixes it. -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 19 December 2006 13:50, Felix Miata wrote:
On 2006/12/19 14:01 (GMT-0600) Darryl Gregorash apparently typed:
The OP has reported that reverting to the 2.6.16 kernel allows him to access the sites. Everyone reporting the problem so far has a 2.6.18 kernel, and the same problem has also been mentioned with other distros using that kernel version.
On my Sempron/NForce2 box that fails to reach it using 10.2 with the stock kernel, booting a generic 2.6.19 kernel instead fixes it.
Everybody with the problem seems to be running SUSE's 2.6.18.2-34-default. So maybe it was something that kernel hackers found and fixed already and we just need to wait till a new 10.2 kernel is releases? -- _____________________________________ John Andersen
On 2006/12/19 14:02 (GMT-0900) John Andersen apparently typed:
On Tuesday 19 December 2006 13:50, Felix Miata wrote:
On 2006/12/19 14:01 (GMT-0600) Darryl Gregorash apparently typed:
The OP has reported that reverting to the 2.6.16 kernel allows him to access the sites. Everyone reporting the problem so far has a 2.6.18 kernel, and the same problem has also been mentioned with other distros using that kernel version.
On my Sempron/NForce2 box that fails to reach it using 10.2 with the stock kernel, booting a generic 2.6.19 kernel instead fixes it.
Everybody with the problem seems to be running SUSE's 2.6.18.2-34-default.
So maybe it was something that kernel hackers found and fixed already and we just need to wait till a new 10.2 kernel is releases?
2.6.18.2-33-default also fails here on PIII/i815. -- "Let your conversation be always full of grace." Colossians 4:6 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dominique Leuenberger wrote:
What I can say so far: in the company, where I have a proxy between my Suse box and this specific server, it works. So it seems to be a problem caused by two 'incompatible' tcp stacks. Very nice thing to find in the net.
I'll stay a bit on it. It could be related to HTTP headers. Proxies do change them a bit.
Russell Jones -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (15)
-
Chip Cooper -
Darryl Gregorash -
Dominique Leuenberger -
Felix Miata -
Hartmut Meyer -
Joe Morris (NTM) -
John Andersen -
Kai Ponte -
Leendert Meyer -
Mark Goldstein -
Michael Nelson -
Nick Zentena -
Patrick Shanahan -
Randall R Schulz -
Russell Jones