search for: 32129

Displaying 7 results from an estimated 7 matches for "32129".

Did you mean: 3129
2018 Feb 08
2
Bad DSA objectGUID ed8970e5-84cc-43dd-89f1-4af8d6ab675a for sid S-1-5-21-570971082-1333357699-3675202899-1375
...ile in DC1 without any backup. Now , I saw the errors in DC1: Feb 08 22:06:04 dc1.adagene.cn samba[32137]: UpdateRefs failed with WERR_DS_DRA_ACCESS_DENIED/NT code 0xc0002105 for ed8970e5-84cc-43dd-89f1-4af8d6ab675a._msdcs.adagene.cn DC=adagene,DC=cn Feb 08 22:06:04 dc1.adagene.cn samba[32129]: [2018/02/08 22:06:04.078274, 0] ../source4/dsdb/common/util.c:4825(dsdb_validate_dsa_guid) Feb 08 22:06:04 dc1.adagene.cn samba[32129]: ../source4/dsdb/common/util.c:4825: Bad DSA objectGUID ed8970e5-84cc-43dd-89f1-4af8d6ab675a for sid S-1-5-21-570971082-1333357699-3675202899-1375 - expected s...
2018 Feb 08
0
Bad DSA objectGUID ed8970e5-84cc-43dd-89f1-4af8d6ab675a for sid S-1-5-21-570971082-1333357699-3675202899-1375
...any backup. > Now , I saw the errors in DC1: > > Feb 08 22:06:04 dc1.adagene.cn samba[32137]: UpdateRefs failed with WERR_DS_DRA_ACCESS_DENIED/NT code 0xc0002105 for ed8970e5-84cc-43dd-89f1-4af8d6ab675a._msdcs.adagene.cn DC=adagene,DC=cn > Feb 08 22:06:04 dc1.adagene.cn samba[32129]: [2018/02/08 22:06:04.078274, 0] ../source4/dsdb/common/util.c:4825(dsdb_validate_dsa_guid) > Feb 08 22:06:04 dc1.adagene.cn samba[32129]: ../source4/dsdb/common/util.c:4825: Bad DSA objectGUID ed8970e5-84cc-43dd-89f1-4af8d6ab675a for sid S-1-5-21-570971082-1333357699-3675202899-1375 - expec...
2018 Feb 09
1
Bad DSA objectGUID ed8970e5-84cc-43dd-89f1-4af8d6ab675a for sid S-1-5-21-570971082-1333357699-3675202899-1375
...any backup. > Now , I saw the errors in DC1: > > Feb 08 22:06:04 dc1.adagene.cn samba[32137]: UpdateRefs failed with WERR_DS_DRA_ACCESS_DENIED/NT code 0xc0002105 for ed8970e5-84cc-43dd-89f1-4af8d6ab675a._msdcs.adagene.cn DC=adagene,DC=cn > Feb 08 22:06:04 dc1.adagene.cn samba[32129]: [2018/02/08 22:06:04.078274, 0] ../source4/dsdb/common/util.c:4825(dsdb_validate_dsa_guid) > Feb 08 22:06:04 dc1.adagene.cn samba[32129]: ../source4/dsdb/common/util.c:4825: Bad DSA objectGUID ed8970e5-84cc-43dd-89f1-4af8d6ab675a for sid S-1-5-21-570971082-1333357699-3675202899-1375 - expec...
2006 Feb 16
1
CentOS FAQ (was ssh attack)
On 16/02/06, Craig White <craigwhite at azapple.com> wrote: > On Thu, 2006-02-16 at 15:18 -0500, John Hinton wrote: > > As someone did suggest though, a FAQ on SSH would be a > > good idea. > ---- > I think it's a great idea - go ahead and do it...why wait for others? I suggested it, and not just for common SSH on CentOS questions but for anything that's, well,
2004 Nov 20
1
Asterisk dead but pid file exists - gdb asterisk core.13089
...ranslator_build_path (dest=64, source=1) at translate.c:110 #4 0x08061008 in ast_set_read_format (chan=0xbf2108a0, fmts=-1088314640) at channel.c:1738 #5 0x02b3b5f0 in socket_read (id=0x8805cb8, fd=17, events=1, cbdata=0x0) at chan_iax2.c:5310 #6 0x080523c0 in ast_io_wait (ioc=0x8804588, howlong=32129) at io.c:267 #7 0x02b3210e in network_thread (ignore=0x0) at chan_iax2.c:6322 #8 0x002eddb2 in pthread_start_thread () from /lib/i686/libpthread.so.0 #9 0x0024635a in clone () from /lib/i686/libc.so.6 (gdb) bt full #0 0x001d8a55 in _int_malloc () from /lib/i686/libc.so.6 No symbol table info av...
2014 Jan 21
2
After USB boot problems on Gigabyte GA-M55Plus-S3G
...th: CHS: 0 / 0 / 63 = LBA 62 64th: CHS: 0 / 1 / 1 = LBA 63 65th: CHS: 0 / 1 / 2 = LBA 64 126th: CHS: 0 / 1 / 63 = LBA 125 127th: CHS: 0 / 2 / 1 = LBA 126 189th: CHS: 0 / 2 / 63= LBA 188 16065th: CHS: 0 / 254 / 63= LBA 16064 16066th: CHS: 1 / 0 / 1= LBA 16065 32130th: CHS: 1 / 254 / 63= LBA 32129 32131th: CHS: 2 / 0 / 1= LBA 32130 ... First, if we were talking about values higher than the CHS limit of 1024*255*63 ( 1023 / 254 / 63 ), then every LBA value higher than that one is translated to that max. limit. But in this case we are under that max. limit. For a CHS of " 982 / 254...
2014 Jan 21
3
After USB boot problems on Gigabyte GA-M55Plus-S3G
As I said before, booting is bigger than one bootloader. I am replying to what I think was asked. I might have misunderstood the questions. Whichever the case, this email is less about Syslinux itself. If this is considered too far off-topic in the Syslinux Mailing List, please receive my apologies. > > I still have the factory-set contents of my three USB sticks. A small