Results 1 to 8 of 8

Thread: unknow message in my zimbra server

  1. #1
    tecno_tiago is offline Beginner Member
    Join Date
    Mar 2011
    Posts
    1
    Rep Power
    4

    Default unknow message in my zimbra server

    Hello staff,

    My zimbra server is presenting a strange message that I tried I could not find out more.
    I do not know what it is they know of the message, can anyone help me message is:

    Mar 2 08:30:45 zimbra saslauthd [12044]: zmauth: authenticating Against elected url 'https: / / xxxx.xxxx.com.br: 7071/service/admin/soap /' ...
    Mar 2 08:30:46 zimbra saslauthd [12044]: zmpost: url = 'https: / / xxxx.xxxx.com.br: 7071/service/admin/soap /' returned buffer-> data = '<soap: Envelope xmlns: soap = "http://www.w3.org/2003/05/soap-envelope"> <soap:Header> <Context xmlns="urn:zimbra"> <change token="34552"/> </ context> </ soap: Header> <soap:Body> <AuthResponse xmlns="urn:zimbraAccount"> <authToken> 0_413d3eb248523e14cffc2e08de79670792c86c7f_69643d3 3363a37363163646566632d393166372d343835342d6135633 52d3732633361393738333139663b6578703d31333a3132393 93233383234363030313b747970653d363a7a696d6272613b </ authToken> <lifetime> 172800000 </ lifetime> <skin> beach </ skin> </ AuthResponse > </ soap: Body> </ soap: Envelope> ', hti-> error =''

    i wait for help of ours, and sorry for my english.

    tank´s so muth

    tiago muniz.

  2. #2
    datakid is offline Junior Member
    Join Date
    Sep 2010
    Posts
    7
    Rep Power
    4

    Default

    I have also come across this error for the first time recently and would appreciate some clarification as to what it means?

    The system events I saw in my log had extra info:

    Code:
    Feb 27 16:17:48 sbls saslauthd[14072]: zmauth: authenticating against elected url 'https://mail.XXXX.com:7071/service/admin/soap/' ...
    Feb 27 16:17:49 mail saslauthd[14072]: zmauth: authenticating against elected url 'https://mail.XXXX.com:7071/service/admin/soap/' ...
    Feb 27 16:17:49 sbls saslauthd[14072]: zmpost: url='https://mail.XXXX.com:7071/service/admin/soap/' returned buffer->data='<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><context xmlns="urn:zimbra"><change token="309552"/></context></soap:Header><soap:Body><AuthResponse xmlns="urn:zimbraAccount"><authToken>0_089d3bea4fe359d94d54ab01a1c9a5bc7f0888a7_69643d33363a63663139323431622d343436642d346633302d393565342d3266353432616366333362613b6578703d31333a313239383935363636393236333b747970653d363a7a696d6272613b</authToken><lifetime>172800000</lifetime><skin>beach</skin></AuthResponse></soap:Body></soap:Envelope>', hti->error=''
    Feb 27 16:17:49 sbls saslauthd[14072]: auth_zimbra: user_name at XXXX.com auth OK
    Feb 27 16:17:49 mail saslauthd[14072]: zmpost: url='https://mail.XXXX.com:7071/service/admin/soap/' returned buffer->data='<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><context xmlns="urn:zimbra"><change token="309552"/></context></soap:Header><soap:Body><AuthResponse xmlns="urn:zimbraAccount"><authToken>0_089d3bea4fe359d94d54ab01a1c9a5bc7f0888a7_69643d33363a63663139323431622d343436642d346633302d393565342d3266353432616366333362613b6578703d31333a313239383935363636393236333b747970653d363a7a696d6272613b</authToken><lifetime>172800000</lifetime><skin>beach</skin></AuthResponse></soap:Body></soap:Envelope>', hti->error=''
    Feb 27 16:17:49 mail saslauthd[14072]: auth_zimbra: user_name at XXXX.com auth OK
    Feb 27 16:50:27 sbls saslauthd[14073]: zmauth: authenticating against elected url 'https://mail.XXXX.com:7071/service/admin/soap/' ...
    Feb 27 16:50:27 sbls saslauthd[14073]: zmpost: url='https://mail.XXXX.com:7071/service/admin/soap/' returned buffer->data='<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><context xmlns="urn:zimbra"><change token="309554"/></context></soap:Header><soap:Body><AuthResponse xmlns="urn:zimbraAccount"><authToken>0_98745bd2b810e7412eeb1de5892184dce0d79820_69643d33363a63663139323431622d343436642d346633302d393565342d3266353432616366333362613b6578703d31333a313239383935383632373630383b747970653d363a7a696d6272613b</authToken><lifetime>172800000</lifetime><skin>beach</skin></AuthResponse></soap:Body></soap:Envelope>', hti->error=''
    Feb 27 16:50:27 mail saslauthd[14073]: zmauth: authenticating against elected url 'https://mail.XXXX.com:7071/service/admin/soap/' ...
    Feb 27 16:50:27 sbls saslauthd[14073]: auth_zimbra: user_name at XXXX.com auth OK
    Feb 27 16:50:27 mail saslauthd[14073]: zmpost: url='https://mail.XXXX.com:7071/service/admin/soap/' returned buffer->data='<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><context xmlns="urn:zimbra"><change token="309554"/></context></soap:Header><soap:Body><AuthResponse xmlns="urn:zimbraAccount"><authToken>0_98745bd2b810e7412eeb1de5892184dce0d79820_69643d33363a63663139323431622d343436642d346633302d393565342d3266353432616366333362613b6578703d31333a313239383935383632373630383b747970653d363a7a696d6272613b</authToken><lifetime>172800000</lifetime><skin>beach</skin></AuthResponse></soap:Body></soap:Envelope>', hti->error=''
    Feb 27 16:50:27 mail saslauthd[14073]: auth_zimbra: user_name at XXXX.com auth OK
    Feb 27 16:58:01 sbls saslauthd[14074]: zmauth: authenticating against elected url 'https://mail.XXXX.com:7071/service/admin/soap/' ...
    Feb 27 16:58:01 sbls saslauthd[14074]: zmpost: url='https://mail.XXXX.com:7071/service/admin/soap/' returned buffer->data='<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><context xmlns="urn:zimbra"><change token="309554"/></context></soap:Header><soap:Body><AuthResponse xmlns="urn:zimbraAccount"><authToken>0_6280d223fe7084349900fce68ec38fe56bb5e716_69643d33363a63663139323431622d343436642d346633302d393565342d3266353432616366333362613b6578703d31333a313239383935393038313835363b747970653d363a7a696d6272613b</authToken><lifetime>172800000</lifetime><skin>beach</skin></AuthResponse></soap:Body></soap:Envelope>', hti->error=''
    Feb 27 16:58:01 mail saslauthd[14074]: zmauth: authenticating against elected url 'https://mail.XXXX.com:7071/service/admin/soap/' ...
    Feb 27 16:58:02 sbls saslauthd[14074]: auth_zimbra: user_name at XXXX.com auth OK
    Feb 27 16:58:02 mail saslauthd[14074]: zmpost: url='https://mail.XXXX.com:7071/service/admin/soap/' returned buffer->data='<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><context xmlns="urn:zimbra"><change token="309554"/></context></soap:Header><soap:Body><AuthResponse xmlns="urn:zimbraAccount"><authToken>0_6280d223fe7084349900fce68ec38fe56bb5e716_69643d33363a63663139323431622d343436642d346633302d393565342d3266353432616366333362613b6578703d31333a313239383935393038313835363b747970653d363a7a696d6272613b</authToken><lifetime>172800000</lifetime><skin>beach</skin></AuthResponse></soap:Body></soap:Envelope>', hti->error=''
    Feb 27 16:58:02 mail saslauthd[14074]: auth_zimbra: user_name at XXXX.com auth OK

  3. #3
    datakid is offline Junior Member
    Join Date
    Sep 2010
    Posts
    7
    Rep Power
    4

    Default um, bumpity?

    bump. I find it hard to believe that not one single person even knows what this error msg means. I can understand that google can't find it - but aren't there zimbra employed ppl in this forum somewhere?

  4. #4
    John Siu is offline Loyal Member
    Join Date
    Feb 2011
    Posts
    82
    Rep Power
    4

    Default

    Quote Originally Posted by tecno_tiago View Post
    ...
    <soap: Envelope xmlns: soap = "http://www.w3.org/2003/05/soap-envelope"> <soap:Header> <Context xmlns="urn:zimbra"> <change token="34552"/> </ context> </ soap: Header> <soap:Body> <AuthResponse xmlns="urn:zimbraAccount"> <authToken> 0_413d3eb248523e14cffc2e08de79670792c86c7f_69643d3 3363a37363163646566632d393166372d343835342d6135633 52d3732633361393738333139663b6578703d31333a3132393 93233383234363030313b747970653d363a7a696d6272613b </ authToken> <lifetime> 172800000 </ lifetime> <skin> beach </ skin> </ AuthResponse > </ soap: Body> </ soap: Envelope>
    Code:
    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
        <soap:Header>
            <Context xmlns="urn:zimbra">
                <change token="34552" />
            </Context>
        </soap:Header>
        <soap:Body>
            <AuthResponse xmlns="urn:zimbraAccount">
                <authToken>0_413d3eb248523e14cffc2e08de79670792c86c7f_69643d33363a37363163646566632d393166372d343835342d613563352d3732633361393738333139663b6578703d31333a313239393233383234363030313b747970653d363a7a696d6272613b</authToken>
                <lifetime>172800000</lifetime>
                <skin>beach</skin>
            </AuthResponse>
        </soap:Body>
    </soap:Envelope>
    hmm ... the auth is successful, maybe just normal logging message?? A bit surprise the auth code is logged though.
    Last edited by John Siu; 03-16-2011 at 10:28 PM.

  5. #5
    datakid is offline Junior Member
    Join Date
    Sep 2010
    Posts
    7
    Rep Power
    4

    Default

    Quote Originally Posted by John Siu View Post
    Are you doing custom soap request to the server? The above soap message contain too many extra spaces and causing soap parsing error.
    Hmm, not that I'm aware of. I can't see any extra spaces in the above - do you mean too many chars?

  6. #6
    cogs66 is offline Starter Member
    Join Date
    Nov 2009
    Posts
    2
    Rep Power
    5

    Default

    Hi all

    Seeing the same error as tecno_tiago

    Has any found a fix yet?

    Thanks

    Andy

  7. #7
    datakid is offline Junior Member
    Join Date
    Sep 2010
    Posts
    7
    Rep Power
    4

    Default Yes, an Answer found

    On this thread:

    Error on Zimbra.log

  8. #8
    cogs66 is offline Starter Member
    Join Date
    Nov 2009
    Posts
    2
    Rep Power
    5

    Default

    Thanks for the link, looks ok to ignore then I guess. Odd though must be a V7 thing? I look after a few Zimbra installs and this is the first time I have seen this.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. fatal: parameter "smtpd_recipient_restrictions"
    By Robin in forum Administrators
    Replies: 8
    Last Post: 12-22-2010, 05:48 AM
  2. Old Backup stay in TO_DELETE status and no clearing..
    By bartounet in forum Administrators
    Replies: 0
    Last Post: 10-05-2010, 07:40 AM
  3. My Zimbra Server crashed this morning...
    By glitch23 in forum Administrators
    Replies: 3
    Last Post: 04-07-2008, 01:28 PM
  4. dspam logrotate errors
    By michaeln in forum Users
    Replies: 7
    Last Post: 02-19-2007, 12:45 PM
  5. 3.1 on FC4 problems
    By cohnhead in forum Installation
    Replies: 8
    Last Post: 05-26-2006, 11:16 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •