ltsp-build-client and ltsp-update-image fails if inetd.conf is not cleared

Bug #138204 reported by Roland Ronquist
2
Affects Status Importance Assigned to Milestone
ltsp (Ubuntu)
Fix Released
Undecided
Oliver Grawert

Bug Description

When I run ltsp-build-client or ltsp-update-image, both fails if
the nbdrootd line for port 2000 is not removed.

This is not a big showstopper for me since quick jab with emacs
will help me around it, but I can imagine teachers without
much unix experience not knowing anything about neither
inetd or how to configure the same.

And yes, I am running the plain vanilla inetd that comes
standard with *buntu, no xinetd or anything fancy.
Well according to /etc/init.d it is actually from openbsd.
It may be a good thing updating inetd, but beware,
when running thin clients we do expect user to have
complex needs and many may not be served well
with the stock inetd package and I would rather see
that the tools create images and things like the name
implies rather then messing with config files that should
be left to the system manager to handle.

Though I had other problems earlier, I did not run into
this particular issue until running an upgrade yesterday.

Best,
R.R.

Revision history for this message
Oliver Grawert (ogra) wrote :

whats the error message and whats your ltsp version ?
the error message was turned into a warning with the 5.0.26 upload (see below)

ltsp (5.0.26) gutsy; urgency=low

  [Oliver Grawert <email address hidden>]
  * new udeb postinst (and new template) added, fixes (LP: #121547)
    we have full progress reporting in the installer now :)
  * added option --skipimage to ltsp-build-client to supress ltsp-update-image
    execution in d-i (we run it separately in the udeb)
  * its not an error if the port is set in inetd.conf.
...

Revision history for this message
Oliver Grawert (ogra) wrote :

in a second look, that code needs some mode modifications, will be fixed in the next upload

Revision history for this message
Oliver Grawert (ogra) wrote :

fixed in 5.0.28

Changed in ltsp:
assignee: nobody → ogra
status: New → Fix Released
Revision history for this message
cornbread (corn13read) wrote : Re: ltsp-build-client

i think i'm having the same problem. Running edubuntu gutsy at the end of ltsp-build-client --arch i386 on an amd64 box it will sit indefinately at "Info: updating inetd config" until i press enter a few times then this happens:

Use of uninitialized value in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 109, <GEN0> line 1.

info: LTSP client installation completed successfully

but inetd.conf never gets updated.

Changed in ltsp:
status: Fix Released → In Progress
Revision history for this message
Oliver Grawert (ogra) wrote :

are you sure you have version 5.0.28 or higher installed ? can you post the output of:
dpkg -l ltsp-server

Revision history for this message
Roland Ronquist (roland-ronquist) wrote :

sorry for not reporting back in time, it do work now without editing the inetd.conf.

BTW are things supposed to work with xinetd as well?

Revision history for this message
Scott Balneaves (sbalneav) wrote :

No, we're not supporting xinetd at the moment. Just the openbsd-inetd.

Scott

Revision history for this message
hasan (hassanidin) wrote :

I am experiencing the same problem as well, running
$sudo ltsp-build-client
....
.....
       shadow (42)
        dhcp (101)
        fuse (106)
        utmp (43)
        staff (50)
        src (40)
        mail (8)
        klog (103)
Info: updating inetd config
........
and then pressing ^C yields
.......
umount: /opt/ltsp/i386//proc: not mounted
..........
$dpkg -l ltsp-*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=================================-=================================-==================================================================================
ii ltsp-server 5.0.34 Basic LTSP server environment
ii ltsp-server-standalone 5.0.34 Complete LTSP server environment
un ltsp-utils <none> (no description available)

How do I deal wiith this problem?

Revision history for this message
Oliver Grawert (ogra) wrote :

inetd isnt touched if port or imagename are found in inetd.conf anymore since quite a while, closing the bug ...

Changed in ltsp (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.