IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 21 October 2017   (all times are UTC)

01:39adrianor1 has joined IRC (adrianor1!~adrianorg@179.187.31.50.dynamic.adsl.gvt.net.br)
01:41adrianorg has left IRC (adrianorg!~adrianorg@187.115.111.239, Ping timeout: 240 seconds)
02:27ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 264 seconds)
02:28ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
05:41[foo]bar has left IRC ([foo]bar!~asdfasdf@unaffiliated/foobar/x-9027208, Remote host closed the connection)
06:19ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:38Statler has joined IRC (Statler!~Georg@p579FE42D.dip0.t-ipconnect.de)
07:44markus_e92 has left IRC (markus_e92!~markus_e9@91-115-209-0.hdsl.highway.telekom.at, Ping timeout: 255 seconds)
07:45markus_e92 has joined IRC (markus_e92!~markus_e9@192.164.155.251)
10:05Statler has left IRC (Statler!~Georg@p579FE42D.dip0.t-ipconnect.de, Quit: Leaving)
10:24GodFather has joined IRC (GodFather!~rcc@cpe-74-75-116-248.maine.res.rr.com)
11:19truth_ has joined IRC (truth_!~Tara@dslb-084-056-127-074.084.056.pools.vodafone-ip.de)
11:58Statler has joined IRC (Statler!~Georg@p579FE42D.dip0.t-ipconnect.de)
12:25adrianor1 is now known as adrianorg
12:38
<truth_>
Hi, I'm using ltsp-pnp for my family which works great - thanks a lot.
12:38
Nevertheless, I have the following printer problem:
12:38
The printer is a network-printer (192.168.14.19) which is not directly connected to the server (192.168.14.1).
12:38
Unfortunately, I was not able to find a manual on how to make this printer available (Port forwarding ..?) also for the clients (192.168.67.*) ...
12:38
Is there a web-page describing this problem?
12:55
<alkisg>
!printer
12:55
<ltsp>
printer: Quick how-to: RCFILE_01="/usr/sbin/jetpipe /dev/usb/lp0 9100 &" in lts.conf, reboot client, then go to server's add printer dialog, and specify network printer → jetdirect → ltsp123.local
12:55
<alkisg>
Hmm no foget that
12:55
truth_: you normally install the printer on the server (add network printer) and then you enable printer sharing via cups and the clients automatically see it
13:01Statler has left IRC (Statler!~Georg@p579FE42D.dip0.t-ipconnect.de, Remote host closed the connection)
13:11
<truth_>
I'm not sure that I understand your quick how-to:
13:11
First of all the web-pages I've found (e.g.http://wiki.ltsp.org/wiki/Tips_and_Tricks/Devices#Printer) describe how to connect a printer to the client, right?
13:11
When I look into the lts.conf example I usually do not see something like RCFILE_01= ...
13:11
I'm able to user the network-printer (via cups) from the server and the printer is shared to other computers within the subnet 192.168.14.*
13:18
Ok - I've found the RCFILE command within the manpage of lts.conf ...
13:39
.
13:39
I still do not understand this: ... then go to server's add printer dialog, and specify network printer → jetdirect → ltsp123.local
13:39
I just looked into cups but I couldn't find out what you mean with jetdirect --> ltsp123.local
13:43
<alkisg>
truth_: which desktop environment are you using?
13:44
truth_: you basically need to do things that are NOT related to ltsp
13:44
And then the clients will automatically see the printer
13:44
For example, in mate the dialog is called `system-config-printer`
13:45
truth_: here is a picture of the dialog: https://www.howtogeek.com/wp-content/uploads/2014/06/ubuntu-print-server-settings.png
13:46
So you can find the documentation by searching for e.g. "ubuntu add printer"
13:46
<truth_>
My Desktop is Gnome on Debian, sorry for the confusion ...
13:46
<alkisg>
truth_: ok, run system-config-printer then add use the add printer dialog
13:47
It's in the gnome menus
13:47
*and then use... meh, typo
13:48
In other words. FIrst step. Ignore LTSP and install your printer normally.
13:49
Second step. In the same dialog, there's a "allow printing" check box, check it.
13:49
Third ltsp, ltsp-related: nothing. LTSP clients will automatically see the printer.
13:51
<truth_>
I'm using the client right now ... so I will switch to the server for further test ...
13:51
<alkisg>
truth_: or you can use a thin client
13:52
Thin client session runs on the server, so it's the same like using the server
13:54
<truth_>
Ok
13:55
... I thought ltsp-pnp is using fat-clients.
13:55
<alkisg>
truth_: ltsp-pnp supports both, and you switch with LTSP_FATCLIENT=True/False in lts.conf
13:56
So you can just change 1 line and log in as thin client
14:05
<truth_>
I will relogin in a minute ...
14:05truth_ has left IRC (truth_!~Tara@dslb-084-056-127-074.084.056.pools.vodafone-ip.de)
14:08truth_ has joined IRC (truth_!~Tara@dslb-084-056-127-074.084.056.pools.vodafone-ip.de)
14:26
<truth_>
... ok, I'm back.
14:26
I was able to open the system-config-printer dialog (@server) - the network-printer which I have installed via cups was also visible in this dialog (active and shared).
14:26
After restarting the fat-client I still do not see the printer :-(
14:26
Is it possible that this problem is related to the fat-client?
14:27
<alkisg>
truth_: what is the output of `cupsctl` ?
14:28
$ cupsctl | grep share
14:28
_share_printers=1
14:29
<truth_>
_share_printers=0 :-(
14:29
<alkisg>
So no, you didn't find the "share printers" check box
14:29
sudo cupsctl _share_printers=1
14:29
This sets it from the command line, but normally we use the GUI
14:29
(all this is not ltsp-related)
14:30
<truth_>
... I will check again ...
14:36truth_ has left IRC (truth_!~Tara@dslb-084-056-127-074.084.056.pools.vodafone-ip.de, Quit: ChatZilla 0.9.93 [Firefox 52.3.0/20170811091919])
14:39truth_ has joined IRC (truth_!~Tara@dslb-084-056-127-074.084.056.pools.vodafone-ip.de)
14:47
<truth_>
... ok, if I enable _share_printers from console and restart the fat-client I can see the printer on the client. :-)
14:47
However, I'm sure the share-button was already check before within the system-config-printer dialog (also it is named "Freigabe" in german language ...)
14:47
Thanks so far - I will do more test later, to further analyze the origin of this behavior ...
14:47
<alkisg>
truth_: if you find some bug in cups, do report it in cups ;)
14:47
You're welcome
14:49
<truth_>
Manny thanks.
14:49truth_ has left IRC (truth_!~Tara@dslb-084-056-127-074.084.056.pools.vodafone-ip.de)
14:51lucascastro has joined IRC (lucascastro!~lucas@224.91.55.177.conecte.psi.br)
15:07lucascastro has left IRC (lucascastro!~lucas@224.91.55.177.conecte.psi.br, Remote host closed the connection)
15:54neops has joined IRC (neops!~neops@unaffiliated/neops)
15:54
<neops>
hello
15:54
hello alkisg
15:54
<alkisg>
Hello
15:55
<neops>
do you still have time to help me?
15:55
I'm at home
15:55
<alkisg>
neops: ok, run vnc:
15:55
!vnc-dide
15:55
<ltsp>
vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
15:55
<alkisg>
and tell me the issue again
15:56
<neops>
as a reminder, the problem is that I have a black screen
15:56
<alkisg>
On one specific client, or on all of them?
15:57
<neops>
on all customers
15:57
<alkisg>
Boot one of them
15:58
<neops>
ok
15:58
it's done I reboot a Vm
16:00
<alkisg>
Is the VM 64bit?
16:00
<neops>
yes
16:00
<alkisg>
Boot it again
16:01
<neops>
ok
16:02
Dhcp and Pxe ok then + BLACK screen
16:02
I can make a capture for you
16:03
<alkisg>
neops: can I install KVM to see a VM for myself?
16:04
Or virtualbox?
16:04
<neops>
yes
16:04
<alkisg>
Where are you running the VM from, linux or windows?
16:04
<neops>
this is a test vm you can install
16:04
Windows 10 (vmware workstatio
16:04
<alkisg>
Btw, why are you not using ltsp-manager?
16:04
!ltsp-manager
16:04
<ltsp>
ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
16:04
<alkisg>
This would set up ltsp fine...
16:05
!kvm
16:05
<ltsp>
kvm: Virtual thin client: kvm -m 256 -vga vmware -ctrl-grab -no-shutdown -net nic,model=virtio -net user,tftp=/var/lib/tftpboot,bootfile=/ltsp/i386/pxelinux.0
16:07
<neops>
I will learn about ltsp-manager
16:08
I can show you the tutorial I used for installaion LTSP but it is in french
16:08
<alkisg>
No I don't recommend other tutorials, only the upstream ones
16:08
!ltsp-manager
16:08
<ltsp>
ltsp-manager: LTSP Manager is a GUI tool that makes LTSP maintenance easy. It's the recommended way to install LTSP in common setups. More info: http://wiki.ltsp.org/wiki/Ltsp-manager
16:08
<alkisg>
That one ^
16:08
<neops>
I understand
16:10
<alkisg>
The client tries to boot the i386 image
16:10
Which dhcp are you using?
16:10
It's configured wrong
16:10
<neops>
it does not bother me if it fixes my problem we can put i386
16:11
<alkisg>
It bothers troubleshooting
16:11
Because we were trying to fix amd64
16:11
And you were using i386...
16:12
<neops>
aptitude install isc-dhcp-server tftpd-hpa nfs-kernel-server ltsp-server-standalone
16:12
<alkisg>
No, you're not using the dhcp of the ltsp server
16:12
You may have pfsense or something else
16:12
<neops>
I did not succeed in doing otherwise
16:13
during lstp installationhe did not want to put the Dhcp package
16:13
i did not put pfsense
16:15
I reboot the vm ??
16:17
<alkisg>
!root
16:17
<ltsp>
I do not know about 'root', but I do know about these similar topics: 'ROOT_PASSWORD_HASH'
16:18
<alkisg>
!ROOT_PASSWORD_HASH
16:18
<ltsp>
ROOT_PASSWORD_HASH: to be able to login as root in vt1, with password "qwer1234", put this in lts.conf: INIT_COMMAND_01="sed 's!^root:[^:]*:!root:$6$p2LdWE6j$PDd1TUzGvvIkj9SE8wbw1gA/MD66tHHlStqi1.qyv860oK47UnKcafSKqGp7cbgZUPlgyPv6giCVyCSCdJt1b0:!' -i /etc/shadow"
16:18
<alkisg>
!ssh
16:18
<ltsp>
I do not know about 'ssh', but I do know about these similar topics: 'sshkeys', 'ltsp-update-sshkeys', 'INIT_COMMAND_SSH'
16:18
<alkisg>
!INIT
16:18
<ltsp>
I do not know about 'INIT', but I do know about these similar topics: 'lowram-initramfs', 'INIT_COMMAND_SSH', 'INIT_COMMAND_EPOPTES', 'INIT_COMMAND_GUEST'
16:18
<alkisg>
!INIT_COMMAND_EPOPTES
16:18
<ltsp>
INIT_COMMAND_EPOPTES: To troubleshoot epoptes certificate issues, this lts.conf directive trusts the server on boot: INIT_COMMAND_EPOPTES="epoptes-client -c server"
16:18Statler has joined IRC (Statler!~Georg@p579FE42D.dip0.t-ipconnect.de)
16:19
<alkisg>
neops: you seem to have installed dhcp server in the chroot, and possibly other programs that broke it
16:19
<neops>
'ltsp-update-sshkeys
16:19
<alkisg>
It's a very broken installation, maybe a very bad tutorial...
16:20
<neops>
I can repat a zero I made a snapshoot
16:22
<alkisg>
!tftp
16:22
<ltsp>
tftp: Here's a page to help you troubleshoot TFTP problems in Ubuntu: https://help.ubuntu.com/community/UbuntuLTSP/Troubleshooting/TFTP
16:26
<neops>
lollol
16:27
the problem comes from dhcp or tftp
16:30
<alkisg>
No, the problem came from a very bad tutorial
16:30
You created a broken chroot
16:30
<neops>
ok
16:30
<alkisg>
I'll create a good image and we'll see
16:30
<neops>
okay
16:35
alkisg,
16:35
is good
16:35
<alkisg>
Yes I'll also fix the VM
16:36
<neops>
im reboot vm ver2
16:37
how did you solve the problem
16:39
<alkisg>
neops: I created a new chroot, using the ltsp-manager method
16:39
As I said, it was a bad tutorial
16:40
If you want to do it from the beginning, read !ltsp-manager
16:40
Or !ltsp-pnp
16:40
<neops>
ok
16:40
thank you very much
16:40
<alkisg>
You're welcome
16:40
(I closed vnc)
16:41
<neops>
ok
16:41
I must understand what I have done wrong
16:42
<alkisg>
I can't fix all bad tutorials on the internet
16:43
This chroot was very broken, it even had dhcp server in it
16:43
<neops>
can I show you my pdf? (this is important to see found error)
16:44
<alkisg>
I've sent you a personal message here in irc
16:49Natureshadow has left IRC (Natureshadow!~Naturesha@commu.teckids.org, Ping timeout: 260 seconds)
18:10Statler has left IRC (Statler!~Georg@p579FE42D.dip0.t-ipconnect.de, Remote host closed the connection)
18:17Natureshadow has joined IRC (Natureshadow!~Naturesha@commu.teckids.org)
18:22markus_e92 has left IRC (markus_e92!~markus_e9@192.164.155.251, Ping timeout: 240 seconds)
18:28markus_e92 has joined IRC (markus_e92!~markus_e9@192.164.155.251)
18:55
<bennabiy>
alkisg, my issue with ltsp-manager, and ltsp-pnp method is the requirement for the same arch as the server. All my clients are 32 bit, and my server is a 64 bit install.
18:56
<alkisg>
bennabiy: you can either use i386 on the server, or a template client, or a vm
18:56
If none of these suit you, you can still use ltsp-manager with a chroot
18:57
(or ltsp-pnp with a chroot)
18:57
<bennabiy>
I never thought about a template client... that is a thought
19:01
<alkisg>
Btw in general, *all* ltsp-pnp servers are 64bit, yet they install i386.iso for convenience
19:02
bennabiy: how many clients do you have? any one of them with gigabit?
19:02
<bennabiy>
All with gigabit, but all i386
19:02
<alkisg>
How many?
19:03
<bennabiy>
at this location we have about 4 full time and are about to expand to a couple dozen potentially
19:03
<alkisg>
with a couple dozen fat clients, you could have a template client be the nbd server, yeah
19:03
And use LDM_SERVER=the other server
19:04
Fat or thins?
19:04
<bennabiy>
thins
19:04
I am looking into fat, but not there yet
19:05
most of my users just need thin
19:05
<alkisg>
Eh, just ltsp-manager + one ltsp-build-client for thins then
19:05
Nothing important
19:06
<bennabiy>
yes,
19:06
I might give it a try
19:06
but not today :)
19:06
<alkisg>
Sure, just talking...
19:09
<bennabiy>
Thank you for the suggestion. I was hoping to find a way to test out ltsp-manager, and you might have given me the right clues
19:10* bennabiy waves
19:15
<alkisg>
bb
21:44neops has left IRC (neops!~neops@unaffiliated/neops, Read error: Connection reset by peer)
22:07ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
22:28GodFather has left IRC (GodFather!~rcc@cpe-74-75-116-248.maine.res.rr.com, Quit: Ex-Chat)
22:28GodFather has joined IRC (GodFather!~rcc@cpe-74-75-116-248.maine.res.rr.com)
23:22
<gehidore>
fkjkfc~
23:39
<quinox>
well put