Warning: file_get_contents(/data/phpspider/zhask/data//catemap/8/python-3.x/18.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Configuration SonarQube LDAP插件未启动/工作_Configuration_Active Directory_Ldap_Sonarqube - Fatal编程技术网

Configuration SonarQube LDAP插件未启动/工作

Configuration SonarQube LDAP插件未启动/工作,configuration,active-directory,ldap,sonarqube,Configuration,Active Directory,Ldap,Sonarqube,所以我开始工作,添加了LDAP插件,然后配置插件。按照LDAP插件页面上的说明进行操作。见下文。我能够启动sonar,它从配置的插件开始。启动时没有问题。我能够访问广告服务器,如果不能,您将看到一个错误 我正在使用: sonar-ldap-plugin-2.1.0.507.jar 和 sonarqube-6.2 记录在配置下面 LDAP configuration General Configuration sonar.security.realm=LDAP ldap.url=ldaps:/

所以我开始工作,添加了LDAP插件,然后配置插件。按照LDAP插件页面上的说明进行操作。见下文。我能够启动sonar,它从配置的插件开始。启动时没有问题。我能够访问广告服务器,如果不能,您将看到一个错误

我正在使用:

sonar-ldap-plugin-2.1.0.507.jar 和 sonarqube-6.2

记录在配置下面

 LDAP configuration
 General Configuration
sonar.security.realm=LDAP
ldap.url=ldaps://adaddres:636
ldap.bindDn=username
ldap.bindPassword=password
sonar.forceAuthentication=true

 User Configuration
ldap.user.baseDn=ou=Users,dc=name,dc=com
ldap.user.request=(&(objectClass=user)(sAMAccountName={login}))
ldap.user.realNameAttribute=cn
ldap.user.emailAttribute=mail

Spawning intermediate process...
Spawning daemon process...
--> Wrapper Started as Daemon
Using tick timer.
server listening on port 32000.
Command[0] : java
Command[1] : -Dsonar.wrapped=true
Command[2] : -Djava.awt.headless=true
Command[3] : -Xms8m
Command[4] : -Xmx8m
Command[5] : -Djava.library.path=./lib
Command[6] : -classpath
Command[7] : ../../lib/jsw/wrapper-3.2.3.jar:../../lib/sonar-application-6.2.jar
Command[8] : -Dwrapper.key=UFNH8UhRw1QG0rs4
Command[9] : -Dwrapper.port=32000
Command[10] : -Dwrapper.jvm.port.min=31000
Command[11] : -Dwrapper.jvm.port.max=31999
Command[12] : -Dwrapper.debug=TRUE
Command[13] : -Dwrapper.pid=8416
Command[14] : -Dwrapper.version=3.2.3
Command[15] : -Dwrapper.native_library=wrapper
Command[16] : -Dwrapper.service=TRUE
Command[17] : -Dwrapper.cpu.timeout=10
Command[18] : -Dwrapper.jvmid=1
Command[19] : org.tanukisoftware.wrapper.WrapperSimpleApp
Command[20] : org.sonar.application.App
Launching a JVM...
WrapperManager class initialized by thread: main  Using classloader: sun.misc.Launcher$AppClassLoader@33909752
Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
  Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.
Wrapper Manager: JVM #1
Running a 64-bit JVM.
Wrapper Manager: Registering shutdown hook
Wrapper Manager: Using wrapper
Load native library.  One or more attempts may fail if platform specific libraries do not exist.
Loading native library failed: libwrapper-linux-x86-64.so  Cause: java.lang.UnsatisfiedLinkError: no wrapper-linux-x86-64 in java.library.path
Loaded native library: libwrapper.so
Calling native initialization method.
Inside native WrapperManager initialization method
Java Version   : 1.8.0_121-b13 OpenJDK 64-Bit Server VM
Java VM Vendor : Oracle Corporation
Startup runner thread started.
Control event monitor thread started.
WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@85ede7b, args[]) called by thread: main
Communications runner thread started.
Open socket to wrapper...Wrapper-Connection
Failed attempt to bind using local port 31000
Opened Socket from 31001 to 32000
Send a packet KEY : UFNH8UhRw1QG0rs4
handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001])
accepted a socket from 127.0.0.1 on port 31001
read a packet KEY : UFNH8UhRw1QG0rs4
Got key from JVM: UFNH8UhRw1QG0rs4
send a packet LOW_LOG_LEVEL : 1
send a packet PING_TIMEOUT : 0
send a packet PROPERTIES : (Property Values)
Start Application.
send a packet START : start
Received a packet LOW_LOG_LEVEL : 1
Wrapper Manager: LowLogLevel from Wrapper is 1
Received a packet PING_TIMEOUT : 0
PingTimeout from Wrapper is 0
Received a packet PROPERTIES : (Property Values)
Received a packet START : start
calling WrapperListener.start()
Waiting for WrapperListener.start runner thread to complete.
WrapperListener.start runner thread started.
WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete.
WrapperSimpleApp: invoking main method
2017.03.09 15:47:38 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /root/sonarqube-6.2/temp
2017.03.09 15:47:38 INFO  app[][o.s.p.m.JavaProcessLauncher] Launch process[es]: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/bin/java -Djava.awt.headless=true -Xmx1G -Xms256m -Xss256k -Djna.nosys=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/root/sonarqube-6.2/temp -javaagent:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/search/* org.sonar.search.SearchServer /root/sonarqube-6.2/temp/sq-process1338894911459281579properties
Send a packet START_PENDING : 5000
read a packet START_PENDING : 5000
JVM signalled a start pending with waitHint of 5000 millis.
Send a packet START_PENDING : 5000
WrapperSimpleApp: start(args) end.  Main Completed=false, exitCode=null
2017.03.09 15:48:06 INFO  app[][o.s.p.m.Monitor] Process[es] is up
2017.03.09 15:48:06 INFO  app[][o.s.p.m.JavaProcessLauncher] Launch process[web]: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djruby.management.enabled=false -Djruby.compile.invokedynamic=false -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/root/sonarqube-6.2/temp -javaagent:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/server/*:/root/sonarqube-6.2/lib/jdbc/postgresql/postgresql-9.4.1209.jre7.jar org.sonar.server.app.WebServer /root/sonarqube-6.2/temp/sq-process3363637881001490888properties
send a packet PING : ping
Received a packet PING : ping
Send a packet PING : ok
read a packet PING : ok
Got ping response from JVM
send a packet PING : ping
2017.03.09 15:48:51 INFO  app[][o.s.p.m.Monitor] Process[web] is up
2017.03.09 15:48:51 INFO  app[][o.s.p.m.JavaProcessLauncher] Launch process[ce]: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/bin/java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Xmx512m -Xms128m -XX:+HeapDumpOnOutOfMemoryError -Djava.io.tmpdir=/root/sonarqube-6.2/temp -javaagent:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/lib/management-agent.jar -cp ./lib/common/*:./lib/server/*:./lib/ce/*:/root/sonarqube-6.2/lib/jdbc/postgresql/postgresql-9.4.1209.jre7.jar org.sonar.ce.app.CeServer /root/sonarqube-6.2/temp/sq-process6807607337463053511properties
send a packet PING : ping
Received a packet PING : ping
read a packet PING : ok
Got ping response from JVM
2017.03.09 15:49:07 INFO  app[][o.s.p.m.Monitor] Process[ce] is up
2017.03.09 15:49:07 INFO  app[][o.s.application.App] SonarQube is up

所以问题是什么?如果有任何错误,您会在web.log中看到什么?Sonarqubes文档说明:

1。通过编辑SONARQUBE_HOME/conf/sonar.properties文件(见下表)2来配置LDAP插件。重新启动SonarQube服务器并检查日志文件:INFO org.sonar.INFO Security realm:LDAP。。。信息o.s.p.l.LdapContextFactory测试LDAP连接:确定3.登录SonarQube 4.注销时,用户将显示登录页面(/sessions/login),在该页面中,他们可以通过传递适当的凭据选择以技术用户或域用户身份登录。当我尝试使用LDAP凭据登录时,它不起作用。我已经证实我使用的是正确的信条。但我无法登录。web.log还显示上的测试LDAP连接ldaps://adserver:636: OK 2017.03.10 14:02:15信息网络[][org.sonar.INFO]安全领域已启动