yum update issue with ltspbr0

Discussion:

William Fragakis

2013-05-16 16:52:55 UTC

I don't know if this will shed any light for those who've been suffering
similar woes.

short version: on ltsp server restart, ltsp-dhcpd failed to start and
ltspbr0 was dead. thin clients couldn't boot. update erased
ifcfg-ltspbr0 but copying ifcfg-ltspbr0, bringing up ltspbr0 and
starting ltsp-dhcpd solved everything.

long version:

We had a server restart this morning. Someone unfortunately punched the
reset button on the ltsp server instead of the dead windows box.

Server came back online but thin clients couldn't get ip address to
begin booting. Panic developed as this was in the middle of a workday.

service ltsp-dhcpd status showed dhcp was dead and restarting it failed
with system log saying something about undeclared subnets, etc.

ifconfig didn't show anything for ltspbr0

Listed the files in /etc/sysconfig/network-scripts that started with
ifcfg-l and got
ifcfg-lo ifcfg-ltspbr0~ and ifcfg-ltspbr0.rpmnew

But no ifcfg-ltspbr0

Copied ifcfg-ltspbr0.rpmnew to ifcfg-ltspbr0 , did an ifup on
ifcfg-ltspbr0 and then ltsp-dhcpd restarted without any problems. thin
clients booted and my heart was no longer pounding.

Moral of the story, an update incorrectly killed existing ltspbr0 config
file. Hope this helps. I didn't see this mentioned elsewhere so sorry
if it duplicates anything.

Not sure which update killed it or to whom I should submit bug report.
Suggestions appreciated.

thanks,
William

Jim Kinney

2013-05-16 18:23:07 UTC

Permalink

check /var/log/yum.log for updates. It will show dates and packages but not
sources.

since there _use_ to be a ifcfg-ltspbr0 file that came in with the initial
LTSP install, the update for that was the fail point.

Run

rpm --whatprovides /etc/sysconfig/network-scripts/ifcfg-ltspbr0

to find package name for this file.

Solution to button pusher problem: glue an O-ring around the power button.
Glue a piece of clear plexiglass to a short tube that just fits around the
O-ring. Put a nicely printed small sign that reads "WARNING! SHOCK HAZARD!
DO NOT TOUCH!" just above the now covered power button.

Post by William Fragakis
I don't know if this will shed any light for those who've been suffering
similar woes.
short version: on ltsp server restart, ltsp-dhcpd failed to start and
ltspbr0 was dead. thin clients couldn't boot. update erased
ifcfg-ltspbr0 but copying ifcfg-ltspbr0, bringing up ltspbr0 and
starting ltsp-dhcpd solved everything.
We had a server restart this morning. Someone unfortunately punched the
reset button on the ltsp server instead of the dead windows box.
Server came back online but thin clients couldn't get ip address to
begin booting. Panic developed as this was in the middle of a workday.
service ltsp-dhcpd status showed dhcp was dead and restarting it failed
with system log saying something about undeclared subnets, etc.
ifconfig didn't show anything for ltspbr0
Listed the files in /etc/sysconfig/network-scripts that started with
ifcfg-l and got
ifcfg-lo ifcfg-ltspbr0~ and ifcfg-ltspbr0.rpmnew
But no ifcfg-ltspbr0
Copied ifcfg-ltspbr0.rpmnew to ifcfg-ltspbr0 , did an ifup on
ifcfg-ltspbr0 and then ltsp-dhcpd restarted without any problems. thin
clients booted and my heart was no longer pounding.
Moral of the story, an update incorrectly killed existing ltspbr0 config
file. Hope this helps. I didn't see this mentioned elsewhere so sorry
if it duplicates anything.
Not sure which update killed it or to whom I should submit bug report.
Suggestions appreciated.
thanks,
William
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

--
--
James P. Kinney III
*
*Every time you stop a school, you will have to build a jail. What you gain
at one end you lose at the other. It's like feeding a dog on his own tail.
It won't fatten the dog.
- Speech 11/23/1900 Mark Twain
*
http://electjimkinney.org
http://heretothereideas.blogspot.com/
*

Sergio Chaves

2013-05-20 01:01:09 UTC

Permalink

Well, may be the laziness in me worked to my advantage :-)
I am still to fix my second server and will try this approach!

Thanks for the tip William!