Weiter zum Inhalt
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Hell
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dunkel
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. ioBroker MySQL nach einiger Zeit "connection refused" --> MySQL Problem?

NEWS

  • Neuer ioBroker-Blog online: Monatsrückblick März/April 2026
    BluefoxB
    Bluefox
    6
    1
    249

  • Verwendung von KI bitte immer deutlich kennzeichnen
    HomoranH
    Homoran
    9
    1
    240

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    18
    1
    899

ioBroker MySQL nach einiger Zeit "connection refused" --> MySQL Problem?

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
mysqlconnection refused
1 Beiträge 1 Kommentatoren 293 Aufrufe 2 Beobachtet
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • A Offline
    A Offline
    adarof
    schrieb am zuletzt editiert von
    #1

    Hallo

    NUC mit ioBroker und Historian auf einer lokalen MySQL

    Ich hatte nun 3x hintereinander, dass grob nach 3 Tagen meine MySQL im Hintergrund von ioBroker "grundlos" nicht mehr da war. Das hab ich dann nur zufällig gemerkt, weil in der Vis eine LogAnzeige steht...

    Nun habe ich mal ins MySQL-Log geschaut und staune nicht schlecht (log unten)

    1. Als Warnung für Euch ... falls auf einmal keine historischen Daten gelogged werden...
    2. Wie behebe ich das? Die Doku sagt mir nichts und wenn ich google komme ich zum droppen von irgendwelchen internen Tabels ... da hab ich etwas bedenken :-(

    Eure Meinung?

    Gruss -

    2019-05-01T04:58:36.367452Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
    2019-05-01T04:58:36.369284Z 0 [Note] mysqld (mysqld 5.7.26-0ubuntu0.18.04.1) starting as process 17250 ...
    2019-05-01T04:58:36.374677Z 0 [Note] InnoDB: PUNCH HOLE support available
    2019-05-01T04:58:36.374711Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    2019-05-01T04:58:36.374718Z 0 [Note] InnoDB: Uses event mutexes
    2019-05-01T04:58:36.374724Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    2019-05-01T04:58:36.374728Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
    2019-05-01T04:58:36.374733Z 0 [Note] InnoDB: Using Linux native AIO
    2019-05-01T04:58:36.374991Z 0 [Note] InnoDB: Number of pools: 1
    2019-05-01T04:58:36.375100Z 0 [Note] InnoDB: Using CPU crc32 instructions
    2019-05-01T04:58:36.376709Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
    2019-05-01T04:58:36.386140Z 0 [Note] InnoDB: Completed initialization of buffer pool
    2019-05-01T04:58:36.388461Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
    2019-05-01T04:58:36.400768Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
    2019-05-01T04:58:36.429016Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
    2019-05-01T04:58:36.429130Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
    2019-05-01T04:58:36.464405Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
    2019-05-01T04:58:36.465475Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
    2019-05-01T04:58:36.465493Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
    2019-05-01T04:58:36.466037Z 0 [Note] InnoDB: Waiting for purge to start
    2019-05-01T04:58:36.516314Z 0 [Note] InnoDB: 5.7.26 started; log sequence number 589734102
    2019-05-01T04:58:36.516739Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
    2019-05-01T04:58:36.517257Z 0 [Note] Plugin 'FEDERATED' is disabled.
    2019-05-01T04:58:36.526020Z 0 [Warning] InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-tr
    oubleshooting.html for how to resolve the issue.
    mysqld: Table 'mysql.gtid_executed' doesn't exist
    2019-05-01T04:58:36.526090Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
    2019-05-01T04:58:36.526210Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key
    2019-05-01T04:58:36.529528Z 0 [Warning] Insecure configuration for --pid-file: Location '/tmp' in the path is accessible to all OS users. Consider choosing a different directory.
    2019-05-01T04:58:36.529727Z 0 [Warning] InnoDB: Cannot open table mysql/server_cost from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-trou
    bleshooting.html for how to resolve the issue.
    2019-05-01T04:58:36.529747Z 0 [Warning] Failed to open optimizer cost constant tables
    
    2019-05-01T04:58:36.530457Z 0 [Warning] System table 'time_zone_leap_second' is expected to be transactional.
    2019-05-01T04:58:36.530470Z 0 [Warning] System table 'time_zone_name' is expected to be transactional.
    2019-05-01T04:58:36.530474Z 0 [Warning] System table 'time_zone' is expected to be transactional.
    2019-05-01T04:58:36.530477Z 0 [Warning] System table 'time_zone_transition_type' is expected to be transactional.
    2019-05-01T04:58:36.530481Z 0 [Warning] System table 'time_zone_transition' is expected to be transactional.
    2019-05-01T04:58:36.530699Z 0 [Warning] System table 'servers' is expected to be transactional.
    2019-05-01T04:58:36.530933Z 0 [ERROR] Column count of performance_schema.events_waits_current is wrong. Expected 19, found 16. Created with MySQL 50560, now running 50726. Please use mysql_upgrade to fix this error.
    2019-05-01T04:58:36.531008Z 0 [ERROR] Column count of performance_schema.events_waits_history is wrong. Expected 19, found 16. Created with MySQL 50560, now running 50726. Please use mysql_upgrade to fix this error.
    2019-05-01T04:58:36.531067Z 0 [ERROR] Column count of performance_schema.events_waits_history_long is wrong. Expected 19, found 16. Created with MySQL 50560, now running 50726. Please use mysql_upgrade to fix this error.
    2019-05-01T04:58:36.531234Z 0 [ERROR] Incorrect definition of table performance_schema.events_waits_summary_by_thread_by_event_name: expected column 'THREAD_ID' at position 0 to have type bigint(20), found type int(11).
    2019-05-01T04:58:36.531493Z 0 [ERROR] Column count of performance_schema.file_summary_by_event_name is wrong. Expected 23, found 5. Created with MySQL 50560, now running 50726. Please use mysql_upgrade to fix this error.
    2019-05-01T04:58:36.531548Z 0 [ERROR] Column count of performance_schema.file_summary_by_instance is wrong. Expected 25, found 6. Created with MySQL 50560, now running 50726. Please use mysql_upgrade to fix this error.
    2019-05-01T04:58:36.531668Z 0 [ERROR] Incorrect definition of table performance_schema.mutex_instances: expected column 'LOCKED_BY_THREAD_ID' at position 2 to have type bigint(20), found type int(11).
    2019-05-01T04:58:36.531824Z 0 [ERROR] Incorrect definition of table performance_schema.rwlock_instances: expected column 'WRITE_LOCKED_BY_THREAD_ID' at position 2 to have type bigint(20), found type int(11).
    2019-05-01T04:58:36.532557Z 0 [ERROR] Column count of performance_schema.threads is wrong. Expected 17, found 3. Created with MySQL 50560, now running 50726. Please use mysql_upgrade to fix this error.
    2019-05-01T04:58:36.536546Z 0 [Note] mysqld: ready for connections.
    Version: '5.7.26-0ubuntu0.18.04.1'  socket: '/tmp/tmp.YoLu6wwr9W/mysqld.sock'  port: 0  (Ubuntu)
    2019-05-01T04:58:36.560792Z 2 [Warning] InnoDB: Cannot open table mysql/innodb_table_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/inno
    db-troubleshooting.html for how to resolve the issue.
    2019-05-01T04:58:36.563090Z 0 [Note] Giving 0 client threads a chance to die gracefully
    2019-05-01T04:58:36.563120Z 0 [Note] Shutting down slave threads
    2019-05-01T04:58:36.563132Z 0 [Note] Forcefully disconnecting 0 remaining clients
    2019-05-01T04:58:36.563194Z 0 [Note] Binlog end
    2019-05-01T04:58:36.565282Z 0 [Note] Shutting down plugin 'ngram'
    2019-05-01T04:58:36.565302Z 0 [Note] Shutting down plugin 'partition'
    2019-05-01T04:58:36.565307Z 0 [Note] Shutting down plugin 'BLACKHOLE'
    2019-05-01T04:58:36.565312Z 0 [Note] Shutting down plugin 'ARCHIVE'
    2019-05-01T04:58:36.565316Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'
    2019-05-01T04:58:36.565342Z 0 [Note] Shutting down plugin 'MRG_MYISAM'
    2019-05-01T04:58:36.565347Z 0 [Note] Shutting down plugin 'MyISAM'
    2019-05-01T04:58:36.565354Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'
    2019-05-01T04:58:36.565358Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
    2019-05-01T04:58:36.565362Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
    2019-05-01T04:58:36.565365Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
    2019-05-01T04:58:36.565369Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
    2019-05-01T04:58:36.565372Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
    2019-05-01T04:58:36.565376Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
    2019-05-01T04:58:36.565379Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
    2019-05-01T04:58:36.565383Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
    2019-05-01T04:58:36.565386Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
    2019-05-01T04:58:36.565389Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
    2019-05-01T04:58:36.565393Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
    2019-05-01T04:58:36.565396Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
    2019-05-01T04:58:36.565409Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
    2019-05-01T04:58:36.565413Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED'
    2019-05-01T04:58:36.565417Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'
    2019-05-01T04:58:36.565420Z 0 [Note] Shutting down plugin 'INNODB_METRICS'
    2019-05-01T04:58:36.565424Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO'
    2019-05-01T04:58:36.565427Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'
    2019-05-01T04:58:36.565430Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'
    2019-05-01T04:58:36.565434Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'
    2019-05-01T04:58:36.565437Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'
    2019-05-01T04:58:36.565440Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'
    2019-05-01T04:58:36.565444Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'
    2019-05-01T04:58:36.565447Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM'
    2019-05-01T04:58:36.565450Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET'
    2019-05-01T04:58:36.565454Z 0 [Note] Shutting down plugin 'INNODB_CMP'
    2019-05-01T04:58:36.565458Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'
    2019-05-01T04:58:36.565461Z 0 [Note] Shutting down plugin 'INNODB_LOCKS'
    2019-05-01T04:58:36.565464Z 0 [Note] Shutting down plugin 'INNODB_TRX'
    2019-05-01T04:58:36.565468Z 0 [Note] Shutting down plugin 'InnoDB'
    2019-05-01T04:58:36.565520Z 0 [Note] InnoDB: FTS optimize thread exiting.
    2019-05-01T04:58:36.565585Z 0 [Note] InnoDB: Starting shutdown...
    2019-05-01T04:58:36.565643Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190501  6:58:36
    2019-05-01T04:58:36.565676Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
    2019-05-01T04:58:36.565859Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 190501  6:58:36
    2019-05-01T04:58:38.080886Z 0 [Note] InnoDB: Shutdown completed; log sequence number 589734121
    2019-05-01T04:58:38.085720Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
    2019-05-01T04:58:38.085778Z 0 [Note] Shutting down plugin 'MEMORY'
    2019-05-01T04:58:38.085798Z 0 [Note] Shutting down plugin 'CSV'
    2019-05-01T04:58:38.085813Z 0 [Note] Shutting down plugin 'sha256_password'
    2019-05-01T04:58:38.085825Z 0 [Note] Shutting down plugin 'mysql_native_password'
    2019-05-01T04:58:38.086057Z 0 [Note] Shutting down plugin 'binlog'
    2019-05-01T04:58:38.086506Z 0 [Note] mysqld: Shutdown complete
    
    
    1 Antwort Letzte Antwort
    0

    Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.

    Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.

    Mit deinem Input könnte dieser Beitrag noch besser werden 💗

    Registrieren Anmelden
    Antworten
    • In einem neuen Thema antworten
    Anmelden zum Antworten
    • Älteste zuerst
    • Neuste zuerst
    • Meiste Stimmen


    Support us

    ioBroker
    Community Adapters
    Donate
    FAQ Cloud / IOT
    HowTo: Node.js-Update
    HowTo: Backup/Restore
    Downloads
    BLOG

    406

    Online

    32.8k

    Benutzer

    82.8k

    Themen

    1.3m

    Beiträge
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
    ioBroker Community 2014-2025
    logo
    • Anmelden

    • Du hast noch kein Konto? Registrieren

    • Anmelden oder registrieren, um zu suchen
    • Erster Beitrag
      Letzter Beitrag
    0
    • Home
    • Aktuell
    • Tags
    • Ungelesen 0
    • Kategorien
    • Unreplied
    • Beliebt
    • GitHub
    • Docu
    • Hilfe