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, > 'WERR_NOT_ENOUGH_MEMORY') > File "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/drs.py", > line 47, in drsuapi_connect > (ctx.drsuapi, ctx.drsuapi_handle, ctx.bind_supported_extensions) > drs_utils.drsuapi_connect(ctx.server, ctx.lp, ctx.creds) > File "/usr/local/samba/lib/python2.7/site-packages/samba/drs_utils.py", > line 59, in drsuapi_connectthis is on DC02. When I do the same on DC01 (which hasn't been upgraded), it reports errors talking to the DC, e.g.> DC=DomainDnsZones,DC=rvx,DC=is > Default-First-Site-Name\DC02 via RPC > DSA object GUID: 564fb63e-e2eb-45f9-b868-7d85e71c8dcc > Last attempt @ Fri Dec 28 14:26:16 2018 UTC failed, result > 8 (WERR_NOT_ENOUGH_MEMORY) > 206 consecutive failure(s). > Last success @ NTTIME(0)This all worked previously. I don't believe that memory is really the problem, rather this appears to be a generic error percolating up. my samba.log shows this:> [2018/12/28 15:30:44.911645, 0] > ../source4/smbd/server.c:510(binary_smbd_main) > samba version 4.9.4 started. > Copyright Andrew Tridgell and the Samba Team 1992-2018 > [2018/12/28 15:30:47.282129, 0] > ../source4/smbd/server.c:696(binary_smbd_main) > binary_smbd_main: samba: using 'standard' process model > [2018/12/28 15:30:47.371819, 0] > ../source4/dsdb/common/util.c:1815(samdb_reference_dn_is_our_ntdsa) > Failed to find object DC=rvx,DC=is for attribute fsmoRoleOwner - Cannot > find DN DC=rvx,DC=is to get attribute fsmoRoleOwner for reference dn: No > such Base DN: DC=rvx,DC=is > [2018/12/28 15:30:47.403897, 0] > ../lib/util/become_daemon.c:138(daemon_ready) > daemon_ready: STATUS=daemon 'samba' finished starting up and ready to > serve connections > [2018/12/28 15:30:47.445485, 0] > ../source4/smbd/service_task.c:36(task_server_terminate) > task_server_terminate: task_server_terminate: [kdc: krb5_init_context > samdb RODC connect failed] > [2018/12/28 15:30:47.473993, 0] > ../source4/smbd/service_task.c:36(task_server_terminate) > task_server_terminate: task_server_terminate: [dreplsrv: Failed to > connect to local samdb: WERR_DS_UNAVAILABLE > ] > [2018/12/28 15:30:47.504721, 0] > ../source4/smbd/service_task.c:36(task_server_terminate) > task_server_terminate: task_server_terminate: [kccsrv: Failed to connect > to local samdb: WERR_DS_UNAVAILABLE > ] > [2018/12/28 15:30:47.509377, 0] > ../source4/dsdb/dns/dns_update.c:127(dnsupdate_rebuild) > [2018/12/28 15:30:50.030324, 0] > ../source3/winbindd/winbindd_cache.c:3160(initialize_winbindd_cache) > initialize_winbindd_cache: clearing cache and re-creating with version > number 2 > [2018/12/28 15:30:50.123864, 0] > ../source3/passdb/pdb_interface.c:180(make_pdb_method_name) > pdb backend samba_dsdb did not correctly init (error was > NT_STATUS_UNSUCCESSFUL) > [2018/12/28 15:30:50.155000, 0] > ../source3/passdb/pdb_interface.c:180(make_pdb_method_name) > pdb backend samba_dsdb did not correctly init (error was > NT_STATUS_UNSUCCESSFUL) > [2018/12/28 15:30:50.317037, 0] > ../lib/util/become_daemon.c:138(daemon_ready) > daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to > serve connections > [2018/12/28 15:30:50.384582, 0] > ../lib/util/become_daemon.c:138(daemon_ready) > daemon_ready: STATUS=daemon 'winbindd' finished starting up and ready to > serve connections > [2018/12/28 15:30:50.402061, 0] > ../source3/passdb/pdb_interface.c:180(make_pdb_method_name) > pdb backend samba_dsdb did not correctly init (error was > NT_STATUS_UNSUCCESSFUL)Any thoughts? I've found similar issues from a few years ago, e.g. https://bugzilla.samba.org/show_bug.cgi?id=10955 but they don't appear to apply to my case. -- Kv, Kristján Valur Jónsson, RVX
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, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Kristján Valur Jónsson via samba > Verzonden: vrijdag 28 december 2018 16:39 > Aan: Samba List > Onderwerp: [Samba] replication failing for 4.9.4 > > 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, > > 'WERR_NOT_ENOUGH_MEMORY') > > File > "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/drs.py", > > line 47, in drsuapi_connect > > (ctx.drsuapi, ctx.drsuapi_handle, > ctx.bind_supported_extensions) > > drs_utils.drsuapi_connect(ctx.server, ctx.lp, ctx.creds) > > File > "/usr/local/samba/lib/python2.7/site-packages/samba/drs_utils.py", > > line 59, in drsuapi_connect > > > this is on DC02. When I do the same on DC01 (which hasn't > been upgraded), > it reports errors talking to the DC, e.g. > > > DC=DomainDnsZones,DC=rvx,DC=is > > Default-First-Site-Name\DC02 via RPC > > DSA object GUID: > 564fb63e-e2eb-45f9-b868-7d85e71c8dcc > > Last attempt @ Fri Dec 28 14:26:16 2018 UTC > failed, result > > 8 (WERR_NOT_ENOUGH_MEMORY) > > 206 consecutive failure(s). > > Last success @ NTTIME(0) > > > This all worked previously. I don't believe that memory is really the > problem, rather this appears to be a generic error percolating up. > my samba.log shows this: > > > [2018/12/28 15:30:44.911645, 0] > > ../source4/smbd/server.c:510(binary_smbd_main) > > samba version 4.9.4 started. > > Copyright Andrew Tridgell and the Samba Team 1992-2018 > > [2018/12/28 15:30:47.282129, 0] > > ../source4/smbd/server.c:696(binary_smbd_main) > > binary_smbd_main: samba: using 'standard' process model > > [2018/12/28 15:30:47.371819, 0] > > ../source4/dsdb/common/util.c:1815(samdb_reference_dn_is_our_ntdsa) > > Failed to find object DC=rvx,DC=is for attribute > fsmoRoleOwner - Cannot > > find DN DC=rvx,DC=is to get attribute fsmoRoleOwner for > reference dn: No > > such Base DN: DC=rvx,DC=is > > [2018/12/28 15:30:47.403897, 0] > > ../lib/util/become_daemon.c:138(daemon_ready) > > daemon_ready: STATUS=daemon 'samba' finished starting up > and ready to > > serve connections > > [2018/12/28 15:30:47.445485, 0] > > ../source4/smbd/service_task.c:36(task_server_terminate) > > task_server_terminate: task_server_terminate: [kdc: > krb5_init_context > > samdb RODC connect failed] > > [2018/12/28 15:30:47.473993, 0] > > ../source4/smbd/service_task.c:36(task_server_terminate) > > task_server_terminate: task_server_terminate: [dreplsrv: Failed to > > connect to local samdb: WERR_DS_UNAVAILABLE > > ] > > [2018/12/28 15:30:47.504721, 0] > > ../source4/smbd/service_task.c:36(task_server_terminate) > > task_server_terminate: task_server_terminate: [kccsrv: > Failed to connect > > to local samdb: WERR_DS_UNAVAILABLE > > ] > > [2018/12/28 15:30:47.509377, 0] > > ../source4/dsdb/dns/dns_update.c:127(dnsupdate_rebuild) > > [2018/12/28 15:30:50.030324, 0] > > ../source3/winbindd/winbindd_cache.c:3160(initialize_winbindd_cache) > > initialize_winbindd_cache: clearing cache and re-creating > with version > > number 2 > > [2018/12/28 15:30:50.123864, 0] > > ../source3/passdb/pdb_interface.c:180(make_pdb_method_name) > > pdb backend samba_dsdb did not correctly init (error was > > NT_STATUS_UNSUCCESSFUL) > > [2018/12/28 15:30:50.155000, 0] > > ../source3/passdb/pdb_interface.c:180(make_pdb_method_name) > > pdb backend samba_dsdb did not correctly init (error was > > NT_STATUS_UNSUCCESSFUL) > > [2018/12/28 15:30:50.317037, 0] > > ../lib/util/become_daemon.c:138(daemon_ready) > > daemon_ready: STATUS=daemon 'smbd' finished starting up > and ready to > > serve connections > > [2018/12/28 15:30:50.384582, 0] > > ../lib/util/become_daemon.c:138(daemon_ready) > > daemon_ready: STATUS=daemon 'winbindd' finished starting > up and ready to > > serve connections > > [2018/12/28 15:30:50.402061, 0] > > ../source3/passdb/pdb_interface.c:180(make_pdb_method_name) > > pdb backend samba_dsdb did not correctly init (error was > > NT_STATUS_UNSUCCESSFUL) > > > Any thoughts? > I've found similar issues from a few years ago, e.g. > https://bugzilla.samba.org/show_bug.cgi?id=10955 but they > don't appear to > apply to my case. > > > > > > -- > Kv, > Kristján Valur Jónsson, RVX > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
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 'samba.drs_utils.drsException'>): DRS connection to > dc02.rvx.is > > failed - drsException: DRS connection to dc02.rvx.is failed: (8, > > 'WERR_NOT_ENOUGH_MEMORY') > > File > > "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/drs.py", > > line 47, in drsuapi_connect (ctx.drsuapi, ctx.drsuapi_handle, > > ctx.bind_supported_extensions) > > drs_utils.drsuapi_connect(ctx.server, ctx.lp, ctx.creds) File > > "/usr/local/samba/lib/python2.7/site-packages/samba/drs_utils.py", > > line 59, in drsuapi_connect > > > this is on DC02. When I do the same on DC01 (which hasn't been > upgraded), it reports errors talking to the DC, e.g. > > > DC=DomainDnsZones,DC=rvx,DC=is > > Default-First-Site-Name\DC02 via RPC > > DSA object GUID: > > 564fb63e-e2eb-45f9-b868-7d85e71c8dcc Last attempt @ Fri Dec 28 > > 14:26:16 2018 UTC failed, result 8 (WERR_NOT_ENOUGH_MEMORY) > > 206 consecutive failure(s). > > Last success @ NTTIME(0) > > > This all worked previously. I don't believe that memory is really the > problem, rather this appears to be a generic error percolating up. > my samba.log shows this: > > > [2018/12/28 15:30:44.911645, 0] > > ../source4/smbd/server.c:510(binary_smbd_main) > > samba version 4.9.4 started. > > Copyright Andrew Tridgell and the Samba Team 1992-2018 > > [2018/12/28 15:30:47.282129, 0] > > ../source4/smbd/server.c:696(binary_smbd_main) > > binary_smbd_main: samba: using 'standard' process model > > [2018/12/28 15:30:47.371819, 0] > > ../source4/dsdb/common/util.c:1815(samdb_reference_dn_is_our_ntdsa) > > Failed to find object DC=rvx,DC=is for attribute fsmoRoleOwner - > > Cannot find DN DC=rvx,DC=is to get attribute fsmoRoleOwner for > > reference dn: No such Base DN: DC=rvx,DC=is > > [2018/12/28 15:30:47.403897, 0] > > ../lib/util/become_daemon.c:138(daemon_ready) > > daemon_ready: STATUS=daemon 'samba' finished starting up and > > ready to serve connections > > [2018/12/28 15:30:47.445485, 0] > > ../source4/smbd/service_task.c:36(task_server_terminate) > > task_server_terminate: task_server_terminate: [kdc: > > krb5_init_context samdb RODC connect failed]Drat, this is the second time this has happened in a week, upgrade from 4.7.x to 4.9.4 and Samba cannot find the base DN and throws up a line referring to an RODC. This sounds like a bug, but I have no idea where to start. Any ideas Jeremy ? Rowland
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 DC01 as the first remote. This does not appear to be a DNS issue. As per recommendation, I am first upgrading the non-fsmo servers (DC01 has all the FSMO roles). This log line does look suspicous: [2018/12/28 15:30:47.371819, 0] ../source4/dsdb/common/util.c:1815(samdb_reference_dn_is_our_ntdsa) Failed to find object DC=rvx,DC=is for attribute fsmoRoleOwner - Cannot find DN DC=rvx,DC=is to get attribute fsmoRoleOwner for reference dn: No such Base DN: DC=rvx,DC=is None of the config has been changed. On Fri, 28 Dec 2018 at 15:50, L.P.H. van Belle <belle at bazuin.nl> wrote: 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, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Kristján Valur Jónsson via samba > Verzonden: vrijdag 28 december 2018 16:39 > Aan: Samba List > Onderwerp: [Samba] replication failing for 4.9.4 > > 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, > > 'WERR_NOT_ENOUGH_MEMORY') > > File > "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/drs.py", > > line 47, in drsuapi_connect > > (ctx.drsuapi, ctx.drsuapi_handle, > ctx.bind_supported_extensions) > > drs_utils.drsuapi_connect(ctx.server, ctx.lp, ctx.creds) > > File > "/usr/local/samba/lib/python2.7/site-packages/samba/drs_utils.py", > > line 59, in drsuapi_connect > > > this is on DC02. When I do the same on DC01 (which hasn't > been upgraded), > it reports errors talking to the DC, e.g. > > > DC=DomainDnsZones,DC=rvx,DC=is > > Default-First-Site-Name\DC02 via RPC > > DSA object GUID: > 564fb63e-e2eb-45f9-b868-7d85e71c8dcc > > Last attempt @ Fri Dec 28 14:26:16 2018 UTC > failed, result > > 8 (WERR_NOT_ENOUGH_MEMORY) > > 206 consecutive failure(s). > > Last success @ NTTIME(0) > > > This all worked previously. I don't believe that memory is really the > problem, rather this appears to be a generic error percolating up. > my samba.log shows this: > > > [2018/12/28 15:30:44.911645, 0] > > ../source4/smbd/server.c:510(binary_smbd_main) > > samba version 4.9.4 started. > > Copyright Andrew Tridgell and the Samba Team 1992-2018 > > [2018/12/28 15:30:47.282129, 0] > > ../source4/smbd/server.c:696(binary_smbd_main) > > binary_smbd_main: samba: using 'standard' process model > > [2018/12/28 15:30:47.371819, 0] > > ../source4/dsdb/common/util.c:1815(samdb_reference_dn_is_our_ntdsa) > > Failed to find object DC=rvx,DC=is for attribute > fsmoRoleOwner - Cannot > > find DN DC=rvx,DC=is to get attribute fsmoRoleOwner for > reference dn: No > > such Base DN: DC=rvx,DC=is > > [2018/12/28 15:30:47.403897, 0] > > ../lib/util/become_daemon.c:138(daemon_ready) > > daemon_ready: STATUS=daemon 'samba' finished starting up > and ready to > > serve connections > > [2018/12/28 15:30:47.445485, 0] > > ../source4/smbd/service_task.c:36(task_server_terminate) > > task_server_terminate: task_server_terminate: [kdc: > krb5_init_context > > samdb RODC connect failed] > > [2018/12/28 15:30:47.473993, 0] > > ../source4/smbd/service_task.c:36(task_server_terminate) > > task_server_terminate: task_server_terminate: [dreplsrv: Failed to > > connect to local samdb: WERR_DS_UNAVAILABLE > > ] > > [2018/12/28 15:30:47.504721, 0] > > ../source4/smbd/service_task.c:36(task_server_terminate) > > task_server_terminate: task_server_terminate: [kccsrv: > Failed to connect > > to local samdb: WERR_DS_UNAVAILABLE > > ] > > [2018/12/28 15:30:47.509377, 0] > > ../source4/dsdb/dns/dns_update.c:127(dnsupdate_rebuild) > > [2018/12/28 15:30:50.030324, 0] > > ../source3/winbindd/winbindd_cache.c:3160(initialize_winbindd_cache) > > initialize_winbindd_cache: clearing cache and re-creating > with version > > number 2 > > [2018/12/28 15:30:50.123864, 0] > > ../source3/passdb/pdb_interface.c:180(make_pdb_method_name) > > pdb backend samba_dsdb did not correctly init (error was > > NT_STATUS_UNSUCCESSFUL) > > [2018/12/28 15:30:50.155000, 0] > > ../source3/passdb/pdb_interface.c:180(make_pdb_method_name) > > pdb backend samba_dsdb did not correctly init (error was > > NT_STATUS_UNSUCCESSFUL) > > [2018/12/28 15:30:50.317037, 0] > > ../lib/util/become_daemon.c:138(daemon_ready) > > daemon_ready: STATUS=daemon 'smbd' finished starting up > and ready to > > serve connections > > [2018/12/28 15:30:50.384582, 0] > > ../lib/util/become_daemon.c:138(daemon_ready) > > daemon_ready: STATUS=daemon 'winbindd' finished starting > up and ready to > > serve connections > > [2018/12/28 15:30:50.402061, 0] > > ../source3/passdb/pdb_interface.c:180(make_pdb_method_name) > > pdb backend samba_dsdb did not correctly init (error was > > NT_STATUS_UNSUCCESSFUL) > > > Any thoughts? > I've found similar issues from a few years ago, e.g. > https://bugzilla.samba.org/show_bug.cgi?id=10955 but they > don't appear to > apply to my case. > > > > > > -- > Kv, > Kristján Valur Jónsson, RVX > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >-- Kv, Kristján Valur Jónsson, RVX
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> wrote:> 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 'samba.drs_utils.drsException'>): DRS connection to > > dc02.rvx.is > > > failed - drsException: DRS connection to dc02.rvx.is failed: (8, > > > 'WERR_NOT_ENOUGH_MEMORY') > > > File > > > "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/drs.py", > > > line 47, in drsuapi_connect (ctx.drsuapi, ctx.drsuapi_handle, > > > ctx.bind_supported_extensions) > > > drs_utils.drsuapi_connect(ctx.server, ctx.lp, ctx.creds) File > > > "/usr/local/samba/lib/python2.7/site-packages/samba/drs_utils.py", > > > line 59, in drsuapi_connect > > > > > > this is on DC02. When I do the same on DC01 (which hasn't been > > upgraded), it reports errors talking to the DC, e.g. > > > > > DC=DomainDnsZones,DC=rvx,DC=is > > > Default-First-Site-Name\DC02 via RPC > > > DSA object GUID: > > > 564fb63e-e2eb-45f9-b868-7d85e71c8dcc Last attempt @ Fri Dec 28 > > > 14:26:16 2018 UTC failed, result 8 (WERR_NOT_ENOUGH_MEMORY) > > > 206 consecutive failure(s). > > > Last success @ NTTIME(0) > > > > > > This all worked previously. I don't believe that memory is really the > > problem, rather this appears to be a generic error percolating up. > > my samba.log shows this: > > > > > [2018/12/28 15:30:44.911645, 0] > > > ../source4/smbd/server.c:510(binary_smbd_main) > > > samba version 4.9.4 started. > > > Copyright Andrew Tridgell and the Samba Team 1992-2018 > > > [2018/12/28 15:30:47.282129, 0] > > > ../source4/smbd/server.c:696(binary_smbd_main) > > > binary_smbd_main: samba: using 'standard' process model > > > [2018/12/28 15:30:47.371819, 0] > > > ../source4/dsdb/common/util.c:1815(samdb_reference_dn_is_our_ntdsa) > > > Failed to find object DC=rvx,DC=is for attribute fsmoRoleOwner - > > > Cannot find DN DC=rvx,DC=is to get attribute fsmoRoleOwner for > > > reference dn: No such Base DN: DC=rvx,DC=is > > > [2018/12/28 15:30:47.403897, 0] > > > ../lib/util/become_daemon.c:138(daemon_ready) > > > daemon_ready: STATUS=daemon 'samba' finished starting up and > > > ready to serve connections > > > [2018/12/28 15:30:47.445485, 0] > > > ../source4/smbd/service_task.c:36(task_server_terminate) > > > task_server_terminate: task_server_terminate: [kdc: > > > krb5_init_context samdb RODC connect failed] > > > Drat, this is the second time this has happened in a week, upgrade from > 4.7.x to 4.9.4 and Samba cannot find the base DN and throws up a line > referring to an RODC. > > This sounds like a bug, but I have no idea where to start. > > Any ideas Jeremy ? > > Rowland > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba-- Kv, Kristján Valur Jónsson, RVX
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> wrote: > > > 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 'samba.drs_utils.drsException'>): DRS connection to > > > dc02.rvx.is > > > > failed - drsException: DRS connection to dc02.rvx.is failed: (8, > > > > 'WERR_NOT_ENOUGH_MEMORY') > > > > File > > > > "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/drs.py", > > > > line 47, in drsuapi_connect (ctx.drsuapi, ctx.drsuapi_handle, > > > > ctx.bind_supported_extensions) > > > > drs_utils.drsuapi_connect(ctx.server, ctx.lp, ctx.creds) File > > > > "/usr/local/samba/lib/python2.7/site-packages/samba/drs_utils.py", > > > > line 59, in drsuapi_connect > > > > > > > > > this is on DC02. When I do the same on DC01 (which hasn't been > > > upgraded), it reports errors talking to the DC, e.g. > > > > > > > DC=DomainDnsZones,DC=rvx,DC=is > > > > Default-First-Site-Name\DC02 via RPC > > > > DSA object GUID: > > > > 564fb63e-e2eb-45f9-b868-7d85e71c8dcc Last attempt @ Fri Dec 28 > > > > 14:26:16 2018 UTC failed, result 8 (WERR_NOT_ENOUGH_MEMORY) > > > > 206 consecutive failure(s). > > > > Last success @ NTTIME(0) > > > > > > > > > This all worked previously. I don't believe that memory is > > > really the problem, rather this appears to be a generic error > > > percolating up. my samba.log shows this: > > > > > > > [2018/12/28 15:30:44.911645, 0] > > > > ../source4/smbd/server.c:510(binary_smbd_main) > > > > samba version 4.9.4 started. > > > > Copyright Andrew Tridgell and the Samba Team 1992-2018 > > > > [2018/12/28 15:30:47.282129, 0] > > > > ../source4/smbd/server.c:696(binary_smbd_main) > > > > binary_smbd_main: samba: using 'standard' process model > > > > [2018/12/28 15:30:47.371819, 0] > > > > ../source4/dsdb/common/util.c:1815(samdb_reference_dn_is_our_ntdsa) > > > > Failed to find object DC=rvx,DC=is for attribute > > > > fsmoRoleOwner - Cannot find DN DC=rvx,DC=is to get attribute > > > > fsmoRoleOwner for reference dn: No such Base DN: DC=rvx,DC=is > > > > [2018/12/28 15:30:47.403897, 0] > > > > ../lib/util/become_daemon.c:138(daemon_ready) > > > > daemon_ready: STATUS=daemon 'samba' finished starting up and > > > > ready to serve connections > > > > [2018/12/28 15:30:47.445485, 0] > > > > ../source4/smbd/service_task.c:36(task_server_terminate) > > > > task_server_terminate: task_server_terminate: [kdc: > > > > krb5_init_context samdb RODC connect failed] > > > > > > Drat, this is the second time this has happened in a week, upgrade > > from 4.7.x to 4.9.4 and Samba cannot find the base DN and throws up > > a line referring to an RODC. > > > > This sounds like a bug, but I have no idea where to start. > > > > Any ideas Jeremy ? > > > > RowlandDowngrade again if possible, there appears to be a problem with upgrading from 4.7.x to 4.9.x Rowland
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 experiments in mind... > > > > On Fri, 28 Dec 2018 at 16:07, Rowland Penny via samba > > <samba at lists.samba.org> wrote: > > > > > 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 'samba.drs_utils.drsException'>): DRS connection to > > > > dc02.rvx.is > > > > > failed - drsException: DRS connection to dc02.rvx.is failed: > > > > > (8, 'WERR_NOT_ENOUGH_MEMORY') > > > > > File > > > > > "/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/drs.py", > > > > > line 47, in drsuapi_connect (ctx.drsuapi, ctx.drsuapi_handle, > > > > > ctx.bind_supported_extensions) > > > > > drs_utils.drsuapi_connect(ctx.server, ctx.lp, ctx.creds) File > > > > > "/usr/local/samba/lib/python2.7/site-packages/samba/drs_utils.py", > > > > > line 59, in drsuapi_connect > > > > > > > > > > > > this is on DC02. When I do the same on DC01 (which hasn't been > > > > upgraded), it reports errors talking to the DC, e.g. > > > > > > > > > DC=DomainDnsZones,DC=rvx,DC=is > > > > > Default-First-Site-Name\DC02 via RPC > > > > > DSA object GUID: > > > > > 564fb63e-e2eb-45f9-b868-7d85e71c8dcc Last attempt @ Fri Dec 28 > > > > > 14:26:16 2018 UTC failed, result 8 (WERR_NOT_ENOUGH_MEMORY) > > > > > 206 consecutive failure(s). > > > > > Last success @ NTTIME(0) > > > > > > > > > > > > This all worked previously. I don't believe that memory is > > > > really the problem, rather this appears to be a generic error > > > > percolating up. my samba.log shows this: > > > > > > > > > [2018/12/28 15:30:44.911645, 0] > > > > > ../source4/smbd/server.c:510(binary_smbd_main) > > > > > samba version 4.9.4 started. > > > > > Copyright Andrew Tridgell and the Samba Team 1992-2018 > > > > > [2018/12/28 15:30:47.282129, 0] > > > > > ../source4/smbd/server.c:696(binary_smbd_main) > > > > > binary_smbd_main: samba: using 'standard' process model > > > > > [2018/12/28 15:30:47.371819, 0] > > > > > ../source4/dsdb/common/util.c:1815(samdb_reference_dn_is_our_ntdsa) > > > > > Failed to find object DC=rvx,DC=is for attribute > > > > > fsmoRoleOwner - Cannot find DN DC=rvx,DC=is to get attribute > > > > > fsmoRoleOwner for reference dn: No such Base DN: DC=rvx,DC=is > > > > > [2018/12/28 15:30:47.403897, 0] > > > > > ../lib/util/become_daemon.c:138(daemon_ready) > > > > > daemon_ready: STATUS=daemon 'samba' finished starting up and > > > > > ready to serve connections > > > > > [2018/12/28 15:30:47.445485, 0] > > > > > ../source4/smbd/service_task.c:36(task_server_terminate) > > > > > task_server_terminate: task_server_terminate: [kdc: > > > > > krb5_init_context samdb RODC connect failed] > > > > > > > > > Drat, this is the second time this has happened in a week, upgrade > > > from 4.7.x to 4.9.4 and Samba cannot find the base DN and throws > > > up a line referring to an RODC. > > > > > > This sounds like a bug, but I have no idea where to start. > > > > > > Any ideas Jeremy ? > > > > > > Rowland > > Downgrade again if possible, there appears to be a problem with > upgrading from 4.7.x to 4.9.x > > Rowland > >No, it doesn't 'appear to be a problem', it is definitely a problem, you cannot upgrade from 4.7.x to 4.9.4 using packages. I would raise a bug report, but I don't know what to point the finger at :-( Rowland