Proxmox ve 1.4 beta web console logon problem

D

drsaunder

New Member
Sep 14, 2009
3
0
1
I am trying out proxmox ve 1.4 beta and I find that i can not log on from the web console. I get redirected to the https://<my_ip>/nrd/LOGIN page and a message pops up saying that I can not be authenticated.

For comparison I have a machine right beside it running proxmox ve 1.3 with an identical setup and it works fine. I am guessing this is a certificate problem but should I be looking at apache config or pve config? The apache logs have some error messages about the RSA server certificate not matching the server name, however this is not a problem for 1.3.

Has anyone else seen this login problem or have any comments on it. I do not have access to our main DNS here so I am running DNS on the proxmox server itself, with a dummy domain and address records, just to keep apache happy.

btw
I have 1.4 running on a new Intel S5520WB motherboard with two Xeon 5520 CPUs, lots of DDR3 RAM and SATA drives. The proxmox ve 1.3 kernel has very slow I/O on this hardware combination while the 1.4 kernel runs just fine. I can post test results if anyone is interested.
 
drsaunder said:
I am trying out proxmox ve 1.4 beta and I find that i can not log on from the web console. I get redirected to the https://<my_ip>/nrd/LOGIN page and a message pops up saying that I can not be authenticated.

For comparison I have a machine right beside it running proxmox ve 1.3 with an identical setup and it works fine. I am guessing this is a certificate problem but should I be looking at apache config or pve config? The apache logs have some error messages about the RSA server certificate not matching the server name, however this is not a problem for 1.3.

Has anyone else seen this login problem or have any comments on it. I do not have access to our main DNS here so I am running DNS on the proxmox server itself, with a dummy domain and address records, just to keep apache happy.

btw
I have 1.4 running on a new Intel S5520WB motherboard with two Xeon 5520 CPUs, lots of DDR3 RAM and SATA drives. The proxmox ve 1.3 kernel has very slow I/O on this hardware combination while the 1.4 kernel runs just fine. I can post test results if anyone is interested.
Click to expand...

try using another browser/desktop - I assume an old certificate is stored or cached somewhere (or find and delete it).

hardware results:
yes, pls post details about your good working hardware so that other´s can benefit from your setup.
 
