[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] SMBLDAP script with Fedora Core 4? (dahopkins@comcast.net)



Matt,

Thanks, late last night I caught the _ vs - change ... but ..... the installer now completes (I also removed the k12ltsp rpm requirement) and ... samba will not start.  I am getting an error as shown below.  I am now officially at wits end.  I need to get this server online and working to replace the existing LDAP server (which is samba 2.x based).  The new system is dual opteron (64 bit) and I am discovering that this may not be such a good thing. ;)  

>From /var/log/samba/log.smbd

[2005/07/07 16:12:18, 0] passdb/secrets.c:secrets_init(64)
  Failed to open /etc/samba/secrets.tdb
[2005/07/07 16:12:18, 0] passdb/secrets.c:secrets_init(64)
  Failed to open /etc/samba/secrets.tdb
[2005/07/07 16:12:18, 0] passdb/secrets.c:secrets_init(64)
  Failed to open /etc/samba/secrets.tdb
[2005/07/07 16:12:18, 0] passdb/secrets.c:secrets_init(64)
  Failed to open /etc/samba/secrets.tdb
[2005/07/07 16:12:18, 0] passdb/machine_sid.c:pdb_generate_sam_sid(176)
  pdb_generate_sam_sid: Failed to store generated machine SID.
[2005/07/07 16:12:18, 0] lib/util.c:smb_panic2(1517)
  PANIC: Could not generate a machine SID

[2005/07/07 16:12:18, 0] lib/util.c:smb_panic2(1525)
  BACKTRACE: 6 stack frames:
   #0 smbd(smb_panic2+0x6d) [0x5555556ee8e0]
   #1 smbd(get_global_sam_sid+0x2a4) [0x5555556b1a44]
   #2 smbd(init_guest_info+0x4e) [0x55555572b239]
   #3 smbd(main+0x222) [0x55555575d5d6]
   #4 /lib64/libc.so.6(__libc_start_main+0xdc) [0x2aaaac0e24cc]
   #5 smbd [0x5555555a3989]

I am clueless on what is happening at this point.  I went through the detailed instructions (did not use the sbmldap-installer) and end up at the same point with the same errors.

I am now up to the point of manually building samba from source, and don't know what directories to use (it appears that the rpm's do not use the default directories).

Aaaarrrrrgghhhh!!!!!  I have 36 hours before I have to leave for a few weeks (medical issue) and this?  It is looking like August is going to be very, very rough.  Then again, perhaps I will magically find the solution 'real soon' (like installing a 32-bit version of Fedora core 4 on my opteron system)

Sincerely,
Dave Hopkins


> _______________________________________________
> K12OSN mailing list
> K12OSN redhat com
> https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>

--- Begin Message ---
> Date: Wed, 06 Jul 2005 22:22:16 +0000
> From: dahopkins comcast net
> Subject: [K12OSN] SMBLDAP script with Fedora Core 4?
> 
> I have been following the thread on the SMBLDAP installer, so I tried it on a straight Fedora Core 4 x86_64 install (actually I need it as well).
> 
> I 'simply copied the fedora-core-3 section in the distro.pm, and then manually added every rpm that the script said could not be found using the fc4 equiv.  But ... I have two rpm checks that I can't get satisfied.
> ----------------------------------------------------------------------------------
> Checking for perl-Net_SSLeay-1.*.rpm...not found.
> ...
> Checking for perl-Net_SSLeay-1.23-8.k12ltsp.0.3.1.i386.rpm...not found.
> ...
> I need to install perl-Net_SSLeay-1.*.rpm (located on cd #4 of the distro media)
> I need to install perl-Net_SSLeay-1.23-8.k12ltsp.0.3.1.i386.rpm (included with t his script)

Yep - I ran into this last night working with K12LTSP-4.4.0-beta,
which is based on FC4.  In fact, I'd recommend downloading version
2.0-alpha of the Samba/LDAP Installer and trying the
K12LTSP-4.4.0-beta installation on FC4; you might have decently good
luck.

In any case, I suspect the problem here is that the name of the
perl-Net_SSLeay package changed to "perl-Net-SSLeay".  Now how lame is
that?  :-p

Version 2.0-alpha of the Samba/LDAP Installer (available on the website
ATM) *should* be able to get past this problem for you.  In any case,
with 2.0-alpha you can install the RPMs manually if you want and just
run "make configure" to skip all the dependency checking.  That should
work fine for you.

--matt

Attachment: signature.asc
Description: Digital signature


--- End Message ---

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]