* sigh * this is becoming an exercise in frustration. * Performing a direct migration of my Samba 3.3.4 box by copying .tdb and related files to the new machine looks like a non-starter, as the group_mappings file went from an ldb to a .tdb format, and it appears the only conversion occurs during an in-place version upgrade. * The next step, it appears, looks to be some sort of upgrade to the *existing* 3.3.4 box to a later Samba incarnation. That *might* solve what I think now is a dependency issue that's subsequently caused wbinfo to stop working entirely. It *might* also solve whatever SMB signing issue is preventing net rpc vampire from working on the BDC. * Given the age of the setup, are there recommended "increments" for upgrading a 3.3.4 setup? Or should I be able to go to at least 3.6 (the last 3.x series release) directly in place without much risk? -David -- View this message in context: http://samba.2283325.n4.nabble.com/Problems-in-SAMBA-3-3-to-4-0-migration-tp4680653p4680750.html Sent from the Samba - General mailing list archive at Nabble.com.
Update I did update my Samba 3.3.4 PDC to 3.6.24 after MUCH grief, overcoming (at least) two library incompatibilities PLUS recalling the dusty old memories that if you start with Slackware, you use Slack's samba installer, not the source from Samba itself. I've fixed two library problems with libtalloc and libwbclient that prevented smbd from starting (with a Signal 6 - hard crash). It now starts...but my original problem between wbinfo and winbindd persists. I think there's a similar library problem going on here that's causing wbinfo to break off the pipe back to winbindd when it requests...anything. Ironically, wbinfo from my new BDC works just fine. But I still can't vampire. This library issue may be at hand with my "Segmentation Fault" when trying to do the vampire. Not sure, but if anyone has any suggestions in that regard, I'd sure appreciate the boost. I've read additional non-Slackware posts indicating a problem between wbinfo and libwbclient versions, so I'm suspecting I've introduced that issue here, but now I'm just too tired to sort through it any more for now. Been working on this all day, and my brain is toast, and I realize my situation may be so specific there's no way anyone could really offer much insight, but if for no other reason I thought I'd update this thread and at least try to document what I've done. -- View this message in context: http://samba.2283325.n4.nabble.com/Problems-in-SAMBA-3-3-to-4-0-migration-tp4680653p4680891.html Sent from the Samba - General mailing list archive at Nabble.com.
On 15/02/15 04:41, soonerdave wrote:> Update > > I did update my Samba 3.3.4 PDC to 3.6.24 after MUCH grief, overcoming (at > least) two library incompatibilities PLUS recalling the dusty old memories > that if you start with Slackware, you use Slack's samba installer, not the > source from Samba itself. > > I've fixed two library problems with libtalloc and libwbclient that > prevented smbd from starting (with a Signal 6 - hard crash). It now > starts...but my original problem between wbinfo and winbindd persists. I > think there's a similar library problem going on here that's causing wbinfo > to break off the pipe back to winbindd when it requests...anything. > Ironically, wbinfo from my new BDC works just fine. But I still can't > vampire. This library issue may be at hand with my "Segmentation Fault" when > trying to do the vampire. Not sure, but if anyone has any suggestions in > that regard, I'd sure appreciate the boost. I've read additional > non-Slackware posts indicating a problem between wbinfo and libwbclient > versions, so I'm suspecting I've introduced that issue here, but now I'm > just too tired to sort through it any more for now. > > Been working on this all day, and my brain is toast, and I realize my > situation may be so specific there's no way anyone could really offer much > insight, but if for no other reason I thought I'd update this thread and at > least try to document what I've done. > > > > > > -- > View this message in context: http://samba.2283325.n4.nabble.com/Problems-in-SAMBA-3-3-to-4-0-migration-tp4680653p4680891.html > Sent from the Samba - General mailing list archive at Nabble.com.I wonder if your problems are being caused by the use of the smbpasswd passdb ? If you examine 'man smb.conf' for 3.6, you will find this (under 'passdb backend') : ? smbpasswd - The old plaintext passdb backend. Some Samba features will not work if this passdb backend is used. Perhaps if you migrate to tdbsam it will work, not sure because I have never had to do it, but it is worth trying in a test setup, I believe that you can do this with pdbedit. Rowland