I believe I have solved my problem. I like to use root passwords with punctuation characters :)(^ and so on. Apparently the pve 1.4 authentication does not like these, (although they work with 1.3) I reinstalled using normal alpha-num characters and that works fine. Where does proxmox ve/apache2 store password strings, I assume that /etc/shadow is not being parsed directly by some Perl black magic.

Useful server specs:
We put together a server from parts for virtualization purposes. Lenny 5 and Proxmox ve 1.4 beta run just fine on this hardware. Proxmox ve 1.3 with the older kernel does not, some necessary functionality may have been left out of the build.

1x - Mother board: Intel S5500WB
2x - Xeon 5520 cpus
6x - 2GB DDR3 1066 MHz RAM
4x - 320 GB SATA 7200 RPM drives
1x - Intel 6 bay hot swap drive cage - AXX6DRV3G
1x - Intel Dual PCIe 4x NIC - EXP19402PT

hdparm results for proxmox ve 1.3 on this server
:/dev/mapper/storage-storage:
Timing cached reads: 8954 MB in 2.00 seconds = 4485.37 MB/sec
Timing buffered disk reads: 10 MB in 3.64 seconds = 2.74 MB/sec

hdparm results for 1.4 beta on the same hardware
/dev/mapper/storage-storage:
Timing cached reads: 14374 MB in 1.99 seconds = 7209.74 MB/sec
Timing buffered disk reads: 336 MB in 3.00 seconds = 112.00 MB/sec

The different is pretty dramatic, the 1.3 kernel was doing a lot of I/O waiting, possibly disk caching was not working.
 
drsaunder said:
I believe I have solved my problem. I like to use root passwords with punctuation characters :)(^ and so on. Apparently the pve 1.4 authentication does not like these, (although they work with 1.3) I reinstalled using normal alpha-num characters and that works fine. Where does proxmox ve/apache2 store password strings, I assume that /etc/shadow is not being parsed directly by some Perl black magic.

Useful server specs:
We put together a server from parts for virtualization purposes. Lenny 5 and Proxmox ve 1.4 beta run just fine on this hardware. Proxmox ve 1.3 with the older kernel does not, some necessary functionality may have been left out of the build.

1x - Mother board: Intel S5500WB
2x - Xeon 5520 cpus
6x - 2GB DDR3 1066 MHz RAM
4x - 320 GB SATA 7200 RPM drives
1x - Intel 6 bay hot swap drive cage - AXX6DRV3G
1x - Intel Dual PCIe 4x NIC - EXP19402PT

hdparm results for proxmox ve 1.3 on this server
:/dev/mapper/storage-storage:
Timing cached reads: 8954 MB in 2.00 seconds = 4485.37 MB/sec
Timing buffered disk reads: 10 MB in 3.64 seconds = 2.74 MB/sec

hdparm results for 1.4 beta on the same hardware
/dev/mapper/storage-storage:
Timing cached reads: 14374 MB in 1.99 seconds = 7209.74 MB/sec
Timing buffered disk reads: 336 MB in 3.00 seconds = 112.00 MB/sec

The different is pretty dramatic, the 1.3 kernel was doing a lot of I/O waiting, possibly disk caching was not working.
Click to expand...

thanks for info.
what raid controller do you use, raid level? can you post the results of 'pveperf' (please run when the server is idle)?
 
For proxmox 1.4, pveperf reports:

CPU BOGOMIPS: 72532.95
REGEX/SECOND: 653252
HD SIZE: 73.33 GB (/dev/pve/root)
BUFFERED READS: 113.24 MB/sec
AVERAGE SEEK TIME: 11.26 ms
FSYNCS/SECOND: 665.97
DNS EXT: 81.49 ms
DNS INT: 2.68 ms (ict.somewhere.ca)


I am not using RAID on this system since it is not a critical production server.
The motherboard has a 82801JR I/O controller that supports software RAID with SATA drives. In order to use it I would have to install the Linux driver that Intel provides; and in order to do that I would need the 2.6.24-8-pve kernel source code. Software RAID isn't all that great anyway.

As a point of interest we were installing VMWare ESX on the previous version of this motherboard (S500VSASCSIR with 6321ESB I/O controller) and the ESX install was unable to detect the software RAID configuration; it just accessed the drives directly. Apparently without the right driver, Intel software RAID is a no go.
 
drsaunder said:
I am trying out proxmox ve 1.4 beta and I find that i can not log on from the web console. I get redirected to the https://<my_ip>/nrd/LOGIN page and a message pops up saying that I can not be authenticated.
Click to expand...

I uploaded a fix for that to the 'pvetest' repository. No you can set password containing utf8 characters again.
 
Hi,
I upgrade proxmox ve from pvetest. I still have a problem with password and special character.
Witch fix do i use ?
Regards
 
Hi,
I fix root password with special character like #!*..., when i try to login with user root to pve via the web interface, i receive a error.
I fix root password whitout special character, i can log to the web interface with user root.
I use pve 1.4 beta2 4340.
Locales are installed with utf8
 
Just tested here using password "#!*...abc" - works without problem. How did you set the password - using the web interface?
 
Hi,
I change the password from the web interface and from linux command ligne with passwd.
Still have the problem :(.
 
Just tell me how to reproduce the bug (give me example passsword that fails for you). Or is it possible to get a login (for debugging)?
 
hi
just installed ve1.3 and apt-dist-upgraded into ve1.4 via commandline.
now - via the webinterface - obvisouly passwords having a "." are still a problem in the final edition.

regards
harald kapper / kapper.net
 
kapper.net said:
hi
just installed ve1.3 and apt-dist-upgraded into ve1.4 via commandline.
now - via the webinterface - obvisouly passwords having a "." are still a problem in the final edition.
Click to expand...

No, at least I can't reproduce it here. Please can you provide an example password and a way to reproduce the bug?
 
You must log in or register to reply here.
Top Bottom