howto update

Discussion:

howto update

Paul Mulroney

2013-04-22 00:47:16 UTC

Hi Joshua,

I have a CentOS 6.4 server that was running LTSP 5.2.17(?) successfully. I ran yum update, and didn't notice that it upgraded LTSP to 5.4.5. Now the diskless workstations won't login to the server. They boot and get to a login screen, but when the user puts in their credentials they get a "no response from server, restarting".

In trying to resolve this issue I have followed these instructions below, and now the ltsp-build-client fails with some sort of python error.

I also setup a test system, did a fresh install of Cent OS 6.4 and then followed your instructions below, and ltsp-build-client still fails with the same error.

I'm not sure where to start with debugging this, can you offer any suggestions?

Regards,
Paul.

Hello Joshua,
i've tested this; this seems to work.
rpm -Uvh
http://mirror.ancl.hawaii.edu/~k12linux/rpm/ltsp-release-5.noarch.rpm
gave me
Retrieving
http://mirror.ancl.hawaii.edu/~k12linux/rpm/ltsp-release-5.noarch.rpm
curl: (22) The requested URL returned error: 404 Not Found
fout: skipping
http://mirror.ancl.hawaii.edu/~k12linux/rpm/ltsp-release-5.noarch.rpm -
transfer failed
but I downloaded the rpm from the site.

