Can you see any errors in the /usr/local/ispmgr/var/vdsmgr.log when you open VDSmanager URL?

Please run command killall vdsmgr and open https://node-ip/manager/vdsmgr and check logfile.

What operation system version and virtualzation you have on this server?

So there is no way a VPS customer can reboot his VPS via his own IP as I asked (listed below from previous post)? This is a big deal for us.

"The VPS owner's control panel is accessible at https://vps-ip:xxxx/ and it doesn't matter on which physical node the VPS is located - VPS owner always uses VPS IP to access the Power Panel."

Virtual servers are completely independent from the node machine and for connect to VPS users use own IP-address.

I understand how VPS's work as we are a large VPS company. My question still hasn't been answered. The GUI tool that each VPS user would get with their VPS to reboot, restart their VPS requires the host node IP's to access it with your software it seems. Is there anyway they can access this GUI tool (not control panel like cPanel) rather VZPP (like Virtuozzo Powerpanel) via their VPS IP not the host node itself? As explained above this is important and if it's not possible please just say it's not possible. The reason this is a problem is simple. If we move a VPS from one server to another then we also need to tell them a new IP to reboot their VPS which is really not necessary and not needed with other Virtualization software. Let me know asap.

slava,

Can you please reply to my PM?

Thanks.

Current version IPmanager work only with DNS zone configuration files and must be installed into server where DNS server allocated. If IP address have no revers record or name like 'free' (it can be changed) - addres is free and can be allocated to new VPS. Also administrator can configure address blocks for different reasons (projects or primary/secondary ip). If our developer team will add additional checks for find free IPaddress it will we written in changelog http://ispsystem.com/software/ipmanager/changelog/

So IPmanager allocates to VPS's based on if an IP has a reverse DNS entry, is that what you're saying? Igor had said that you'll be releasing in 1-2 days (said that two days ago) with the ability to ping the IP address to see if it is available. Can you check and see the status of this release?

is it possible to get someone to log in to our box and see why the openvz are not showing?

sample output

Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='d
isktemplate' key='fedora-9-i386-default'
Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='d
isktemplate' key='gentoo-20060317-i686-stage3'
Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='d
isktemplate' key='centos-5-i386-hostinabox571'
Jun 12 21:39:17 ../../src/openvz.cpp:106 TRACE BuildVdsCache
Jun 12 21:39:17 EXTINFO Load config '/etc/vz/conf/1670.conf'
Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='v
ds' key='ip'
Jun 12 21:39:17 EXTINFO Load config '/etc/vz/conf/1160.conf'
Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='v
ds' key='ip'
Jun 12 21:39:17 EXTINFO Load config '/etc/vz/conf/1570.conf'
Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='v
ds' key='ip'
Jun 12 21:39:17 EXTINFO Load config '/etc/vz/conf/230.conf'
Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='v
ds' key='ip'
Jun 12 21:39:17 EXTINFO Load config '/etc/vz/conf/1370.conf'
Jun 12 21:39:17 ../../src/tdata.cpp:1322 TRACE RecordSet::Post(insert) rsname='v
ds' key='ip'

haha! modified each individual conf with a wrtie command even if no changes made and they now show!