Contrib.social

Grep sometimes misunderstands the Nagios values as binary

Open on Drupal.org →
Created on 26 April 2023, over 1 year ago
Updated 27 April 2023, over 1 year ago

Problem/Motivation

I recently started seeing an "unknown" return on one site in Icinga with this message:
HTTP returned an error code. HTTP: Binary file /tmp/tmp.YA1w644yOT matches

Steps to reproduce

I imagine it'd be difficult to reproduce, but here is what the Nagios return value *should* have been, and surely it's something about my watchdog message that provoked this.

DRUPAL CRITICAL, WATCHDOG:CRITICAL=2023-04-24 18:14:16 php Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away: INSERT INTO "cache_default" ("cid", "expi
re", "created", "tags", "checksum", "data", "serialized") VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_p
laceholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6) ON DUPLICATE KEY UPDATE "cid" = VALUES("cid"), "expire" = VALUES("expire"), "created" = VALUES("created"), &quo
t;tags" = VALUES("tags"), "checksum" = VALUES("checksum"), "data" = VALUES("data"), "serialized" = VALUES("serialized"); Array

Proposed resolution

We add the `--text` argument to the grep commands in `check_drupal`.

🐛 Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

🇺🇸United States MegaphoneJon

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024