Bug Description
Database not ready .
To Reproduce
Steps to reproduce the behavior:
use k8s deploy 3 node follow doc
config 3 Mnode, everyone is Mnode
sometimes node happen error and the taos-check is failed, so it always restart
in the time, first node sync failed, because the second and three is
failed to start
cannot but reomve taos-check andredeploy finally, DND ERROR
failed to send status msg since Databasenot ready, need retry,
numOfEps:3 inUse:0
DND ERROR failed to send status msg since Database not ready, need retry, numOfEps:3 inUse:0
Environment:
OS: k8s
Memory, CPU, current Disk Space: 4C8G
TDengine Version : 3.0.16
Related
I working a react project, I am trying to push it in GitHub, I don't know where is the problem that it give such kind of an error.
The error is like:
error: RPC failed; curl 18 OpenSSL SSL_read: Connection was reset, errno 10054
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly
Everything up-to-date
If your repository is large, you may need to increase the buffer size, you increase the git buffer size with the following command,
git config http.postBuffer 524288000
Please read the http.postBuffer parameter in the git documentation, before performing this command,
https://git-scm.com/docs/git-config
I'm configuring a multi-physical node cluster deployment.
1. The controller node is on linux debian of Oracle virtual machine( bridge mode)
2. The agent node and data nodes are on the windows of the host machine.
3. Agent node and controller node can ping each other, but why can't the controller node find the agent node?
Agent node log:: HeartBeatsSender exception: Failed to read response header from the socket with IO error type
Agent node log:: Failed to enable TCP_NODELAY with error code 10038
data node log: AsynchronousRemoteExecutor::closeConnection to master #10 numConnections=0 Failed to connect
data node log: : close connection to master #10 with error: Failed to connect
Any suggestions will be appreciated.
why not deploy DolphinDB on linux os. there is no such case for deploying across different os.
I'm trying to upgrade our Flink cluster from 1.4.2 to 1.7.2
When I bring up the cluster, the task managers refuse to connect to the job managers with the following error.
2019-03-14 10:34:41,551 WARN akka.remote.ReliableDeliverySupervisor
- Association with remote system [akka.tcp://flink#cluster:22671] has failed, address is now gated for [50] ms. Reason: [Association failed with [akka.tcp://flink#cluster:22671]] Caused by: [cluster: Name or service not known]
Now, this works correctly if I add the following line into the /etc/hosts file.
x.x.x.x job-manager-address.com cluster
Why is Flink 1.7.2 connecting to JM using cluster in the address? Flink 1.4.2 used to have the job manager's address instead of the word cluster.
The jobmanager.sh script was being invoked with a second argument called cluster.
${Flink_HOME}/bin/jobmanager.sh start cluster
Prior to 1.5, the script expected an execution mode (local or cluster) but this is no longer the case. Invoking the script without the second argument solved this issue.
${Flink_HOME}/bin/jobmanager.sh start
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-1-7-2-Task-Manager-not-able-to-connect-to-Job-Manager-td26707.html
https://github.com/apache/flink/commit/d61664ca64bcb82c4e8ddf03a2ed38fe8edafa98
https://github.com/apache/flink/blob/c6878aca6c5aeee46581b4d6744b31049db9de95/flink-dist/src/main/flink-bin/bin/jobmanager.sh#L21-L25
Running Neo4j Desktop version 1.0.15. Trying to start DB causes the start fail:
Database failed to start:
DB [database-f8950fdd-6b5f-4fea-8c9f-e8457ee1da9a] 'v3.3.1' exited
with status 'KILLED'. Check the logs
Major Log parts are below
2018-02-26 23:03:38.004+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase#6411d3c8' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect". Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase#6411d3c8' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect".
Caused by: java.lang.RuntimeException: Error starting org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory, C:\Users\kiril\AppData\Roaming\Neo4j Desktop\Application\neo4jDatabases\database-f8950fdd-6b5f-4fea-8c9f-e8457ee1da9a\installation-3.3.1\data\databases\graph.db
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.backup.OnlineBackupKernelExtension#c6e0f32' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect".
Suppressed: org.neo4j.kernel.lifecycle.LifecycleException: Exception during graceful attempt to stop partially started component. Please use non suppressed exception to see original component failure.
Caused by: java.io.IOException: Unable to establish loopback connection
It might be your neo4j was still running.
I solved this problem by shutting down the database and restarting it.
Platform: Windows 10;
Neo4j Desktop version: 1.1.13
Open a commend-line window and go to the directory of your neo4j database.
run
bin\neo4j status
to check the status of your database.
If it is running, run
bin\neo4j stop
to shut down your database.
Then go back to the Neo4j Desktop, click the start button, and it could be symptom-free.
I had the same problem and the issue was resolved when I cloned the graph I was connecting. Thereafter, I could connect to the new graph without any problem.
On Development Server, whenever I add an taskqueue
taskqueue.add(queue_name='default', url='/_tasks/do_something', params={'key': 1})
The following error occurred
taskqueue_stub.py:1974] Task task1 failed to execute. This task will retry in 819.200 seconds
After getting some hint from this post:
http://www.rogerthat.net/2012/03/27/google-app-engine-push-task-queues-the-development-environment/
I suspect it could be something to do with the hostname. I am using http://test.me:8088 (where test.me point to 127.0.0.1 using host file). The problem goes away when I change the hostname (test.me) to "localhost".
I can't just use localhost due to some app configuration issue.
The code edit rogerthat.net point out is no longer valid.
Any other solution?