Koozali.org: home of the SME Server

Linux Workstations on SME

crimsonline

Linux Workstations on SME
« Reply #15 on: January 07, 2005, 02:32:40 PM »
Hi Damian,
on ypbind -debug -bradcast I got;

add_server() domain: something, broadcast
[Welcome to ypbind-mt, version 1.17.3]

do_broadcast() for domain 'test' is called
broadcast: RPC: Time out
leave do_broadcast() for domain 'something''
trylock=success

I just did a clean installation again but it gives me the same problem

Louis

Damian

Linux Workstations on SME
« Reply #16 on: January 07, 2005, 03:00:37 PM »
Louis,

The RPC Timeout error suggests that the NIS server isn't responding to broadcast requests.

Even though you're not going to use it later I'd suggest installing ypbind on the server and getting it to bind to itself first. It doesn't take long. Then you'll know whether the issue is on the server or the client.

Damian

crimsonline

Linux Workstations on SME
« Reply #17 on: January 07, 2005, 03:27:59 PM »
damian,

i'm going to do the ypbind on server now, will let you know shortly

louis

crimsonline

Linux Workstations on SME
« Reply #18 on: January 07, 2005, 04:07:11 PM »
ok on my sme server, when i do a ypbind -debug -broadcast I get;

ypbind-mt already running (pid2752)

so i stoped ypbind with ./ypbind stop and ran it again

add_server() domain: test broadcast slot:0
[welcome to ypbind-mt, version 1.10]

Answer for domain 'test' from server 'server.test.com'
Pining all active server .....

I did not get the line "leave do_broadcast()...."

Is this good or bad?

Damian

Linux Workstations on SME
« Reply #19 on: January 07, 2005, 04:24:38 PM »
That's OK.

The line "Answer for domain 'test' from server 'server.test.com'" shows that the NIS server is responding to broadcasts. Excellent.

So, on the server do the following commands return something useful ?

ypwhich
ypcat passwd

If so, try restarting ypbind on the client again and trying these commands there.

Damian

crimsonline

Linux Workstations on SME
« Reply #20 on: January 07, 2005, 05:19:34 PM »
on SME;
ypwhich
server.test.com
ypcat passwd
louis!!5000:5000......

on Suse;
ypwhich
cant ypbind: Reason: Domain not bound no such map passwd by name

ypcat passwd
Reason: cant bind to server wich serves this domain

hmmmm......

Offline Mjohnson

  • *
  • 172
  • +0/-0
Linux Workstations on SME
« Reply #21 on: January 07, 2005, 05:28:04 PM »
At the risk of sounding really dumb, because frankly I am no expert, I was having the same problems last evening.  I noted in Jespers HowTo that he recommended naming the NIS Domain something different than the DNS Domain.  I renamed my NIS domain "johnson" and had no luck in forging the NIS connection.

I then, on a whim, renamed it "johnson.com" and the ypbind and serve connection came to life.

Again, I have no idea if this even makes sense from a technical standpoint, or if it was merely an empirical coincidence.

...and Thank You very much Damian...  your assistance has been excellent!!
......

Damian

Linux Workstations on SME
« Reply #22 on: January 07, 2005, 06:46:16 PM »
Hi Mr Johnson,

You're right, technically that shouldn't work if your server config is set the way you thought is should be. Type "domainname" on your SME server to see what NIS domain it should be the master for. Happy you've got it going though  :-)

Louis,

Your NIS master is allowing the local ypbinding so you're sorted on the server side.

On the SuSE machine:

grep YPBIND /etc/sysconfig/ypbind

Post your answers: my answers are shown:
YPBIND_OPTIONS=""
YPBIND_LOCAL_ONLY="no"
YPBIND_BROADCAST="no"
YPBIND_BROKEN_SERVER="no"

cat /etc/defaultdomain
something

more /etc/yp.conf
ypserver 192.168.100.40
domain something

ps ax | grep portmap | grep -v grep
 2909 ?        Ss     0:00 /sbin/portmap

