similar to: Network card throwing messages I dont understand

I am having an issue where eth1 is throwing some messages and stops responding. Restarting networking doesn't work and also just bringing down eth1 with 'ifdown' doesn't fix it. I have never seen anything like these messages: eth1: no IPv6 routers present r8169 0000:03:00.0: eth1: rtl_counters_cond == 1 (loop: 1000, delay: 10). r8169 0000:03:00.0: eth1: rtl_chipcmd_cond == 1

Hello, Please excuse my complete xen ignorance but I am hoping someone will be able ot help me out here. I recently built my first Xen box using a 2, 1TB drives in a raid configuration, 2TB total. I installed Xen, I am able to access it via XenCenter. However, I am trying to use some of that 2TB as a local datastore but for the life of me I cannot get it mounted, I keep on getting this error:

Hi All, I have 2 NICS in this system. CentOS 6.4 eth0 is the virtual IP from PFSense mapping connected to the router, works fine. eth1 is a second NIC that I have assigned a private IP to and connected it to a switch on the private network. I have many other private devices, so I know this setup works. When I connect the cable to the switch and bring up eth1 the system basically stops taking

Hi All, I was able to create a public key for one of my servers that I log into frequently. Now I want to do this for a few more servers (where I use the same user id) and my user id on my laptop is the same as the servers. I also want to use PKA for other users accounts on the servers (for website editing and SFTP transfers) where my id on my laptop does NOT match the user on the server. I

Hi All, I setup Fetchmail and wanted to use Mutt to read e-mail. I used to use Pine and I just am sick of GUI e-mail clients these days. Bloat, complication and unreliable. Pine was my first ever e-mail client. I prefer to use POP still as I want may mail on my machine at all times. I can go into mutt and execute: 'fetchmail -v' and watch it bring down my e-mail. But in mutt i dont see

Hi Karthik, thanks for taking a look at this. I'm not working with gluster long enough to make heads or tails out of the logs. The logs are attached to this mail and here is the other information: # gluster volume info home Volume Name: home Type: Replicate Volume ID: fe6218ae-f46b-42b3-a467-5fc6a36ad48a Status: Started Snapshot Count: 1 Number of Bricks: 1 x 3 = 3 Transport-type: tcp