I set up my 16.04 Xubuntu computer as an LTSP server. I have booted a client
from it successfully, but under two special circumstances: (a) using a second
NIC and ltsp-server-standalone; (b) using dnsmasq as a dhcp server. When I set
up dnsmasq as a dhcp proxy, the client always fails when it tr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07.07.2015 12:34, Charles Barnwell wrote:
> Ivan,
>
> A delayed response to say thankyou.
Hi Charles,
you are welcome. This is the reason why mailinglist are.
- --
Ivan Minčík
ivan.min...@gmail.com GPG: 0x79529A1E
http://imincik.github.io/0x795
> > I am having a serious problem that I am finding hard to diagnose.
>
> Hi Charles, I have had similar misterious problems when I had either IP
> conflict or conflict of MAC addresses created by two clients in VirtualBox
> with the same MAC. Try to make sure if one of these is not your problem.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/19/2015 12:51 PM, Charles Barnwell wrote:
> I am having a serious problem that I am finding hard to diagnose.
Hi Charles, I have had similar misterious problems when I had either IP
conflict or conflict of MAC addresses created by two clients in
t; An: Funke, Martin
> Cc: ltsp-discuss@lists.sourceforge.net
> Betreff: Re: AW: [Ltsp-discuss] NBD crashing
>
>
>
> On 20 Mar 2015 06:54, "Funke, Martin" wrote:
>>
>> Hi,
>>
>> i checked my syslog when my client boots up:
>> Mar 19 11
endet: Donnerstag, 19. März 2015 12:51
An: ltsp-discuss@lists.sourceforge.net
Betreff: [Ltsp-discuss] NBD crashing
I am having a serious problem that I am finding hard to diagnose.
I am running Ubuntu 14.04.1 LTS Trusty Tahir with LTSP 5.5.1-1ubuntu2.
Both the server and client images are at the l
I am having a serious problem that I am finding hard to diagnose.
I am running Ubuntu 14.04.1 LTS Trusty Tahir with LTSP 5.5.1-1ubuntu2.
Both the server and client images are at the latest level and are kept
up to date.
Occasionally when one client is powered up and negotiates a DHCP
address all
@lists.sourceforge.net
Subject: Re: [Ltsp-discuss] NBD content drop?!?
>
> There are a number of services that are disabled at boot by default on
> Debian/Ubuntu LTSP clients. You may need to add cron and other services
> you want to KEEP_SYSTEM_SERVICES in lts.conf.
>
> Look for /u
>
> There are a number of services that are disabled at boot by default on
> Debian/Ubuntu LTSP clients. You may need to add cron and other services
> you want to KEEP_SYSTEM_SERVICES in lts.conf.
>
> Look for /usr/share/ltsp/init-ltsp.d/50-rm-system-services in the client
> chroot/image for the co
>
>
>
> From: Vagrant Cascadian [vagr...@debian.org]
> Sent: 30 January 2015 22:40
> To: ltsp-discuss@lists.sourceforge.net
> Subject: Re: [Ltsp-discuss] NBD content drop?!?
>
> On 2015-01-30, Lars Madsen wrote:
> >
On 2015-01-30, Lars Madsen wrote:
> Today I just noticed that on the images servered up by the production
> system some services are not running. For example cron.
...
> also no cron is listed in /etc/init.d/, even though it *is* in
> /opt/ltsp/i386/etc/init.d in the chroot.
>
> I also tried unpack
I'm taking the liberty to spam again.
I'm currently observing some rather odd behaviour.
My LTSP system (Ubuntu 12.04 clients) runs in Virtual Box on my office PC.
Everything thing working just fine.
For the production system (also running Ubuntu 12.04), I have a virtual server
acting as the b
I'm still trying to debug our LDM freezing problem.
At the moment I'm guessing the problem lies with the NBD servier serving the
images to the clients.
If the client looses its connection to the NBD server, then it freezes. Fair
enough. But why are we getting so mange of these connection drops.
Hi all
I'm trying to optimize network performance on a 250+ NBD fat clients by
mean of caching data in client's hard disk (actually only used for swap)
I've located fscache modules and cachefilesd daemon, but seems only to
work only with NFS and CIFS remote mounts ¿Is this correct?
Else ¿Any easy
Heureka, I resolved the problem. My own question eventually led me
there, (and reading the f*ing manual helped, as usually ;-) ). I would
not have managed if I hadn't asked the question at this list. Thanks!
First observation:
--
Yes, as Peter confirmed, the entries in /etc/inetd
I took my entry out as well.
Peter
On Mon, Jul 1, 2013 at 12:43 PM, Rüdiger Kupper wrote:
> Hello Ben!
>
> The server log reads:
>
> Jul 1 11:23:09 ltsp6 nbd_server[5300]: negotiation failed
> Jul 1 11:23:09 ltsp6 nbd_server[5300]: Exiting.
>
> My config files look exactly as yours do.
>
> Qu
Hello Ben!
The server log reads:
Jul 1 11:23:09 ltsp6 nbd_server[5300]: negotiation failed
Jul 1 11:23:09 ltsp6 nbd_server[5300]: Exiting.
My config files look exactly as yours do.
Question: this means that the nbd-server uses the name-based protocol,
right? There still is en entry in /etc/i
Quoting Rüdiger Kupper :
> Hi Peter,
> thanks for the idea.
>
> You mean some unmounted device in the chroot has been packed into the
> BSD image? No, the BSD image is actually quite moderate, it has 505M:
>
I've had this problem, its was the nbd-server having an incorrect
configuration. Check
Hi Peter,
thanks for the idea.
You mean some unmounted device in the chroot has been packed into the
BSD image? No, the BSD image is actually quite moderate, it has 505M:
snip
linadmin@ltsp6:~$ ls -lh /opt/ltsp/images/i386.img
-rw-r--r-- 1 root root 505M Jun 30 20:25 /opt/ltsp/images/i38
Did you by any chance forget to unmount a device on chroot ??
Peter
On Sun, Jun 30, 2013 at 8:43 PM, Rüdiger Kupper wrote:
> Hello!
>
> Today I have updated our LTSP servers from 12.04 to 13.04 (raring), and
> regenerated the client chroots.
>
> But now the clients fail to boot via nbd, tellin
Hello!
Today I have updated our LTSP servers from 12.04 to 13.04 (raring), and
regenerated the client chroots.
But now the clients fail to boot via nbd, telling me: "exported device
is too big for me".
Nbd boot worked fine with precise (12.04). What did I do wrong?
Thanks for your help,
Regards
On Wed, Nov 30, 2011 at 6:32 PM, Stéphane Graber wrote:
> You only need to restart nbd-server if the nbd server configuration
> changes, so if for example you add a new image or change the name of
> an image.
Thank you for the clarification.
db
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/30/2011 06:02 PM, David Burgess wrote:
> One thing that appears less friendly on Ubuntu 11.10 compared to
> 11.04, each time I ltsp-update-image I get prompted to restart
> nbd-server and then restart my clients (which of course means a
> har
Your second post sounds unfortunate, I hope we don't have to restart all
clients on nbd update in the new Ubuntu versions.
To be honest I was surprised about what 'magic' was going on that allowed
you to update the NBD image and somehow the clients could still read the
old one until they were rebo
One thing that appears less friendly on Ubuntu 11.10 compared to
11.04, each time I ltsp-update-image I get prompted to restart
nbd-server and then restart my clients (which of course means a hard
reset if they lose their rootfs). As far as I can tell, this was never
necessary under 11.04 and prior
On Tue, Nov 29, 2011 at 4:11 PM, David Burgess wrote:
> Unless my memory is failing me, I'm pretty sure I've never had to
> manually configure this in the past. Is this a feature or a bug? Have
> I done something wrong here?
Disregard that. I see that nbd-server is listening on a different port
I just did a fresh install of ltsp-server on an Ubuntu 11.10 amd64
virtual server and the nbd server does not appear to be listening on
port 2000 (or any other). Comparing /etc/inetd.conf onmy 11.04
production server to the new server, I see the former has a line to
handle this, while the latter do
Here is an account of a learning/troubleshooting experience that
Google may some day find for the help of others.
Today I upgraded my home LTSP server to Ubuntu 11.10 using Ubuntu's
built-in command-line distribution upgrade tool, then worked through the
suggestions on the web page at
https:/
Hi Ragu,
as fas as I recall, you can specify nfs over the kernel-cmdline at boot.
If you have thinclients that dont support this (e.g. my IBM NetVista
N2200) you man need to use ugly hacks. Two years ago I simply changed
the "init" script of the init-rd (around line 175) like this:
run_script
Hello,
same to me.-/ Is there a switch using NFS as /
or anybody who has a cookbook to do this.
Just now I tried changing things in /etc/initramfs-tools/initramfs.conf to
NFS. In ubuntu,
there is more to do. Is there anybody with more experience changing root to
NFS.
bye,
rainer
Am Freitag
Exactly the same reason why I also use NFS - and I am sad to see NFS is slowly
going out of the scene.
Ondrej
On 30.09.2010 19:38, Jordan Erickson wrote:
Hey all,
Over the years that Ubuntu started using NBD for the primary client
filesystem, there have been a few bumps in the road. I remembe
Hey all,
Over the years that Ubuntu started using NBD for the primary client
filesystem, there have been a few bumps in the road. I remember the
primary reasons for switching over was for "security" and a speed boost.
Yet, even these days there seems to be many issues (or at least it seems
to me t
Hey all. I am having a problem with my clients logging out at random
intervals. I will be using a client, everything will be going well, then the
client will log itself out to LDM. When I log back in, I cannot execute any
localapps programs, but everything on the server will run fine. I can't even
This precedence find is spot-on. Thank you!
While it is obvious that nothing is broken and no functionality changed with
an update, I am glad that we went through this rigmarole, as I hope it will
help future generations of LTSP users.
Cheers Alkis, thank you again.
-Michael
On Tue, Aug 17, 201
This precedence find is spot-on. Thank you!
While it is obvious that nothing was every really 'broken' and no
functionality changed with an update - (what changed was my
hosts.allow), I am glad that we went through this rigmarole. I hope it
will help future generations of LTSP users.
Cheers Alkis
Στις 16-08-2010, ημέρα Δευ, και ώρα 13:49 -0400, ο/η Michael Blinn
έγραψε:
> Through more testing (thank you Alkis!) we've narrowed the problem
> down to hosts.allow syntax.
> ...
> This does not:
> ALL: 192.168.
> nbdrootd: ALL: keepalive
>
> This does not:
> ALL: 192.168.0.0/16
> nbdrootd: ALL:
Thank you for finding that, I was wondering if that was what was going
on in #ltsp yesterday morning.
I just made a few fresh copies of my ltsp servers due to some
storms/power issues causing trouble and am starting with a nice new load
of nbd processes that were only created today.
Here was
Through more testing (thank you Alkis!) we've narrowed the problem
down to hosts.allow syntax.
This respects keepalive:
nbdrootd: 192.168.: keepalive
This respects keepalive:
nbdrootd: ALL: keepalive
This respects keepalive:
nbdrootd: ALL: keepalive
ALL: 192.168.
This does not:
ALL: 192.168.
On Sat, Aug 14, 2010 at 9:50 AM, Alkis Georgopoulos wrote:
> Στις 13-08-2010, ημέρα Παρ, και ώρα 10:50 -0400, ο/η Michael Blinn
> έγραψε:
>> I figure it's about time to open a bug - I just don't know whether I
>> should open it against tcpd or inetd or ltsp
>
> Hi Michael,
>
> can you use some oth
I reverted to the 2.6.24-26-generic kernel on both server and client
and still experience the same issues:
Aug 16 08:04:54 www nbdrootd[27934]: connect from ws1-195 (192.168.1.195)
Aug 16 08:04:54 www nbd_server[27935]: connect from 192.168.1.195,
assigned file is /opt/ltsp/images/i386.img
Aug 16
Στις 13-08-2010, ημέρα Παρ, και ώρα 10:50 -0400, ο/η Michael Blinn
έγραψε:
> I figure it's about time to open a bug - I just don't know whether I
> should open it against tcpd or inetd or ltsp
Hi Michael,
can you use some other program to test that your system is capable of
sending keep alive pac
Client boot
Aug 13 08:44:23 edward dhcpd: DHCPREQUEST for 10.0.2.22 (10.0.0.53) from
00:08:c7:21:0d:30 via eth0
Aug 13 08:44:23 edward dhcpd: DHCPACK on 10.0.2.22 to 00:08:c7:21:0d:30
via eth0
Aug 13 08:44:23 edward nbdrootd[6277]: connect from 10.0.2.22 (10.0.2.22)
Aug 13 08:44:23 edward nbd_se
MORE testing:
r...@www:~# grep nbd /etc/hosts.allow
nbdrootd: ALL: keepalive
nbdswapd: ALL: keepalive
r...@www:~# cat /proc/sys/net/ipv4/tcp_keepalive_intvl
75
r...@www:~# cat /proc/sys/net/ipv4/tcp_keepalive_probes
9
r...@www:~# cat /proc/sys/net/ipv4/tcp_keepalive_time
7200
Boot a client:
Au
Further debugging on the same client:
Aug 12 08:15:11 www nbdrootd[27834]: connect from ws1-195 (192.168.1.195)
Aug 12 08:15:11 www nbd_server[27835]: connect from 192.168.1.195,
assigned file is /opt/ltsp/images/i386.img
Aug 12 08:15:11 www nbd_server[27835]: Size of exported file/device is 2009
Unfortunately I'm still seeing issues with my nbd processes after
setting tcp_keepalive values back to their defaults.
Logs from this morning - turned on a client:
Aug 12 08:15:11 www nbdrootd[27834]: connect from ws1-195 (192.168.1.195)
Aug 12 08:15:11 www nbd_server[27835]: connect from 192.168
Michael,
That sounds good, I did not get a chance to throw those execs in
yesterday so I may wait to see what you find out. I had checked my
sysctl.conf and I am still at the defaults.
Grant
On 08/09/2010 11:38 AM, Michael Blinn wrote:
> Please note:
>
> In working with alkisg in #ltsp, we've
Please note:
In working with alkisg in #ltsp, we've identified tcp keepalive values
in sysctl.conf that I had set:
net.ipv4.tcp_keepalive_time = 7200
net.ipv4.tcp_keepalive_intvl = 7200
net.ipv4.tcp_keepalive_probes = 6
Meaning my intervals are 14 hours, not 2. I'm resetting these to the
defaul
Here's a good synopsis of what I've seen. If I read previous posts
correctly, then these nbd processes should be killed after two hours.
Here are the results of my experiments:
r...@www:~# grep nbd /etc/hosts.allow
nbdrootd: ALL: keepalive
nbdswapd: ALL: keepalive
Client boots - here are serve
Michael,
I do have that same issue. I am going to give the exec a try that Alkis
was talking about. I appreciate the explanation by the way. Pretty
interesting to understand it a bit more.
I am not horribly worried about the swap files since they have been
moved to a swap server that has plen
The number of nbd server processes I see is greater than the number of
thin clients I have. I don't know that it's 2* greater though, as each
client gets one nbd-server for i386.img and one for the /tmp/tmp.??
swap file. I've set up some more testing for this morning to
illustrate what I'm saying.
> You should separate the machine setup from the user setup.
Yes, but LTSP involves both "machine setup" (think of scripts SCREEN_XX, or
xorg conf, that are configurable through ltsp.conf) and user setup (scripts
ldm/rc*).
Still, I have to admin that ltsp.conf is mainly about machine setup and l
Alkis Georgopoulos schrieb am 09. Aug 2010 um 10:05:48 CEST:
> Στις 09-08-2010, ημέρα Δευ, και ώρα 09:52 +0200, ο/η Helmut Lichtenberg
> έγραψε:
> > Hi Alkis,
> > thanks for your explanations. May I ask some more details?
>
> > Until now I imagined this connection somehow like opening a file over
Στις 09-08-2010, ημέρα Δευ, και ώρα 09:52 +0200, ο/η Helmut Lichtenberg
έγραψε:
> Hi Alkis,
> thanks for your explanations. May I ask some more details?
> Until now I imagined this connection somehow like opening a file over the
> network and getting something like a filehandle. I could not unders
Frédéric Grelot schrieb am 09. Aug 2010 um 09:30:36 CEST:
> > The number of nbd server processes is not related to the users logged
> > in, but to the machines connected.
>
> Well, maybe that could be an option of ltsp since ldm is quite light :
> active nbd/swap (launch client+swapon device) when
Στις 09-08-2010, ημέρα Δευ, και ώρα 09:30 +0200, ο/η Frédéric Grelot
έγραψε:
> Well, maybe that could be an option of ltsp since ldm is quite light :
> active nbd/swap (launch client+swapon device) when a user logs in, and
> disactive it (if possible) when no user is logged on (swapoff+close
> nbd
Hi Alkis,
thanks for your explanations. May I ask some more details?
Alkis Georgopoulos schrieb am 09. Aug 2010 um 09:31:16 CEST:
> In a 10.04 default installation:
> * the client runs nbd-proxy to connect to the server
> * and then nbd-client to connect to nbd-proxy locally
> * the server open
> The number of nbd server processes is not related to the users logged
> in, but
> to the machines connected.
Well, maybe that could be an option of ltsp since ldm is quite light : active
nbd/swap (launch client+swapon device) when a user logs in, and disactive it
(if possible) when no user is
Στις 09-08-2010, ημέρα Δευ, και ώρα 09:13 +0200, ο/η Helmut Lichtenberg
έγραψε:
> Alkis Georgopoulos schrieb am 06. Aug 2010 um 15:44:16 CEST:
> > You can put an extra `exec` at the last line of /usr/sbin/nbdrootd so
> > that no nbdrootd processes exist at all:
> > PATH=/usr/bin:/bin:$PATH exec nbd
grant schrieb am 06. Aug 2010 um 15:14:45 CEST:
> A client that runs displays around the office was also
> connected to that server at the time I killed the processes yesterday.
> It is still running fine, I did not search out it's process because I
> did not care if it needed to be restarted.
Michael Blinn schrieb am 06. Aug 2010 um 15:23:06 CEST:
> And even with the regression to the -27 kernel on my 8.04.4 servers, I
> have 25 nbd-server processes laying around with only 3 users logged in
> as of this morning.
The number of nbd server processes is not related to the users logged in,
Στις 06-08-2010, ημέρα Παρ, και ώρα 08:14 -0500, ο/η grant έγραψε:
> Ok checked today and I have 17 nbdrootd processes running.
>
> ps aux | grep nbdrootd | grep -v grep
> nobody8390 0.0 0.0 4092 640 ?Ss Aug05 0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> ...
And even with the regression to the -27 kernel on my 8.04.4 servers, I
have 25 nbd-server processes laying around with only 3 users logged in
as of this morning.
r...@www:~# ps auxw |grep nbd |grep tmp
nobody3655 0.0 0.0 9864 1068 ?SAug05 0:00
/bin/nbd-server 0 /tmp/tmp.DgDq
Ok checked today and I have 17 nbdrootd processes running.
ps aux | grep nbdrootd | grep -v grep
nobody8390 0.0 0.0 4092 640 ?Ss Aug05 0:00 /bin/sh
/usr/sbin/nbdrootd /opt/ltsp/images/i386.img
nobody8396 0.0 0.0 4092 640 ?Ss Aug05 0:00 /bin/sh
/usr/sbi
Hello Grant,
maybe is about nbd-proxy.
I found an patch to disabling nbd-proxy (sorry, I don't know anymore where I
get it). For me,
I haven't still now problems with never ending nbd processes.
You have to patch the chroot!
bye,
rainer
Am Mittwoch August 4 2010, um 14:55:42 schrieb grant:
>
I've reverted to kernel 2.6.24-27 to see if the problem was introduced
in -28. Will let you know what I find.
Regards,
Michael
On Thu, Aug 5, 2010 at 10:07 AM, grant wrote:
> Michael,
>
> Yes, I end up with a /tmp dir full of swap files. To remedy I made a
> second swap server, but I still have
helmut,
Thank you very much, I will check out what the kernel is set too and
check out your script.
Grant
On 08/05/2010 01:40 AM, Helmut Lichtenberg wrote:
> Hi Grant,
>
> grant schrieb am 04. Aug 2010 um 14:55:42 CEST:
>
>> I have recently had some issues with nbd and was wondering if thi
Michael,
Yes, I end up with a /tmp dir full of swap files. To remedy I made a
second swap server, but I still have a large number of nbdrootd
processes running. There was a entry in the /etc/hosts.allow for
# nbdrootd: ALL: keepalive
as you see I commented it out yesterday but I still have a
Hi Grant,
grant schrieb am 04. Aug 2010 um 14:55:42 CEST:
> I have recently had some issues with nbd and was wondering if this was
> normal.
depends, what you expect as normal. :^)
> The first is one of my ubuntu 10.04 servers has about 65 nbdrootd
> processes running right now, they are all f
I also have this issue in 8.04.4 -- was researching the issue and
then fell to pneumonia.
Are you say, the tmp files created by nbdswapd are also still left
around because nbdswapd processes are still running. This is what got
me - 8 GB of /tmp fills in a few days, killing the server.
Now that
Hello,
I have recently had some issues with nbd and was wondering if this was
normal.
The first is one of my ubuntu 10.04 servers has about 65 nbdrootd
processes running right now, they are all for serving the image, moved
nbd swap to swap server a bit ago. I only have about 10 users per day
Thanks, looks like it will be useful. Have a problem though - getting this
error:
lsof: WARNING: can't stat() fuse.ltspfs file system
/tmp/.test1-ltspfs/-mmcblk0p1
Output information may be incomplete.
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system
/home/test1/.gvfs
Output informati
Hi Steven,
Steven Taylor schrieb am 15. Jul 2010 um 03:58:54 CEST:
> Thanks, looks like it will be useful. Have a problem though - getting this
> error:
>
> lsof: WARNING: can't stat() fuse.ltspfs file system
> /tmp/.test1-ltspfs/-mmcblk0p1
> Output information may be incomplete.
> lsof: WARNING:
Hi folks,
I have written a short Perl script for the nbd-server, to show which thin
client is connected. The output looks like this:
nbd-connections of Thin Clients
Nr. ThinClientPIDStarted at Image/Swap file
I recently installed Ubuntu Lucid alpha 3 in a VM using the F4-install
ltsp server option and tried booting a client therefrom. It gets an IP
address, loads the kernel, but fails immediately after with a
negotiation error and failed to establish connection to nbd server.
Server is amd64, client is
On Mon, Aug 17, 2009 at 3:09 PM, Shahar Or wrote:
>
> lts.conf options don't have any affect on clients.
>
> I've found errors in the dmesg of clients. Here it is:
> http://pastebin.com/f59984166
>
> And this is the daemon.log of the server when the client boots:
> http://pastebin.com/f6077df9a
>
>
Am Donnerstag, den 20.08.2009, 13:10 -0300 schrieb Osvaldo Filho:
> un squashfs-sourcenenhuma
>
> NOT Installed
doesnt matter, its source code for a module, if it was ever built the
module might still be there, no matter if the package containing the
sourcecode is inst
un squashfs-sourcenenhuma
NOT Installed
2009/8/20 Oliver Grawert :
> hi,
> Am Mittwoch, den 19.08.2009, 15:58 -0300 schrieb Osvaldo Filho:
>> +++-=-=-==
>>
hi,
Am Donnerstag, den 20.08.2009, 11:53 +0300 schrieb Shahar Or:
> On Thu, Aug 20, 2009 at 11:33 AM, Oliver Grawert wrote:
> > i didnt refer to ltsp but to the "squashfs-source" package you
> > apparently had installed on yor system before ...
>
> I didn't, Oliver. Never had. Perhaps you're confu
On Thu, Aug 20, 2009 at 11:33 AM, Oliver Grawert wrote:
> i didnt refer to ltsp but to the "squashfs-source" package you
> apparently had installed on yor system before ...
I didn't, Oliver. Never had. Perhaps you're confusing me with Osvaldo.
-
hi,
Am Donnerstag, den 20.08.2009, 11:18 +0300 schrieb Shahar Or:
> Sorry, I didn't built it from source. I just used ltsp-build-client
> like I did several times before and like most users do.
i didnt refer to ltsp but to the "squashfs-source" package you
apparently had installed on yor system bef
On Thu, Aug 20, 2009 at 10:40 AM, Oliver Grawert wrote:
>> un squashfs-source (nenhuma
>> descrição disponível)
> did you use it when it was installed ? (did you compile squashfs from
> it ?) note that in recent kernel squashfs is upstream, no need for
> compiling it by
hi,
Am Mittwoch, den 19.08.2009, 15:58 -0300 schrieb Osvaldo Filho:
> +++-=-=-==
> un squashfs-source(nenhuma
> descrição disponível)
did you use it when it w
Well, I have exactly the same versions.
On Wed, Aug 19, 2009 at 10:00 PM, Osvaldo Filho wrote:
> The SquashFS is exported with NBD
>
> On Server:
> dpkg -l *nbd*
> Desejado=U=Desconhecido/Instalar/Remover/exPurgar/H=Reter
> |
> Estado=Não/Inst/arqs-Cfg/U=Descomp/Falhou-cfg/H=semi-inst/W=trig-adia
The SquashFS is exported with NBD
On Server:
dpkg -l *nbd*
Desejado=U=Desconhecido/Instalar/Remover/exPurgar/H=Reter
|
Estado=Não/Inst/arqs-Cfg/U=Descomp/Falhou-cfg/H=semi-inst/W=trig-adiado/Trig-pend
|/ Erro?=(nenhum)/H=Ret/precisa-Reinst/X=ambos-problemas (Est,Err:
maiúsculas=ruim)
||/ Nome
On Server:
==
dpkg -l *squash*
Desejado=U=Desconhecido/Instalar/Remover/exPurgar/H=Reter
|
Estado=Não/Inst/arqs-Cfg/U=Descomp/Falhou-cfg/H=semi-inst/W=trig-adiado/Trig-pend
|/ Erro?=(nenhum)/H=Ret/precisa-Reinst/X=ambos-problemas (Est,Err:
maiúsculas=ruim)
||/ Nome
On Wed, Aug 19, 2009 at 5:50 PM, Peter Stein wrote:
> You didn't do sth. like ltsp-build-client --dist
Sorry, what?
> We sometimes have problems that more than one nbd server is running.
> Try ps aux | grep nbd and kill all nbd processes. Restart nbd. Maybe
> that helps.
Well, nbd isn't r
You didn't do sth. like ltsp-build-client --dist
We sometimes have problems that more than one nbd server is running.
Try ps aux | grep nbd and kill all nbd processes. Restart nbd. Maybe
that helps.
Otherwise: I ran out of ideas.
2009/8/19 Shahar Or :
> On Mon, Aug 17, 2009 at 3:40 PM, Pe
On Mon, Aug 17, 2009 at 3:40 PM, Peter Stein wrote:
> Do you have the same version of sqashfs installed in the client's kernel and
> the server's kernel?
Well, probably. I built the client using Ubuntu's ltsp-build-client so
I guess it is.
But doesn't this seem like a problem with nbd, first?
--
[ 85.923452] nbd9: unknown partition table
[ 86.038570] nbd9: NBD_DISCONNECT
[ 86.039925] nbd9: Receive control failed (result -32)
[ 86.043099] nbd9: queue cleared
Do you have the same version of sqashfs installed in the client's kernel and
the server's kernel?
2009/8/17 Shahar Or
> O
On Mon, Aug 17, 2009 at 2:20 PM, Jim McQuillan wrote:
> debug what?
Sorry.
lts.conf options don't have any affect on clients.
I've found errors in the dmesg of clients. Here it is:
http://pastebin.com/f59984166
And this is the daemon.log of the server when the client boots:
http://pastebin.com/
debug what?
You didn't provide any details.
Jim McQuillan
j...@ltsp.org
Shahar Or wrote:
> Does anyone know how to debug this, please?
>
> --
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
Does anyone know how to debug this, please?
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, c
On Tue, Aug 11, 2009 at 2:11 PM, Peter Stein wrote:
> Mh,
> is lts.conf file in the correct folder? If you do not use standard
> setup that might cause the problem. Maybe the squashfs image wasn't
> created succesfully. Look if your nbd-server runs fine. NBD has
> sometimes a strange behavior.
Dea
Mh,
is lts.conf file in the correct folder? If you do not use standard
setup that might cause the problem. Maybe the squashfs image wasn't
created succesfully. Look if your nbd-server runs fine. NBD has
sometimes a strange behavior.
2009/8/2 Shahar Or :
> Dear friends,
>
> I SSH into a booted clie
Dear friends,
I SSH into a booted client and see these in dmesg:
[ 41.964840] nbd0: NBD_DISCONNECT
[ 41.966252] nbd0: Receive control failed (result -32)
[ 41.966552] nbd0: queue cleared
[ 41.997293] nbd0: Attempted send on closed socket
[ 41.997440] end_request: I/O error, dev nbd0, sector 37834
On Sat, Feb 7, 2009 at 4:27 PM, wrote:
>
> Martin Vuk wrote:
>
> On Mon, Nov 17, 2008 at 11:31 PM, wrote:
>>
> Still I do not understand the NBD-related error. Since in a different
> test set-up (Intel Xeon server, Dell Optiplex GX1 Pentium III clients),
> the thin clients seem to get hung over
On Monday 09 February 2009 22:28:53 ltsp-discuss-requ...@lists.sourceforge.net
wrote:
> > > > Still I do not understand the NBD-related error. Since in a different
> > > > test set-up (Intel Xeon server, Dell Optiplex GX1 Pentium III
> > > > clients), the thin clients seem to get hung over that er
Martin Vuk wrote:
On Mon, Nov 17, 2008 at 11:31 PM, wrote:
>
Still I do not understand the NBD-related error. Since in a different
test set-up (Intel Xeon server, Dell Optiplex GX1 Pentium III clients),
the thin clients seem to get hung over that error. The error messages
(as stated before) on
Στις 07-02-2009, ημέρα Σαβ, και ώρα 08:54 +0900, ο/η jam έγραψε:
> Despite all my RFM and trying I have not been able to get Virtualbox to PXE
> boot so I can use it as a LTSP test client. What did you do ?
>
> James
1. Host networking
--
Should work fine out of the box (the newe
On Sat, Feb 07, 2009 at 08:54:17AM +0900, jam wrote:
> On Saturday 07 February 2009 07:56:27 ltsp-discuss-
> requ...@lists.sourceforge.net wrote:
> > > Still I do not understand the NBD-related error. Since in a different
> > > test set-up (Intel Xeon server, Dell Optiplex GX1 Pentium III clients),
1 - 100 of 157 matches
Mail list logo