Checks that portmap is running on the client too.

When successfully bound you should be able to check this ...

find /var/yp -exec ls -ld {} \;
drwxr-xr-x  3 root root 104 May 26  2004 /var/yp
-rw-r--r--  1 root root 185 Apr  6  2004 /var/yp/nicknames
drwxr-xr-x  2 root root 112 Jan  7 17:43 /var/yp/binding
-rw-r--r--  1 root root 14 Jan  7 17:43 /var/yp/binding/something.1
-rw-r--r--  1 root root 14 Jan  7 17:43 /var/yp/binding/something.2

This shows that binding files have been created correctly for NIS v1 & v2.

I assume that "ypbind -broadcast" on the client still doesn't work ? Post your answers!

Damian

whistleruk

Linux Workstations on SME
« Reply #23 on: January 07, 2005, 07:19:22 PM »
Got this Setup perfect using SME 6
Clients using Suse 9
At the Suse logon I see all user accounts listed but when trying to logon I'm getting the message "Xsesson disabled for user [userid]"
This is the closes and goes back to the logon screen, so this is either a client problem or the user data being pulled from the SME server is restricting the logon, not sure how I'm gona fix this one..... any ideas?

Damian

Linux Workstations on SME
« Reply #24 on: January 07, 2005, 07:56:28 PM »
Hi Whistler(UK)

The error is because Xsession doesn't allow X-window logins when the shell provided by the passwd entry for that user is not a recognised one. In SuSE's /usr/lib/X11/xdm/Xsession it says:

#
# Disable graphical login if normal login is disabled
#
login=false
while read sh ; do
    if test "$sh" = "$SHELL" ; then
        login=true
        break
    fi
done < /etc/shells

If you ypcat the passwd file and grep for the user you're logging in as it'll probably give the shell as /bin/false.

To fix that, on SME login as root, change user shell in /etc/passwd from /bin/false to /bin/bash for that (or those) users and save it out:

cd /var/yp
make

This gets past the "Xsession disabled" error but KDE's DCOP will complain that it can't edit/save the required session info into the user's .kde dir. This because it's using the NIS passwd info to find the user's homedir and that path doesn't make sense (yet) on the  client.

What we need here is NFS. Probably the automounter too but because SME doesn't lay out it's user homedir like other unices (/home/username) it'll take a little tweaking.

I'd hold off rolling any of this out until your test environments work. ;-)

Damian

whistleruk

Linux Workstations on SME
« Reply #25 on: January 07, 2005, 08:08:27 PM »
Quote from: "Damian"
Hi Whistler(UK)

The error is because Xsession doesn't allow X-window logins when the shell provided by the passwd entry for that user is not a recognised one. In SuSE's /usr/lib/X11/xdm/Xsession it says:

#
# Disable graphical login if normal login is disabled
#
login=false
while read sh ; do
    if test "$sh" = "$SHELL" ; then
        login=true
        break
    fi
done < /etc/shells

If you ypcat the passwd file and grep for the user you're logging in as it'll probably give the shell as /bin/false.

To fix that, on SME login as root, change user shell in /etc/passwd from /bin/false to /bin/bash for that (or those) users and save it out:

cd /var/yp
make

This gets past the "Xsession disabled" error but KDE's DCOP will complain that it can't edit/save the required session info into the user's .kde dir. This because it's using the NIS passwd info to find the user's homedir and that path doesn't make sense (yet) on the  client.

What we need here is NFS. Probably the automounter too but because SME doesn't lay out it's user homedir like other unices (/home/username) it'll take a little tweaking.

I'd hold off rolling any of this out until your test environments work. ;-)

Damian


Cheers for that! Think alot of testing is needed here lol.... but be great if we could get something sorted for people who want to implement a full linux environment. :)

Offline versa

  • ***
  • 109
  • +0/-0
