similar to: Access Problem after update to CentOS 7.1

On Fri, 2015-04-10 at 18:25 -0700, Greg Lindahl wrote: > On Fri, Apr 10, 2015 at 06:33:27AM -0500, Johnny Hughes wrote: > > > What may be happening is that you may need to be on the console and > > accept the license on the first reboot after the update. > > > > We tried to turn this off for CLI only installs, but in some > > combinations of software, you may

On Sat, 2015-04-04 at 16:47 -0500, Gregory P. Ennis wrote: > Everyone, > > This morning I did a manual yum update on our a mail server to 7.1 > without any incident or problems. A new kernel was installed, and I > rebooted after the update. > > When I rebooted the machine I could not gain ssh access to it from an > external ip address. I was able to ssh to this mail

I hope I am not just mudding the water but I ran into a problem in updating to 7.1 and a license accptance, which I solved - for me.?I booted into a gui in 7.0, opened a terminal and issued a sudo yum update command. I don't know at this time whether that qualifies as a GUI update or a CLI update. After the update to 7.1, the reboot (in the terminal in X) hung up on a message that said

> On 05 Apr 2015, at 14:35, Gregory P. Ennis <PoMec at PoMec.Net> wrote: > I sure need some help on this one, if any of you have ideas of what to > do next I would surely appreciate it. An additional aspect of this > scenario is that when I have used ssh to connect to this mail server via > the internal network, I am able to ssh out of the machine to one of the > internal

On 04/09/2015 03:50 PM, Gregory P. Ennis wrote: > I am still having difficulty with this problem. # ip addr show # ip route show # iptables -L -n -v # tcpdump -nn -i <your primary interface> host <ip.ad.dr.es> Watch tcpdump's output and try to connect from the IP address you name on the command line. Don't ssh to that host and then back, or tcpdump will show you your

On Thu, 2015-04-09 at 17:02 -0700, Gordon Messmer wrote: > On 04/09/2015 03:50 PM, Gregory P. Ennis wrote: > > I am still having difficulty with this problem. > > # ip addr show > > # ip route show > > # iptables -L -n -v > > # tcpdump -nn -i <your primary interface> host <ip.ad.dr.es> > > Watch tcpdump's output and try to connect from

> > > > Thanks as always for what you and the rest of the CentOS team do, just > > appreciation and admiration for all you guys (and gals?) do for the > > community. > > Rob > > To be perfectly honest, I am not thrilled with the movement either from > the enterprise stability point of view .. BUT .. with respect to desktop > and software development it

On 04/04/2015 04:47 PM, Gregory P. Ennis wrote: > Everyone, > > This morning I did a manual yum update on our a mail server to 7.1 > without any incident or problems. A new kernel was installed, and I > rebooted after the update. > > When I rebooted the machine I could not gain ssh access to it from an > external ip address. I was able to ssh to this mail server

On Sat, 2015-04-04 at 16:47 -0500, Gregory P. Ennis wrote: > Everyone, > > This morning I did a manual yum update on our a mail server to 7.1 > without any incident or problems. A new kernel was installed, and I > rebooted after the update. > > When I rebooted the machine I could not gain ssh access to it from an > external ip address. I was able to ssh to this mail

On Fri, Apr 10, 2015 at 06:33:27AM -0500, Johnny Hughes wrote: > What may be happening is that you may need to be on the console and > accept the license on the first reboot after the update. > > We tried to turn this off for CLI only installs, but in some > combinations of software, you may still get the acceptance screen and > have to complete it. So just to be clear, some

On 04/04/2015 04:47 PM, Gregory P. Ennis wrote: > Everyone, > > This morning I did a manual yum update on our a mail server to 7.1 > without any incident or problems. A new kernel was installed, and I > rebooted after the update. > > When I rebooted the machine I could not gain ssh access to it from an > external ip address. I was able to ssh to this mail server

On 04/12/2015 10:29 PM, Rob Kampen wrote: > On 04/13/2015 11:42 AM, Gregory P. Ennis wrote: >> On Fri, 2015-04-10 at 18:25 -0700, Greg Lindahl wrote: >>> On Fri, Apr 10, 2015 at 06:33:27AM -0500, Johnny Hughes wrote: >>> >>>> What may be happening is that you may need to be on the console and >>>> accept the license on the first reboot after the

On 04/14/2015 01:07 AM, Johnny Hughes wrote: > On 04/13/2015 06:49 AM, Johnny Hughes wrote: >> On 04/12/2015 10:29 PM, Rob Kampen wrote: >>> On 04/13/2015 11:42 AM, Gregory P. Ennis wrote: >>>> On Fri, 2015-04-10 at 18:25 -0700, Greg Lindahl wrote: >>>>> On Fri, Apr 10, 2015 at 06:33:27AM -0500, Johnny Hughes wrote: >>>>>

On 04/13/2015 11:17 PM, Rob Kampen wrote: > On 04/14/2015 01:07 AM, Johnny Hughes wrote: >> On 04/13/2015 06:49 AM, Johnny Hughes wrote: >>> On 04/12/2015 10:29 PM, Rob Kampen wrote: >>>> On 04/13/2015 11:42 AM, Gregory P. Ennis wrote: >>>>> On Fri, 2015-04-10 at 18:25 -0700, Greg Lindahl wrote: >>>>>> On Fri, Apr 10, 2015 at

Everyone, This morning I did a manual yum update on our a mail server to 7.1 without any incident or problems. A new kernel was installed, and I rebooted after the update. When I rebooted the machine I could not gain ssh access to it from an external ip address. I was able to ssh to this mail server through a different machine on the local network. At first I thought the problem was

I have a screwed up disk arrangement, but I have had no trouble because of it after using it over a year. Recently I did a yum update. After starting the update, which included a new kernel, it seemed to either freeze or loop. It was a long time at the? prompt and I got impatient and did a Ctrl C. I then tried to re-boot. The result was a kernel panic. I am keeping 5 kernels and when I select? the

On 04/13/2015 11:42 AM, Gregory P. Ennis wrote: > On Fri, 2015-04-10 at 18:25 -0700, Greg Lindahl wrote: >> On Fri, Apr 10, 2015 at 06:33:27AM -0500, Johnny Hughes wrote: >> >>> What may be happening is that you may need to be on the console and >>> accept the license on the first reboot after the update. >>> >>> We tried to turn this off for CLI

On 04/13/2015 06:49 AM, Johnny Hughes wrote: > On 04/12/2015 10:29 PM, Rob Kampen wrote: >> On 04/13/2015 11:42 AM, Gregory P. Ennis wrote: >>> On Fri, 2015-04-10 at 18:25 -0700, Greg Lindahl wrote: >>>> On Fri, Apr 10, 2015 at 06:33:27AM -0500, Johnny Hughes wrote: >>>> >>>>> What may be happening is that you may need to be on the console

Message: 8 On Jan 1, 2015, at 3:49 PM, Don Vogt <dnvot at yahoo.com> wrote: > when I select? the second kernel it boots OK. Now I would like to remove the bad kernel. The only thing that makes this tricky is that you can?t just say ?rpm -e kernel? because there is more than one ?kernel? package installed.? You need to know the exact package name. >> I?m assuming you?re using

On 30.07.2015 15:25, Sandro Bonazzola wrote: > Note that qemu-kvm-ev > is built within Virt SIG too in kvm-common-testing CBS repo Packages from kvm-common-testing probably is not a good choice for using in production environment. I found in internet package http://cbs.centos.org/repos/virt7-kvm-common-release/source/SRPMS/qemu-kvm-ev-2.1.2-23.el7_1.3.1.src.rpm