This little issues is driving me crazy, I have search the internet to no
prevail. Everything appeared fine until I added an admin user in chroot and
did a ltsp-upgrade-image then this error started.
I moved /opt/ltsp/i386 to /opt/ltsp/i386-ORIG and i did a sudo
ltsp-build-client --arch i386
After playing around with it a bit it really appears that after every new
build or image update you need to re-run
(cat EOF
ipappend 3
EOF
) | sudo tee -a /var/lib/tftpboot/ltsp/{arch}/pxelinux.cfg/default
on every build in your LTSP.
--
You received this bug notification because you are a
[Expired for ltsp (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ltsp (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/951526
Hi Alkis
The nbd-server does not start sometimes - it does not start at boot at
all. If I try to boot a thin client after server reboot - the thin
client drops to BusyBox. If I login as a user and restart the nbd-server
manually, the thin clients can login without a problem.
I also did a fresh
Question - how and where is nbd-server started during startup ? What
could prevent nbd-server from starting ?
nbd-server ships an initscript in /etc/init.d/nbd-server
If `sudo service nbd-server restart` didn't work, it would be a configuration
problem, and since LTSP is responsible for the
Alkis - Thank you for the reply and assistance. The mystery for me was
that the nbd-server was actually not loading during startup at all.
Finally solved - and it had nothing to do with an LTSP config problem in
the end. It turned out to be my own custom startup script that called
the Network
OK so your problem is unrelated to this bug report; and I also think it's not
an LTSP bug but a misconfiguration.
Best way to get help in troubleshooting it would be to join the #ltsp
irc.freenode.net channel, or to ask in the ltsp-discuss mailing list.
IPAPPEND 3 is required in proxyDHCP mode
niplas did an upgrade and had a wrong /etc/nbd-
server/conf.d/ltsp_i386.conf from his older setup
Just to clarify:
I've tampered with some parts of the ltsp-setup but never touched the
nbd-servers configuration up until now.
This might give a hint towards the problem...
My quickfix was to
Have the same issue. My thin clients were working perfectly yesterday.
Now the client drops to Busybox after the latest round of updates.
I have double checked all my configuration files and they seem fine.
Also read, and re-read all the posts here and many others.
It seems that nbd-server is
What I found that worked was installing: ltsp-server-standalone
Then purge ltsp-server-standalone, to install ltsp-server
I only then modified the
/var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default file
Only add IPAPPEND 3, nothing else. Add it to the end of the default file
DO NOT CHANGE the
Using the proxyDHCP page from the ubuntu ltsp website doesn't work for
12.04.
Anthony, please edit the wiki page and write your findings there, as it's there
that will help people, while here it just messes up the bug report.
In the next LTSP version an ltsp-server-dnsmasq package will be
I can confirm TrialandError's findings. I also am running virtualbox 4.1.14
with extension pack.
The nbd-server, ltsp_i386.Conf file is not empty, it was created when I did
ltsp-build-client.
Anthony, trial-and-error's problem was an empty configuration file.
I'm not sure what your problem
Yes I restarted nbd-server after ltsp-update-image. However even though
nbd-server was restarted, the daemon is not listening on port 2000.
My problem is that upon booting the clients, the clients drop to a busy
box shell.
If I understand correctly, nbd-server doesn't use port 2000 anymore.
Even
The bottom line here is that I have built a ltsp-server using the
proxydhcp info from here:
https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP
I realize that it is not meant for 12.04, but most of the information
works.
I do not need to put ipappend 3 in like it suggests. However if I do,
I can confirm TrialandError's findings. I also am running virtualbox
4.1.14 with extension pack.
I have the same results. After removinng the quiet splash I get the
results that Trial posted above.
Specs:
Virtualbox 4.1.14 w/ extension pack
AMD fx 6 core
16gb ram
WIndows 7 Ultimate host OS
If I understood correctly so far,
trial-and-error tried a beta 12.04 installation, and the problem was an initial
empty /etc/nbd-server/conf.d/ltsp_i386.conf, which we don't know how it was
generated,
and niplas did an upgrade and had a wrong /etc/nbd-server/conf.d/ltsp_i386.conf
from his older
My install was clean. It was with i386, with updates installed while
Ubuntu was installing.
The nbd-server, ltsp_i386.Conf file is not empty, it was created when I
did ltsp-build-client.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same problem here, appears to happen when: ltsp-build-client...
I do actually have the complete ltsp-build-client output, unfortunatelly it's
in Swedish.
I can paste it somewhere if you like.
As a sidenote, when executed the second time no message about restarting
NBD-server shows up (!)
Previous LTSP specific NBD conf differs from new generic default
generated (?) on new build..
New:
[generic]
user = nbd
group = nbd
includedir = /etc/nbd-server/conf.d
Old:
[generic]
user = nobody
group = nogroup
oldstyle = false
Pardon, I never changed anything?! I did a clean install of a earlier
12.04 and ltsp-server-standalone.
The point is that any program might change a .conf file. So in the case
of an update there is the question what to do with an non-standard .conf
file. This is a good thing and a ltsp install
perhaps an existing ltsp_i386.conf should be deleted automatically?
No, because it would mean that the user manually edited the file, so we
should respect his changes.
I don't know what created an empty ltsp_i386.conf file in your case. Maybe a
bug in some previous Precise LTSP package which
Am 13.03.2012 12:03, schrieb Alkis Georgopoulos:
perhaps an existing ltsp_i386.conf should be deleted automatically?
No, because it would mean that the user manually edited the file, so we
should respect his changes.
OK, then in this case there should be a notification, that manual
editing is
If a user edits a configuration file and deliberately empties its
contents, I don't see why nbd-server or LTSP should bother notifying the
user that what he did may (or may not, depending on his other
configuration files) impact his server functionality.
I think that the question at this point is
Could you remove quiet splash from
/var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default and then reboot the
client and upload a photo of its screen when it drops to busybox, so
that we see where the problem is?
Also post the output of the following commands on your server:
ip -oneline -family inet
** Attachment added: screenshot1.jpg
https://bugs.launchpad.net/bugs/951526/+attachment/2856708/+files/screenshot1.jpg
** Attachment added: screenshot2.jpg
https://bugs.launchpad.net/bugs/951526/+attachment/2856709/+files/screenshot2.jpg
--
You received this bug notification because you
The problem is that you don't have an /etc/nbd-server/conf.d/ltsp_i386.conf
file and so nbd-server doesn't start itself.
That file is generated by ltsp-update-image. So the next information you need
to include is any errors that you see after running:
sudo ltsp-update-image
(you might also
It is a default Virtualbox install, but here your are informations
anyway:
ltsp@ltsp:~$ ip -oneline -family inet addr show
1: loinet 127.0.0.1/8 scope host lo
2: eth0inet 192.168.1.100/24 brd 192.168.1.255 scope global eth0
ltsp@ltsp:~$ grep -v ^# /etc/nbd-server/config
Sorry, but if I only had tried it once I would not have filed a bug.
I am building the chroot on 12.04 i386 constantly from scratch for a
while now: erros are getting lesser but ...
ltsp-built-client complained about an existing ltsp_i386.conf which was
empty.
After deleting it and
28 matches
Mail list logo
