Anoop C S
2015-Jun-02 11:08 UTC
[Gluster-users] gluster-3.7 cannot start volume & ganesha feature cannot turn on problem
On 06/02/2015 01:42 PM, ??? wrote:> Hi all, > > I have two question for glusterfs-3.7 on fedora-22 > > I used to have a glusterfs cluster version 3.6.2. > > The following configuration can be work in version-3.6.2, but not > in version-3.7 > > > > There is 2 node for glusterfs. > > OS: fedora 22 > > Gluster: 3.7 on > https://download.gluster.org/pub/gluster/glusterfs/3.7/3.7.0/ > > > > #gluster peer probe n1 > > #gluster volume create ganesha n1:/data/brick1/gv0 > n2:/data/brick1/gv0 > > > > Volume Name: ganesha > > Type: Distribute > > Volume ID: cbb8d360-0025-419c-a12b-b29e4b91d7f8 > > Status: Created > > Number of Bricks: 2 > > Transport-type: tcp > > Bricks: > > Brick1: n1:/data/brick1/gv0 > > Brick2: n2:/data/brick1/gv0 > > Options Reconfigured: > > performance.readdir-ahead: on > > > > The problem to start the volume "ganesha" > > #gluster volume start ganesha > > > > volume start: ganesha: failed: Commit failed on localhost. Please > check the log file for more details. > > > > LOG in /var/log/glusterfs/bricks/data-brick1-gv0.log > > > > [2015-06-02 08:02:55.232923] I [MSGID: 100030] > [glusterfsd.c:2294:main] 0-/usr/sbin/glusterfsd: Started running > /usr/sbin/glusterfsd version 3.7.0 (args: /usr/sbin/glusterfsd -s > n2 --volfile-id ganesha.n2.data-brick1-gv0 -p > /var/lib/glusterd/vols/ganesha/run/n2-data-brick1-gv0.pid -S > /var/run/gluster/73ea8a39514304f5ebd440321d784386.socket > --brick-name /data/brick1/gv0 -l > /var/log/glusterfs/bricks/data-brick1-gv0.log --xlator-option > *-posix.glusterd-uuid=35547067-d343-4fee-802a-0e911b5a07cd > --brick-port 49157 --xlator-option > ganesha-server.listen-port=49157) > > [2015-06-02 08:02:55.284206] I > [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started > thread with index 1 > > [2015-06-02 08:02:55.397923] W [xlator.c:192:xlator_dynload] > 0-xlator: /usr/lib64/glusterfs/3.7.0/xlator/features/changelog.so: > undefined symbol: changelog_select_event >This particular error for "undefined symbol changelog_select_event" was identified recently and corresponding fix [ http://review.gluster.org/#/c/11004/ ] is already in master and hopefully will be available with v3.7.1.> [2015-06-02 08:02:55.397963] E [graph.y:212:volume_type] 0-parser: > Volume 'ganesha-changelog', line 30: type 'features/changelog' is > not valid or not found on this machine > > [2015-06-02 08:02:55.397992] E [graph.y:321:volume_end] 0-parser: > "type" not specified for volume ganesha-changelog > > [2015-06-02 08:02:55.398214] E [MSGID: 100026] > [glusterfsd.c:2149:glusterfs_process_volfp] 0-: failed to construct > the graph > > [2015-06-02 08:02:55.398423] W [glusterfsd.c:1219:cleanup_and_exit] > (--> 0-: received signum (0), shutting down > > > > I cannot google method to resolve it. > > Does anyone have across this problem? > > > > Another question is the feature in nfs-ganesha(version 2.2) > > The volume command I cannot turn on this feature. > > I try to copy the demo glusterfs-ganesha video but cannot work. > > Demo link: > https://plus.google.com/events/c9omal6366f2cfkcd0iuee5ta1o > > > > [root at n1 brick1]# gluster nfs-ganesha enable > > Enabling NFS-Ganesha requires Gluster-NFS to be disabled across the > trusted pool. Do you still want to continue? (y/n) y > > nfs-ganesha: failed: Commit failed on localhost. Please check the > log file for more details. > >Adding ganesha folks to the thread.> > Does anyone have the detail configuration? > > THANKS for giving advice. > > > > Regards, > > Ben > > > > > > > _______________________________________________ Gluster-users > mailing list Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users >
Meghana Madhusudhan
2015-Jun-02 13:01 UTC
[Gluster-users] gluster-3.7 cannot start volume & ganesha feature cannot turn on problem
Hi Anoop, Can you add the ID of the person who asked this question and forward the same? =======================================================================================================Can you please attach the glusterd logs here? You are having trouble to even start the volume here right? And also HA configuration is mandatory to use NFS-Ganesha in this release. Once you have the volume started, I can help you with the remaining steps in detail. Thanks Meghana ----- Original Message ----- From: "Anoop C S" <achiraya at redhat.com> To: gluster-users at gluster.org Cc: "Meghana Madhusudhan" <mmadhusu at redhat.com>, "Soumya Koduri" <skoduri at redhat.com> Sent: Tuesday, June 2, 2015 4:38:39 PM Subject: Re: [Gluster-users] gluster-3.7 cannot start volume & ganesha feature cannot turn on problem manadatroy On 06/02/2015 01:42 PM, ??? wrote:> Hi all, > > I have two question for glusterfs-3.7 on fedora-22 > > I used to have a glusterfs cluster version 3.6.2. > > The following configuration can be work in version-3.6.2, but not > in version-3.7 > > > > There is 2 node for glusterfs. > > OS: fedora 22 > > Gluster: 3.7 on > https://download.gluster.org/pub/gluster/glusterfs/3.7/3.7.0/ > > > > #gluster peer probe n1 > > #gluster volume create ganesha n1:/data/brick1/gv0 > n2:/data/brick1/gv0 > > > > Volume Name: ganesha > > Type: Distribute > > Volume ID: cbb8d360-0025-419c-a12b-b29e4b91d7f8 > > Status: Created > > Number of Bricks: 2 > > Transport-type: tcp > > Bricks: > > Brick1: n1:/data/brick1/gv0 > > Brick2: n2:/data/brick1/gv0 > > Options Reconfigured: > > performance.readdir-ahead: on > > > > The problem to start the volume "ganesha" > > #gluster volume start ganesha > > > > volume start: ganesha: failed: Commit failed on localhost. Please > check the log file for more details. > > > > LOG in /var/log/glusterfs/bricks/data-brick1-gv0.log > > > > [2015-06-02 08:02:55.232923] I [MSGID: 100030] > [glusterfsd.c:2294:main] 0-/usr/sbin/glusterfsd: Started running > /usr/sbin/glusterfsd version 3.7.0 (args: /usr/sbin/glusterfsd -s > n2 --volfile-id ganesha.n2.data-brick1-gv0 -p > /var/lib/glusterd/vols/ganesha/run/n2-data-brick1-gv0.pid -S > /var/run/gluster/73ea8a39514304f5ebd440321d784386.socket > --brick-name /data/brick1/gv0 -l > /var/log/glusterfs/bricks/data-brick1-gv0.log --xlator-option > *-posix.glusterd-uuid=35547067-d343-4fee-802a-0e911b5a07cd > --brick-port 49157 --xlator-option > ganesha-server.listen-port=49157) > > [2015-06-02 08:02:55.284206] I > [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started > thread with index 1 > > [2015-06-02 08:02:55.397923] W [xlator.c:192:xlator_dynload] > 0-xlator: /usr/lib64/glusterfs/3.7.0/xlator/features/changelog.so: > undefined symbol: changelog_select_event >This particular error for "undefined symbol changelog_select_event" was identified recently and corresponding fix [ http://review.gluster.org/#/c/11004/ ] is already in master and hopefully will be available with v3.7.1.> [2015-06-02 08:02:55.397963] E [graph.y:212:volume_type] 0-parser: > Volume 'ganesha-changelog', line 30: type 'features/changelog' is > not valid or not found on this machine > > [2015-06-02 08:02:55.397992] E [graph.y:321:volume_end] 0-parser: > "type" not specified for volume ganesha-changelog > > [2015-06-02 08:02:55.398214] E [MSGID: 100026] > [glusterfsd.c:2149:glusterfs_process_volfp] 0-: failed to construct > the graph > > [2015-06-02 08:02:55.398423] W [glusterfsd.c:1219:cleanup_and_exit] > (--> 0-: received signum (0), shutting down > > > > I cannot google method to resolve it. > > Does anyone have across this problem? > > > > Another question is the feature in nfs-ganesha(version 2.2) > > The volume command I cannot turn on this feature. > > I try to copy the demo glusterfs-ganesha video but cannot work. > > Demo link: > https://plus.google.com/events/c9omal6366f2cfkcd0iuee5ta1o > > > > [root at n1 brick1]# gluster nfs-ganesha enable > > Enabling NFS-Ganesha requires Gluster-NFS to be disabled across the > trusted pool. Do you still want to continue? (y/n) y > > nfs-ganesha: failed: Commit failed on localhost. Please check the > log file for more details. > >Adding ganesha folks to the thread.> > Does anyone have the detail configuration? > > THANKS for giving advice. > > > > Regards, > > Ben > > > > > > > _______________________________________________ Gluster-users > mailing list Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users >
Soumya Koduri
2015-Jun-02 13:03 UTC
[Gluster-users] gluster-3.7 cannot start volume & ganesha feature cannot turn on problem
On 06/02/2015 04:38 PM, Anoop C S wrote:> > > On 06/02/2015 01:42 PM, ??? wrote: >> Hi all, >> >> I have two question for glusterfs-3.7 on fedora-22 >> >> I used to have a glusterfs cluster version 3.6.2. >> >> The following configuration can be work in version-3.6.2, but not >> in version-3.7 >> >> >> >> There is 2 node for glusterfs. >> >> OS: fedora 22 >> >> Gluster: 3.7 on >> https://download.gluster.org/pub/gluster/glusterfs/3.7/3.7.0/ >> >> >> >> #gluster peer probe n1 >> >> #gluster volume create ganesha n1:/data/brick1/gv0 >> n2:/data/brick1/gv0 >> >> >> >> Volume Name: ganesha >> >> Type: Distribute >> >> Volume ID: cbb8d360-0025-419c-a12b-b29e4b91d7f8 >> >> Status: Created >> >> Number of Bricks: 2 >> >> Transport-type: tcp >> >> Bricks: >> >> Brick1: n1:/data/brick1/gv0 >> >> Brick2: n2:/data/brick1/gv0 >> >> Options Reconfigured: >> >> performance.readdir-ahead: on >> >> >> >> The problem to start the volume "ganesha" >> >> #gluster volume start ganesha >> >> >> >> volume start: ganesha: failed: Commit failed on localhost. Please >> check the log file for more details. >> >> >> >> LOG in /var/log/glusterfs/bricks/data-brick1-gv0.log >> >> >> >> [2015-06-02 08:02:55.232923] I [MSGID: 100030] >> [glusterfsd.c:2294:main] 0-/usr/sbin/glusterfsd: Started running >> /usr/sbin/glusterfsd version 3.7.0 (args: /usr/sbin/glusterfsd -s >> n2 --volfile-id ganesha.n2.data-brick1-gv0 -p >> /var/lib/glusterd/vols/ganesha/run/n2-data-brick1-gv0.pid -S >> /var/run/gluster/73ea8a39514304f5ebd440321d784386.socket >> --brick-name /data/brick1/gv0 -l >> /var/log/glusterfs/bricks/data-brick1-gv0.log --xlator-option >> *-posix.glusterd-uuid=35547067-d343-4fee-802a-0e911b5a07cd >> --brick-port 49157 --xlator-option >> ganesha-server.listen-port=49157) >> >> [2015-06-02 08:02:55.284206] I >> [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started >> thread with index 1 >> >> [2015-06-02 08:02:55.397923] W [xlator.c:192:xlator_dynload] >> 0-xlator: /usr/lib64/glusterfs/3.7.0/xlator/features/changelog.so: >> undefined symbol: changelog_select_event >> > > This particular error for "undefined symbol changelog_select_event" > was identified recently and corresponding fix [ > http://review.gluster.org/#/c/11004/ ] is already in master and > hopefully will be available with v3.7.1. > >> [2015-06-02 08:02:55.397963] E [graph.y:212:volume_type] 0-parser: >> Volume 'ganesha-changelog', line 30: type 'features/changelog' is >> not valid or not found on this machine >> >> [2015-06-02 08:02:55.397992] E [graph.y:321:volume_end] 0-parser: >> "type" not specified for volume ganesha-changelog >> >> [2015-06-02 08:02:55.398214] E [MSGID: 100026] >> [glusterfsd.c:2149:glusterfs_process_volfp] 0-: failed to construct >> the graph >> >> [2015-06-02 08:02:55.398423] W [glusterfsd.c:1219:cleanup_and_exit] >> (--> 0-: received signum (0), shutting down >> >> >> >> I cannot google method to resolve it. >> >> Does anyone have across this problem? >> >> >> >> Another question is the feature in nfs-ganesha(version 2.2) >> >> The volume command I cannot turn on this feature. >> >> I try to copy the demo glusterfs-ganesha video but cannot work. >> >> Demo link: >> https://plus.google.com/events/c9omal6366f2cfkcd0iuee5ta1o >> >> >> >> [root at n1 brick1]# gluster nfs-ganesha enable >> >> Enabling NFS-Ganesha requires Gluster-NFS to be disabled across the >> trusted pool. Do you still want to continue? (y/n) y >> >> nfs-ganesha: failed: Commit failed on localhost. Please check the >> log file for more details. >> >>As you may have seen in the demo video, there are many pre-requisites to be followed before enabling nfs-ganesha. Can you please re-check if you have all those steps taken care of ? Also look at the logs '/var/log/ganesha.log' and '/var/log/messages' for any specific errors logged. Thanks, Soumya> > Adding ganesha folks to the thread. > >> >> Does anyone have the detail configuration? >> >> THANKS for giving advice. >> >> >> >> Regards, >> >> Ben >> >> >> >> >> >> >> _______________________________________________ Gluster-users >> mailing list Gluster-users at gluster.org >> http://www.gluster.org/mailman/listinfo/gluster-users >>
Anoop C S
2015-Jun-02 15:07 UTC
[Gluster-users] gluster-3.7 cannot start volume & ganesha feature cannot turn on problem
-------- Forwarded Message -------- Subject: Re: [Gluster-users] gluster-3.7 cannot start volume & ganesha feature cannot turn on problem Date: Tue, 2 Jun 2015 09:01:38 -0400 (EDT) From: Meghana Madhusudhan <mmadhusu at redhat.com> To: Anoop C S <achiraya at redhat.com> CC: gluster-users at gluster.org, Soumya Koduri <skoduri at redhat.com> Hi Anoop, Can you add the ID of the person who asked this question and forward the same? =======================================================================================================Can you please attach the glusterd logs here? You are having trouble to even start the volume here right? And also HA configuration is mandatory to use NFS-Ganesha in this release. Once you have the volume started, I can help you with the remaining steps in detail. Thanks Meghana ----- Original Message ----- From: "Anoop C S" <achiraya at redhat.com> To: gluster-users at gluster.org Cc: "Meghana Madhusudhan" <mmadhusu at redhat.com>, "Soumya Koduri" <skoduri at redhat.com> Sent: Tuesday, June 2, 2015 4:38:39 PM Subject: Re: [Gluster-users] gluster-3.7 cannot start volume & ganesha feature cannot turn on problem manadatroy On 06/02/2015 01:42 PM, ??? wrote:> Hi all, > > I have two question for glusterfs-3.7 on fedora-22 > > I used to have a glusterfs cluster version 3.6.2. > > The following configuration can be work in version-3.6.2, but not > in version-3.7 > > > > There is 2 node for glusterfs. > > OS: fedora 22 > > Gluster: 3.7 on > https://download.gluster.org/pub/gluster/glusterfs/3.7/3.7.0/ > > > > #gluster peer probe n1 > > #gluster volume create ganesha n1:/data/brick1/gv0 > n2:/data/brick1/gv0 > > > > Volume Name: ganesha > > Type: Distribute > > Volume ID: cbb8d360-0025-419c-a12b-b29e4b91d7f8 > > Status: Created > > Number of Bricks: 2 > > Transport-type: tcp > > Bricks: > > Brick1: n1:/data/brick1/gv0 > > Brick2: n2:/data/brick1/gv0 > > Options Reconfigured: > > performance.readdir-ahead: on > > > > The problem to start the volume "ganesha" > > #gluster volume start ganesha > > > > volume start: ganesha: failed: Commit failed on localhost. Please > check the log file for more details. > > > > LOG in /var/log/glusterfs/bricks/data-brick1-gv0.log > > > > [2015-06-02 08:02:55.232923] I [MSGID: 100030] > [glusterfsd.c:2294:main] 0-/usr/sbin/glusterfsd: Started running > /usr/sbin/glusterfsd version 3.7.0 (args: /usr/sbin/glusterfsd -s > n2 --volfile-id ganesha.n2.data-brick1-gv0 -p > /var/lib/glusterd/vols/ganesha/run/n2-data-brick1-gv0.pid -S > /var/run/gluster/73ea8a39514304f5ebd440321d784386.socket > --brick-name /data/brick1/gv0 -l > /var/log/glusterfs/bricks/data-brick1-gv0.log --xlator-option > *-posix.glusterd-uuid=35547067-d343-4fee-802a-0e911b5a07cd > --brick-port 49157 --xlator-option > ganesha-server.listen-port=49157) > > [2015-06-02 08:02:55.284206] I > [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started > thread with index 1 > > [2015-06-02 08:02:55.397923] W [xlator.c:192:xlator_dynload] > 0-xlator: /usr/lib64/glusterfs/3.7.0/xlator/features/changelog.so: > undefined symbol: changelog_select_event >This particular error for "undefined symbol changelog_select_event" was identified recently and corresponding fix [ http://review.gluster.org/#/c/11004/ ] is already in master and hopefully will be available with v3.7.1.> [2015-06-02 08:02:55.397963] E [graph.y:212:volume_type] 0-parser: > Volume 'ganesha-changelog', line 30: type 'features/changelog' is > not valid or not found on this machine > > [2015-06-02 08:02:55.397992] E [graph.y:321:volume_end] 0-parser: > "type" not specified for volume ganesha-changelog > > [2015-06-02 08:02:55.398214] E [MSGID: 100026] > [glusterfsd.c:2149:glusterfs_process_volfp] 0-: failed to construct > the graph > > [2015-06-02 08:02:55.398423] W [glusterfsd.c:1219:cleanup_and_exit] > (--> 0-: received signum (0), shutting down > > > > I cannot google method to resolve it. > > Does anyone have across this problem? > > > > Another question is the feature in nfs-ganesha(version 2.2) > > The volume command I cannot turn on this feature. > > I try to copy the demo glusterfs-ganesha video but cannot work. > > Demo link: > https://plus.google.com/events/c9omal6366f2cfkcd0iuee5ta1o > > > > [root at n1 brick1]# gluster nfs-ganesha enable > > Enabling NFS-Ganesha requires Gluster-NFS to be disabled across the > trusted pool. Do you still want to continue? (y/n) y > > nfs-ganesha: failed: Commit failed on localhost. Please check the > log file for more details. > >Adding ganesha folks to the thread.> > Does anyone have the detail configuration? > > THANKS for giving advice. > > > > Regards, > > Ben > > > > > > > _______________________________________________ Gluster-users > mailing list Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users >
Anoop C S
2015-Jun-02 15:18 UTC
[Gluster-users] gluster-3.7 cannot start volume & ganesha feature cannot turn on problem
Can you please attach the glusterd logs here? You are having trouble to even start the volume here right? And also HA configuration is mandatory to use NFS-Ganesha in this release. Once you have the volume started, I can help you with the remaining steps in detail. Thanks Meghana ----- Original Message ----- From: "Anoop C S" <achiraya at redhat.com> To: gluster-users at gluster.org Cc: "Meghana Madhusudhan" <mmadhusu at redhat.com>, "Soumya Koduri" <skoduri at redhat.com> Sent: Tuesday, June 2, 2015 4:38:39 PM Subject: Re: [Gluster-users] gluster-3.7 cannot start volume & ganesha feature cannot turn on problem manadatroy On 06/02/2015 01:42 PM, ??? wrote:> Hi all, > > I have two question for glusterfs-3.7 on fedora-22 > > I used to have a glusterfs cluster version 3.6.2. > > The following configuration can be work in version-3.6.2, but not > in version-3.7 > > > > There is 2 node for glusterfs. > > OS: fedora 22 > > Gluster: 3.7 on > https://download.gluster.org/pub/gluster/glusterfs/3.7/3.7.0/ > > > > #gluster peer probe n1 > > #gluster volume create ganesha n1:/data/brick1/gv0 > n2:/data/brick1/gv0 > > > > Volume Name: ganesha > > Type: Distribute > > Volume ID: cbb8d360-0025-419c-a12b-b29e4b91d7f8 > > Status: Created > > Number of Bricks: 2 > > Transport-type: tcp > > Bricks: > > Brick1: n1:/data/brick1/gv0 > > Brick2: n2:/data/brick1/gv0 > > Options Reconfigured: > > performance.readdir-ahead: on > > > > The problem to start the volume "ganesha" > > #gluster volume start ganesha > > > > volume start: ganesha: failed: Commit failed on localhost. Please > check the log file for more details. > > > > LOG in /var/log/glusterfs/bricks/data-brick1-gv0.log > > > > [2015-06-02 08:02:55.232923] I [MSGID: 100030] > [glusterfsd.c:2294:main] 0-/usr/sbin/glusterfsd: Started running > /usr/sbin/glusterfsd version 3.7.0 (args: /usr/sbin/glusterfsd -s > n2 --volfile-id ganesha.n2.data-brick1-gv0 -p > /var/lib/glusterd/vols/ganesha/run/n2-data-brick1-gv0.pid -S > /var/run/gluster/73ea8a39514304f5ebd440321d784386.socket > --brick-name /data/brick1/gv0 -l > /var/log/glusterfs/bricks/data-brick1-gv0.log --xlator-option > *-posix.glusterd-uuid=35547067-d343-4fee-802a-0e911b5a07cd > --brick-port 49157 --xlator-option > ganesha-server.listen-port=49157) > > [2015-06-02 08:02:55.284206] I > [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started > thread with index 1 > > [2015-06-02 08:02:55.397923] W [xlator.c:192:xlator_dynload] > 0-xlator: /usr/lib64/glusterfs/3.7.0/xlator/features/changelog.so: > undefined symbol: changelog_select_event >This particular error for "undefined symbol changelog_select_event" was identified recently and corresponding fix [ http://review.gluster.org/#/c/11004/ ] is already in master and hopefully will be available with v3.7.1.> [2015-06-02 08:02:55.397963] E [graph.y:212:volume_type] 0-parser: > Volume 'ganesha-changelog', line 30: type 'features/changelog' is > not valid or not found on this machine > > [2015-06-02 08:02:55.397992] E [graph.y:321:volume_end] 0-parser: > "type" not specified for volume ganesha-changelog > > [2015-06-02 08:02:55.398214] E [MSGID: 100026] > [glusterfsd.c:2149:glusterfs_process_volfp] 0-: failed to > construct the graph > > [2015-06-02 08:02:55.398423] W > [glusterfsd.c:1219:cleanup_and_exit] (--> 0-: received signum (0), > shutting down > > > > I cannot google method to resolve it. > > Does anyone have across this problem? > > > > Another question is the feature in nfs-ganesha(version 2.2) > > The volume command I cannot turn on this feature. > > I try to copy the demo glusterfs-ganesha video but cannot work. > > Demo link: > https://plus.google.com/events/c9omal6366f2cfkcd0iuee5ta1o > > > > [root at n1 brick1]# gluster nfs-ganesha enable > > Enabling NFS-Ganesha requires Gluster-NFS to be disabled across > the trusted pool. Do you still want to continue? (y/n) y > > nfs-ganesha: failed: Commit failed on localhost. Please check the > log file for more details. > >Adding ganesha folks to the thread.> > Does anyone have the detail configuration? > > THANKS for giving advice. > > > > Regards, > > Ben > > > > > > > _______________________________________________ Gluster-users > mailing list Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users >