canonical / canonical/microceph

microceph bootstrap - control.socket: connect: no such file or directory

Open
#452 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
396
Forks
74
Avg merge
2d 20h
Merged PRs (30d)
7

Description

# Issue report

I tried installing microceph on a x86_64 KVM vps machine with 4 cpus and 8 GB ram. But I run in the issue below. What can I do?

## What version of MicroCeph are you using ?

quincy/edge

## What are the steps to reproduce this issue ?

1. sudo snap install microceph --channel quincy/edge
2. sudo snap refresh --hold microceph
3. sudo microceph cluster bootstrap

## What happens (observed behaviour) ?

The third command returns `Error: Post "http://control.socket/cluster/control": dial unix /var/snap/microceph/common/state/control.socket: connect: no such file or directory`

## What were you expecting to happen ?

The cluster bootstraps

## Relevant logs, error output, etc.

## Additional comments.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the three listed snap and microceph commands on the reported x86_64 KVM setup, then inspect why /var/snap/microceph/common/state/control.socket is absent. The issue provides no logs or source entry point; done would require identifying the bootstrap failure and confirming that microceph cluster bootstrap succeeds or documenting the necessary fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cloud, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.