Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cluster Slave Error #138

Open
ChoByoungHwan opened this issue Apr 4, 2022 · 2 comments
Open

Cluster Slave Error #138

ChoByoungHwan opened this issue Apr 4, 2022 · 2 comments

Comments

@ChoByoungHwan
Copy link

Cluster configuration and startup
Slave error occurred
I can't figure out the cause.
Can I get help?

Salve Error Log #1
[359840] 04 Apr 16:32:19.336 # Background AOF rewrite terminated by signal 1
[359840] 04 Apr 16:32:21.156 * Background append only file rewriting started by pid 104308
[359840] 04 Apr 16:32:21.270 # fork operation failed
[359840] 04 Apr 16:32:21.278 # Background AOF rewrite terminated by signal 1
[359840] 04 Apr 16:32:23.067 * Background append only file rewriting started by pid 134988
[359840] 04 Apr 16:32:23.181 # fork operation failed
[359840] 04 Apr 16:32:23.189 # Background AOF rewrite terminated by signal 1
[359840] 04 Apr 16:32:24.995 * Background append only file rewriting started by pid 172612
[359840] 04 Apr 16:32:24.995 - Accepted cluster node 127.0.0.1:55056
[359840] 04 Apr 16:32:24.996 - Accepted cluster node 127.0.0.1:55055
[359840] 04 Apr 16:32:25.104 # fork operation failed
[359840] 04 Apr 16:32:25.113 # Background AOF rewrite terminated by signal 1
[359840] 04 Apr 16:32:26.938 * Background append only file rewriting started by pid 18280
[359840] 04 Apr 16:32:27.054 # fork operation failed
[359840] 04 Apr 16:32:27.063 # Background AOF rewrite terminated by signal 1
[359840] 04 Apr 16:32:28.864 * Background append only file rewriting started by pid 27076
[359840] 04 Apr 16:32:28.977 # fork operation failed
[359840] 04 Apr 16:32:28.985 # Background AOF rewrite terminated by signal 1
[359840] 04 Apr 16:32:30.792 * Background append only file rewriting started by pid 85844
[359840] 04 Apr 16:32:30.792 - Accepted cluster node 127.0.0.1:55066
[359840] 04 Apr 16:32:30.792 - Accepted cluster node 127.0.0.1:55065
[359840] 04 Apr 16:32:30.902 # fork operation failed
[359840] 04 Apr 16:32:30.910 # Background AOF rewrite terminated by signal 1
[359840] 04 Apr 16:32:32.699 * Background append only file rewriting started by pid 187100
[359840] 04 Apr 16:32:32.812 # fork operation failed
[359840] 04 Apr 16:32:32.821 # Background AOF rewrite terminated by signal 1
[359840] 04 Apr 16:32:34.641 * Background append only file rewriting started by pid 188348
[359840] 04 Apr 16:32:34.641 - Accepted cluster node 127.0.0.1:55072
[359840] 04 Apr 16:32:34.741 # fork operation failed
[359840] 04 Apr 16:32:34.750 # Background AOF rewrite terminated by signal 1
[359840] 04 Apr 16:32:36.520 * Background append only file rewriting started by pid 31420
[359840] 04 Apr 16:32:36.521 - Accepted cluster node 127.0.0.1:55076
[359840] 04 Apr 16:32:36.521 - Accepted cluster node 127.0.0.1:55075
[359840] 04 Apr 16:32:36.636 # fork operation failed
[359840] 04 Apr 16:32:36.645 # Background AOF rewrite terminated by signal 1
[359840] 04 Apr 16:32:38.435 * Background append only file rewriting started by pid 183224
[359840] 04 Apr 16:32:38.546 # fork operation failed
[359840] 04 Apr 16:32:38.554 # Background AOF rewrite terminated by signal 1
[359840] 04 Apr 16:32:40.352 * Background append only file rewriting started by pid 185932
[359840] 04 Apr 16:32:40.463 # fork operation failed

Salve Error Log #2
[229940] 04 Apr 16:33:20.914 #
*** FATAL CONFIG FILE ERROR ***

