Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 44 Next »


Table of Contents

Overview

This document list the information needed for most common problems when creating a new ticket.
In some cases support needs more information which is not listed here because of the unknown nature of the problem.

Information for Mobile Apps can be found here:  Mobile Apps

General:


OX App Suite / Dovecot Pro / OX PowerDNS

For all tickets, we need the following information:

 Support Key: OX-SUPPORT-OR-LICENSE-KEY-XXX
Server: url of the machine
Server Version: server version or package list
Platform:
GUI Version: GUI version or package list
Category:
Severity: 4, 3, 2, 1
Track-ID: the customer's internal tracking number, e.g. from its Bugzilla
Product:
Date/time of last changes to configuration or installing updates (with description)
or any other changes that were done within at least the last 24 hours or:
...
Issue Description:
...
Steps to reproduce:
  • Provide a detailed description of the issue/incident and ideally a step-by-step description
 Used OS/Browser/Client (with version):
 ...
Date/time of test (with timezone):
...
Current behaviour / Error or Unexpected Results (Date/time):
...
Expected behaviour:
...
Test account to reproduce issue: 

as an attachment:

OX App Suite (Middleware or UI):

    • oxsysreport 
      /opt/open-xchange/sbin/oxsysreport
    • test account(s)

 Dovecot Pro: 

    • dovecot logs 
    • doveconf -n 
      please also include .ext files and other files included in the configuration, but feel free to remove any passwords and sensitive information.
    • /usr/bin/dovecot-package-list-deps.sh
    • crashes:  core dump, if a crash occurred. The trace should have as much information as possible, so for e.g. the "gdb" debugger use "bt full" and if possible, install dovecot debug packages. 

OX PowerDNS: 

    • powerdns logs
    • ‘dig’ output for any failing query
    • crashes:  core dump

Additional Information Needed based on Situation



OX App Suite

Dovecot Pro

OX PowerDNS

High load /
high memory usage

  • run command:
    strace -tt -s 100 -p <pid of high CPU load process>
    and paste the output to OTRS ticket

  • Hostname  in our private metrics server,

    and/or

  • Graphs from customer-internal system

Communication link error

  • check the network and the server mentioned at the beginning of the stack trace
    with Dovecot:  add Dovecot logs
    with Database:  see next section

  • recursor trace logs (rec_control trace-regex or – trace config setting) for failing lookup

Database issue

  • include general oxsysreport
  • DB slow logs from the time the issue first occurred

  • run the following show global status
    show processlist
    show engine innodb status/G
  • monitoring data of the affected servers (graphs) - at least day and week

  • as for Appsuite, except for oxsysreport

Login issue

  • exact date and time
  • apache logs from the time frame
  • general information and oxsysreport
  • (network traces and sniffs to watch and monitor the network traffic of specific services.)
  • Dovecot logs in verbose mode
    if possible, reproduce the issue with auth_debug=yes enabled
    please make sure .ext configuration files of passdb and userdb blocks are included with the provided configuration.
  • webapp logs

Auth issue 

  • OX 
    general information and oxsysreport

  • OX Login is working but not Dovecot
    check OX logs, in case of error regarding password change
    Dovecot logs in verbose mode
  • Dovecot logs in verbose mode
    if possible, reproduce the issue with auth_debug=yes enabled
    please make sure .ext configuration files of passdb and userdb blocks are included with the provided configuration.
  • webapp logs

UI issue

  • test account to reproduce the issue
  • general information and oxsysreport
  • browser type with version number
  • screenshots showing the problem
  • check JavaScript console and provide additional errors or attach har-file
  • check the network tab if request fail, timeout or simply take to long

  • as for Appsuite, except for oxsysreport

API issues


  • show full request and response (tcpdump)
  • general information and oxsysreport

  • show full request and response
  • describe how seen behavior differs from expected behavior
  • No labels