Computers make very fast, very accurate mistakes.
(Geeky One Line Jokes http://bit.ly/XU8lFD)

--
Paul W. Mulroney Logical Developments
***@logicaldevelopments.com.au 86 Coolgardie Street
www.logicaldevelopments.com.au BENTLEY WA 6102
Ph: +61 8 9458 3889 Fax: +61 8 9458 2169

Joshua Trimm

2013-04-22 17:21:05 UTC

Permalink

Paul,
The website instructions are undergoing a bit of a change-around
while I get everything organized. The most up to date installation
instructions will always be found at this link:

http://wiki.ltsp.org/wiki/Category:Fedora

Post by Paul Mulroney
Hi Joshua,
I have a CentOS 6.4 server that was running LTSP 5.2.17(?) successfully. I ran yum update, and didn't notice that it upgraded LTSP to 5.4.5. Now the diskless workstations won't login to the server. They boot and get to a login screen, but when the user puts in their credentials they get a "no response from server, restarting".
In trying to resolve this issue I have followed these instructions below, and now the ltsp-build-client fails with some sort of python error.
I also setup a test system, did a fresh install of Cent OS 6.4 and then followed your instructions below, and ltsp-build-client still fails with the same error.
I'm not sure where to start with debugging this, can you offer any suggestions?
Regards,
Paul.

Computers make very fast, very accurate mistakes.
(Geeky One Line Jokes http://bit.ly/XU8lFD)

Paul Mulroney

2013-04-24 01:26:48 UTC

Permalink

Hi Joshua

Thanks for your email. I was able to roll back to 5.2.17 and they're up and running again.

rpm --import http://ltsprepo.s3.amazonaws.com/rpm/RPM-GPG-KEY-ltsp
rpm -Uvh
http://ltsprepo.s3.amazonaws.com/rpm/el6/x86_64/ltsp-release-5-9.el6.noarch.rpm
yum install ltsp-server
Edit config files in /etc/ltsp/
ltsp-build-client
Read the docs!!

Regards,
Paul.

Paul,
The website instructions are undergoing a bit of a change-around
while I get everything organized. The most up to date installation
http://wiki.ltsp.org/wiki/Category:Fedora

"Beware of half truths... you may get the wrong half." @funnyoneliners on twitter

--
Paul W. Mulroney Logical Developments
***@logicaldevelopments.com.au 86 Coolgardie Street
www.logicaldevelopments.com.au BENTLEY WA 6102
Ph: +61 8 9458 3889 Fax: +61 8 9458 2169

Eddie Bonifacio Yanguas-Johnson

2013-04-24 02:51:08 UTC

Permalink

Joshua,

I thought it was just I having the issue LTSP. Look forward to the
responses. I did not get the error for LTSP until I solved the DNS issue
first. All this after a major yum update after from 6.3 to 6.4.

Ed
On Apr 21, 2013 8:51 PM, "Paul Mulroney" <

Post by Paul Mulroney
Hi Joshua,
I have a CentOS 6.4 server that was running LTSP 5.2.17(?) successfully.
I ran yum update, and didn't notice that it upgraded LTSP to 5.4.5. Now
the diskless workstations won't login to the server. They boot and get to
a login screen, but when the user puts in their credentials they get a "no
response from server, restarting".
In trying to resolve this issue I have followed these instructions below,
and now the ltsp-build-client fails with some sort of python error.
I also setup a test system, did a fresh install of Cent OS 6.4 and then
followed your instructions below, and ltsp-build-client still fails with
the same error.
I'm not sure where to start with debugging this, can you offer any suggestions?
Regards,
Paul.

Computers make very fast, very accurate mistakes.
(Geeky One Line Jokes http://bit.ly/XU8lFD)
--
Paul W. Mulroney
Logical Developments
www.logicaldevelopments.com.au BENTLEY WA 6102
Ph: +61 8 9458 3889 Fax: +61 8 9458 2169
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

Wadim Incognito

2013-04-24 07:07:20 UTC

Permalink

Hi Paul.

I've run in such issue, and the solution is to update chroot (/opt/ltsp/i386) to CentOS 6.4 After that, the problem with login is gone.

Regards,
Vadim.

Computers make very fast, very accurate mistakes.
(Geeky One Line Jokes http://bit.ly/XU8lFD )
--
Paul W. Mulroney Logical Developments
www.logicaldevelopments.com.au BENTLEY WA 6102
Ph: +61 8 9458 3889 Fax: +61 8 9458 2169
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see < http://www.k12os.org >

Joshua Trimm

2013-04-24 13:44:50 UTC

Permalink

_______________________________________________
K12OSN mailing list
***@redhat.com
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

Jeff Siddall

2013-04-25 19:38:05 UTC

Permalink

Post by Wadim Incognito
Hi Paul.
I've run in such issue, and the solution is to update chroot
(/opt/ltsp/i386) to CentOS 6.4 After that, the problem with login is gone.

I did a full update on my chroot _except_ for ltsp-client, which is
still at ltsp-client-5.2.17-1.el6.i686

However, even after running ltsp-update-sshkeys I still cannot get
logged in. LDM reports "no response from server". So it appears there
is something bad in ldm-2.2.11-3.el6.i686 which I believe came from epel.

I also noticed most of the session choices disappeared from that version
of LDM.

Reverting to ldm-2.2.4-1.el6.i686 from the old k12linux repo seems to
have fixed it and I can login again.

I should point out I did _not_ upgrade the ltsp-server package.

Joshua,

Is this something you are working on? It is a bad thing to have a
serious regression in a package that is part of widely used repositories
so removing that for now would probably be wise.

Thanks,

Jeff

Michel Donais

2013-04-27 06:24:02 UTC

Permalink

Centos 5.9
I'm setting up a server with 10 thin clients who will have to access
internet.
I'm stuck with iptables
Actually, the thin clients and the server can communicate; in between.
the server can go to the wan but not the thin clients.

lan address 192.168.0.100 to 109 255.255.255.0 gw
192.168.0.254
server: lan nic 192.168.0.254 255.255.255.0
gw 192.168.0.254
server: wan nic 192.168.2.210 255.255.255.0
gw 192.168.2.1
router: 192.168.2.1 255.255.255.0
gw our fix addres

Can somebody gives some clues.

---
Michel Donais

Jim Kinney

2013-04-27 12:33:05 UTC

Permalink

echo "1" > /proc/sys/net/ipc4/ip_forward

and edit /etc/sysctl.conf and make the change permanent there with a
setting of 1 for ip_forward.

Post by Michel Donais
Centos 5.9
I'm setting up a server with 10 thin clients who will have to access
internet.
I'm stuck with iptables
Actually, the thin clients and the server can communicate; in between.
the server can go to the wan but not the thin clients.
lan address 192.168.0.100 to 109 255.255.255.0
gw 192.168.0.254
server: lan nic 192.168.0.254 255.255.255.0 gw
192.168.0.254
server: wan nic 192.168.2.210 255.255.255.0 gw
192.168.2.1
router: 192.168.2.1 255.255.255.0 gw
our fix addres
Can somebody gives some clues.
---
Michel Donais
______________________________**_________________
K12OSN mailing list
https://www.redhat.com/**mailman/listinfo/k12osn<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/
*

Michel Donais

2013-04-27 15:33:47 UTC

Permalink

Thanks Jim to care my request,

echo "1" > /proc/sys/net/ipc4/ip_forward

I don't have /proc/sys/net/ipc4/ip_forward but ipv_4 instead

in /etc/sysctl.conf net.ipv4.ipv_forward is already at 1

and it's not working

---
Michel Donais

michel

2013-04-27 15:44:51 UTC

Permalink

Post by Michel Donais
Thanks Jim to care my request,

Here is my iptables -L
-----------------------------------------------------------------------------------------------
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEPT udp -- anywhere anywhere udp dpt:domain
ACCEPT tcp -- anywhere anywhere tcp dpt:domain
ACCEPT udp -- anywhere anywhere udp dpt:bootps
ACCEPT tcp -- anywhere anywhere tcp dpt:bootps
ACCEPT udp -- anywhere anywhere udp dpt:domain
ACCEPT tcp -- anywhere anywhere tcp dpt:domain
ACCEPT udp -- anywhere anywhere udp dpt:bootps
ACCEPT tcp -- anywhere anywhere tcp dpt:bootps
RH-Firewall-1-INPUT all -- anywhere anywhere

Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere 192.168.122.0/24 state
RELATED,ESTABLISHED
ACCEPT all -- 192.168.122.0/24 anywhere
ACCEPT all -- anywhere anywhere
REJECT all -- anywhere anywhere reject-with
icmp-port-unreachable
REJECT all -- anywhere anywhere reject-with
icmp-port-unreachable
ACCEPT all -- anywhere 192.168.122.0/24 state
RELATED,ESTABLISHED
ACCEPT all -- 192.168.122.0/24 anywhere
ACCEPT all -- anywhere anywhere
REJECT all -- anywhere anywhere reject-with
icmp-port-unreachable
REJECT all -- anywhere anywhere reject-with
icmp-port-unreachable
RH-Firewall-1-INPUT all -- anywhere anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain RH-Firewall-1-INPUT (2 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere icmp any
ACCEPT esp -- anywhere anywhere
ACCEPT ah -- anywhere anywhere
ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns
ACCEPT udp -- anywhere anywhere udp dpt:ipp
ACCEPT tcp -- anywhere anywhere tcp dpt:ipp
ACCEPT all -- anywhere anywhere state
RELATED,ESTABLISHED
ACCEPT tcp -- anywhere anywhere state NEW tcp
dpt:ssh
REJECT all -- anywhere anywhere reject-with
icmp-host-prohibited
------------------------------------------------------------------------------------------------------

---
Michel Donais

2013-04-29 19:38:45 UTC

Permalink

Post by michel

Post by Michel Donais
Thanks Jim to care my request,

Here is my iptables -L

[snip]

192.168.0.100 - 192.168.0.109 needs to be masqueraded or dnat'd through 192.168.2.210

If you are worried about people on your local wan ( 192.168.2.210 ) getting to the TC's
or terminal server then keep your current rules ( but add Masq, or Dnat ). If you are
not worried, set everything:

input -i eth? -j ACCEPT
forward -i eth? -j ACCEPT
output -o eth? -j ACCEPT to keep stuff simple.

You just need to add a 'prerouting' statement.
-t nat -A PREROUTING -o eth(192.168.2.210 is on ) -j MASQUERADE

I don't remember the dnat syntax just now. www.netfilter.com for syntax
--
Todd Hackett Chief Bottle Washer
PoBox 1168
Libby, MT 59923
406.291.6241

Johan Vermeulen

2013-05-30 13:23:35 UTC

Permalink

Post by Jeff Siddall

Post by Wadim Incognito
Hi Paul.
I've run in such issue, and the solution is to update chroot
(/opt/ltsp/i386) to CentOS 6.4 After that, the problem with login is gone.

I did a full update on my chroot _except_ for ltsp-client, which is
still at ltsp-client-5.2.17-1.el6.i686
However, even after running ltsp-update-sshkeys I still cannot get
logged in. LDM reports "no response from server". So it appears
there is something bad in ldm-2.2.11-3.el6.i686 which I believe came
from epel.
I also noticed most of the session choices disappeared from that
version of LDM.
Reverting to ldm-2.2.4-1.el6.i686 from the old k12linux repo seems to
have fixed it and I can login again.
I should point out I did _not_ upgrade the ltsp-server package.
Joshua,
Is this something you are working on? It is a bad thing to have a
serious regression in a package that is part of widely used
repositories so removing that for now would probably be wise.
Thanks,
Jeff
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
,

hello All,

after updating, I can boot thinclients without issues.

But laptops / workstations that are also on the lan cannot connect
connect to the outside world, e.g. ping 8.8.8.8

* ***@centos-server ~]# /sbin/sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1

* ltps-server-tweaks gives me :

[***@centos-server ~]# ltsp-server-tweaks
About to overwrite your default iptables (firewall) configuration.
hit Ctrl-C if unsure.

and hangs, even is firewall = off.

* here is my /etc/sysconfig/iptables:

# Firewall configuration written by system-config-firewall
# Manual customization of this file is not recommended.
*nat
:PREROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
-A POSTROUTING -o em2 -j MASQUERADE
-A POSTROUTING -o ltspbr0 -j MASQUERADE
COMMIT
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i em2 -j ACCEPT
-A INPUT -i ltspbr0 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
-A FORWARD -p icmp -j ACCEPT
-A FORWARD -i lo -j ACCEPT
-A FORWARD -i em2 -j ACCEPT
-A FORWARD -i ltspbr0 -j ACCEPT
-A FORWARD -o em2 -j ACCEPT
-A FORWARD -o ltspbr0 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT

Can anyone offer further advise on this?

greetings, J.

b***@thealmquists.net

2013-04-27 15:43:11 UTC

Permalink

Isn't there a service that turns this on and off?

Post by Michel Donais
Thanks Jim to care my request,
echo "1" > /proc/sys/net/ipc4/ip_forward
I don't have /proc/sys/net/ipc4/ip_forward but ipv_4 instead
in /etc/sysctl.conf net.ipv4.ipv_forward is already at 1
and it's not working
---
Michel Donais
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

michel

2013-04-27 15:53:19 UTC

Permalink

Post by b***@thealmquists.net
Isn't there a service that turns this on and off?

net.ipv4.ip_forward = 1 in /etc/sysctl.conf
tur on packet forwarding at boot

/sbin/sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1
tell it's on

--
Michel Donais