Linux Workstations on SME
« Reply #26 on: January 07, 2005, 09:06:13 PM »
Hi Guys just to give my .02c,I have been using SME for about 6 months now and have a mix of Xandros linux and XP on workstations, it works like a treat. I did try SuSe and Fedora but I had a problem with when I loged in I could not get acess to my user/home i-bay. I had some sucess with using smb4k but I am no linux whiz so I stuck with Xandros as it worked out of the box for me and has all I need as a linux desktop.
......

Damian

Linux Workstations on SME
« Reply #27 on: January 07, 2005, 10:05:56 PM »
Hi Versa, Pleased it's working for you  :-D

Some successes ....NIS account logins using the automounter and user homedirs from SME ...... here we go:


On SME:

Make sure you have nfs-utils-0.3.3-5 installed (get it  from ftp://fr.rpmfind.net/linux/redhat/7.3/en/os/i386/RedHat/RPMS/ or a mirror)

After installing add the following to /etc/exports:

/home/e-smith/files/users       192.168.100.117(rw) 192.168.100.118(rw)

(name your clients or use a wildcard)

chkconfig nfs on
/etc/init.d/nfs start

create /var/yp/push and fill with:
grep "/home/e-smith/files/users" /etc/passwd | awk -F: ' {print $1":"$2":"$3":"$4":"$5":\/home\/"$1":\/bin\/bash"}' > /etc/passwd.dist
make

chmod 755 /var/yp/push

Edit /var/yp/Makefile and change the line which says:
PASSWD      = $(YPPWDDIR)/passwd
to
PASSWD      = $(YPPWDDIR)/passwd.dist

When you run /var/yp/push only the user entries from /etc/passwd are crunched into an alternative passwd file with corrected homedir paths for the client automounters to use. Also we don't want to distribute SME's root password to everyone do we ?

Run /var/yp/push

On SuSE:

Make the following the only entries in /etc/auto.master
/home           auto.home

Create /etc/auto.home and add the following
*  -fstype=nfs,soft,intr,rsize=8192,wsize=8192,nosuid 192.168.100.40:/home/e-smith/files/users/&/home

Replacing the IP address for your SME's address (as usual)

Go into yast and in the "NIS Client" section enable the automounter

Restart ypbind (rcypbind restart).

I had some trouble with running in and out of NIS bind status and found it was down to nscd caching the previous status settings. Probably best to turn this off until it's all working (rcnscd stop)

OK, try and "su - sme-user" from the commandline. If it works, log out of KDE and try KDE with that user. If things aren't working you'll find your environment screwed so just stop the automounter and ypbind to recover (rcautofs stop:rcypbind stop)

I may have missed something in this list as I wrote it after the event. Comments Please!

Damian

Damian

Linux Workstations on SME
« Reply #28 on: January 07, 2005, 10:32:48 PM »
For anyone quick off the mark reading the previous post, read it again because I added some NFS stuff at the top  :lol:
Damian

crimsonline

Linux Workstations on SME
« Reply #29 on: January 08, 2005, 10:00:32 AM »
hi damian,
I have reinstalled my SME and Suse this moring to give myself hope !! enyway
On the SuSE machine:

grep YPBIND /etc/sysconfig/ypbind
YPBIND_OPTIONS=""
YPBIND_LOCAL_ONLY="no"
YPBIND_BROADCAST="no"
YPBIND_BROKEN_SERVER="no"

cat /etc/defaultdomain
test.com

more /etc/yp.conf
ypserver 192.168.2.100
domain test.com brpadcast

ps ax | grep portmap | grep -v grep
7623 ? Ss 0:00 /sbin/portmap

Checked portmap is running on the client.

I got:
find /var/yp -exec ls -ld {} \;
drwxr-xr-x 3 root root 104 May 26 2004 /var/yp
-rw-r--r-- 1 root root 185 Apr 6 2004 /var/yp/nicknames
drwxr-xr-x 2 root root 112 Jan 7 17:43 /var/yp/binding

but not:
-rw-r--r-- 1 root root 14 Jan 7 17:43 /var/yp/binding/something.1
-rw-r--r-- 1 root root 14 Jan 7 17:43 /var/yp/binding/something.2

louis