Illegal characters are mixed in the enroll message.
enrollâ 153.122.86.245 noiser6â f64f77b27f7971a3ff65f6f32f06a010547c1fad889c6323340d6e67d0a8115f
I guess that this situation will occur when entering a space.
It is recommended that you type in the complete alphabet mode, entering manually anything other than the public key.
Please send me a message again.
Thank you.
Dear MIZUNASHI Rin-san
Thank you for your advice.
I try it again but i don’t know why this phenomenon occur.
Thanks.
Dear Minarin-san and BR
Yesterday, I sent hand typing message again.
Please check it.
Today, I sent different message like above.(alias name:noiser5)
Please check it too.
Thank you.
I got better than last time but I still have one place.
enroll 153.122.86.245 noiser6â f64f77b27f7971a3ff65f6f32f06a010547c1fad889c6323340d6e67d0a8115f
If it seems impossible, I think that @BloodyRookie will manually respond.
Please try again or ask Dev to deal with it.
ちなもにenrollメッセージを送信しているお使いのOSはなんでしょうか？
thanks
Are you trying to change the delegated key you are using for the supernode?
that cannot be done that way, i have to manually disable the old entry and add a new entry in the db.
You can send a PM with the changed supernode data for each supernode you want to change.
みなりんさん
いろいろとすみません。
OSはWindows10です。特段特別なものは使っていません。
今回はNCCからnanowalletに移行しようと思い、delegated keyを
nanowalletのものでenrollメッセージを送った次第です。
（ついでに鯖も借り替えたのでipアドレスも違っています）
先ほどBRさんからもメッセージをもらっていますが、うまく訳せず困っております。汗
当方でどのように対処すべきか、アドバイスいただけると助かります。
@chibi さん。
Noiser6 (211.125.67.26) というサーバを別途立てていませんんか？
一度問題を整理したいと思います。
同じIPでなくても、現在登録されているエイリアス名と同一のサーバは登録ができません。
もし同じ名前で登録する場合は、スーパーノードを管理するDBを直接消去する必要があります。
NoiseR6を移行するのかと思いますが、この場合、先代のNoiseR6を先にデータベースから抹消する必要があります。
Even if it is not the same IP, you can not register the same server as the currently registered alias name.
If you register with the same name, you need to erase the DB which manages the super node directly.
I think whether to migrate NoiseR6, but in this case, it is necessary to delete the previous NoiseR 6 from the database first.
Migration from NCC to NanoWallet, Remote address changed.
However, he also changed the server at the same time, and the IP address is new.
Because enroll is a syntax error, I do not know exactly, but can the same alias name be registered?
This is my personal doubt.
thanks
Same alias cannot be used twice. He should pm me the new details for each node that has changed data.
Any ideas why I’ve had random ‘height/chain’ failures on my supernode?
I have to reboot everytime, cause it just seems to stop … so if I dont catch it soon, it’ll fail multiple periods.
It seems that sometimes the AsyncHttpCleint used by NIS is running out of sockets.
The exact value how many sockets the vps supports by default is different from provider to provider.
You can check the amount by issuing “ulimit -a” in the vps console. You might see something like
open files (-n) 1024
meaning that your user can have up to 1024 open files (open sockets).
You can try to increase that number by editing the file /etc/security/limits.conf and adding the lines
<your_user_name> soft nofile 100000
<your_user_name> hard nofile 100000
meaning that your user now can have up to 100000 open files. you can replace <your_user_name> by * to allow all users to have that limit.
Whether the above is possible or not is again depending on the VPS virtualization but for most it should be possible.
I guess you need to restart NIS after the changes.
That being said, i am not an expert on those things but it might be worth a try.
Maybe linux experts can comment on this.
thanks for the reply.
I checked ulimit -a
open files (-n) 65536
I’ll see about editing the limits.conf
Hmmm…that should be enough, can you provide the log for your supernode?
how do I provide the ‘log’?
depending on your server, the logs shoul be in /home/ /nem/nis/logs.
nis-0.log is probably the relevant one.
みなりんさん
はい、Noiser6 (211.125.67.26) サーバを立てていて、運用しています。
このサーバはNCCのdelegated keyで動かしています。
今回のお願いは、
①NCC→nanowalletへ移行したいこと（delegate key変更）
②サーバも211.125.67.26→153.122.86.245したいこと
③Alias nameはNoiseR6のままとしたいこと
となるかと思います。
最近supernodeでfailがよく出るためサーバを変更するのと同時に、
今後はnanowalletが主流となるとのことでしたので、nanoへの移行もやりたかった次第です。
いろいろとご面倒をおかけしてすみませんが、
正当なやり方をご教授いただけると助かります。
（あと数台同様の変更を行いたいので）
以上、よろしくお願いいたします。
正当な方法で行いたいという内容を把握致しました。
拝見させていただきましたところ、5台中4台は、153.122.. で動いていると思いますが、この4台も同一会社にて、借り換えを行うという認識であっていますか？
どちらにせよ、同じ事を複数回繰り返す事になりますので、1回の正式な手順を書きます。
これらを並行で進めるか、1台ずつ進めるかは、おまかせ致します。
正式には、この手順となりますが、2の手順で3の手順までやってもらえる可能性が大きいです。
よろしくお願いいたします。
As I can see, it seems that 4 out of 5 machines are running at 153.122. *. *, But are they recognizing that refinancing is carried out at the same company as these 4 machines?
In either case, I will repeat the same thing more than once, so write a formal procedure one time.
I will leave you to proceed in parallel or one by one.
Formally, this is the procedure, but there is a high possibility that you can get up to the third step by the second step.
Thank you.
Hi there. Nodes name is nemster_2. Any idea why it failed last tests?
Please give it a full day to have stable results.
ok, will do. however now it shows the version didnt pass. Pretty sure the versions are allright.