<div dir="ltr"><div><div>Hi Andy,<br></div>Thanks for your fast answer !<br></div>Glad to have started testing Debian-Lan.<br>I was heager to start using it.<br><div><div class="gmail_extra"><br><br><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
GOsa is not implemented in the Squeeze setup. I decided to do that<br>
only for Wheezy, as it will hopefully be released soon.<br></blockquote><div><br></div><div>OK, no issue as Wheezy will soon be the stable release. And indeed, it's not in the Squeeze repo.<br></div><div>Although, we will unfortunately use a 2.7 version. The latest seems promising.<br>
</div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><br>
> Then, I tried the wheezy CD image but it got problems to get the network<br>
> connection though the network card was recognized. (I wont be able to check<br>
> this further because it now runs, and I want to get it in production asap -<br>
> Challenge started)<br>
<br>
</div>(I should probably update the CD image to the latest version in git ...)<br></blockquote><div><br></div><div>Tell me if I can help. I can also host some files if it helps. <br><br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><br>
> I finally installed wheezy and made a conversion.<br>
><br>
> As is, I can say NFS, KDC are not OK yet. This will be checked right<br>
> now.<br>
<br>
</div>OK, looking forward for the reasons/problems ...<br></blockquote><div><br></div><div>Here is the content of /var/log/fai/mainserver/softupdate-20130227_130645/error.log<br><br>fai.log:/usr/bin/fai-class: WARNING. Following classes are defined multiple times: 2 DEBIAN<br>
fai.log: 404 Not Found [IP: 77.243.184.65 80]<br>fai.log:W: Failed to fetch <a href="http://http.debian.net/debian-backports/dists/wheezy-backports/main/binary-amd64/Packages" target="_blank">http://http.debian.net/debian-backports/dists/wheezy-backports/main/binary-amd64/Packages</a> 404 Not Found [IP: 77.243.184.65 80]<br>
fai.log:E: Some index files failed to download. They have been ignored, or old ones used instead.<br>fai.log:The following packages have unmet dependencies:<br>fai.log:Warning: The home dir /var/run/nslcd/ you specified can't be accessed: No such file or directory<br>
fai.log:! Warning: you may need to reload your webservice!<br>fai.log:E: Some index files failed to download. They have been ignored, or old ones used instead.<br><br></div><div>This one seems to explain the passwd problem for the various services. I don't remember that it has been asked (I didn't recorded the session...)<br>
fai.log:KDC_LDAP/10-slapd-KDC FAILED with exit code 127.<br>fai.log:KDC_LDAP/10-slapd-KDC FAILED with exit code 127.<br>shell.log:ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)<br>shell.log:./KDC_LDAP/10-slapd-KDC: line 68: dialog: command not found<br>
shell.log:./KDC_LDAP/10-slapd-KDC: line 71: dialog: command not found<br>shell.log:KDC_LDAP/10-slapd-KDC FAILED with exit code 127.<br>shell.log:ln: failed to create symbolic link `//media/cdrom/cdrom0': File exists<br>
shell.log:mv: cannot stat `//etc/icinga/objects/localhost_icinga.cfg': No such file or directory<br>shell.log:ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)<br>shell.log:./KDC_LDAP/10-slapd-KDC: line 68: dialog: command not found<br>
shell.log:./KDC_LDAP/10-slapd-KDC: line 71: dialog: command not found<br>shell.log:KDC_LDAP/10-slapd-KDC FAILED with exit code 127.<br>status.log:KDC_LDAP/10-slapd-KDC FAILED with exit code 127.<br>status.log:KDC_LDAP/10-slapd-KDC FAILED with exit code 127. <br>
</div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><br>
> I will also need to integrate:<br>
> - samba because of windows clients.<br>
> - ddclient (or alike) because of ... well, budget considerations.<br>
> - ldaps<br>
><br>
<br>
</div>OK, samba is a good point. LDAP is kerberized via GSSAPI and uses TLS<br>
already, so no need to use ldaps.<br></blockquote><div><br></div><div>Right, I saw afterward that it was configured with TLS. That's fine!<br></div><div>Though, having recently made a setup of openldap/tls/samba, I saw the config of openldap was a bit changed. It now uses ldif.<br>
</div><div>Are you interested in defining the configuration following this method? Config space in ldap DB will become the new standard (I read that in <a href="http://wiki.debian.org">wiki.debian.org</a> somewhere)<br></div>
<div>If yes, I will collect the config files I used and look at your scripts.<br></div><div><br>
</div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><br>
> The only question I have right now is, what is the default gosa's admin<br>
> password?<br>
<br>
</div>You should have been asked for a password for 'admin' during<br>
installation. Use 'admin' and that password for login into GOsa.<br></blockquote><div><br></div><div>unfortunately not, or I missed it.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><br>
> There is one in /root/installation/LDAPadminPWD but it is not accepted.<br>
> Pardon me if I missed the information somewhere.<br>
<br>
</div>This is the password of the LDAP admin, try:<br>
<br>
ldapvi -ZZ -D cn=admin,dc=intern -w `cat /root/installation/LDAPadminPWD`<br>
<br>
It is used for the ldapscripts i.e. the debian-lan command and GOsa's<br>
internal access to LDAP. Usually you should not need it (anymore), an<br>
anything should be done with the admin password and kerberos (except<br>
GOsa login, where no Kerberos is used (but the same password)).<br></blockquote><div><br></div><div>I will try that.<br></div><div>Otherwise, is it possible to launch the scripts again manually from the "converted" server or do I need to reinstall from scratch?<br>
<br></div><div>Thereby, I suppose that if I change mainserver.intern to whatever.domain, I will need to adapt the whole ldap config and directory accordingly?<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I hope they are useful. Please report all problems, that's pretty<br>
appreciated! I might live in my filter bubble already, so it's great<br>
to have some input from someone else.<br></blockquote><div><br></div><div>They are !<br></div><div>I will do. As I told you, I'm very interested in the project and will do my best to help out. <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Best regards,<br>
<br>
Andi<br></blockquote><div><br><br></div><div>Greetings<br></div><div>Julien<br></div></div></div></div></div>