Ad Widget

Collapse

Weird email behavior

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • gregecslo
    Junior Member
    • Mar 2017
    • 3

    #1

    Weird email behavior

    Hi all!

    I just updated to Zabbix server 3.2.4 (revision 65975) and agents on Windows to Zabbix 3.2.0 (revision 62444).

    For my problem below it is server upgrade that borked it.
    With old 3.0.X agents same data in emails was sent by zabbix server so I believe that agents are not problematic here.

    Problem:

    I have configured selected mail template to be sent:

    Code:
    HOST: {HOST.NAME}
    Trigger: {TRIGGER.NAME}
    Trigger status: {TRIGGER.STATUS}
    Trigger severity: {TRIGGER.SEVERITY}
    Trigger URL: {TRIGGER.URL}
    Event time: {EVENT.TIME}
    Event date: {EVENT.DATE}
    
    Item values:
    
    1. {ITEM.NAME1} ({HOST.NAME1}:{ITEM.KEY1}): {ITEM.VALUE1}
    
    Origin: {EVENT.ID}
    Emails I`ve been getting since upgrade:
    Code:
    HOST: VM-DB
    Trigger: Version of zabbix_agent(d) was changed on VM-DB
    Trigger status: PROBLEM
    Trigger severity: Information
    Trigger URL: 
    Event time: 20:40:44
    Event date: 2017.03.02
    
    Item values:
    
    1. Version of zabbix_agent(d) running (VM-DB:agent.version): 3.2.0
    
    O
    or

    Code:
    HOST: HOSTNAME
    Trigger: RDP logon on HOSTNAME
    Trigger status: PROBLEM
    Trigger severity: Information
    Trigger URL: 
    Event time: 18:44:58
    Event date: 2017.03.02
    
    Item values:
    
    1. Logiraj RDP evente - logons (hostname:eventlog[Microsoft-Windows-TerminalServices-RemoteConnectionManager/Operational,,,,"1149"]): Remote Desktop Services: User authentication succeeded:
    
    User: Administrator
    Domain: MYDOMAIN
    Source Network Address: 192.168.
    or

    Code:
    HOST: HOSTNAME
    Trigger: Account logon failed on HOSTNAME Trigger status: PROBLEM Trigger severity: Warning Trigger URL: 
    Event time: 18:25:12
    Event date: 2017.03.02
    
    Item values:
    
    1. Logiraj security evente - failed logins (HOSTNAME:eventlog[Security,,,,"4771|4625"]): An account failed to log on.
    
    Subject:
    	Security ID:		S-1-3-11
    	Account Name:		HOSTNAME$
    	Account Domain:		DOMAIN
    	Logon ID:		0x3E7
    
    Logon Type:			3
    
    Account For Which Logon Failed:
    	Security ID:		S-1-0-0
    	Account Name:		
    	Account Domain:		
    
    Failure Information:
    	Failure Reason:		Account currently disabled.
    	Status:			0xC000006E
    	Sub Status:		0xC0000072
    
    Process Information:
    	Caller Process ID:	0x1834
    	Caller Process Name:	C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeMailboxAssistants.exe
    
    Network Information:
    	Workstation Name:	HOSTNAME HERE
    	Source Network Address:	-
    	Source Port:		-
    
    Detailed Authentication Information:
    	Logon Process:		Authz   
    	Authentication Package:	Kerberos
    	Transited Services:	-
    	Package Name (NTLM only):	-
    	Key Length:		0
    
    This event is generated when a logon request fails. It is generated on the computer where access was attempted.
    
    The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
    
    The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
    
    The Process Information fields indicate which account and process on the system requested the logon.
    
    The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
    
    The authentication information fields provide detailed information about this specific logon request.
    	- Transited services indicate which intermediate services have participated in this logon request.
    	- Package name indicates which sub-protocol was used among the NTLM protocols.
    	- Key length indicates the length of the generated session key. This will be 0

    In first original ID is missing on second IP is cut off and in third half of text is missing...

    Any idea how to begin to troubleshoot this or should I file bugreport?

    Thanks!
  • gseeley
    Junior Member
    • Mar 2017
    • 3

    #2
    I just upgraded to 3.2.4 as well and I see the same truncated emails. I think it might be related to the base64 encoding that is used but I can't confirm this. I built from the latest source so I was thinking about added some debugging to see if I could isolate where this happens.

    Comment

    • vic
      Member
      • Jul 2013
      • 58

      #3
      I am seeing something similar after upgrading from v3.0.7 to v3.2.4 CE7 RPM

      {ITEM.VALUE1} is either being truncated or not populated.

      I see the same thing in Action > Logs.

      The value is being generated and logged. Just not being populated into Action value.
      Last edited by vic; 09-03-2017, 17:08.

      Comment

      • gregecslo
        Junior Member
        • Mar 2017
        • 3

        #4
        Yeah same here.. This really crippled our helpdesk.. 🙁

        Comment

        • wasabi
          Member
          • Mar 2014
          • 30

          #5
          oddly truncated emails here, too....Zabbix 3.2.4

          Dear forum,

          in email action I am lacking in most emails a part of the text. In my case the problem only seems to affect the recovery mails and with different length.
          It also only seems to affect the last line in my case (4. Problem duration: {EVENT.AGE}).

          examples:

          4. Problem duratio
          4. Problem dura
          4. Problem dur
          4. Problem duration: 4
          4. Problem duration: 5m

          The problem seems to have appeared after the upgrade from 3.2.3 to 3.2.4 here.

          My platform is ubuntu 14.04 with deb package installation.

          If I can contribute in fixing this problem then please let me know.

          Best regards, Claudio

          Comment

          • gseeley
            Junior Member
            • Mar 2017
            • 3

            #6
            I did another test where I added extra text to the end of the Action messages like this:
            Code:
            123456789012345678901234567890123456789012345678901234567890
            123456789012345678901234567890123456789012345678901234567890
            123456789012345678901234567890123456789012345678901234567890
            and waited for a trigger to occur and when it did, this is what I saw in the Operations message:
            Code:
            123456789012345678901234567890123456789012345678901234567890
            123456789012345678901234567890123456789012345678901234567890
            12345678901234567890123456789012
            and the Recovery message:
            Code:
            123456789012345678901234567890123456789012345678901234567890
            123456789012345678901234567890123456789012345678901234567890
            1234567890123456789012345678901234567890
            So it looks to me like the amount of text truncated in the message is variable to it's related to the content somehow.

            Comment

            • Atsushi
              Senior Member
              • Aug 2013
              • 2028

              #7
              It may be the following problem.

              ZBX-11855
              Carriage Return Causes Data Truncation During Escaping

              Comment

              • andresf
                Junior Member
                • Jan 2017
                • 16

                #8
                Hello

                I have the same problem. It happens on Ubuntu Server 14.04 but not in Ubuntu Desktop 14.04.

                Comment

                • andresf
                  Junior Member
                  • Jan 2017
                  • 16

                  #9
                  Solved (Workaround)

                  Hi there

                  With my team we found a workaround. The problem is in the <ENTER> added to the message.

                  To solve this issue, you have to add extra "character" (you can use a "dot", DO NOT USE SPACES) at the end of the message for each <ENTER> that you have wrote on the message.

                  This issue seems to be only found on version Ubuntu Server 14.04 and zabbix 3.2.4 revision 65975 it´s not happens on Ubuntu Desktop 14.04.

                  I hope you enjoy this bug

                  Comment

                  • wasabi
                    Member
                    • Mar 2014
                    • 30

                    #10
                    Originally posted by andresf
                    To solve this issue, you have to add extra "character" (you can use a "dot", DO NOT USE SPACES) at the end of the message for each <ENTER> that you have wrote on the message.
                    Hi @andresf,

                    Please help!

                    first of all I want to thank you for your workaround. Unfortunately I am no native speaker and thus cannot get it to work. I tried your workaround as follows (ex. Action -> Recovery Operation):

                    Code:
                    Trigger: {TRIGGER.NAME}.
                    Trigger status: {TRIGGER.STATUS}.
                    Trigger severity: {TRIGGER.SEVERITY}.
                    .
                    Item values:.
                    .
                    1. {ITEM.NAME1} ({HOST.NAME1}:{ITEM.KEY1}): {ITEM.VALUE1}.
                    2. IP address {IPADDRESS1}.
                    3. Location: {PROFILE.LOCATION}.
                    4. Problem duration: {EVENT.AGE}.
                    Please post an example of your workaround.
                    Best regards and maaaany thanks!

                    Claudio

                    Comment

                    • andresf
                      Junior Member
                      • Jan 2017
                      • 16

                      #11
                      Hi Claudio

                      I wrote that you need to add an "extra character" (you can use a "dot character" for me is mor visual) at the end of the message, not the end of each line.

                      Suppose the following example

                      Code:
                      Trigger: {TRIGGER.NAME}
                      Trigger status: {TRIGGER.STATUS}
                      Trigger severity: {TRIGGER.SEVERITY}
                      
                      Item values:
                      
                      1. {ITEM.NAME1} ({HOST.NAME1}:{ITEM.KEY1}): {ITEM.VALUE1}
                      2. IP address {IPADDRESS1}
                      3. Location: {PROFILE.LOCATION}
                      4. Problem duration: {EVENT.AGE}.........
                      Note the 9 "dot" at the end of the message. Because you have 9 "enters".

                      Please check it out and let me know if it works.

                      Andres.


                      Originally posted by wasabi
                      Hi @andresf,

                      Please help!

                      first of all I want to thank you for your workaround. Unfortunately I am no native speaker and thus cannot get it to work. I tried your workaround as follows (ex. Action -> Recovery Operation):

                      Code:
                      Trigger: {TRIGGER.NAME}.
                      Trigger status: {TRIGGER.STATUS}.
                      Trigger severity: {TRIGGER.SEVERITY}.
                      .
                      Item values:.
                      .
                      1. {ITEM.NAME1} ({HOST.NAME1}:{ITEM.KEY1}): {ITEM.VALUE1}.
                      2. IP address {IPADDRESS1}.
                      3. Location: {PROFILE.LOCATION}.
                      4. Problem duration: {EVENT.AGE}.
                      Please post an example of your workaround.
                      Best regards and maaaany thanks!

                      Claudio
                      Last edited by andresf; 10-04-2017, 14:51. Reason: i forgot to add 1 dot

                      Comment

                      • wasabi
                        Member
                        • Mar 2014
                        • 30

                        #12
                        it works!

                        Hi Andres,

                        it works exactly as you described it.

                        Many thanks - now I can see again from the recovery mail the duration of the problem!

                        I hope this will be fixed soon in one of the next Zabbix versions

                        Best regards,
                        Claudio

                        Comment

                        • gseeley
                          Junior Member
                          • Mar 2017
                          • 3

                          #13
                          This issue is fixed in 3.2.5.

                          Comment

                          Working...