Missing Logger Table, Fatal GuzzleHttp Error

  • Resolved machouinard

    (@machouinard)


    4 years, 1 month ago

    We’re looking for suggestions.

    Auto RETS import has not been working consistently.

    After attempting to manually execute the auto import schedule we see this message x5 (import limit is 5):

    WordPress database error: [Table '[prefix]_es_mls_logger' doesn't exist]
SHOW FULL COLUMNS FROM <code>[prefix]_es_mls_logger</code>

    Sure enough, there is no es_mls_logger table in the database.

    Every time the scheduled import runs we also get this in debug.log:

    PHP Fatal error: Uncaught Error: Call to undefined method GuzzleHttp\Exception\ClientException::Search() in PATH/wp-content/plugins/estatik-premium/mls/classes/apis/class-rets-api.php:463

    Manual import also triggers the fatal error in debug.log, shows message “Nothing to import”.

    We’re experiencing the same issues on the live site, staging (Siteground) and local development (Local by Flywheel).

    WordPress 5.5.1
    Estatik Premium 3.9.7

    • This topic was modified 4 years, 1 month ago by machouinard. Reason: add staging, prod and local info
Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter machouinard

    (@machouinard)

    PHP Fatal error: Uncaught Error: Call to a member function build_query_string() on null in PATH/wp-content/plugins/estatik-premium/mls/classes/schedules/class-mls-import-schedule.php:107

    Auto import is occasionally working on local dev site. Still not working on staging.

    We have a single set of MLS Credentials using RETS, connecting through Bridge Interactive. We are receiving data and have been able to configure fields.

    Thread Starter machouinard

    (@machouinard)

    The previous error appears whenever cron runs the es_mls_schedule_hook.

    We switched to a real cron job and, unsurprisingly, here is the output:

    --2020-09-19 21:50:01--  URL/wp-cron.php?doing_wp_cron
Resolving URL (URL)... #.#.#.#
Connecting to URL (URL)#.#.#.#:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2020-09-19 21:50:01 ERROR 500: Internal Server Error.
    • This reply was modified 4 years, 1 month ago by machouinard. Reason: add detail
    Thread Starter machouinard

    (@machouinard)

    Upon further debugging, it seems the plugin was using the profile_id of a deleted set of RETS credentials.

    Actually there’s a ton of leftover stuff in the database after deleting the connection. I would not have thought deleting a connection would leave behind so much.

    I realize the RETS stuff is more advanced and client needs to purchase support. Feel free to ignore the above comments as I’m unable to delete them.

    Plugin Author Estatik

    (@estatik)

    Hi Mark,
    The most probable reason for this issue:

    PHP Fatal error: Uncaught Error: Call to undefined method GuzzleHttp\Exception\ClientException::Search() in PATH/wp-content/plugins/estatik-premium/mls/classes/apis/class-rets-api.php:463

    is requests blocking by MLS server. Please, try to set up Cron connections less often.
    Unfortunately we cannot discover the reason for Error 500 – Internal Server Error without additional information.
    So, we would appreciate if you contact us>> directly.
    Thanks.

    • This reply was modified 4 years, 1 month ago by Estatik.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Missing Logger Table, Fatal GuzzleHttp Error’ is closed to new replies.