Recent content by Kordian

The browsers were tested. Cache was tested. The error messages in the first post are the error messages you are asking for.

I totally cannot understand you and your "I am the God" statements. I will give you an example: who gave you the right to claim this: "the issue can not be reproduced" The fact is I am capable of reproducing the issue at any time and cannot understand how a person can write such thing. I am...

Once again: does any of you know the guys that programmed the proxmoxlib.js within the proxmox-widget-toolkit? Please stick to the subject of this post. Thank you in advance!

Well, since I found a solution, what is the point??? The culprit is the proxmoxlib.js within the proxmox-widget-toolkit. Secondly, are you expecting me to run another upgrade with the knowledge of the future problem on a production cluster? Sorry, but are you the programmer of the file?

I am running normal upgrade over GUI. Nothing special, no post-install...

What browser? In Firefox, press F12 for the console tools and check errors there. Let me guess: proxmoxlib.js?

Hello, Coming back to my original post. I have no patching of my clusters. Neither anything special installed. The only thing is the proxmox-widget-toolkit, which -correct me if I am wrong - is an official proxmox tool. Therefore I think tha case is strictly for the widget guys, and the result...

Hello, I had this issue already when upgrading from 8 to 9. Now it is there again. When I try accessing the GUI I get these errors: Uncaught SyntaxError: missing } after property list proxmoxlib.js:750:2note: { opened at line 42, column 29proxmoxlib.js:42:29 Uncaught TypeError: can't access...

Thank you for the help. In my case I think it was the problem how proxmox and the storage communicate and cooperate. But using parted solved the issue and now I can freely expand the resources.

Thank you, will test.

Thank you. So if I do not create any label nor "partition" on FC SAN, this should then go without problems?

Hello, I have a proxmox cluster and a shared FC LUN. I am trying to extend currently used storage, following this: Rescan should be done on ALL nodes: pvs -o +tags multipath -ll LUN_name echo 1 >/sys/block/sdX/device/rescan echo 1 >/sys/block/sdY/device/rescan echo 1...

What does this have to do with the problem, or the fact that the upgrade does not upgrade a critical component? If you have nothing to do, keep on doing nothing, instead of posting useless comments. Thank you in advance.

Yes, I read it. No word of ifupdown problems afterwards. Actually before the upgrades I added the hwaddress to the config, as suggested. Still it all went wrong!

Well, since I am after 6 hours of fighting with getting my production system working, first of all many thanks to the whole Proxmox team for screwing the upgrade process up and not informing users of it! I hope karma will thank you better than I can. The story: 2 days ago I decided to upgrade my...