[229940] 04 Apr 16:33:20.915 # Reading the configuration file, at line 0

[229940] 04 Apr 16:33:20.915 # >>> '(null)'

[229940] 04 Apr 16:33:20.915 # replicaof directive not allowed in cluster mode

[185276] 04 Apr 16:33:22.833 #
*** FATAL CONFIG FILE ERROR ***

[185276] 04 Apr 16:33:22.833 # Reading the configuration file, at line 0

[185276] 04 Apr 16:33:22.833 # >>> '(null)'

[185276] 04 Apr 16:33:22.833 # replicaof directive not allowed in cluster mode

[217312] 04 Apr 16:33:24.729 #
*** FATAL CONFIG FILE ERROR ***

[217312] 04 Apr 16:33:24.730 # Reading the configuration file, at line 0

[217312] 04 Apr 16:33:24.730 # >>> '(null)'

[217312] 04 Apr 16:33:24.730 # replicaof directive not allowed in cluster mode

[226940] 04 Apr 16:33:26.653 #
*** FATAL CONFIG FILE ERROR ***

[226940] 04 Apr 16:33:26.654 # Reading the configuration file, at line 0

[226940] 04 Apr 16:33:26.654 # >>> '(null)'

[226940] 04 Apr 16:33:26.654 # replicaof directive not allowed in cluster mode

[211660] 04 Apr 16:33:28.598 #
*** FATAL CONFIG FILE ERROR ***

[211660] 04 Apr 16:33:28.598 # Reading the configuration file, at line 0

[211660] 04 Apr 16:33:28.598 # >>> '(null)'

[211660] 04 Apr 16:33:28.598 # replicaof directive not allowed in cluster mode

[227568] 04 Apr 16:33:30.512 #
*** FATAL CONFIG FILE ERROR ***

[227568] 04 Apr 16:33:30.513 # Reading the configuration file, at line 0

[227568] 04 Apr 16:33:30.513 # >>> '(null)'

[227568] 04 Apr 16:33:30.513 # replicaof directive not allowed in cluster mode

@trentbarry1
Copy link

trentbarry1 commented Apr 22, 2022

I am seeing this error as well after upgrading a cluster from 5.0.10 to 5.0.14.1.
Masters OK, Slaves have the problem.
Built a new cluster (since for upgrade I did the binary file replacement). Same issue on the new cluster.

Turning off appendonly in the slave allows it to work...and it can become a master. but basically any node that has appendonly yes can not startup or become a slave.

This looks to be related to the changes in 5.0.14.1.
Changed to 5.0.14 and it works fine with the slaves and appendonly yes.

I am not currently using additonal redis modules so I feel that 5.0.14 is good for me at the moment.

??? loadServerConfig(configfile,options,NULL);.

@ShenXiuLi
Copy link

[28356] 10 Apr 19:49:44.131 * Connecting to MASTER 109.242.233.245:22
[28356] 10 Apr 19:49:44.132 * MASTER <-> REPLICA sync started
[28356] 10 Apr 19:50:05.134 * Non blocking connect for SYNC fired the event.
[28356] 10 Apr 19:50:05.135 # Sending command to master in replication handshake: -Writing to master: 找不到指定的模块。
[28356] 10 Apr 19:50:05.204 * Connecting to MASTER 109.242.233.245:22
[28356] 10 Apr 19:50:05.205 * MASTER <-> REPLICA sync started
[28356] 10 Apr 19:50:26.208 * Non blocking connect for SYNC fired the event.
[28356] 10 Apr 19:50:26.209 # Sending command to master in replication handshake: -Writing to master: 找不到指定的模块。
[28356] 10 Apr 19:50:26.283 * Connecting to MASTER 109.242.233.245:22
[28356] 10 Apr 19:50:26.284 * MASTER <-> REPLICA sync started
[28356] 10 Apr 19:50:47.288 * Non blocking connect for SYNC fired the event.
[28356] 10 Apr 19:50:47.289 # Sending command to master in replication handshake: -Writing to master: 找不到指定的模块。

I had this problem too, but I didn't set up the master-slave relationship!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants