Bad server response 5.4.3

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Dominion
    Member
    • Feb 2016
    • 38

    Bad server response 5.4.3

    Hello,
    I've noticed the Bad server response error while trying search in Contacts. The same error I have in any part of system when trying search. The system is 5.4.3. I've tried to clear the cache, rebuild, etc. Logs shows nothing. Could somebody please help me with the issue?
    Thanks!
  • tanya
    Senior Member
    • Jun 2014
    • 4308

    #2
    Hi,
    by what field are you filtered?
    What is in espocrm log? (data/logs)

    Comment

    • Dominion
      Member
      • Feb 2016
      • 38

      #3
      Hello,
      Just when I try to find a name in Contacts and click "Search".

      Comment

      • tanya
        Senior Member
        • Jun 2014
        • 4308

        #4
        What is in espocrm log? (data/logs)

        Comment

        • Dominion
          Member
          • Feb 2016
          • 38

          #5
          I look at /data/logs/espo-2018-10-08.log and see no log of such behavior. Only notes which are irrelevant to this case.

          Code:
          [2018-10-08 17:50:03] Espo.ERROR: Google Calendar Synchronization: Сергій Торчук could not connect to Google Server when synchronizing the calendar "ФОП в регистрации" [] []
          [2018-10-08 17:50:03] Espo.ERROR: Google Calendar Synchronization: Сергій Торчук could not connect to Google Server when synchronizing the calendar "Подтверждение данных" [] []
          [2018-10-08 17:50:03] Espo.ERROR: Google Calendar Synchronization: Сергій Торчук could not connect to Google Server when synchronizing the calendar "Main" [] []

          Comment

          • tanya
            Senior Member
            • Jun 2014
            • 4308

            #6
            click Search again and check log again. Also you can check server error log. The reason has been logged

            Comment

            • Dominion
              Member
              • Feb 2016
              • 38

              #7
              I've clicked several times and nothing in the data/logs, but, I find something in apache2 log - please see the txt file attached.
              Attached Files

              Comment

              • tanya
                Senior Member
                • Jun 2014
                • 4308

                #8
                you attached access log, not error

                Comment

                • Dominion
                  Member
                  • Feb 2016
                  • 38

                  #9
                  Sorry, it was newest file by date, I didn't pay enough attention to filename.
                  I've checked once more data/logs: there are daily log files there like espo-2018-10-09.log and nothing relevant inside. No new information after I click "search" several times with the error message.
                  e.g. the ending of espo-2018-10-09.log irrelevant to this error
                  Code:
                  [2018-10-09 17:10:02] Espo.ERROR: Google Calendar Synchronization: Сергій Торчук could not connect to Google Server when synchronizing the calendar "st@dominion.od.ua" [] []
                  [2018-10-09 17:10:02] Espo.ERROR: Google Calendar Synchronization: Сергій Торчук could not connect to Google Server when synchronizing the calendar "ФОП в регистрации" [] []
                  [2018-10-09 17:10:02] Espo.ERROR: Google Calendar Synchronization: Сергій Торчук could not connect to Google Server when synchronizing the calendar "Подтверждение данных" [] []
                  [2018-10-09 17:10:02] Espo.ERROR: Google Calendar Synchronization: Сергій Торчук could not connect to Google Server when synchronizing the calendar "Main" [] []
                  Also I've checked /var/log and /var/log/apache2 - error.log for current date contains two lines only
                  Code:
                  [Tue Oct 09 06:25:03.733379 2018] [mpm_prefork:notice] [pid 644] AH00163: Apache/2.4.10 (Debian) mpm-itk/2.4.7-02 configured -- resuming normal operations
                  [Tue Oct 09 06:25:03.733438 2018] [core:notice] [pid 644] AH00094: Command line: '/usr/sbin/apache2'

                  Comment

                  • tanya
                    Senior Member
                    • Jun 2014
                    • 4308

                    #10
                    Check owner of espo-2018-10-09.log? Is it the same user, as server user?
                    Seams file is not writable for server user. It could happen only if cron is run by other user (maybe root), and log is not writable for server user

                    Comment

                    • Dominion
                      Member
                      • Feb 2016
                      • 38

                      #11
                      no, the owner of all *.log files in /data/logs is root:root
                      I've changed data/config.php logger to DEBUG and got new lines in espo-2018-10-09.log after clicking search
                      Code:
                      [2018-10-09 17:41:02] Espo.DEBUG: BPM: processPendingFlows [] []
                      [2018-10-09 17:42:02] Espo.DEBUG: BPM: processPendingFlows [] []
                      [2018-10-09 17:43:03] Espo.DEBUG: BPM: processPendingFlows [] []
                      [2018-10-09 17:44:02] Espo.DEBUG: BPM: processPendingFlows [] []
                      [2018-10-09 17:45:02] Espo.DEBUG: BPM: processPendingFlows [] []
                      [2018-10-09 17:46:03] Espo.DEBUG: BPM: processPendingFlows [] []
                      [2018-10-09 17:47:02] Espo.DEBUG: BPM: processPendingFlows [] []
                      [2018-10-09 17:48:03] Espo.DEBUG: BPM: processPendingFlows [] []
                      [2018-10-09 17:49:03] Espo.DEBUG: BPM: processPendingFlows [] []
                      [2018-10-09 17:50:02] Espo.DEBUG: BPM: processPendingFlows [] []

                      Comment

                      • tanya
                        Senior Member
                        • Jun 2014
                        • 4308

                        #12
                        change owner to server user:group (maybe www-data:www-data)

                        Comment

                        • Dominion
                          Member
                          • Feb 2016
                          • 38

                          #13
                          aha! that was the case. Now it writes more info

                          Code:
                          [2018-10-09 18:34:15] Espo.ERROR: Uncaught Exception Error: "Call to undefined function Espo\Core\SelectManagers\mb_strpos()" at /var/www/                                                application/Espo/Core/SelectManagers/Base.php line 1729 {"exception":"[object] (Error(code: 0): Call to undefined function Espo\\Core\\Sel                                                ectManagers\\mb_strpos() at /var/www/application/Espo/Core/SelectManagers/Base.php:1729)"} []
                          [2018-10-09 18:34:15] Espo.ERROR: Uncaught Exception Error: "Call to undefined function Espo\Core\SelectManagers\mb_strpos()" at /var/www/                                                application/Espo/Core/SelectManagers/Base.php line 1729 {"exception":"[object] (Error(code: 0): Call to undefined function Espo\\Core\\Sel                                                ectManagers\\mb_strpos() at /var/www/application/Espo/Core/SelectManagers/Base.php:1729)"} []
                          [2018-10-09 18:34:15] Espo.ERROR: Uncaught Exception Error: "Call to undefined function Espo\Core\SelectManagers\mb_strpos()" at /var/www/                                                application/Espo/Core/SelectManagers/Base.php line 1729 {"exception":"[object] (Error(code: 0): Call to undefined function Espo\\Core\\Sel                                                ectManagers\\mb_strpos() at /var/www/application/Espo/Core/SelectManagers/Base.php:1729)"} []
                          [2018-10-09 18:34:16] Espo.ERROR: Uncaught Exception Error: "Call to undefined function Espo\Core\SelectManagers\mb_strpos()" at /var/www/                                                application/Espo/Core/SelectManagers/Base.php line 1729 {"exception":"[object] (Error(code: 0): Call to undefined function Espo\\Core\\Sel                                                ectManagers\\mb_strpos() at /var/www/application/Espo/Core/SelectManagers/Base.php:1729)"} []
                          [2018-10-09 18:34:16] Espo.ERROR: Uncaught Exception Error: "Call to undefined function Espo\Core\SelectManagers\mb_strpos()" at /var/www/                                                application/Espo/Core/SelectManagers/Base.php line 1729 {"exception":"[object] (Error(code: 0): Call to undefined function Espo\\Core\\Sel                                                ectManagers\\mb_strpos() at /var/www/application/Espo/Core/SelectManagers/Base.php:1729)"} []
                          [2018-10-09 18:34:16] Espo.ERROR: Uncaught Exception Error: "Call to undefined function Espo\Core\SelectManagers\mb_strpos()" at /var/www/                                                application/Espo/Core/SelectManagers/Base.php line 1729 {"exception":"[object] (Error(code: 0): Call to undefined function Espo\\Core\\Sel                                                ectManagers\\mb_strpos() at /var/www/application/Espo/Core/SelectManagers/Base.php:1729)"} []

                          Comment

                          • tanya
                            Senior Member
                            • Jun 2014
                            • 4308

                            #14
                            install php mbstring extension

                            Comment

                            • Dominion
                              Member
                              • Feb 2016
                              • 38

                              #15
                              Originally posted by tanya
                              install php mbstring extension
                              Done! And the problem is gone! Everything works perfectly now.
                              Thank you kindly

                              Comment

                              Working...