It’s outrageous
I’ve been wrong before
Finally, I adjusted the time to 200000
Then it is created successfully.
Then I jumped to 2000
Then test:
It’s outrageous that it was created successfully
It’s outrageous
I’ve been wrong before
Finally, I adjusted the time to 200000
Then it is created successfully.
Then I jumped to 2000
Then test:
It’s outrageous that it was created successfully
1. Check the error status:
./zkserver.sh status
check the error reason:
./zkserver.sh start forest
The default server port number is 8080, which has been occupied.
go to the configuration file to modify the default server port number:
admin. Serverport = 2180
Weblogic error message:
<Error> <Console> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <webuser> <> <> <1624366734323> <BEA-240003> <Administration Console encountered the following error: weblogic.management.provider.UpdateException: [Management:141191]The prepare phase of the configuration update failed with an exception.
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateDeploymentContext(RuntimeAccessDeploymentReceiverService.java:777)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentReceiverCallbackDeliverer.java:147)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCallbackDeliverer.java:28)
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:203)
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.handlePrepare(ReceivedPrepare.java:112)
at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.receivedPrepare(ReceivedPrepare.java:52)
at weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(TargetRequestImpl.java:211)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$1.run(CommonMessageReceiver.java:457)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:553)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
Caused by: java.lang.Throwable: Substituted for the exception com.bea.xml.SchemaTypeLoaderException which lacks a String contructor, original message - XML-BEANS compiled schema: Could not locate compiled schema resource schemacom_bea_xml/system/s0BC706AE0F5CDA9F4183EB0C5C434EEA/keystores8f60elemtype.xsb (schemacom_bea_xml.system.s0BC706AE0F5CDA9F4183EB0C5C434EEA.keystores8f60elemtype) - code 0
at com.bea.xbean.schema.SchemaTypeSystemImpl$XsbReader.<init>(SchemaTypeSystemImpl.java:1519)
at com.bea.xbean.schema.SchemaTypeSystemImpl.resolveHandle(SchemaTypeSystemImpl.java:3505)
at com.bea.xml.SchemaComponent$Ref.getComponent(SchemaComponent.java:113)
at com.bea.xml.SchemaType$Ref.get(SchemaType.java:872)
at com.bea.xbean.schema.SchemaParticleImpl.getType(SchemaParticleImpl.java:194)
at com.bea.xbean.validator.Validator.beginEvent(Validator.java:389)
at com.bea.xbean.validator.Validator.nextEvent(Validator.java:241)
at com.bea.xbean.validator.ValidatingXMLStreamReader.validate_event(ValidatingXMLStreamReader.java:581)
at com.bea.xbean.validator.ValidatingXMLStreamReader.next(ValidatingXMLStreamReader.java:546)
at com.bea.xbean.richParser.XMLStreamReaderExtImpl.next(XMLStreamReaderExtImpl.java:1122)
at com.bea.staxb.runtime.internal.MarshalStreamUtils.advanceToNextStartElement(MarshalStreamUtils.java:120)
at com.bea.staxb.runtime.internal.UnmarshalResult.advanceToNextStartElement(UnmarshalResult.java:830)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:57)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184)
at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156)
at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:67)
at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199)
at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:67)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:327)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.handleConfigTreeLoad(RuntimeAccessDeploymentReceiverService.java:1092)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.updateDeploymentContext(RuntimeAccessDeploymentReceiverService.java:697)
>
Because SSL is configured in Weblogic, an error is reported during activation. There is a cluster in the project, and this error occurs,
solve:
Stop the server services corresponding to other cluster nodes, and then modify and activate them. At this time, the changes can be activated normally.
If one node is configured in the cluster, other nodes need to be configured.
Start zookeeper under windows and prompt zookeeper audit is disabled; Indicates that the startup failed, as follows:
Reason: I’m running zookeeper version 3.6.3. It seems that there will be this phenomenon in versions above 3.6. The reason is that the newly added audit log of zookeeper is turned off by default when the new version is started, so this situation occurs.
terms of settlement:
1. In the configuration file conf of zookeeper, open the file zoo.cfg:
Attachment: the zoo.cfg file is a copy of the zoo_ Sample.cfg file. In the zoo.cfg file, the data storage path and the port number used when starting zookeeper are modified.
2. Modify the zoo.cfg file by adding admin.enable = true
3. Save, restart zookeeper (double-click zkserver. CMD in bin directory), start successfully!
Hope to help you!!
div>
Zookeeper connection timeout problem, and refused to connect to solve the problem
Code exception
processing method
1. Check and close firewall
2. Check VIM/etc/hosts
port conflict
delete 127.0.0.1 in the first line
Error: keepererrorcode = nonode for/HBase/master error occurred when inputting command in HBase shell
Error screenshot:
solution:
solution 1: close zookeeper, delete the version-2 folder under your own dataDir path, and then restart (used)
solution 2: add a paragraph in hbase-site.xml
<property>
<name>hbase.unsafe.stream.capability.enforce</name>
<value>false</value>
</property>
The method can be used for the purpose of applying a tube, and for the purpose of this problem, I would like to say that there are three things: Core site HDFS site HBase site HBase. Rootdir . Plan 5: we have a large amount of disambiguation ( s> *) cause: namede on namespaceid and datanode It was found that the number of nodes under the nodal de nodal de nodal de paceme was not significant. The first language resolution method is: dfs.datanode. Data. Dir in dandoop Hadoop S>
The second edition disambiguation method: clusterid in data under current/current versioning.
div>
2014-12-19 01:05:42,141 (lifecycleSupervisor-1-1) [WARN – org.apache.flume.sink.AbstractRpcSink.start(AbstractRpcSink. java:294 )] Unable to create Rpc client using hostname: xxx.xxx.xxx.xxx, port: 41100
org.apache.flume.FlumeException: NettyAvroRpcClient { host: 121.41.49.51, port: 41100 }: RPC connection error
This problem occurs when flume uses Avro to accept data.
First, let’s see if the port of the connected server is monitored
If you want to send data to port 4383 of 192.168.1.1, you need a server listening to this window, otherwise RPC connection failure will occur
1. Install image
docker pull zookeeper:3.6.2
2. Start ZK
docker run --privileged=true -d --name zookeeper -p 2181:2181 \ -v /home/workspace/zookeeper/data:/data \ -v /home/workspace/zookeeper/logs:/datalog \ -d zookeeper:3.6.2
3. Go to ZK image summary
docker exec -it zookeeper /bin/bash
3. View ZK log
docker logs -f zookeeper
4. Validation and FAQs
Refer to my last article:
https://blog.csdn.net/qq_ 42390636/article/details/114986157
Kafka prompts when executing the following command:
bin/kafka-console-consumer.sh --zookeeper localhost102:2181 --topic test
WARN [console-consumer-87796_ localhost002-1592779486563-9b43649b], no brokers found when trying to rebalance.( kafka.consumer.ZookeeperConsumerConnector )
The reason is that the Kafka process is not started or there is no Kafka cluster information on zookeeper
[root@localhost002 ~]# jps
3667 DataNode
3365 ResourceManager
21446 QuorumPeerMain
23386 Jps
3230 NodeManager
Solve the problem after starting Kafka
When installing zookeeper under Linux, the following error occurs:
[ hadoop@hadoop-master bin]$ ./ zkServer.sh start
JMX disabled by user request
Using config: /opt/zookeeper-3.3.3/bin/../conf/ zoo.cfg
Starting zookeeper …
STARTED
[ hadoop@hadoop-master bin]$ 2011-07-05 10:33:57,587 – INFO [ main:QuorumPeerConfig@90 ] – Reading configuration from: /opt/zookeeper-3.3.3/bin/../conf/ zoo.cfg
2011-07-05 10:33:57,596 – WARN [ main:QuorumPeerMain@105 ] – Either no config or no quorum defined in config, running in standalone mode
Exception in thread “main” java.lang.NoSuchMethodError : method java.lang.management . ManagementFactory.getPlatformMBeanServer with signature () Ljavax.management.MBeanServer ; was not found.
at org.apache.zookeeper . jmx.ManagedUtil.registerLog4jMBeans ( ManagedUtil.java:48 )
at org.apache.zookeeper . server.ZooKeeperServerMain.initializeAndRun ( ZooKeeperServerMain.java:73 )
at org.apache.zookeeper . server.ZooKeeperServerMain.main ( ZooKeeperServerMain.java:51 )
at org.apache.zookeeper . server.quorum.QuorumPeerMain .initializeAndRun( QuorumPeerMain.java:108 )
at org.apache.zookeeper . server.quorum.QuorumPeerMain .main( QuorumPeerMain.java:76 )
Found, not found java.lang.management The next way. If you are using the standard JDK, such an error should not occur. So check it out zkServer.sh Script. It is found that the script to start the Java program is as follows:
Bash code
java “- Dzookeeper.log.dir= ${ZOO_ LOG_ DIR}” “- Dzookeeper.root.logger= ${ZOO_ LOG4J_ PROP}” \
-cp “$CLASSPATH” $JVMFLAGS $ZOOMAIN “$ZOOCFG” &
Executing Java command directly under Linux, the output is as follows:
Bash code
[ hadoop@hadoop-master bin]$ java
Usage: gij [OPTION] … CLASS [ARGS] …
to invoke CLASS.main , or
gij -jar [OPTION] … JARFILE [ARGS] …
to execute a jar file
Try `gij –help’ for more information.
Obviously, zkServer.sh Incorrect java used. Use the Java of Gij. To solve this problem, simply change the script to:
Bash code
$JAVA_ HOME/bin/java “- Dzookeeper.log.dir= ${ZOO_ LOG_ DIR}” “- Dzookeeper.root.logger= ${ZOO_ LOG4J_ PROP}” \
-cp “$CLASSPATH” $JVMFLAGS $ZOOMAIN “$ZOOCFG” &
After this modification, it can run normally.
It is mainly to replace the system’s own Java path, so that he can identify his own installed Java (it’s better to delete the system’s own JDK before installing software)
For example, zookeeper was not started repeatedly, but was started for the first time. The reason may be that zookeeper cluster is not shut down normally, such as abnormal shutdown, power failure, etc. Zookeeper saves the last started process number in zookeeper_ server.pid In this file, this file is in zookeeper_ HOME/conf/ zoo.cfg In the directory specified by the dataDir configuration item in, delete the file directly, and then restart zookeeper.
Friendly tips: do not shut down the virtual machine directly, but use the script to shut down the cluster first, otherwise some unexpected exceptions may appear next time.
Tar ZXVF – apache – they are – 3.6.1 track – bin. Tar. Gz
Create folders
mkdir /usr/local/
3. Move folders
Mv apache – they are – 3.6.1 track – bin/usr/local /
4. Rename configuration files
CD/usr/local/apache – they are – 3.6.1 track – bin/conf
Cp zoo_sample. CFG zoo. CFG
5. Modify the configuration file
Vi Zoo. CFG, modify the corresponding content as follows
dataDir=/usr/local/apache-zookeeper-3.6.1-bin/data
# new
admin.serverPort=18888
6, start,
CD/usr/local/apache – they are – 3.6.1 track – bin/bin
./zkServer.sh start
7, test,
netstat -anp|grep 2181