So, I'm getting an error where the network service and NetworkManager apparently don't agree on how to bring up vlans on bonded nics. Things come up if you 'ifup ..' manually. I thought I'd check if there were any updates, forgetting to fix what NetworkManger had done to /etc/resolv.conf and:
http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 30381 milliseconds') Trying other mirror. ^C^C^C ^C^C^C
Current download cancelled, interrupt (ctrl-c) again within two seconds to exit.
Yeah - I did hit it about 6 times there. What do you have to do to make it actually stop in some reasonable amount of time?
try CTRL-Z to put that running process in your shell to sleep, then:
bg 1
to put the process in the background. Then you can run:
killall -TERM yum
to kill all the yum processes. If that doesn't kill it after running a couple of times, then use:
killall -9 yum
and that should do it.
Chris
On Fri, Feb 20, 2015 at 4:00 PM, Les Mikesell lesmikesell@gmail.com wrote:
So, I'm getting an error where the network service and NetworkManager apparently don't agree on how to bring up vlans on bonded nics. Things come up if you 'ifup ..' manually. I thought I'd check if there were any updates, forgetting to fix what NetworkManger had done to /etc/resolv.conf and:
http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 30381 milliseconds') Trying other mirror. ^C^C^C ^C^C^C
Current download cancelled, interrupt (ctrl-c) again within two seconds to exit.
Yeah - I did hit it about 6 times there. What do you have to do to make it actually stop in some reasonable amount of time?
-- Les Mikesell lesmikesell@gmail.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Oh, and if you don't have killall installed, you can use:
ps -ef | grep yum
to get the pid and then use:
kill -TERM pid
or easier even is:
kill -TERM `pid of yum`
Chris
On Fri, Feb 20, 2015 at 4:13 PM, Chris Stone axisml@gmail.com wrote:
try CTRL-Z to put that running process in your shell to sleep, then:
bg 1
to put the process in the background. Then you can run:
killall -TERM yum
to kill all the yum processes. If that doesn't kill it after running a couple of times, then use:
killall -9 yum
and that should do it.
Chris
On Fri, Feb 20, 2015 at 4:00 PM, Les Mikesell lesmikesell@gmail.com wrote:
So, I'm getting an error where the network service and NetworkManager apparently don't agree on how to bring up vlans on bonded nics. Things come up if you 'ifup ..' manually. I thought I'd check if there were any updates, forgetting to fix what NetworkManger had done to /etc/resolv.conf and:
http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 30381 milliseconds') Trying other mirror. ^C^C^C ^C^C^C
Current download cancelled, interrupt (ctrl-c) again within two seconds to exit.
Yeah - I did hit it about 6 times there. What do you have to do to make it actually stop in some reasonable amount of time?
-- Les Mikesell lesmikesell@gmail.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Chris Stone AxisInternet, Inc. www.axint.net
oops - it's Friday - that should be:
kill -TERM `pidof yum`
no space between pid and of.
Chris
On Fri, Feb 20, 2015 at 4:15 PM, Chris Stone axisml@gmail.com wrote:
Oh, and if you don't have killall installed, you can use:
ps -ef | grep yum
to get the pid and then use:
kill -TERM pid
or easier even is:
kill -TERM `pid of yum`
Chris
On Fri, Feb 20, 2015 at 4:13 PM, Chris Stone axisml@gmail.com wrote:
try CTRL-Z to put that running process in your shell to sleep, then:
bg 1
to put the process in the background. Then you can run:
killall -TERM yum
to kill all the yum processes. If that doesn't kill it after running a couple of times, then use:
killall -9 yum
and that should do it.
Chris
On Fri, Feb 20, 2015 at 4:00 PM, Les Mikesell lesmikesell@gmail.com wrote:
So, I'm getting an error where the network service and NetworkManager apparently don't agree on how to bring up vlans on bonded nics. Things come up if you 'ifup ..' manually. I thought I'd check if there were any updates, forgetting to fix what NetworkManger had done to /etc/resolv.conf and:
http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 30381 milliseconds') Trying other mirror. ^C^C^C ^C^C^C
Current download cancelled, interrupt (ctrl-c) again within two seconds to exit.
Yeah - I did hit it about 6 times there. What do you have to do to make it actually stop in some reasonable amount of time?
-- Les Mikesell lesmikesell@gmail.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Chris Stone AxisInternet, Inc. www.axint.net
-- Chris Stone AxisInternet, Inc. www.axint.net
On Fri, Feb 20, 2015 at 04:13:13PM -0700, Chris Stone wrote:
try CTRL-Z to put that running process in your shell to sleep, then:
bg 1
You're missing a % there
killall -TERM yum
Or just "control-Z" and then 'kill -9 %1'
You don't need to background the job and then kill every process matching a name.
On Fri, Feb 20, 2015 at 5:19 PM, Stephen Harris lists@spuddy.org wrote:
On Fri, Feb 20, 2015 at 04:13:13PM -0700, Chris Stone wrote:
try CTRL-Z to put that running process in your shell to sleep, then:
bg 1
You're missing a % there
killall -TERM yum
Or just "control-Z" and then 'kill -9 %1'
You don't need to background the job and then kill every process matching a name.
I probably would have just ssh'd in from a different window, except that ssh logins take forever with DNS broken. Thanks - and I think I found the source of the network issue. I had a typo in the NM_CONTROLLED=no line in the ifcfg-bond0 file and NetworkManger was failing with: Error: no device found for connection 'System bond0' when it shouldn't even have been involved.
-
Chris Stone -
Les Mikesell -
Stephen Harris