NE-ONE: If you are not able to access NE-ONE WEB GUI
If you can't access NE-ONE WEB GUI but can access the console menu via SSH, there are 3 possibilities:
1-) Your disk space is full
Check your disk space by running the following command:
df -H
You will see an output like the one below.
neone@NE-ONE:~$ df -H
Filesystem Size Used Avail Use% Mounted on
udev 4.2G 0 4.2G 0% /dev
tmpfs 835M 959k 834M 1% /run
/dev/sda1 106G 39G 62G 100% /
tmpfs 4.2G 0 4.2G 0% /dev/shm
tmpfs 5.3M 0 5.3M 0% /run/lock
tmpfs 4.2G 0 4.2G 0% /sys/fs/cgroup
tmpfs 835M 0 835M 0% /run/user/1000
neone@NE-ONE:~$
Please follow the steps below if it is full (Use% = 100% or close to 100%).
2-) Missing grub files after upgrading the system
Check ippe.log file to see whether your machine keeps rebooting repeatedly.
You should see an output like the one below.
2023-12-08 11:09:16.626834: IPPE Version: 2023.10.1377.1
2023-12-08 11:09:16.626837: IPPE Build Date: 202310091245
2023-12-08 11:09:16.626839: Host Id: UNKNOWN
2023-12-08 11:09:16.626841: Running on VM: No
2023-12-08 11:09:16.626941: Fingerprint: XXXXXXXXXXXXXXXXXX
2023-12-08 11:09:16.642400: Importing python module [IPPE_python_filesystem]
2023-12-08 11:09:16.660415: Importing python module [IPPE_setup]
2023-12-08 11:09:16.666596: Importing python module [IPPE_python_ldap]
2023-12-08 11:09:16.727910: Importing python module [IPPE_v8v9_to_v10]
2023-12-08 11:09:16.728153: Importing python module [IPPE_ne1v5_to_v10]
2023-12-08 11:09:16.728480: Importing python module [IPPE_ne1v5_its_to_v10]
2023-12-08 11:09:16.728899: Python version: 3.7.16
2023-12-08 11:09:16.728906: Running setup and environment checks
2023-12-08 11:09:18.483208: Setup failed
[31mERROR: 2023-12-08 11:09:18.483272: Normal Exit
[0m2023-12-08 11:09:19.126627:
To check ippe.log, please follow the steps below.
If you see an error like the one above, please check startup.log (under /ippe/logs folder) to find which files are missing.
Example:
2023-12-08 12:28:41.005493: Total memory (KB): 32747008
2023-12-08 12:28:41.005556: System memory (KB): 8186752
2023-12-08 12:28:41.005574: Reserved memory (KB): 24560256
2023-12-08 12:28:41.005595: Using 1GB Huge Pages
2023-12-08 12:28:41.005628: This machine has 10 cores
2023-12-08 12:28:41.005645: Using page size 1G
2023-12-08 12:28:41.005660: Allocating 23 pages
2023-12-08 12:28:41.005825: chroot /host/ bash -c "cat /proc/cmdline"
2023-12-08 12:28:41.013872: boot_image=/boot/vmlinuz-5.15.0-86-generic root=uuid=74f4168a-66a3-4fc3-9cc9-29731abe5518 ro splash quiet isolcpus=1-9 nohz_full=1-9 rcu_nocbs=1-9 default_hugepagesz=1g hugepagesz=1g hugepages=24 intel_iommu=on iommu=1 nmi_watchdog=0 net.ifnames=0 biosdevname=0 nvme_core.default_ps_max_latency_us=5500
2023-12-08 12:28:41.013899: Found Linux boot command line
2023-12-08 12:28:41.013932: hugepages has the incorrect value [24] [23]
2023-12-08 12:28:41.013942: Incorrect Linux Kernel parameters for grub, updating...
2023-12-08 12:28:41.013947: Updating boot parameters..
2023-12-08 12:28:41.014093: Updating /host/etc/default/grub
2023-12-08 12:28:41.014149: [Errno 2] No such file or directory: '/host/etc/default/grub' -> '/host/etc/default/grub.d/50-cloudimg-settings.cfg.bak1'
2023-12-08 12:28:41.014330: Traceback (most recent call last):
File "IPPE_setup.py", line 908, in ippe_setup
File "IPPE_setup.py", line 596, in ippe_setup_verify_grub
File "IPPE_setup.py", line 516, in ippe_setup_edit_default_grub
FileNotFoundError: [Errno 2] No such file or directory: '/host/etc/default/grub' -> '/host/etc/default/grub.d/50-cloudimg-settings.cfg.bak1'
Then, please double-check to see whether grub.d file exists by going to /etc/default folder (Command that you need to use: cd /etc/default and ls -l)
Create the missing folder: sudo mkdir /etc/default/grub.d
Reboot your appliance: sudo reboot
3-) Docker container issues
Check running containers
sudo docker ps
Example output:
neone@neone:~$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
4f2e5999a73c ippe:2023-12-05-00-32 "/ippe/bin/ipperte -d" 7 days ago Up 7 days ippe
If you can't see any running docker container,
try to reboot the engine
sudo /etc/rc.local
if it doesn't work, please follow the steps below. (ask Support for the .tgz image file)