proxmox 1.8 and web page problems?

  • Thread starter Thread starter joeblow
  • Start date Start date
J

joeblow

Guest
Greets,

New install of proxmox 1.8 on an IBM 3650 M2 rackmount box. Network is plugged into cisco 3650G switch.

Having a problem with the web pages "timing out" for lack of a better term. I'm using firefox 3.6.13 on a centos 5.5 box. I get similar results with IE6 on a dohs box.

------------------------------------

1. approx 60% of the time the login page will time out on after trying to log in.

--------------------------------------

2. https://proxmox/storage/index.htm gives:

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, root and inform them of the time the error occurred, and anything you might have done that may have caused the error.

[2658]ERR: 24: Error in Perl code: 500 read timeout

Apache Embperl 2.2.0 [Wed Apr 20 14:28:51 2011]

-----------------------------------------------------------
3. If login is successful, the page brings up

https://proxmox/vmlist/index.htm

Selecting "create" times out with :

https://proxmox/vmlist/create.htm

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, root and inform them of the time the error occurred, and anything you might have done that may have caused the error.

[2658]ERR: 24: Error in Perl code: 500 read timeout

Apache Embperl 2.2.0 [Wed Apr 20 15:06:21 2011]

-------------------------------------------------------
4. https://proxmox/storage/index.htm gives:

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, root and inform them of the time the error occurred, and anything you might have done that may have caused the error.

[2658]ERR: 24: Error in Perl code: 500 read timeout

Apache Embperl 2.2.0 [Wed Apr 20 14:28:51 2011]

------------------------------------

That's as far as I've gone. Any thoughts?

Thanks!
 
Last edited by a moderator:
At the time you tried, Proxmox ISP was down and hence pveam and other utilities that need to get info/updates from "HQ" would have timed out. Try now and if possible upgrade to FireFox v3.6.16. There were some issues with v3.6.14 or so if I recall correctly.
 
Thank you for the reply.

Does this mean that proxmox expects always-on access to the public Internet?
 
No, this is not related.
 
joeblow said:
Thank you for the reply.

Does this mean that proxmox expects always-on access to the public Internet?
Click to expand...

no. it looks that you configured a storage that is not accessible anymore. bring that storage online or remove it in /etc/pve/storage.cfg.
 
that seems to have been the case. the NFS server with all the isos seems to have barfed. Upon restart, proxmox worked smoothly again.

If I may suggest a 'feature enhancement', perhaps a trap for this condition (maybe even the specific pool that is not accessible?) could be displayed upon seeing such a condition.

Thanks!
 
yes, in the upcoming 2.0 you will see if a storage is offline.
 
Sounds good.

I also perked to the LDAP/AD integration. Very nice, and will make it easier to go into "enterprise" environments. Good call.
 
Hello. I have an issue with the web interface as well. Even though everything has been fine so far, after a recent upgrade "https://servername/vmlist/index.htm" no longer works. The browser keeps showing that it is loading but nothing happens no matter how long I wait.

FYI pveversion show the following:
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.8-33
pve-kernel-2.6.32-4-pve: 2.6.32-33
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.28-1pve1
vzdump: 1.2-14
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.1-1
ksm-control-daemon: 1.0-6


Thank you...
 
Well that's very strange... I was actually trying it using the IP as it has worked for me so far. Now that you mentioned it I tried using the host name instead of the IP. And guess what? It works! Now that's very very strange. It would make more sense the other way out...

Anyway, thanks for the suggestion! (I feel kinda silly...)
 
You must log in or register to reply here.
Top Bottom