Displaying 20 results from an estimated 10000 matches similar to: "Need to upgrade very old samba: 4.6 AD to current release"
2023 Mar 25
1
Need to upgrade very old samba: 4.6 AD to current release
On 24/03/2023 19:54, xyz via samba wrote:
> Hello
> I need to upgrade Samba v.4.6 with AD enabled, which is built from sources
> and installed on Ubuntu 12.04.
Ouch, they are both very old.
>
> Trying .configure script in v.4.9 it complains: Samba AD DC and
> --enable-selftest requires lmdb 0.9.16 or later
Do really need selftest ?
>
> In this state of the outdated
2023 Mar 25
1
Need to upgrade very old samba: 4.6 AD to current release
Thank you Rowland I will verify proposed path h in a lab environment.
The most important thing for me is that I have confirmation that it is
better to add new controllers and transfer roles than to restore copies and
update backups
Cheers!
sob., 25 mar 2023 o 12:30 Rowland Penny via samba <samba at lists.samba.org>
napisa?(a):
>
>
> On 24/03/2023 19:54, xyz via samba wrote:
>
2023 Mar 25
1
Need to upgrade very old samba: 4.6 AD to current release
I did something very similar recently. Joined a new 4.17.6 Debian Bullseye DC to an old 4.1.9 domain running on Wheezy and transferred roles, then demoted the original old DC. I did it in a sandbox environment but everything seemed to go smoothly. I?ve yet to do it in a live environment but since it?s a VM I?m quite confident there are no hiccups.
YMMV as my environment doesn't use GPOs for
2018 Sep 13
3
lmdb requirement for AD DC
On Thu, 2018-09-13 at 14:41 +0100, miguel medalha via samba wrote:
> Hello
>
> In one of my DCs, when I run ./configure for Samba 4.9.0, it fails
> with the following message:
>
> Checking for lmdb >= 0.9.16 via header check : not
> found
> Samba AD DC and --enable-selftest requires lmdb 0.9.16 or later
>
> My ./configure command line does not contain the
2018 Sep 13
2
lmdb requirement for AD DC
>> Did you specify --without-ldb-ldmb?
Nope. I didn't specify "–enable-selftest" either. The default for this option being "no", why does "configure" stop after complaining that "–enable-selftest" requires lmdb? Maybe I'm just being stupid... It happens.
2018 Sep 13
4
[Announce] Samba 4.9.0 Available for Download
========================================================
"Former police chief of Houston once
said of me: “Frank Abagnale could write
a check on toilet paper, drawn on the
Confederate States Treasury, sign it
‘U.R. Hooked’ and cash it at any bank
in town, using a Hong Kong driver’s
license for identification.”
Frank W. Abagnale, Catch Me If You Can:
The True Story
2018 Sep 13
4
[Announce] Samba 4.9.0 Available for Download
========================================================
"Former police chief of Houston once
said of me: “Frank Abagnale could write
a check on toilet paper, drawn on the
Confederate States Treasury, sign it
‘U.R. Hooked’ and cash it at any bank
in town, using a Hong Kong driver’s
license for identification.”
Frank W. Abagnale, Catch Me If You Can:
The True Story
2018 Sep 13
2
[Announce] Samba 4.9.0 Available for Download
On Thu, 13 Sep 2018 14:41:54 +0100
miguel medalha via samba <samba at lists.samba.org> wrote:
> Hello
>
> In one of my DCs, when I run ./configure for Samba 4.9.0, it fails
> with the following message:
>
> Checking for lmdb >= 0.9.16 via header check : not
> found Samba AD DC and --enable-selftest requires lmdb 0.9.16 or later
>
> My ./configure command
2018 Sep 13
2
lmdb requirement for AD DC
>> As per the release notes, it should work unless you say "--without-ldb-
>> lmdb". The message just got mucked up.
The "configure" stage actually failed. How can it be a message problem only?
2018 Sep 13
0
[Announce] Samba 4.9.0 Available for Download
Hello
In one of my DCs, when I run ./configure for Samba 4.9.0, it fails with the following message:
Checking for lmdb >= 0.9.16 via header check : not found
Samba AD DC and --enable-selftest requires lmdb 0.9.16 or later
My ./configure command line does not contain the option "–enable-selftest", and "../configure –help" gives the following output:
--enable-selftest
2019 Apr 17
2
Is possible use BIND9 as DNS Back End on a new Samba DC?
I'm sorry to I forgot answer appropriate.
I'm running CentOS 7 with all packages upgraded. I've followed instruction
in
https://wiki.samba.org/index.php/Package_Dependencies_Required_to_Build_Samba
with
some need modifications (yum line is bellow this text) and I've installed
python 3.4. I've installed Bind9 from package manager where Bind9 version
is 9.9.4.
YUM command to
2023 Mar 14
1
Updating samba version 4.17.5 to version 4.17.6 from Debian backports - armel architecture
On 13 March 2023 15:19 Dr. Nicola Mingotti wrote:
> Hi,
>
> Just an idea,
>
> i was moving samba in the last days, i put in my note that i did:
> ---
> $> sudo apt install -t bullseye-backports winbind
> ---
>
> So maybe, if you installed the stable winbind and the backported samba there are issues.
>
> You might try to remove winbind and reinstall it from
2024 Jun 26
1
Error when raising Samba 4.19 Functional Level
Hi Felipe,
Le 25/06/2024 ? 17:14, Felipe Ribeiro de Oliveira via samba a ?crit?:
> Hi, I raised the functional level of my Samba 4.19 server with the commands
> below, the Schema update took a long time but ended successfully, however
> when raising the functional level with the second command the error below
> occurred and I was unable to complete the complete process. Can anyone
2023 Mar 13
1
Updating samba version 4.17.5 to version 4.17.6 from Debian backports - armel architecture
I have several devices, mostly amd64 and armhf architectures, all of which updated samba to 4.17.6 without any problems. But one which is armel architecture failed to update; instead I get the following when I try to update:
root at goflex:~# samba -V
Version 4.17.5-Debian
root at goflex:~# apt update
Hit:1 http://ftp.uk.debian.org/debian bullseye InRelease
Get:2 http://ftp.uk.debian.org/debian
2023 Mar 17
1
Updating samba version 4.17.5 to version 4.17.6 from Debian backports - armel architecture
On 16 March 2023 20:22 Michael Tokarev wrote:
> 14.03.2023 13:02, spindles seven via samba wrote:
> This is one of many examples why I thought it is not a good idea to have the same
> version of samba packages for bullseye on my repository as on testing/unstable.
> But people insisted :)
>
> The thing is: both my bullseye 4.17 repository and debian unstable now has version
>
2023 Mar 18
1
Updating samba version 4.17.5 to version 4.17.6 from Debian backports - armel architecture
18.03.2023 01:56, spindles seven wrote:
> On 16 March 2023 20:22 Michael Tokarev wrote:
..
>> Once you remove my 4.17 repo from your sources.list, apt wont be able to find the
>> right version of samba for bullseye, even if "almost" the same version is available in
>> bpo11.
>
> Thanks for this. However, I don't understand this last statement - once I
2019 Sep 24
2
Repacking database from v1 to v2 format: how long does it take?
On 23/09/2019 20:41, Andrew Bartlett wrote:
> On Mon, 2019-09-23 at 11:25 +0200, Francesco Malvezzi via samba wrote:
>> hi all,
>>
>> I updated a small domain with 8k object to samba-4.11.0 and the
>> database
>> conversion from v1 to v2 didn't take a noticeable time.
>>
>> On the other hand, in a larger domain with 67k object, where the
>>
2017 Jan 29
3
classic upgrade fails with 4.6-test
On Sun, Jan 29, 2017 at 4:54 PM, Rowland Penny <rpenny at samba.org> wrote:
> When you built Samba, did you use the '--with-ntvfs-fileserver' or
> '--enable-selftest' options with configure ?
>
I used '--without-ntvfs-fileserver'.
2018 Jun 28
5
DRS and DNS sync are not working after update from 4.8.2 to 4.8.3
After update I have got this:
samba-tool drs kcc -Uadm2 -d 9
INFO: Current debug levels:
all: 9
tdb: 9
printdrivers: 9
lanman: 9
smb: 9
rpc_parse: 9
rpc_srv: 9
rpc_cli: 9
passdb: 9
sam: 9
auth: 9
winbind: 9
vfs: 9
idmap: 9
quota: 9
acls: 9
locking: 9
msdfs: 9
dmapi: 9
registry: 9
scavenger: 9
dns: 9
ldb: 9
tevent: 9
auth_audit: 9
2024 Aug 28
1
High RAM consumption
On 22/08/24 19:26, Dinar Yulm via samba wrote:
> Hello,
>
> LDAP Samba processes consume a lot of memory. Each LDAP process loads the
> entire ldb database into memory and does not release it over time. For
> example, for a 4GB ldb database and 4 LDAP processes, Samba will use up
> more than 16 GB of RAM. If only 16GB of RAM is installed on the server,
> then Samba will