Hi,

I checked QluMan 13.7.1 and no changes in LoginData.py were found :-(

Regards Rolandas

On 2024-11-25 14:50, Roland Fehrenbacher via Qlustar General wrote:

Hi,

QluMan 13.7.1 singularity image is uploaded and should fix the issue.

Best,

Roland

On 11/25/24 11:13, ulgs_mrq via Qlustar General wrote:

...

Hi,

singularity image of qluman 13.7.0 and qluman-qt can't work to access at first time. It shows, File "/usr/lib/python3/dist-packages/qluman-13/client/qt/ConnectClusterDialog.py", line 846, in on_okButton_clicked cluster = ClusterInfo(alias=self.aliasLineEdit.text(), File "/usr/lib/python3/dist-packages/qluman-13/common/LoginData.py", line 169, in __init__ (self.client_pubkey, self.client_seckey) = zmq.curve_keypair() NameError: name 'zmq' is not defined

Is there any workaround?

Regards,

---

Qlustar General mailing list -- qlustar-general@qlustar.org To unsubscribe send an email to qlustar-general-leave@qlustar.org

Hi,

Now I checked it is working.

Thank you.

Regards, Morihsia

On 11/26/24 05:56, ulgs_mrq via Qlustar General wrote:

Hi Roland,

qluman-13.7.1-singularity.sqash is still unstable. Today I can't connect to qluman, after entering password, suddenly down. This time shows no messages. How to debug it?

Regards, Morihisa

Hi Morihisa,

does it return an error code? If your prompt doesn't show the return value when programs finish then you can print the last return code using

echo $?

Another indication might be found in /var/log/qluman/qluman-router.log and /var/log/qluman/qlumand.log. Both should contain a log entry for when the GUI client connects or disconnects giving an indication how far it got in the connection attempt.

Regards,

Goswin

On 11/27/24 09:39, ulgs_mrq via Qlustar General wrote:

Hi Goswin,

Now I found it cause authorization error. I remove .$HOME/config/Qluman on client host and registered a new key by qluman-cli --gencert on cl-head

Now I can re-connect to test cluster.

Could you let me know, do we need to reissue the key for every connection?

Regards, Morihisa

Hi Morihisa,

no, this should for sure not be the case.

I did once have an issue where ~/.config/Qluman/Qluman.conf got corrupted and QT crashed reading it. If it happens again please make a backup and try removing just that file. It stores the last size of your windows and some other state and no sensitive informations. And if that is the cause please send us a copy so we can reproduce the issue, I unfortuanetly forgot to make a backup myself and couldn't reproduce the issue again.

Regards,

Goswin