jaunty ltsp client creates /etc/resolv.conf with 000 permissions

Bug #347957 reported by PerlStalker
34
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ltsp (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I'm running Jaunty as an LTSP and a Jaunty fat client created with the LTSP client tools included in the ltsp packages. The client boots successfully and properly sets the IP in the interface via DHCP. However, /etc/resolv.conf is an empty file with permissions set to 000. This, of course, prevents DNS from functioning properly.

DHCP successfully handing out IP and DNS information for several hundred other machines.

Client and server `lsb_release -rd`:
# lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

Revision history for this message
Marcelo R. Minholi (minholi) wrote :

I can reproduce this in my local install. There is no DNS on fat clients using Ubuntu 9.04 final.

Revision history for this message
Javier Jaspe (jaspejavier) wrote :

I'm hitting this one too. I'm creating an Ubuntu 9.04 LTSP fat client from scratch as per https://help.ubuntu.com/community/UbuntuLTSP/LTSPFatClients and taking some ideas from http://www.nubae.com/030-fatclient.

I have another fat client image created with ubuntu 8.10 and it's working fine from the same LTSP server.

Revision history for this message
robanon (robert-mcdonald) wrote :

I am having the same problem with 9.04, just ran a default ltsp-build-client, then ssh into the thin client and see this:

# cat /etc/resolv.conf
cat: /etc/resolv.conf: Input/output error
# ls -l /etc/resolv.conf
---------- 1 root root 0 2009-05-13 12:34 /etc/resolv.conf
#

Also noticed this in dmesg output:

[ 14.300167] nbd0: NBD_DISCONNECT
[ 14.301714] nbd0: Receive control failed (result -32)
[ 14.304588] nbd0: queue cleared
[ 14.310657] nbd0: Attempted send on closed socket
[ 14.310665] end_request: I/O error, dev nbd0, sector 372048
[ 14.310680] SQUASHFS error: sb_bread failed reading block 0x2d6a8
[ 14.310683] SQUASHFS error: Unable to read cache block [b5aa08b:1552]
[ 14.310691] SQUASHFS error: Unable to read inode [b5aa08b:1552]

Changed in ltsp (Ubuntu):
status: New → Confirmed
Revision history for this message
Peter Matulis (petermatulis) wrote :

The workaround:

1. Create a script in the chroot whose purpose is to set up proper permissions on the client resolver file:

$ sudo touch /opt/ltsp/i386/etc/init.d/chmod-resolv.sh

Contents:

-----------
#! /bin/sh
chmod 644 /etc/resolv.conf
-----------

2. Rebuild the client image

3. Add options to lts.conf (DNS search domain and nameserver for your network; and location of above file relative to the chroot)

-----------
SEARCH_DOMAIN = example.com
DNS_SERVER = 192.168.1.1
RCFILE_01 = /etc/init.d/chmod-resolv.sh
-----------

Revision history for this message
Stéphane Graber (stgraber) wrote :

This one is fixed in Karmic.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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