The server cannot be restarted, rescue mode does not work, OS cannot be installed. The following error is displayed
Type: 'dhcp_restart_fail' Object: 'DHCP server' Value: 'failed to start'
When assigning IP address to the server, DCImanager adds the corresponding subnet into the DHCP configuration file. To start the DHCP server correctly for each network interface that listens to DHCP service, subnet should be specified in the DHCP configuration file. For each interfaces that the DHCP-service listens, the networks must be specified in the module IP address management.
Issues with Windows installation
A Windows template cannot be installed on the server. After you start the Windows uploader, the system will be redirected to console, and in the log you can see winconfigure strings meaning that am empty parameter was received.
This is caused by the unsolved problem with DHCP client on Windows. The bug is reproduced on some combinations of server and network equipment.
IPMI console upload issue
Error trying to upload the console: "Cannot establish IPMI session. Please contact to your administrator." I has been working resently
Perhaps, the maximum number of open sessions with IPMI has been exceeded. You need to open the IPMI configuration form in the web-interface and complete the following steps:
- Delete /close old sessions;
- Enlarge the session limit for the web-interface (for example, about 10);
- Decrease the session timeout (for example, about 5 minutes).
The error may occur when the user is trying to download the jnlp file again and again.
Error trying to upload the console: "Activate Session command failed. Error: Unable to establish LAN session. Error: Unable to establish IPMI v1.5 / RMCP session"
Connection error with IPMI. Execute the command ipmitool to make sure the device is accessible.
The file was uploaded successfully , but when trying to start it the user receives the following error message from Java:
Java forbids the upload of applications from untrusted sources. The user needs to add the IPMI URL into the list of sites-exceptions for Java. The list is located at"/home/v.petrov/.java/deployment/security/exception.sites". You need to add the record http://<IP-address of the IPMI WEB-interface> or https://<IP address of the IPMI WEB-interface> into the file.
Issues with IPMI via an auxiliary server
Ctrl doesn't work
For security reasons the IPMI WEB-interface blocks Ctrl (before version 5.118), Shift (to block Shift+Click, upper-case letters are not affected), Alt, Menu, Super(Meta/Hyper), F1, F5, F12, and the right mouse button.
Before version 5.118 you cannot terminate the command in the Java-console by pressing Ctrl+C. Some Java-consoles have special tools to send the required combinations of buttons to the server.
In DCImanager before version 5.118, at your own risk you can edit the user auto-start script (<path_to_panel_directory>/etc/ipmi_proxy_v2_xstartup.sh), by commenting the lines that reset the Control button.
Shift doesn't work
Before version 5.145 in some IPMI devices you cannot enter brackets (Shift+9/Shift+0) in the Java-console. To resolve the issue, update the panel or comment the lines which mention Shift in the/home/dci_vnc_template/.vnc/xstartup file on the proxy server, and in the /usr/local/mgr5/etc/ipmi_proxy_v2_xstartup.sh file on the server with DCImanager.
http/https doesn't work
In case of https to DCImanager, you need to enable the option Encrypt connection from noVNC to websockify in the module configuration form. Otherwise, when trying to switch to the IPMI web-interface from the list of servers, you will see the the notification that the web-page cannot be accessed without https.
The WEB-interface doesn't open without WEB-url
If only IP address is specified for the IPMI (no Web URL), the proxy server will generate a URL by adding IP to "https://". If the IPMI doesn't allow to https management, the browser inside noVNC will receive the error message. To resolve the issue, you need to specify Web URL с "http://" at the beginning in the IPMI edit form in DCImanager.
No available ports to connect to noVNC
Before version 5.118 restarting a tab with the IPMI Web-interface may not delete the socket files that do not allow to open the VNC-server on that port next time.
Socket files look like that:
srwxrwxrwx 1 1003 dci_vnc_users 0 12:15 /tmp/.X11-unix/X5901 srwxrwxrwx 1 1003 dci_vnc_users 0 12:16 /tmp/.X11-unix/X5902 srwxrwxrwx 1 1003 dci_vnc_users 0 12:42 /tmp/.X11-unix/X5904
To resolve the issue:
- update the panel to 5.118 or later;
- make sure that ,there are no IPMI-proxy active sessions (команда должна вывести "no active sessions")
ps aux|grep -i [v]nc && echo "found active sessions" || echo "no active sessions"
- delete the files manually.
rm -rf /tmp/.X11-unix/X*
The WEB-url contains a domain name
The "IPMI proxy via auxiliary server" module do not support domain names in the "Web-interface URL" field of the IPMI edit form. The field can contain URLs only with IP addresses. E.g.:
Mounting ISO-images allows to change general files of the ISO-image
Peculiarities of image mounting via IPMI requires write permissions for the ISO-file. That's why the server owner or administrator has write permissions into the available ISO-files.
The NoVNC windows is too large or small
Starting from version 5.136 the standard noVNC window size was enlarged from 1024*768 to 1280*960 for more convenient operation with some Java-consoles. To apply the changes you need to edit the scripts:
- <control_panel_directory>/etc/ipmi_proxy_v2_connect.sh: in -geometry 1280x960 change 1280x960 into desired a size in horizontal and vertical directions;
- <control_panel_directory>/etc/ipmi_proxy_v2_xstartup.sh: in --window-size=1280,960 \ change 1280,960 into a desired size in horizontal and vertical directions.
Please note that the changes in the files will be reset after the panel update!
To apply the changes on the already configured proxy server, you need to edit /home/dci_vnc_template/.vnc/xstartup. Change 1280,960 into a desired size in horizontal and vertical directions;
If you use IPMI HP iLo4 and disable proxy the Java-applet doesn't boot with the following error:
Issues with IPMI if the "Proxy via auxiliary server" module is set up
- To get a more detailed information, set the log level to 9 in the logging configuration form for the following modules:
dci_ipmi dci_servers websockify dci_utils dci_osinstall dci_iso (if ISO-images are used)
- Please, take the note to the records filtered by IPMI proxy v2 in the main log (dcimgr.log) and the whole log websockify.log;
- There are two logs on the proxy server:
- /var/log/ipmiproxyv2_install.log — proxy setup log;
- /var/log/ipmiproxyv2_connect.log — user connection log;
- Software setup log adds the /var/lock/ipmiproxyv2_installed file after successful installation of all components. Further setup attempts will find the file and skip the setup;
- In the logs you can see a username for every connection. On the proxy server you can open it in the VNC log home directory (/home/dci_vnc_user_*/.vnc/*log, where you can see the errors from the browser /java/xdg-open);
- The service setup and user connection scripts are written on bash, and the administrator of the server with DCImanager can modify them (they are located in <control_panel_directory>/etc/ipmi_proxy_v2*.sh). There you can also fund the user start script (<control_panel_directory>/etc/ipmi_proxy_v2_xstartup.sh);
Software re-installation on the proxy server
- delete the IPMIProxyV2Host parameter from the DCImanager configuration file (etc/dcimgr.conf);
- execute the bin/core -m dcimgr exit command to restart DCImanager;
- in proxy module edit form enter the access details to the server and click "ОК". Wait for install to complete.
We can not identify you and respond to your message.