Dear All, Please help me the problem with not able to generate qluman --gencert. The output is as below: Sincerely, Rajendra Adhikari
qluman-cli --gencert ERROR:qlunet.Node:router is not responding to pings: reconnecting ERROR:qlunet.Node:Node.run(): exiting after exception Traceback (most recent call last): File "/usr/lib/python3/dist-packages/qlunet/Node.py", line 333, in run timeout = self._queue.next() File "/usr/lib/python3/dist-packages/qlunet/Timeout.py", line 143, in next item.expired(self) File "/usr/lib/python3/dist-packages/qlunet/Node.py", line 79, in expired self._node.slave_reset_keys() File "/usr/lib/python3/dist-packages/qlunet/Node.py", line 994, in slave_reset_keys self._monitor.setsockopt(zmq.LINGER, 0) AttributeError: 'NoneType' object has no attribute 'setsockopt' ERROR:qlunet.Node:Network thread is quiting on us
Hello,
rajendra.adhikari@ku.edu.np wrote:
Dear All, Please help me the problem with not able to generate qluman --gencert. The output is as below: Sincerely, Rajendra Adhikari
qluman-cli --gencert ERROR:qlunet.Node:router is not responding to pings: reconnecting
This is the real error. The rest of the output you can ignore.
Something is going wrong when the qluman-cli tries to connect to qlumand by way of qluman-router. The most trivial reason for this might be that qluman-router or qlumand aren't running.
If you installed fresh using the latest version then you run into a bug introduced in 11.0.2.6 making logfiles readable only for root. This fails on fresh installs when no logfiles exist yet. Upgrades from older versions are not affected which is why we didn't catch it in time. The bug is fixed in 11.0.2.7 released a few minutes ago. Please apt update + apt upgrade and try again.
If that doesn't solve your problem please check that qluman-router and qlumand are running and check their logfiles for messages.
Sincerely, Goswin von Brederlow
Dear Goswin, Thank you very much for the quick reply, it is now indeed perfectly working. Sincerely, Rajendra Adhikari