Displaying 5 results from an estimated 5 matches for "b1d1".
Did you mean:
11d1
2017 Jun 29
2
sieve/vacation: bad parsing of 'References' header
...01112EB28C7BECB5A5EF14C5DEE10 at YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
?<734f9013-c4a2-eab4-9c0d-2cfc3deafaee at email.com>
?<YTXPR01MB0111660D7D5A73451F3E5B66DEE00 at YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
?<9e3e3c00-a0d8-c061-7c7e-20e660533264 at email.com>
?<e702bae4-b1d1-6671-fa74-87349282ce46 at email.com>
?<YTXPR01MB01119930E4D876F91008D465DE3A0 at YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
?<69c6be47-b17f-9f9a-5a0c-f389c6877f82 at email.com>
?<YTXPR01MB01116BC86CBA49677A29C607DE3A0 at YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
?<YTXPR01MB0111...
2017 Jun 29
0
sieve/vacation: bad parsing of 'References' header
...DEE10 at YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
> <734f9013-c4a2-eab4-9c0d-2cfc3deafaee at email.com>
> <YTXPR01MB0111660D7D5A73451F3E5B66DEE00 at YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
> <9e3e3c00-a0d8-c061-7c7e-20e660533264 at email.com>
> <e702bae4-b1d1-6671-fa74-87349282ce46 at email.com>
> <YTXPR01MB01119930E4D876F91008D465DE3A0 at YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
> <69c6be47-b17f-9f9a-5a0c-f389c6877f82 at email.com>
> <YTXPR01MB01116BC86CBA49677A29C607DE3A0 at YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>...
2017 Jun 29
3
Re: sieve/vacation: bad parsing of 'References' header
...A5EF14C5DEE10 at YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
> <734f9013-c4a2-eab4-9c0d-2cfc3deafaee at email.com>
> <YTXPR01MB0111660D7D5A73451F3E5B66DEE00 at YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
> <9e3e3c00-a0d8-c061-7c7e-20e660533264 at email.com>
> <e702bae4-b1d1-6671-fa74-87349282ce46 at email.com>
> <YTXPR01MB01119930E4D876F91008D465DE3A0 at YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
> <69c6be47-b17f-9f9a-5a0c-f389c6877f82 at email.com>
> <YTXPR01MB01116BC86CBA49677A29C607DE3A0 at YTXPR01MB0111.CANPRD01.PROD.OUTLOOK.COM>
> &...
2019 May 16
0
Error smb_panic(): calling panic action [/bin/sleep 999999999]
...tter for your problem.
>
>
> SAMBA-TOOL drs showrepl on affected Host /slave)
>
> [root at s4slave ~]# samba-tool drs showrepl
> Default-First-Site-Name\S4SLAVE
> DSA Options: 0x00000001
> DSA object GUID: cce36cb1-5fcd-46f2-a49c-f0d51b72e08b
> DSA invocationId: 47c91612-b1d1-4aa5-ae70-9eb32fb5b6a9
>
Everything looks okay there.
Rowland
2019 May 16
3
Error smb_panic(): calling panic action [/bin/sleep 999999999]
No I can not upgrade now it is a working system with x users.
The master dc with the same config is working without any issues.
So when I upgrade I must do the uprgade on both replicating samba server and the samba fileservers?
No hint form e to repair:
May 16 14:00:12 s4slave smbd[7141]: [2019/05/16 14:00:12.438121, 0] ../source3/lib/util.c:801(smb_panic_s3)
May 16 14:00:12 s4slave smbd[7141]: