Bug 1333714 - i am not able to run gluster deamon, always failed , on 28 briock working
Summary: i am not able to run gluster deamon, always failed , on 28 briock working
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.7.11
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-06 08:10 UTC by Semaan
Modified: 2023-09-14 03:22 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-06-21 04:26:01 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Semaan 2016-05-06 08:10:18 UTC
Description of problem: not able to start gluster deamon


Version-Release number of selected component (if applicable): 3.7.11


here is output of journalctl -xn :

--
-- Unit glusterd.service has begun starting up.
May 06 10:01:31 gluster-hk7 systemd[1]: glusterd.service: control process exited, code=exited status=1
May 06 10:01:31 gluster-hk7 systemd[1]: Failed to start GlusterFS, a clustered file-system server.
-- Subject: Unit glusterd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit glusterd.service has failed.
--
-- The result is failed.
May 06 10:01:31 gluster-hk7 systemd[1]: Unit glusterd.service entered failed state.

Comment 1 Atin Mukherjee 2016-05-06 08:43:45 UTC
Please attach the glusterd log file present in /var/log/glusterfs/

Comment 2 Atin Mukherjee 2016-06-21 04:26:01 UTC
Since I've not heard anything from the reporter, I am closing this bug as information given is not sufficient to debug the issue. Feel free to reopen if you can provide us the logs and the reproducer.

Comment 3 Red Hat Bugzilla 2023-09-14 03:22:11 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.