search for: werr_not_enough_memori

Hi there. I'm trying to upgrad from 4.7.7 to 4.9.4. I built from source, running on centos 7.6 on a Raspberry Pi. When testing on a secondary DC, my "samba-tool drs showrepl" errors out with: ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to dc02.rvx.is > failed - drsException: DRS connection to dc02.rvx.is failed: (8, >

On Wed, 2 Jan 2019 09:54:24 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Wed, 2 Jan 2019 09:45:56 +0000 > Kristján Valur Jónsson <kristjan at rvx.is> wrote: > > > Any thoughts? Have code, will debug. The error itself is > > meaningless to me and I am deeply and utterly unfamiliar with samba > > code, but if you have any thought or

On Fri, 28 Dec 2018 15:38:59 +0000 Kristján Valur Jónsson via samba <samba at lists.samba.org> wrote: > Hi there. > I'm trying to upgrad from 4.7.7 to 4.9.4. > I built from source, running on centos 7.6 on a Raspberry Pi. > When testing on a secondary DC, my "samba-tool drs showrepl" errors > out with: > > ERROR(<class

so the DC with FSMO is not done first?     Van: Kristján Valur Jónsson [mailto:kristjan at rvx.is] Verzonden: vrijdag 28 december 2018 17:08 Aan: L.P.H. van Belle Onderwerp: Re: [Samba] replication failing for 4.9.4 dc01 is still running 4.7.7.  No need to restart it.  There is also still a DC03 running 4.7.7.  the only one I've upgraded is DC02.  resolv.conf on DC02 is configured with

On Wed, 2 Jan 2019 09:45:56 +0000 Kristján Valur Jónsson <kristjan at rvx.is> wrote: > Any thoughts? Have code, will debug. The error itself is > meaningless to me and I am deeply and utterly unfamiliar with samba > code, but if you have any thought or experiments in mind... > > On Fri, 28 Dec 2018 at 16:07, Rowland Penny via samba > <samba at lists.samba.org>

Ok, but is there another upgrade path possible, e.g. via 4.8? I am upgrading via source build, btw. The reason I'm asking is because i've been asked me to check using samba git 'master" source to check that pesky bind restart bug ( https://bugzilla.samba.org/show_bug.cgi?id=13214) Since this is in production, I need to get my environment up to "latest" in order to do

Hai, DC1, did you reboot it or just restarted services, i advice a reboot. Then on DC2. Samba internal DNS by accident? If so, stop samba, set log level = 10 Start it wait 30 sec, stop it. Now change the resolv.conf so DC1 is the first contacted. and start it again. Test again. Now im out the office in 15 min, but try this. Keep these logs, a samba dev may ask for it. Greetz,