Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - morphy_richards

Pages: 1 [2] 3
16
Okay, it goes something like this:



  • I've made a gateway using clearos to act as a fairly simple router / iptables firewall between my computer science network and the wider school network. Essentially this is just to provide internet to my own network.
  • I set up a dns server on a raspberry pi using dnsmasq just for internal (computing.lan) server names.
  • "athena" is the zentyal server (for logins and file access). I realise that zentyal could do all of the above jobs too but I only found out about it relatively recently, well into the development of this network and I'm loathe to take everything else away unless I really have to.
  • lovelace is an edubuntu ltsp server. 30 clients (students) normally log on via two subnets using Raspberry Pi's running berryterminal.

mount -t cifs //192.168.0.4/test1 /mnt -o username=test1 and mount -t cifs //192.168.0.10/test1 /mnt -o username=test1 both return the same result on the zentyal server "mount: wrong fs type, bad option, bad superblock..."



17
Hello again ...  :-[

I did a complete re-install of Zentyal.
This time I made sure I have got the file sharing module properly configured and installed.
My client system is (Ed)Ubuntu 12.04 (also pretty much a fresh re-install)

Followed through the tutorial again.
Still I'm getting

Code: [Select]
root@lovelace:~# ssh test1@lovelace
test1@lovelace's password:
[...]

Last login: Wed Jul 10 12:07:29 2013 from localhost
Could not chdir to home directory /home/test1: No such file or directory
test1@lovelace:/$

ssh'ing into the zentyal server and doing
mount -t cifs //192.168.0.10/test1 /mnt -o username=test1,domain=COMPUTING
but still getting
Code: [Select]
mount: wrong fs type, bad option, bad superblock on //192.168.0.10/test1,
       missing codepage or helper program, or other error

sudo netstat -patun | grep samba
returns
Code: [Select]
root@athena:~# sudo netstat -patun | grep samba
tcp        0      0 192.168.0.4:88          0.0.0.0:*               LISTEN      12525/samba     
tcp        0      0 127.0.1.1:88            0.0.0.0:*               LISTEN      12525/samba     
tcp        0      0 127.0.0.1:88            0.0.0.0:*               LISTEN      12525/samba     
tcp        0      0 192.168.0.4:636         0.0.0.0:*               LISTEN      12523/samba     
tcp        0      0 127.0.1.1:636           0.0.0.0:*               LISTEN      12523/samba     
tcp        0      0 127.0.0.1:636           0.0.0.0:*               LISTEN      12523/samba     
tcp        0      0 192.168.0.4:1024        0.0.0.0:*               LISTEN      12520/samba     
tcp        0      0 127.0.1.1:1024          0.0.0.0:*               LISTEN      12520/samba     
tcp        0      0 127.0.0.1:1024          0.0.0.0:*               LISTEN      12520/samba     
tcp        0      0 192.168.0.4:3268        0.0.0.0:*               LISTEN      12523/samba     
tcp        0      0 127.0.1.1:3268          0.0.0.0:*               LISTEN      12523/samba     
tcp        0      0 127.0.0.1:3268          0.0.0.0:*               LISTEN      12523/samba     
tcp        0      0 192.168.0.4:3269        0.0.0.0:*               LISTEN      12523/samba     
tcp        0      0 192.168.0.4:389         0.0.0.0:*               LISTEN      12523/samba     
tcp        0      0 127.0.1.1:3269          0.0.0.0:*               LISTEN      12523/samba     
tcp        0      0 127.0.1.1:389           0.0.0.0:*               LISTEN      12523/samba     
tcp        0      0 127.0.0.1:3269          0.0.0.0:*               LISTEN      12523/samba     
tcp        0      0 127.0.0.1:389           0.0.0.0:*               LISTEN      12523/samba     
tcp        0      0 192.168.0.4:135         0.0.0.0:*               LISTEN      12520/samba     
tcp        0      0 127.0.1.1:135           0.0.0.0:*               LISTEN      12520/samba     
tcp        0      0 127.0.0.1:135           0.0.0.0:*               LISTEN      12520/samba     
tcp        0      0 192.168.0.4:464         0.0.0.0:*               LISTEN      12525/samba     
tcp        0      0 127.0.1.1:464           0.0.0.0:*               LISTEN      12525/samba     
tcp        0      0 127.0.0.1:464           0.0.0.0:*               LISTEN      12525/samba     
udp        0      0 192.168.0.4:389         0.0.0.0:*                           12524/samba     
udp        0      0 127.0.1.1:389           0.0.0.0:*                           12524/samba     
udp        0      0 127.0.0.1:389           0.0.0.0:*                           12524/samba     
udp        0      0 192.168.0.4:464         0.0.0.0:*                           12525/samba     
udp        0      0 127.0.1.1:464           0.0.0.0:*                           12525/samba     
udp        0      0 127.0.0.1:464           0.0.0.0:*                           12525/samba     
udp        0      0 192.168.0.4:88          0.0.0.0:*                           12525/samba     
udp        0      0 127.0.1.1:88            0.0.0.0:*                           12525/samba     
udp        0      0 127.0.0.1:88            0.0.0.0:*                           12525/samba     


18
 :-[
That was it. The module wasn’t enabled. Maximum embarrassment factor!
(I do this kind of thing a lot actually)
In my own defence I (mumble mumble) only started doing this a few months ago and haven’t used a *nix system since '99.

On the bright side this is clearly a great community and my hat is off to you for this product and the excellent support you all give.

It's currently enabling, saving changes and up to 75% done.
I'll try it again once its done and let you know how it went.

Thanks for now.
(Shuffles off in a crablike motion while hoping for holes in the earth that might swallow me up)

19
Hmm... thanks for that

I tried ssh'ing into the actual zentyal server and did:
root@athena:~# mount -t cifs //192.168.0.10/test5 /mnt -o username=test5,domain=COMPUTING
Code: [Select]
mount: wrong fs type, bad option, bad superblock on //192.168.0.10/test5,
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

syslog
Code: [Select]
Jul  5 11:05:56 athena kernel: [4817736.132349] FS-Cache: Loaded
Jul  5 11:05:56 athena kernel: [4817736.146990] FS-Cache: Netfs 'cifs' registered for caching
Jul  5 11:05:56 athena kernel: [4817736.147089] Key type cifs.spnego registered
Jul  5 11:05:56 athena kernel: [4817736.147098] Key type cifs.idmap registered
Jul  5 11:05:56 athena kernel: [4817736.147270] CIFS: no cache= option specified, using "cache=loose". This default will change to "cache=strict" in 3.
Jul  5 11:05:56 athena kernel: [4817736.162685] CIFS VFS: Connecting to DFS root not implemented yet
Jul  5 11:05:56 athena kernel: [4817736.162731] CIFS VFS: cifs_mount failed w/return code = -22

On the remote computer to check I did sudo apt-get install cifs-utils and got the "cifs-utils is already the newest version..." I then removed and re-installed it again just to check but got the same result.

On the actual server itself:
Code: [Select]
root@athena:~# sudo netstat -patun | grep samba
root@athena:~#
There was no result.
(netstat on it's own returns only tcp, tcp6, udp and udp6 results.)

I also tried mount -t cifs -o username=test5,password=test5 //192.168.0.10/test5 ~/testMount5 with the options at the beginning but still got
 
Code: [Select]
wrong fs type, bad option, bad superblock on //192.168.0.10/test5
.....


20
Thanks for your help with this so far!
Looking at the [file sharing] section of the Zentyal web UI :

I have
Realm:    COMPUTING.LAN
NetBIOS domain name:    COMPUTING
NetBIOS computer name:    athena
Server description:    Zentyal File Server

I've tried:
mount -t cifs //192.168.0.10/test5 /mnt -o username=test5,domain=COMPUTING ,domain=COMPUTING.LAN (and even tried domain=athena)
each says
Code: [Select]
root@lovelace:/var/log/samba# mount -t cifs //192.168.0.10/test5 /mnt -o username=test5,domain=COMPUTING
Password:
Unable to find suitable address.
I also had a poke about in my /etc/samba/smb.conf and tried setting
Code: [Select]
[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = COMPUTING
# server string is the equivalent of the NT Description field
#   server string = %h server (Samba, Ubuntu)
  server string = Zentyal File Server

... .. ... ...
 ;   interfaces = 192.168.0.0/24 eth2
(Although I'm really not at all sure what I am doing with this, I thought I would have a try at configuring it)

I looked in the var/log/samba files too but couldn’t see anything that immediately jumped out at me.

Best regards to you as well.


21
Doing this locally I get:
Code: [Select]
root@lovelace:~# mount -t cifs //192.168.0.10/test5 /mnt -o username=test5
Password:
Unable to find suitable address.

However doing it from a remote computer that I have used to ssh in I get:
Code: [Select]
Last login: Thu Jul  4 13:25:57 2013 from kerberos.computing.lan
lovelace_admin@lovelace:~$ sudo -i
[sudo] password for lovelace_admin:
root@lovelace:~# mount -t cifs  //192.168.0.10/test5  /mnt -o username=test5
mount: unknown filesystem type 'cifs '
root@lovelace:~#

:o



22
Sorry about this it doesn't seem to be anything to do with ltsp.
I'm working with a fresh install of (ed)ubuntu 12.10 with nothing else in place.

I've done everything in the tutorial but all I get when I ssh in is:

could not chdir to directory /home/test3 no such file or directory

What could be going wrong?

23
Hi again,
I seem to be having a mild spot of bother.
I have made an ltsp edubuntu server. I set up this server as described in your post and with the modification I described
Quote
<volume user="*" fstype="cifs" server="192.168.0.4" path="%(DOMAIN_USER)" mountpoint="/home/%(DOMAIN_USER)" options="sec=ntlm,nodev,nosuid" />
<volume user="*" fstype="cifs" server="192.168.0.4" path="temp" mountpoint="/home/%(DOMAIN_USER)/SRV/temp" options="sec=ntlm,nodev,nosuid" />
This seemed to make this work for me.
Unfortunately it seems that it's not mounting the homes from the zentyal server when users log in as thin clients. The files just get saved in the ltsp server's /home/username
(although the users were created on the zentyal server)
I can login via ssh and it works as expected or use sshfs but I am finding my users have their files saved in two sperate home locations.
Have you any idea what might be causing this to happen?

24
Hi. Just wanted to thank you for this! It has been fantastically useful.

I came across one issue. In Ubuntu 12.04 a LDAP user on the zentyal box will be able to log in but not mount the home directory.

You need two lines in  /etc/security/pam_mount.conf.xml under  <!-- Volume definitions -->


<volume user="*" fstype="cifs" server="192.168.0.4" path="%(DOMAIN_USER)" mountpoint="/home/%(DOMAIN_USER)" options="sec=ntlm,nodev,nosuid" />
<volume user="*" fstype="cifs" server="192.168.0.4" path="temp" mountpoint="/home/%(DOMAIN_USER)/SRV/temp" options="sec=ntlm,nodev,nosuid" />

It seems it wont work without this temp mount.

Thanks again.

25
It's fixed. You need two lines in  /etc/security/pam_mount.conf.xml under  <!-- Volume definitions -->


<volume user="*" fstype="cifs" server="192.168.0.4" path="%(DOMAIN_USER)" mountpoint="/home/%(DOMAIN_USER)" options="sec=ntlm,nodev,nosuid" />
<volume user="*" fstype="cifs" server="192.168.0.4" path="temp" mountpoint="/home/%(DOMAIN_USER)/SRV/temp" options="sec=ntlm,nodev,nosuid" />



26
Also tried manually creating the directory
/home/test3
I then tried chmod 777 test3

then ssh test3@lovelace
"Could not chdir to home directory /home/test3: No such file or directory"
I then exit

ls -l in /home
and there is only test2, the home directory for test3 has disappeared.

It's very confusing because it works for test2 but not for test3.


27
A little more on this.

I have just created a new ldap user (test3) via the Zentyal users and groups web interface.
I tried to log that user in on a LTSP terminal with no success so i went to the Ubuntu computer and tried to do it in a shell
ssh test3@lovelace
Last login: Tue May 21 13:09:55 2013 from 192.168.1.20
Could not chdir to home directory /home/test3: No such file or directory

192.168.1.x is the subnet for my ltsp clients so it looks like some login happened from here but it was prevented because of the home directory issue.
I can login the ltsp client test2
On the ubuntu computer I can see a directory "test2" in /home. The ldap account "test2" now works.
But I had previously created that directory manually.

If I do
/home$ ls -l

drwxr-xr-x 26 lovelace_admin lovelace_admin 4096 May 21 13:08 lovelace_admin
drwx--x--x 26 test2          __USERS__      4096 May 21 13:07 test2

These exist

If I try to do
mkdir test3
chown test3 test3
I get the following:
Code: [Select]
pam_mount(pam_mount.c:553): pam_mount 2.10: entering session stage
pam_mount(misc.c:38): Session open: (ruid/rgid=1000/1000, e=0/1000)
pam_mount(pam_mount.c:614): no volumes to mount
command: 'pmvarrun' '-u' 'root' '-o' '1'
pam_mount(misc.c:38): set_myuid<pre>: (ruid/rgid=1000/1000, e=0/1000)
pam_mount(misc.c:38): set_myuid<post>: (ruid/rgid=0/1000, e=0/1000)
pmvarrun(pmvarrun.c:252): parsed count value 0
pam_mount(pam_mount.c:440): pmvarrun says login count is 1
pam_mount(pam_mount.c:645): done opening session (ret=0)
pam_mount(pam_mount.c:691): received order to close things
pam_mount(pam_mount.c:693): No volumes to umount
command: 'pmvarrun' '-u' 'root' '-o' '-1'
pam_mount(misc.c:38): set_myuid<pre>: (ruid/rgid=1000/1000, e=0/1000)
pam_mount(misc.c:38): set_myuid<post>: (ruid/rgid=0/1000, e=0/1000)
pmvarrun(pmvarrun.c:252): parsed count value 1
pam_mount(pam_mount.c:440): pmvarrun says login count is 0
pam_mount(pam_mount.c:728): pam_mount execution complete
pam_mount(pam_mount.c:115): Clean global config (1073741824)

but ls -l
still lists owner of test3 as root

ssh test3 still gives "Could not chdir to home directory /home/test3: No such file or directory!











28
I appear to have got it working ...

I dont actually know what I did.

All I did was In my  /etc/security/pam_mount.conf.xml file
<debug enable="1" />

Also - I opened the file /etc/pam.d/common-auth
To check that
auth optional pam_mount.so
was there and it was. So I exited the file without chanign anything.

I then logged in using my ldap test user credentials and instead of seeing the expected "Could not chdir to home directory /home/test2: No such file or directory"
It just ... worked! (???)

29
Not entirely.
I notice in the page you link there is a command to do a manual mount that looks like this:
mount -t cifs //192.168.2.1/C /mnt/Windows-C -o user=name_of_windows_user_account

In my /etc/security/pam_mount.conf.xml on my Ubuntu computer (the one I want to log into using ldap users saved on my zentyal box) I have a command like this:
<volume user="*" fstype="cifs" server="192.168.0.4" path="%(DOMAIN_USER)" mountpoint="/home/%(DOMAIN_USER)" options="sec=ntlm,nodev,nosuid" />

All the manual methods that use "mount" I've seen them use this kind of format:
mount remote_directory local_directory

I tried manually making a /home/test2 on my ubuntu computer
I then did ssh tes2@lovelace
I get this message:

Last login: Tue May 21 11:01:28 2013 from localhost
Could not chdir to home directory /home/test2: No such file or directory

After I exit ssh and look back into the /home directory test2 has disappeared.?





30
Looking at /var/log/auth.log

Code: [Select]
May  9 14:57:28 lovelace sshd[12428]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=localhost  user=test1
May  9 14:57:28 lovelace sshd[12428]: pam_winbind(sshd:auth): getting password (0x00000388)
May  9 14:57:28 lovelace sshd[12428]: pam_winbind(sshd:auth): pam_get_item returned a password
May  9 14:57:28 lovelace sshd[12428]: pam_winbind(sshd:auth): request wbcLogonUser failed: WBC_ERR_AUTH_ERROR, PAM error: PAM_USER_UNKNOWN (10), NTSTAT
May  9 14:57:28 lovelace sshd[12428]: Accepted password for test1 from 127.0.0.1 port 42187 ssh2
May  9 14:57:28 lovelace sshd[12428]: pam_unix(sshd:session): session opened for user test1 by (uid=0)
May  9 14:57:28 lovelace sshd[12428]: pam_mount(mount.c:69): Messages from underlying mount program:
May  9 14:57:28 lovelace sshd[12428]: pam_mount(mount.c:73): Unable to find suitable address.
May  9 14:57:28 lovelace sshd[12428]: pam_mount(pam_mount.c:521): mount of test1 failed

edit - it says here uid=0

but if i try
id test1
I get
Code: [Select]
lovelace_admin@lovelace:/$ id test1
uid=2001(test1) gid=1901(__USERS__) groups=2001(test group),1901(__USERS__)

syslog just says
Code: [Select]
May  9 15:06:33 lovelace kernel: [91361.942857] CIFS VFS: Error connecting to socket. Aborting operation
May  9 15:06:33 lovelace kernel: [91361.943375] CIFS VFS: cifs_mount failed w/return code = -111

My /etc/security/pam_mount.conf.xml

Code: [Select]
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE pam_mount SYSTEM "pam_mount.conf.xml.dtd">
<!--
        See pam_mount.conf(5) for a description.
-->

<pam_mount>

                <!-- debug should come before everything else,
                since this file is still processed in a single pass
                from top-to-bottom -->

<debug enable="1" />

                <!-- Volume definitions -->

<volume user="*" fstype="cifs" server="192.168.0.4" path="%(DOMAIN_USER)" mountpoint="/home/%(DOMAIN_USER)" options="sec=ntlm,nodev,nosuid" />

                <!-- pam_mount parameters: General tunables -->

<!--
<luserconf name=".pam_mount.conf.xml" />
-->

<!-- Note that commenting out mntoptions will give you the defaults.
     You will need to explicitly initialize it with the empty string
     to reset the defaults to nothing. -->
<mntoptions allow="nosuid,nodev,loop,encryption,fsck,nonempty,allow_root,allow_other" />
<!--
<mntoptions deny="suid,dev" />
<mntoptions allow="*" />
<mntoptions deny="*" />
-->
<mntoptions require="nosuid,nodev" />

<logout wait="0" hup="0" term="0" kill="0" />


                <!-- pam_mount parameters: Volume-related -->

<mkmountpoint enable="1" remove="true" />


</pam_mount>

Pages: 1 [2] 3