Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Failed to start up with WSL environment #6480

@hamart

Description

@hamart

Describe the bug
Clickhouse-server failed to start up with defaults

How to reproduce
clickhouse-server --config-file=/etc/clickhouse-server/config.xml

  • Which ClickHouse server version to use
    19.13.1.11 (official build)
  • Which interface to use, if matters
    none
  • Non-default settings, if any
    none
  • CREATE TABLE statements for all tables involved
    none
  • Sample data for all these tables, use clickhouse-obfuscator if necessary
    none
  • Queries to run that lead to unexpected result
    none

Expected behavior
Server start up is successful

Error message and/or stacktrace
2019.08.13 23:29:18.499299 [ 1 ] {} BackgroundSchedulePool: Create BackgroundSchedulePool with 16 threads
2019.08.13 23:29:18.502924 [ 8 ] {} BaseDaemon: ########################################
2019.08.13 23:29:18.503391 [ 8 ] {} BaseDaemon: (version 19.13.1.11 (official build)) (from thread 1) Received signal Aborted (6).
2019.08.13 23:29:18.504350 [ 8 ] {} BaseDaemon:
2019.08.13 23:29:18.505231 [ 8 ] {} BaseDaemon: 0. /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7) [0x7f7a5325ee97]

Aborted (core dumped)

Additional context
Windows 10 with Windows Subsystem for Linux and Ubuntu 18.04 installed

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugConfirmed user-visible misbehaviour in official releasecomp-wslWindows subsystem for Linux related issues.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions