Re: F10, NetworkManager, and intermittent dns -- Update
by McGuffey, David C.
On Mon, 26 Jan 2009 07:21:05 -0700, Christopher A. Williams wrote:
>
> On Mon, 2009-01-26 at 08:47 -0500, Tom Horsley wrote:
> > On Mon, 26 Jan 2009 23:23:49 +1100
> > David Timms wrote:
> >
> > > Tom Horsley wrote:
> > > > On Fri, 23 Jan 2009 13:32:08 -0500
> > > > McGuffey, David C. wrote:
> > > >
> > > >> Update: Intermittent dns is still present.
> > > >
> > > > I'd strongly suspect this is NM getting the resolv.conf file
> > > > correct on initial connect, then screwing it up on
> > > > subsequent DHCP lease renewal.
> > > I get the no entries in /etc/resolv.conf directly after logging in
> > > (workaround - an NM entry with static IP, and dns). Is there a
more
> > > permanent fix for Fedora 10 (upgraded from F9) ?
> >
> > In /etc/sysconfig/network-scripts/ifcfg-eth0
> >
> > I have the line:
> >
> > PEERDNS=no
> >
> > which (in theory) prevents NM from doing anything at all to
> > the resolv.conf file when acting on that interface (of course
> > you then have to make sure you set resolv.conf yourself).
>
> I thought NM had a know bug where it did not yet respect the
PEERDNS=no
> entry.
>
> Has this been fixed?
>
> The only (and most unfortunate) way I have been able to reliably keep
my
> resolf.conf file from getting waxed by NM has been to set it as
> immutable. A _very_ nasty way of doing things, but it does work.
>
> Cheers,
>
> Chris
>
Problem persists. Have had several batches of patches pushed through
yum auto update, but nothing concerning NM to fix this problem.
I set PEERDNS=no with no affect.
I set /etc/resolv.conf to a workable solution and then removed the write
bits and set it immutable. I get errors in /var/log/messages about it,
but the behavior is still the same. After a reboot, all is OK. After a
while, dns dies. Restarting NM brings it back to life...then it dies a
few minutes later. As long as someone is actively accessing the net,
dns seems to stay up. But give it a few minutes of idle time and
something causes it to stop. Here is a snapshot of /var/log/messages
before, during, and after a NM restart. Can anyone figure out what is
going wrong with dns?
Feb 2 21:23:45 desk NetworkManager: <WARN> nm_signal_handler():
Caught signal 15, shutting down normally.
Feb 2 21:23:45 desk NetworkManager: <info> (eth0): now unmanaged Feb
2 21:23:45 desk NetworkManager: <info> (eth0): device state
change: 8 -> 1
Feb 2 21:23:45 desk NetworkManager: <info> (eth0): deactivating device
(reason: 36).
Feb 2 21:23:45 desk NetworkManager: <info> eth0: canceled DHCP
transaction, dhcp client pid 2034 Feb 2 21:23:45 desk NetworkManager:
<WARN>
nm_named_manager_remove_ip4_config(): Could not commit DNS changes.
Error: 'Could not replace /etc/resolv.conf: Operation not permitted#012'
Feb 2 21:23:45 desk NetworkManager: <WARN> check_one_route(): (eth0)
error -34 returned from rtnl_route_del(): Sucess#012 Feb 2 21:23:45
desk avahi-daemon[2071]: Withdrawing address record for
192.168.1.2 on eth0.
Feb 2 21:23:45 desk avahi-daemon[2071]: Leaving mDNS multicast group on
interface eth0.IPv4 with address 192.168.1.2.
Feb 2 21:23:45 desk avahi-daemon[2071]: Interface eth0.IPv4 no longer
relevant for mDNS.
Feb 2 21:23:45 desk NetworkManager: <info> (eth0): cleaning up...
Feb 2 21:23:45 desk NetworkManager: <info> (eth0): taking down device.
Feb 2 21:23:45 desk avahi-daemon[2071]: Withdrawing address record for
fe80::207:e9ff:fef2:b64d on eth0.
Feb 2 21:23:45 desk NetworkManager: <info> disconnected by the system
bus.
Feb 2 21:23:45 desk nm-dispatcher.action: Error in get_property: The
name org.freedesktop.NetworkManager was not provided by any .service
files Feb 2 21:23:46 desk NetworkManager: <info> starting...
Feb 2 21:23:46 desk NetworkManager: <WARN>
nm_generic_enable_loopback(): error -17 returned from
rtnl_addr_add():#012Sucess#012
Feb 2 21:23:46 desk NetworkManager: <info> eth0: driver is 'e100'.
Feb 2 21:23:46 desk NetworkManager: <info> Found new Ethernet device
'eth0'.
Feb 2 21:23:46 desk NetworkManager: <info> (eth0): exported as
/org/freedesktop/Hal/devices/net_00_07_e9_f2_b6_4d
Feb 2 21:23:50 desk NetworkManager: <info> (eth0): device state
change: 1 -> 2
Feb 2 21:23:50 desk NetworkManager: <info> (eth0): bringing up device.
Feb 2 21:23:50 desk kernel: e100: eth0: e100_watchdog: link up,
100Mbps, full-duplex Feb 2 21:23:50 desk kernel: ADDRCONF(NETDEV_UP):
eth0: link is not ready Feb 2 21:23:50 desk kernel:
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Feb 2 21:23:50 desk
NetworkManager: <info> (eth0): preparing device.
Feb 2 21:23:50 desk NetworkManager: <info> (eth0): deactivating device
(reason: 2).
Feb 2 21:23:50 desk NetworkManager: <info> (eth0): carrier now ON
(device state 2) Feb 2 21:23:50 desk NetworkManager: <info> (eth0):
device state
change: 2 -> 3
Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) starting
connection 'System eth0'
Feb 2 21:23:50 desk NetworkManager: <info> (eth0): device state
change: 3 -> 4
Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 1
of 5 (Device Prepare) scheduled...
Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 1
of 5 (Device Prepare) started...
Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 2
of 5 (Device Configure) scheduled...
Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 1
of 5 (Device Prepare) complete.
Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 2
of 5 (Device Configure) starting...
Feb 2 21:23:50 desk NetworkManager: <info> (eth0): device state
change: 4 -> 5
Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 2
of 5 (Device Configure) successful.
Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 3
of 5 (IP Configure Start) scheduled.
Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 2
of 5 (Device Configure) complete.
Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 3
of 5 (IP Configure Start) started...
Feb 2 21:23:50 desk NetworkManager: <info> (eth0): device state
change: 5 -> 7
Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Beginning
DHCP transaction.
Feb 2 21:23:50 desk dhclient: Internet Systems Consortium DHCP Client
4.0.0 Feb 2 21:23:50 desk dhclient: Copyright 2004-2007 Internet
Systems Consortium.
Feb 2 21:23:50 desk dhclient: All rights reserved.
Feb 2 21:23:50 desk dhclient: For info, please visit
http://www.isc.org/sw/dhcp/ Feb 2 21:23:50 desk dhclient:
Feb 2 21:23:50 desk NetworkManager: <info> dhclient started with pid
4747
Feb 2 21:23:50 desk dhclient: Listening on LPF/eth0/00:07:e9:f2:b6:4d
Feb 2 21:23:50 desk dhclient: Sending on LPF/eth0/00:07:e9:f2:b6:4d
Feb 2 21:23:50 desk dhclient: Sending on Socket/fallback
Feb 2 21:23:50 desk NetworkManager: <info> Activation (eth0) Stage 3
of 5 (IP Configure Start) complete.
Feb 2 21:23:50 desk NetworkManager: <info> DHCP: device eth0 state
changed (null) -> preinit Feb 2 21:23:52 desk dhclient: DHCPDISCOVER on
eth0 to 255.255.255.255 port 67 interval 4 Feb 2 21:23:52 desk
avahi-daemon[2071]: Registering new address record for
fe80::207:e9ff:fef2:b64d on eth0.*.
Feb 2 21:23:53 desk dhclient: DHCPOFFER from 192.168.1.1 Feb 2
21:23:53 desk dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Feb 2 21:23:53 desk dhclient: DHCPACK from 192.168.1.1 Feb 2 21:23:53
desk NetworkManager: <info> DHCP: device eth0 state changed preinit ->
bound Feb 2 21:23:53 desk NetworkManager: <info> Activation (eth0)
Stage 4 of 5 (IP Configure Get) scheduled...
Feb 2 21:23:53 desk NetworkManager: <info> Activation (eth0) Stage 4
of 5 (IP Configure Get) started...
Feb 2 21:23:53 desk NetworkManager: <info> address 192.168.1.2
Feb 2 21:23:53 desk NetworkManager: <info> prefix 24 (255.255.255.0)
Feb 2 21:23:53 desk NetworkManager: <info> gateway 192.168.1.1
Feb 2 21:23:53 desk NetworkManager: <info> hostname 'desk'
Feb 2 21:23:53 desk NetworkManager: <info> nameserver '192.168.1.1'
Feb 2 21:23:53 desk NetworkManager: <info> domain name
'seclab.net'
Feb 2 21:23:53 desk NetworkManager: <info> Activation (eth0) Stage 5
of 5 (IP Configure Commit) scheduled...
Feb 2 21:23:53 desk NetworkManager: <info> Activation (eth0) Stage 4
of 5 (IP Configure Get) complete.
Feb 2 21:23:53 desk NetworkManager: <info> Activation (eth0) Stage 5
of 5 (IP Configure Commit) started...
Feb 2 21:23:53 desk avahi-daemon[2071]: Joining mDNS multicast group on
interface eth0.IPv4 with address 192.168.1.2.
Feb 2 21:23:53 desk avahi-daemon[2071]: New relevant interface
eth0.IPv4 for mDNS.
Feb 2 21:23:53 desk avahi-daemon[2071]: Registering new address record
for 192.168.1.2 on eth0.IPv4.
Feb 2 21:23:53 desk dhclient: bound to 192.168.1.2 -- renewal in 80417
seconds.
Feb 2 21:23:54 desk NetworkManager: <WARN>
nm_named_manager_add_ip4_config(): Could not commit DNS changes. Error:
'Could not replace /etc/resolv.conf: Operation not permitted#012'
Feb 2 21:23:54 desk NetworkManager: <info> (eth0): device state
change: 7 -> 8
Feb 2 21:23:54 desk NetworkManager: <WARN>
nm_named_manager_add_ip4_config(): Could not commit DNS changes. Error:
'Could not replace /etc/resolv.conf: Operation not permitted#012'
Feb 2 21:23:54 desk NetworkManager: <info> Policy set 'System eth0'
(eth0) as default for routing and DNS.
Feb 2 21:23:54 desk NetworkManager: <info> Activation (eth0)
successful, device activated.
Feb 2 21:23:54 desk NetworkManager: <info> Activation (eth0) Stage 5
of 5 (IP Configure Commit) complete.
Feb 2 22:56:55 desk NetworkManager: <WARN> nm_signal_handler(): Caught
signal 15, shutting down normally.
Feb 2 22:56:55 desk NetworkManager: <info> (eth0): now unmanaged Feb
2 22:56:55 desk NetworkManager: <info> (eth0): device state
change: 8 -> 1
Feb 2 22:56:55 desk NetworkManager: <info> (eth0): deactivating device
(reason: 36).
Feb 2 22:56:55 desk NetworkManager: <info> eth0: canceled DHCP
transaction, dhcp client pid 4747 Feb 2 22:56:55 desk NetworkManager:
<WARN>
nm_named_manager_remove_ip4_config(): Could not commit DNS changes.
Error: 'Could not replace /etc/resolv.conf: Operation not permitted#012'
Feb 2 22:56:55 desk NetworkManager: <WARN> check_one_route(): (eth0)
error -34 returned from rtnl_route_del(): Sucess#012 Feb 2 22:56:55
desk avahi-daemon[2071]: Withdrawing address record for
192.168.1.2 on eth0.
Feb 2 22:56:55 desk avahi-daemon[2071]: Leaving mDNS multicast group on
interface eth0.IPv4 with address 192.168.1.2.
Feb 2 22:56:55 desk avahi-daemon[2071]: Interface eth0.IPv4 no longer
relevant for mDNS.
Feb 2 22:56:55 desk NetworkManager: <info> (eth0): cleaning up...
Feb 2 22:56:55 desk NetworkManager: <info> (eth0): taking down device.
Feb 2 22:56:55 desk avahi-daemon[2071]: Withdrawing address record for
fe80::207:e9ff:fef2:b64d on eth0.
Feb 2 22:56:55 desk NetworkManager: <info> disconnected by the system
bus.
Feb 2 22:56:56 desk NetworkManager: <info> starting...
Feb 2 22:56:56 desk NetworkManager: <WARN>
nm_generic_enable_loopback(): error -17 returned from
rtnl_addr_add():#012Sucess#012
Feb 2 22:56:56 desk NetworkManager: <info> eth0: driver is 'e100'.
Feb 2 22:56:56 desk NetworkManager: <info> Found new Ethernet device
'eth0'.
Feb 2 22:56:56 desk NetworkManager: <info> (eth0): exported as
/org/freedesktop/Hal/devices/net_00_07_e9_f2_b6_4d
Feb 2 22:57:00 desk NetworkManager: <info> (eth0): device state
change: 1 -> 2
Feb 2 22:57:00 desk NetworkManager: <info> (eth0): bringing up device.
Feb 2 22:57:00 desk kernel: e100: eth0: e100_watchdog: link up,
100Mbps, full-duplex Feb 2 22:57:00 desk kernel: ADDRCONF(NETDEV_UP):
eth0: link is not ready Feb 2 22:57:00 desk kernel:
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Feb 2 22:57:00 desk
NetworkManager: <info> (eth0): preparing device.
Feb 2 22:57:00 desk NetworkManager: <info> (eth0): deactivating device
(reason: 2).
Feb 2 22:57:00 desk NetworkManager: <info> (eth0): carrier now ON
(device state 2) Feb 2 22:57:00 desk NetworkManager: <info> (eth0):
device state
change: 2 -> 3
Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) starting
connection 'System eth0'
Feb 2 22:57:00 desk NetworkManager: <info> (eth0): device state
change: 3 -> 4
Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 1
of 5 (Device Prepare) scheduled...
Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 1
of 5 (Device Prepare) started...
Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 2
of 5 (Device Configure) scheduled...
Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 1
of 5 (Device Prepare) complete.
Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 2
of 5 (Device Configure) starting...
Feb 2 22:57:00 desk NetworkManager: <info> (eth0): device state
change: 4 -> 5
Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 2
of 5 (Device Configure) successful.
Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 3
of 5 (IP Configure Start) scheduled.
Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 2
of 5 (Device Configure) complete.
Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Stage 3
of 5 (IP Configure Start) started...
Feb 2 22:57:00 desk NetworkManager: <info> (eth0): device state
change: 5 -> 7
Feb 2 22:57:00 desk NetworkManager: <info> Activation (eth0) Beginning
DHCP transaction.
Feb 2 22:57:00 desk dhclient: Internet Systems Consortium DHCP Client
4.0.0 Feb 2 22:57:00 desk dhclient: Copyright 2004-2007 Internet
Systems Consortium.
Feb 2 22:57:00 desk dhclient: All rights reserved.
Feb 2 22:57:00 desk dhclient: For info, please visit
http://www.isc.org/sw/dhcp/ Feb 2 22:57:00 desk dhclient:
Feb 2 22:57:00 desk NetworkManager: <info> dhclient started with pid
13377
Feb 2 22:57:00 desk dhclient: Listening on LPF/eth0/00:07:e9:f2:b6:4d
Feb 2 22:57:00 desk dhclient: Sending on LPF/eth0/00:07:e9:f2:b6:4d
Feb 2 22:57:00 desk dhclient: Sending on Socket/fallback
Feb 2 22:57:00 desk dhclient: DHCPDISCOVER on eth0 to 255.255.255.255
port 67 interval 6 Feb 2 22:57:00 desk NetworkManager: <info>
Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Feb 2 22:57:00 desk NetworkManager: <info> DHCP: device eth0 state
changed (null) -> preinit Feb 2 22:57:01 desk avahi-daemon[2071]:
Registering new address record for fe80::207:e9ff:fef2:b64d on eth0.*.
Feb 2 22:57:02 desk dhclient: DHCPOFFER from 192.168.1.1 Feb 2
22:57:02 desk dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Feb 2 22:57:02 desk dhclient: DHCPACK from 192.168.1.1 Feb 2 22:57:02
desk NetworkManager: <info> DHCP: device eth0 state changed preinit ->
bound Feb 2 22:57:02 desk NetworkManager: <info> Activation (eth0)
Stage 4 of 5 (IP Configure Get) scheduled...
Feb 2 22:57:02 desk NetworkManager: <info> Activation (eth0) Stage 4
of 5 (IP Configure Get) started...
Feb 2 22:57:02 desk NetworkManager: <info> address 192.168.1.2
Feb 2 22:57:02 desk NetworkManager: <info> prefix 24 (255.255.255.0)
Feb 2 22:57:02 desk NetworkManager: <info> gateway 192.168.1.1
Feb 2 22:57:02 desk NetworkManager: <info> hostname 'desk'
Feb 2 22:57:02 desk NetworkManager: <info> nameserver '192.168.1.1'
Feb 2 22:57:02 desk NetworkManager: <info> domain name
'seclab.net'
Feb 2 22:57:02 desk NetworkManager: <info> Activation (eth0) Stage 5
of 5 (IP Configure Commit) scheduled...
Feb 2 22:57:02 desk NetworkManager: <info> Activation (eth0) Stage 4
of 5 (IP Configure Get) complete.
Feb 2 22:57:02 desk NetworkManager: <info> Activation (eth0) Stage 5
of 5 (IP Configure Commit) started...
Feb 2 22:57:02 desk avahi-daemon[2071]: Joining mDNS multicast group on
interface eth0.IPv4 with address 192.168.1.2.
Feb 2 22:57:02 desk avahi-daemon[2071]: New relevant interface
eth0.IPv4 for mDNS.
Feb 2 22:57:02 desk avahi-daemon[2071]: Registering new address record
for 192.168.1.2 on eth0.IPv4.
Feb 2 22:57:02 desk dhclient: bound to 192.168.1.2 -- renewal in 84449
seconds.
Feb 2 22:57:03 desk NetworkManager: <WARN>
nm_named_manager_add_ip4_config(): Could not commit DNS changes. Error:
'Could not replace /etc/resolv.conf: Operation not permitted#012'
Feb 2 22:57:03 desk NetworkManager: <info> (eth0): device state
change: 7 -> 8
Feb 2 22:57:03 desk NetworkManager: <WARN>
nm_named_manager_add_ip4_config(): Could not commit DNS changes. Error:
'Could not replace /etc/resolv.conf: Operation not permitted#012'
Feb 2 22:57:03 desk NetworkManager: <info> Policy set 'System eth0'
(eth0) as default for routing and DNS.
Feb 2 22:57:03 desk NetworkManager: <info> Activation (eth0)
successful, device activated.
Feb 2 22:57:03 desk NetworkManager: <info> Activation (eth0) Stage 5
of 5 (IP Configure Commit) complete.
[root@desk ~]#
The error message concerning /etc/resolv.conf is due to the removal of
write bit and setting it immutable. NM does create a file called
/etc/resolv.conf.tmp which appears to be a copy of my immutable
resolv.conf.
Dave McGuffey
Principal Information System Security Engineer // NSA-IEM, NSA-IAM
Save a Tree...Unless necessary don't print this e-mail
15 years, 3 months
is KDE dead - did Gnome win?
by Genes MailLists
I am a long time KDE user - in part for similar reasons to Linus - it
was configurable, flexible and let me set things up the way I wanted -
easily and simply. It had a very nice configuration manager. Gnome by
contrast was rigid, inflexible and to configure it - the bits it
allowed you to - you needed in part to learn about its registry which
warned you that the registry editor may corrupt things in bad ways - use
at your risk. Gnome was undergoing rapid changes - metacity went through
a lot before it was stable .. kde all the while was pretty stable.
That was the way things used to be. Now KDE is harder to configure,
not as flexible and is difficult if not impossible to set up the way I
like things (task manager showing 1 icon per console or per firefox, the
workspace chooser in the middle, the ability to click and save a session
etc etc).
So what I am seeing is some of the KDE users I know are slowly giving
up and moving back to gnome - its the default windowing
manager/environment on fedora and ubuntu and seems more mature and
stable than KDE 4 - and since as far as configurability goes, KDE has
little advantage to offer at this time. Perhaps the next version, or the
one after that will bring back the advantages. Maybe by 4.2 or 4.3 or
4.4 or... 5.0 ..
So seeking guidance from the path others are choosing:
(1) Are the fedora KDE users moving back to gnome ? ... is KDE dead
or alive ?
(2) Are there fedora Gnome users moving to KDE ? It is after all very
similar in its function now ... and does not use spatial mode by default
(;-).
Be very interested in hearing what thoughts others are having.
gene
15 years, 3 months
updating my profile
by Bill
How do I update my profile? I think I may have selected an option which
I want to change.
Thank yo fro your time and assistance.
Bill Wienstein
15 years, 3 months
F10 - boot - how to get into interactive boot?
by Robin Laing
Hello,
Sure, I know to press 'I' but on two machines, it has been a nightmare.
One machine it never worked.
With faster machines, there is no time to press the button.
I found it wouldn't work if the normal Fedora splash screen was up on
the screen. I had to press escape to get it to work. If I pressed to
soon, the keyboard wouldn't work at all. It all happened so fast.
On the second machine, I never got it to work.
This machine has encrypted partitions and the password prompt makes it
harder.
I can just get the Esc button pushed in time for the password to be
requested. I then press 'I" right after pressing 'Enter.' I get a
whole bunch of 'I's" before and after the notice but it still continues
into udev and on into a normal boot. I never could get it to work.
Is there a way to get into interactive mode from grub?
When in the boot process is the keyboard input scanned for the
Interactive? Before or after the message to press "I"?
And is it a "I" or "i"? I have tried both.
--
Robin Laing
15 years, 3 months
Configuring X beyond LCD panel Native Resolution
by Christopher A Williams
All:
I found that if I use the radeonhd drivers, I can configure the display
on my laptop to go well beyond the native resolution (1440x900) by
adjusting the screen resolution applet.
It works quite well.
I'm wondering if there is a way to do this directly in X though. So far,
all attempts to do this via direct configuration in X have come up
fruitless. Any ideas how to make that work?
Cheers,
Chris
--
======================
"Only two things are infinite,
the universe and human stupidity,
and I'm not sure about the former."
-- Albert Einstein
15 years, 3 months
F10 - fall back after disk e2fsck on boot scan issue.
by Robin Laing
Hello,
This is the third issue that I have come across with F10 install problems.
On a machine that had a failing HD, which was not being used, the
machine froze. On a reboot, the system couldn't scan the USB drive that
was connected at freeze but removed on reboot as well as other unmounted
partitions.
The drives were not in /etc/fstab so they shouldn't have been scanned
but they were in /etc/mtab that was left over from the crash.
On the reboot, the boot screen flashed past showing that it failed to
check these drives and dropped into the repair (Right term?) prompt. I
entered the root password and proceeded to try to remove the /etc/mtab
entry. I couldn't as the / partition was mounted (ro). I checked with
'mount' and it stated that the partition was mounted (rw).
I couldn't change the mount status, I couldn't unmount the partition, I
couldn't scan or do anything from the prompt to the / partition. I had
to use a Live CD to mount the partition and remove the /etc/mtab entry
and reboot. The system booted correctly.
Is this a bug that should be reported. I have duplicated this and will
test it on a different install.
Also on a related note, can e2fsck do a boot scan on the ext4 partitions?
--
Robin Laing
15 years, 3 months
[OT] how to acquire a clustered vg on a server without lvm2-cluster
by Gianluca Cecchi
If I have a 2-nodes cluster with a clustered VG, that I copy (for
example dd with cluster switched off), is then possible to acquire
this VG on a third standalone node, or do I have to install the whole
cluster layer on this third node too?
This is on a rhel 5.2 server....
At the moment:
pvscan is ok.
pvscan
PV /dev/dm-11 VG VG_TEST lvm2 [10.00 GB / 0 free]
vgscan
Reading all physical volumes. This may take a while...
Skipping clustered volume group VG_TEST
vgchange -cn VG_TEST
Skipping clustered volume group VG_TEST
vgchange -ae VG_TEST
Skipping clustered volume group VG_TEST
vgchange -al VG_TEST
Invalid argument l
Error during parsing of command line.
Installing lvm2-cluster takes all sort of cluster infrastructure and
probably licenses too...
rpm -ivh lvm2-cluster-2.02.32-4.el5.x86_64.rpm
warning: lvm2-cluster-2.02.32-4.el5.x86_64.rpm: Header V3 DSA
signature: NOKEY, key ID 37017186
error: Failed dependencies:
libcman.so.2()(64bit) is needed by lvm2-cluster-2.02.32-4.el5.x86_64
libdlm.so.2()(64bit) is needed by lvm2-cluster-2.02.32-4.el5.x86_64
rpm -ivh lvm2-cluster-2.02.32-4.el5.x86_64.rpm
../Server/cman-2.0.84-2.el5.x86_64.rpm
warning: lvm2-cluster-2.02.32-4.el5.x86_64.rpm: Header V3 DSA
signature: NOKEY, key ID 37017186
error: Failed dependencies:
openais is needed by cman-2.0.84-2.el5.x86_64
libSaCkpt.so.2()(64bit) is needed by cman-2.0.84-2.el5.x86_64
libSaCkpt.so.2(OPENAIS_CKPT_B.01.01)(64bit) is needed by
cman-2.0.84-2.el5.x86_64
libcpg.so.2()(64bit) is needed by cman-2.0.84-2.el5.x86_64
libcpg.so.2(OPENAIS_CPG_1.0)(64bit) is needed by cman-2.0.84-2.el5.x86_64
perl(Net::Telnet) is needed by cman-2.0.84-2.el5.x86_64
perl(XML::LibXML) is needed by cman-2.0.84-2.el5.x86_64
Thanks in advance,
Gianluca
15 years, 3 months
yum list display some package in 2 rows
by Ambrogio
Hi all,
I use yum list in a script to have everytime I need a list of package
available.
Some packages, that have long names, are displayed in 2 rows, so scripts
are more hard to be coded.
There is an option to have a more simple list of packages, less readable
by umans, but more readable by computer?
Tnx
Ambrogio
15 years, 3 months
