feel free to join our community slack through this url: https://join.slack.com/t/apacheiotdb/shared_invite/zt-2bolm5rfk-0Yimdz7Kp_ZRCIVgJmxoKA
On Fri, Jan 26, 2024 at 2:37 PM Yuan Tian <jackietie...@gmail.com> wrote: > And if you like, we can talk on the slack channel because mail > lists cannot use attachment. > > On Fri, Jan 26, 2024 at 1:25 PM 김천구 <ckim191...@gmail.com> wrote: > >> *Urgent Issue:* >> I was testing on a Linux server with IoTDB version 1.2.2. >> After briefly turning it off with 'stop-standalone.sh' and attempting to >> restart it with 'start-standalone.sh', >> IoTDB does not start. Upon re-executing 'start-standalone.sh', I checked >> the 'log_confignode_all.log' file. >> And continuously found the following message: >> Leader has not been elected yet, wait for 1 second >> >> Furthermore, when I executed 'stop-standalone.sh' after >> 'start-standalone', >> I encountered the following: >> >> stop-standalone.sh: 60: [[: not found >> Check whether the internal_port is used..., port is 10710 >> No ConfigNode to stop >> Maybe you can try to run in sudo mode to detect the process. >> Check whether the rpc_port is used..., port is 6667 >> No DataNode to stop >> Maybe you can try to run in sudo mode to detect the process. >> >> >> The datanode log file did not contain any additional information, so it >> seems that even after executing 'start-standalone.sh' >> confignode and datanode are not running. Despite the absence of processes >> using ports 10710 and 10730, it is unclear what the issue might be. >> Even when executed individually, 'start-confignode.sh' and >> 'start-datanode.sh' do not initiate successfully. >> >> I'm curious if there is any speculation about what could be causing the >> problem. >> >> Best regards, >> ----------------------------------- >> Cheongu Kim >> ckim191...@gmail.com >> >
