server.allow-insecure aka rpc-auth-allow-insecure option does not work
2013-07-09 14:55
429 查看
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Groups: None (edit) |
DescriptionLouis Zuckerman 2013-06-27 22:08:20 EDT Description of problem: I need to allow clients to connect to the volume from insecure (unprivileged) ports >1024. There appears to be an option in 3.4 to do this: server.allow-insecure. However when I set this to "ON" or "on" it has no effect, glusterd still refuses to serve clients on unprivileged ports. Version-Release number of selected component (if applicable): 3.4.0beta3 I'll update this bug with steps to reproduce as soon as I have a good procedure for you. Thanks! Comment 1Louis Zuckerman 2013-06-27 22:30:34 EDT Shortly after I filed this bug Vijay chatted me on IRC to let me know that in addition to setting server.allow-insecure to on, I also needed to manually add an option to glusterd.vol: option rpc-auth-allow-insecure on I restarted glusterd with the updated volfile and now I can use insecure ports. Thanks again! Comment 2Louis Zuckerman 2013-06-27 22:51:33 EDT Ok now I have a real bug to report.... After making the change above to glusterd.vol my insecure client program is able to communicate with glusterd to fetch the volfile, however.... When I try to create a file in the volume, nothing happens -- no error, no crash, no file created. Then when I try to write data into that file, the process crashes and I get a core dump. To reproduce this problem see the instructions in the readme.md file of the libgfapi-jni project: https://github.com/semiosis/libgfapi-jni Those instructions include a "sudo bash" command which will run the test as root. But DO NOT run it as root to reproduce this problem. The test succeeds when run as root, but fails when run as an unprivileged user. Comment 3Louis Zuckerman 2013-06-27 23:00:36 EDT Ok I feel dumb. The insecure client couldn't create or write to the file because the volume permissions didn't allow it. Once i did a chmod ugo+rwx on the volume, it worked. PEBKAC |
相关文章推荐
- ADO.NET Entity Framework: The version of SQL Server in use does not support datatype 'datetime2'
- SyntaxError:Strict mode does not allow function declaration in a lexically nested
- 如何解决sql server2005的“不允许远程连接”错误.(how to resolve the error: "SQL Server does not allow remote connections" for SQL Server2005)
- SyntaxError:Strict mode does not allow function declaration in a lexically nested statement.
- SyntaxError:Strict mode does not allow function declaration in a lexically nested statement.
- parameter "timeout" in socketchannel does not work
- VNC Server in Virtual Mode does not start correctly on Ubuntu 12.04
- Longhorn's Server Core installation option may does not include the server graphic user interface (GUI)
- ie does not support the event of the option in select control
- Service 'china' of type 'MapServer' does not exist or is inaccessible
- JAVA+ Proxool+ SQLserver 2008 “signer information does not match signer information of other classes in the same package”
- HiveServer2 does not return ResultSets in UTF-8 encoding 解决HiveServer2 JDBC显示UTF8乱码的问题
- SyntaxError:Strict mode does not allow function declaration in a lexically nested statement.
- httpModules remove does not work in a folder or virtual directory
- Error: The version of SQL Server in use does not support datatype 'datetime2'
- ERROR: The version of SQL Server in use does not support datatype 'datetime2'.
- SQL Server error "Xml data type is not supported in distributed queries" and workaround for it
- server does not support secure connections
- The Apache Axis2 Web service runtime in Tomcat v6.0 Server does not support the service project
- Error: The version of SQL Server in use does not support datatype 'datetime2