proxmox web interface problem

  • Thread starter Thread starter dinster
  • Start date Start date
D

dinster

Guest
my proxmox svr is running fine. i can access via console anytime. no problem.

but the web interface is not stable at all :confused:

very often i get this msg.. either Firefox or IE.. same problem..
 

Attachments

  • shot01 - proxmox.png
    shot01 - proxmox.png
    24.2 KB · Views: 62
Is that error only on the storage page?

What is the output of:

# pvesm list -a

Does abouve command run without delays?
 
Is that error only on the storage page?

What is the output of:

# pvesm list -a

Does abouve command run without delays?

there u go.. my NFS server no longer exist. no wonder it stucked !

how to remove NFS server from the config file sir?
 

Attachments

  • proxmox pvesm list showing error.png
    proxmox pvesm list showing error.png
    11.2 KB · Views: 21
I wind up with the same error as the screenshot in the first post illustrates- usually just on the storage page, and sometimes on any.

For some reason the NFS share became unavailable, yet remained "bound" in the storage appliance.
I'm not sure if that SSH bind feature can be expected to prevent a connection loss- I was just guessing.

Although both can ping each other- the share still errors when I try to disable or delete it using the web interface.

Rebooting the file server didn't resolve anything.
As soon as I comment out the appropriate entries in /etc/pve/storage.cfg all is well.

I just don't get what happened to make it go awry.

Screenshots:

View attachment 170View attachment 171

EDIT: These attachment links show up in the post editor as screenshots & in the post as links to attachments- I added images from url with the refrence locally option checked...
 
Last edited:
Now I'm faced with a PVE that won't reboot because of this.
I added another NFS storage with the share disabled from the start, to see if it would.
Then I should've known- I had to try...
As soon as I enabled it the page locked up.

This time deleting the entries from /etc/pve/storage.cfg had no effect.
And the box won't reboot.

Is there a timeout I can set to make this not happen again?

Also- I Googled SSH binding... So much for that acting as a keep-alive. Oh, well.

EDIT:
This post mentions admins' efforts to resolve this.
 
Last edited: