Yes, It looks like network.service fails and the glusterd.service is set up to start after network.service. In my case networking is set up by NetworkManager.service that starts later. There is no dependency on NetworkManager.service in glusterd.service
# cat /usr/lib/systemd/system/glusterd.service [Unit] Description=GlusterFS, a clustered file-system server Requires=rpcbind.service After=network.target rpcbind.service Before=network-online.target I will investigate why network.service fails and maybe try to add NetworkManager.service to "After" list. Thanks Jarek On Wed, Oct 17, 2018 at 6:30 AM Vijay Bellur <[email protected]> wrote: > On Tue, Oct 16, 2018 at 6:32 AM Jarosław Prokopowski < > [email protected]> wrote: > >> Hello, >> I'm new here. I tried to google the answer but was not successful. >> To give it a try I configured one node Gluster FS with 2 volumes on >> CentOS 7.5.1804. After server reboot the volumes start but are offline. Is >> there a way to fix that so they are online after reboot? >> >> >> > Upon server reboot, glusterd has the responsibility of re-starting bricks > for started volumes.Checking the brick & glusterd log files can help in > determining why the bricks did not start up. > > HTH, > Vijay >
_______________________________________________ Gluster-users mailing list [email protected] https://lists.gluster.org/mailman/listinfo/gluster-users
