I have this client which initiates a 3 way handshake with a SYN packet but there is no SYN ACK response. We figured out that it was because the client did not pad the end of the TCP headers with 0's or F's but with other values (we used packet builder software to confirm this). The server is Windows XP 32bits version 2002 Service Pack 3. I tried it on Windows 7 and the problem does not occur. Has anyone ever heard of this type of problem? Could it be because the server runs on windows XP? I've tried simplifying the network link (local link), i've tried with the server running in safe mode and same results occur. The providers of the client say they have validated that it works with a windows XP server on their end.
I know how to exclude certain packages when updating RHEL like:
yum update --exclude=kernel
How would I prevent yum from updating from 5.3 to 5.5
I have a pc running windows 7. I have vmwareplayer running RHEL5 I have 1 physical ethernet connection. this ethernet connection is wired to a hub. there is another device on that hub that needs to be in a certain subnetwork (192.168.0.xxx)(lets call him device X) but the general network is 192.168.1.xxx
How can I configure the network adapters so that I can ping device X from RHEL5 in the vm.
Originally I could ping google from both windows and rhel (I was in the .1 network) but not device X since he is on a different subnetwork address. Now that I have put it on the .0 I can ping device X from windows but not from rhel5 and cannot access the web. I did this by manually setting the IP address.
I have 3 identical machines (hardware wise) that all have RHEL 5.3 installed. 2 of those machines have the Xen kernel and one doesnt. I cannot install nvidia drivers on the ones that have the xen kernel and so I was wondering how I managed to do this and how to replace them with normal kernels. Could this of happened during install time when for example I was queried on certain components to install? (development,virtualization, webserver)
UPDATE: I just read somewhere that "VMware conflicts with the Xen hypervisor in the Linux kernel, making their use mutually exclusive" so my guess is the problem is indeed due to the virtualization component I selected during install
UPDATE2: I just read how to do it (by using pirut) but even then there is a known bug Red Hat Bugzilla – Bug 441704 maybe the users didn't do it right so I am going to follow the procedure here Changing to a non-xen kernel in CentOS 5 and if this fails I will simply have to reinstall RHEL from scratch.
UPDATE3: Ok that link worked. the only extra thing I had to do to get the driver to install was to: yum install kernel-devel
The company I work for just bought 3 PowerEdge 2970 servers and they all have the same problem.
- Is this server worth buying or are the problems that come with it make it not worth it?
- Are there alot of issues with using an AMD processors (it's an Opteron)?
- Are you guys able to pin point the problem if I give details on which errors I get in the event logs?
Here is the problem:
1.Power on server. It boots up to the red hat splash screen.
2.In the middle of the boot up the server crashes with the following errors:
-CPU Machine Chk: processor sensor, transition to non-recoverable was asserted
-PCI Parity Err: critical event sensor, PCI PERR (BUS 0 DEVICE 1 FUNC 0)
Then I tried to update the bios and the BMC but the problem was still there. After that I tried to update the OS (it had red hat Enterprise 5.1) to red Hat 5.3 There was something odd there too. I booted the server with the Build and update utility then selected install OS. I selected red hat enterprise 5.3 x86_64. It queried me for the x86_64 media so I put in the disc that said : supplementary disc 1 of 1 for 64-bit AMD64 and Intel 64. It said wrong disc. So then I used the disc that said: installation disc 1 of 1 for 64-bit Intel Itanium. My guess is thats the disc I needed to use all along.
After this the system was able to boot up to the command line login screen. I loggued in and typed : startx to get into the gui environment. At that point less than a page of text scrolled fast and the server crashed without showing anything gui related.
At that point I had at 2 different errors(notice the device is 4 now, gonna check which device it is):
-PCI Parity Err: critical event sensor, PCI PERR (BUS 0 DEVICE 4 FUNC 0)
-PCI Sytem Error:critical event sensor, PCI SERR(BUS 0 DEVICE 4 FUNC 0)
So today the tech guy came with a bunch of parts and basically rebuilt the server (PCI riser, mother board, DIMMs, a SAS card and something else I cant figure off the top of my head)on site but after that the problems were even worse. Some of these errors were(mind you at that point he was putting back some of the original parts so things got messy):
ECC uncorr Err: memory sensor, uncorrectable ECC (DIMM1 DIMM2) was asserted.
E1231 1.2V HT core power GD
E1911 <3 ERRORS check log
E1000 failsafe
Tomorrow he is coming back with a power supply...
UPDATE: Seems like I cant waste anymore time on this. We are calling the sales people and asking for new servers.