search for: a4d9

...ns: 0x00000001 DSA object GUID: b19509be-c3ee-4a58-9fc9-afd61759a23f DSA invocationId: 4f30d79d-2e9c-4235-88a1-c258b8622d23 ==== INBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=ad,DC=microsult,DC=de Default-First-Site-Name\VERDANDI via RPC DSA object GUID: a03bbb51-1dca-44ae-a4d9-7aa8cb4a1ace Last attempt @ Mon May 18 20:33:36 2015 CEST was successful 0 consecutive failure(s). Last success @ Mon May 18 20:33:36 2015 CEST [...] ==== OUTBOUND NEIGHBORS ==== DC=DomainDnsZones,DC=ad,DC=microsult,DC=de Default-First-S...

...> title CentOS (4.9.16-24.el6.centos.plus.x86_64) > root (hd0,1) > kernel /boot/xen.gz dom0_mem=3G,max:3G cpuinfo com1=115200,8n1 > console=com1,tty loglvl=all gue > st_loglvl=all noreboot > module /boot/vmlinuz-4.9.16-24.el6.centos.plus.x86_64 ro > root=UUID=bc0727e1-882c-4fbc-a4d9-e4c > f754d72b7 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD > SYSFONT=latarcyrheb-sun16 crashkernel=auto K > EYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet reboot=pci max_loop=64 > module /boot/initramfs-4.9.16-24.el6.centos.plus.x86_64.img Try removing "rhgb" and "q...

El Lunes 20/03/2017, PJ Welsh escribi?: > Still just starts the kernel and wihtin 4 seconds reboots with 4.9.16-24. > Thanks > PJ Edit grub's entry and add "noreboot" to your xen parameters, maybe when the kernel panicks xen detects it and automatically reboots it. > On Mon, Mar 20, 2017 at 2:23 PM, Johnny Hughes <johnny at centos.org> wrote: > > On

Hi Marc, >> The cause is that the password change didn' reach both AD DCs, but only >> one. The other one still had the old value as could be seen by >> samba-tool ldapcmp. Restarting the DCs and waiting for a couple of >> seconds brings them back to sync and Windows logons work as they used to. >> Any idea, what I should do next time to obtain valuable output

...e grub.conf stanza for the kernel: title CentOS (4.9.16-24.el6.centos.plus.x86_64) root (hd0,1) kernel /boot/xen.gz dom0_mem=3G,max:3G cpuinfo com1=115200,8n1 console=com1,tty loglvl=all gue st_loglvl=all noreboot module /boot/vmlinuz-4.9.16-24.el6.centos.plus.x86_64 ro root=UUID=bc0727e1-882c-4fbc-a4d9-e4c f754d72b7 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto K EYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet reboot=pci max_loop=64 module /boot/initramfs-4.9.16-24.el6.centos.plus.x86_64.img Thanks PJ ... -------------- next part -------------- An HTML...

...l6.centos.plus.x86_64) > > root (hd0,1) > > kernel /boot/xen.gz dom0_mem=3G,max:3G cpuinfo com1=115200,8n1 > > console=com1,tty loglvl=all gue > > st_loglvl=all noreboot > > module /boot/vmlinuz-4.9.16-24.el6.centos.plus.x86_64 ro > > root=UUID=bc0727e1-882c-4fbc-a4d9-e4c > > f754d72b7 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD > > SYSFONT=latarcyrheb-sun16 crashkernel=auto K > > EYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet reboot=pci max_loop=64 > > module /boot/initramfs-4.9.16-24.el6.centos.plus.x86_64.img > > Try removing...

...ook some time to figure out what happened. On my primary DC (SAMBA) I did not notice anything extraordinary. However, my secondary (VERDANDI) reported issues: root at verdandi:~# samba-tool drs showrepl Default-First-Site-Name\VERDANDI DSA Options: 0x00000001 DSA object GUID: a03bbb51-1dca-44ae-a4d9-7aa8cb4a1ace DSA invocationId: 8bdb4f85-1da2-4f5a-b9a9-e8369d202745 ==== INBOUND NEIGHBORS ==== CN=Schema,CN=Configuration,DC=ad,DC=microsult,DC=de Default-First-Site-Name\SAMBA via RPC DSA object GUID: b19509be-c3ee-4a58-9fc9-afd61759a23f Last attempt @...

...l6.centos.plus.x86_64) > > root (hd0,1) > > kernel /boot/xen.gz dom0_mem=3G,max:3G cpuinfo com1=115200,8n1 > > console=com1,tty loglvl=all gue > > st_loglvl=all noreboot > > module /boot/vmlinuz-4.9.16-24.el6.centos.plus.x86_64 ro > > root=UUID=bc0727e1-882c-4fbc-a4d9-e4c > > f754d72b7 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD > > SYSFONT=latarcyrheb-sun16 crashkernel=auto K > > EYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet reboot=pci max_loop=64 > > module /boot/initramfs-4.9.16-24.el6.centos.plus.x86_64.img > > Try removing...