No WEB UI after updating from 1.10.19 to 1.10.20
Opened this issue · 6 comments
I run iventoy via your repo on unraid with the following config based off your example docker compose file:
I use the network bridge option to give iventoy its own IP Address (192.168.1.40) My unraid server runs from (192.168.1.125)
After updating to latest (ziggyds/iventoy:1.0.20) from (ziggyds/iventoy:1.0.19)
Container fails to show WEB UI. I get the following error:
lease open your browser and visit http://127.0.0.1:26000 or http://x.x.x.x:26000 (x.x.x.x is any valid IP address)
2024/05/31 02:10:57.521 [PXE] iventoy.dat <8034564> <15042560>
2024/05/31 02:10:58.261 [PXE] Extract iventoy.dat success.
2024/05/31 02:10:58.262 [PXE] ======= iVentoy 1.0.19 ========
2024/05/31 02:10:58.262 [PXE] tarfs find 179 files
2024/05/31 02:10:58.262 [PXE] Module init OK ...
2024/05/31 02:10:58.262 [PXE] Module init start ...
2024/05/31 02:10:58.262 [PXE] cpio buf:0x14b7cb1a7410 len:4407296 fixoff:343888
2024/05/31 02:10:58.262 [PXE] Module init OK ...
2024/05/31 02:10:58.262 [PXE] [Linux 64] checksum not match
2024/05/31 02:10:58.262 [PXE] ### iVentoy start failed. ###
Manually selecting the '1.10.20' or 'latest' tags give the same errror. Reverting to 1.10.19 fixes it.
I've never had any issues on previous builds but something has changed betwen these 2 versions. Can you advise?
I haven't ran the new version yet myself, a new container is automatically created once a new version is released by the dev.
Will have a look at it this evening and comeback to you
Thanks.
On my side it works fine.
Fyi, probably a typo but you mentioned 1.10.20 instead of 1.0.20
Yup a typo but the issue persists. Would you mind posting your working container config and i'll amend mine if there are any differences present?
Older working version "1.0.19"
Running '1.0.20' or 'latest' as of 18/06/2024
@zidesm - Thanks for looking.
Issue seems to be with the upgrade process and having some image conguration saved from within iventoy it dosn't seem to want to migrate it to the new image correctly. New image dosn't seem to like to run against old persistant data from v1.0.19 (.dat file possible?) from version 1.0.19.
Logs on new instance (1.0.20) do reference version 1.0.19 when older persistant data is referenced.
Setting up a 2nd instance with my container settings listed further up works perfectly normally as expected.
What broke? I have a bit of config for various windows images (drivers, answer file locations for multiple versions etc) and dont want to have to re-make everything as it's a huge pain point.
Might have something to do with .dat migration or similar from 1.0.19 > 1.0.20 as logs in new clean latest image when starting with no previous old persistant data reference the fact that it looks to see if it needs to recover old data during startup.
"data/config.dat not found, no need for recovery." so assuming it fails importing .dat file from previous versions.
Starting the new container (after copying in config.data, inventoy.dat and mac.db from the older instance) manully dosn't retain previous config or cause it to sanity check the old data and reimport it correctly.
UPDATE: Possibly fixed?
- Created a new instance of iVentoy
- Cloned the old persistant data from old container (v1.0.19) to new (latest tag v.1.0.20?)
- Deleted old log.txt file from the new containers persistant data as it grumbles about it when first booted.
- Started container.
Container now runs, but strangely still shows Iventoy version 1.0.19! Is this correct or a glitch? Does yours show iVentoy v1.0.20 in the Web UI? If so migration may be really glitchy?
This screenshot is running the latest tagged image which i was assuming should show a bump in iventoy version to v1.0.20?! (I have also cleaned my browser cache and tried it in 3 other browsers.)
Log from 'latest' new container version.
================================
2024-06-18 16:31:25 INFO Starting iVentoy
2024-06-18 16:31:25 INFO DEBUG:
2024-06-18 16:31:25 DEBUG Copy data files succesful
2024-06-18 16:31:25 DEBUG Copying user files succesful
iventoy start SUCCESS PID=24
Please open your browser and visit http://127.0.0.1:26000 or http://x.x.x.x:26000 (x.x.x.x is any valid IP address)
2024/06/18 16:31:28.880 [PXE] [5] wim </sources/boot.wim> already exist
2024/06/18 16:31:28.881 [PXE] [5] Find in /boot/bcd ...
2024/06/18 16:31:28.881 [PXE] [5] Find wim flag:</boot.wim>
2024/06/18 16:31:28.881 [PXE] [5] Find wim flag:</sources/boot.wim>
2024/06/18 16:31:28.881 [PXE] [5] wim </sources/boot.wim> already exist
2024/06/18 16:31:28.881 [PXE] [5] Find wim flag:</sources/boot.wim>
2024/06/18 16:31:28.881 [PXE] [5] wim </sources/boot.wim> already exist
2024/06/18 16:31:28.882 [PXE] [5] [WIM 0] /sources/boot.wim [Seek:37939200 Size:144734333 RecSeek:0]
2024/06/18 16:31:28.882 [PXE] [5] collect wim files finished.
2024/06/18 16:31:28.882 [PXE] [5] Phase1 parse image <iso/Windows/Windows_7_AIO_(UEFI).iso> finished success
2024/06/18 16:31:32.205 [PXE] [6] No boot.wim found.
2024/06/18 16:31:32.205 [PXE] [6] img <iso/VMWare/VMware_VCSA_all_7.0.1_17327517.iso> OS type:WinPE
2024/06/18 16:31:32.205 [PXE] [6] collect wim files for <iso/VMWare/VMware_VCSA_all_7.0.1_17327517.iso> ...
2024/06/18 16:31:32.205 [PXE] [6] collect wim files finished.
2024/06/18 16:31:32.205 [PXE] [6] Phase1 parse image <iso/VMWare/VMware_VCSA_all_7.0.1_17327517.iso> finished success
2024/06/18 16:31:32.205 [PXE] ================= PXE IMG DUMP =================
2024/06/18 16:31:32.205 [PXE] [1] <Linux/ubuntu-23.10.1-desktop-amd64.iso> <5173995520> <x86_64> Initrd:1
2024/06/18 16:31:32.205 [PXE] [2] <Windows/Win11_23H2_English_x64_(UEFI).iso> <6705289216> Wim:0/1
2024/06/18 16:31:32.205 [PXE] [3] <Windows/Win11_23H2_English_x64_(BIOS).iso> <6860177408> Wim:0/1
2024/06/18 16:31:32.205 [PXE] [4] <Windows/Win10_22H2_EnglishInternational_x64v1(UEFI-BIOS).iso> <6135633920> Wim:0/1
2024/06/18 16:31:32.205 [PXE] [5] <Windows/Windows_7_AIO_(UEFI).iso> <4093181952> Wim:0/1
2024/06/18 16:31:32.205 [PXE] [6] <VMWare/VMware_VCSA_all_7.0.1_17327517.iso> <8092354560> Wim:0/0
2024/06/18 16:31:32.205 [PXE] [7] <VMWare/ESX_7.0U1c.iso> <386863104> Initrd:0
2024/06/18 16:31:32.205 [PXE] [8] <Tools/WinPE11_10_8_Sergei_Strelec_x86_x64_2023.06.25_English.iso> <5026682880> Wim:0/5
2024/06/18 16:31:32.205 [PXE] ================================================
2024/06/18 16:31:32.205 [PXE] Module init OK ...
2024/06/18 16:31:32.205 [PXE] Module init start ...
2024/06/18 16:31:32.205 [PXE] Module init OK ...
2024/06/18 16:31:32.205 [PXE] Module init start ...
2024/06/18 16:31:32.205 [PXE] Module init OK ...
2024/06/18 16:31:32.205 [PXE] Module init start ...
2024/06/18 16:31:32.218 [HTTP] HTTP API service is running on 0.0.0.0:26000 ...
2024/06/18 16:31:32.268 [PXE] Module init OK ...
2024/06/18 16:31:32.268 [PXE] Module init start ...
2024/06/18 16:31:32.282 [PXE] Module init OK ...
2024/06/18 16:31:32.282 [PXE] <535735305a57776f55696b6757475676626968534b5342445546556752544d744d5449304d4342574d69424149444d754e44424853486f3d>
2024/06/18 16:31:32.282 [PXE] <595751354d4449314d444135595455784d4463774e6a41774d6a55354d47466b4e5445355954426c4d47593d>
2024/06/18 16:31:32.282 [PXE] ef274c34ec4ddb76d3a1d0423eed23fb13ab47d2bedb111a6e97947829783f3a
2024/06/18 16:31:32.282 [PXE] ====================== SYSTEM IP LIST ===================================
2024/06/18 16:31:32.282 [PXE] [1] 192.168.1.41 255.255.255.0 192.168.1.1 eth0
2024/06/18 16:31:32.282 [PXE] =========================================================================
2024/06/18 16:31:32.282 [PXE] PXE cofigure recovery ...
2024/06/18 16:31:32.283 [PXE] data/config.dat is valid, now recover data ...
2024/06/18 16:31:32.283 [PXE] Recover: dhcp server mode 1
2024/06/18 16:31:32.283 [PXE] Recover: boot background mode 0
2024/06/18 16:31:32.283 [PXE] Recover: efi boot file 0
2024/06/18 16:31:32.283 [PXE] Recover: boot resolution 1280 x 800
2024/06/18 16:31:32.283 [PXE] Recover: ip:192.168.1.40 mask:255.255.255.0 gateway:192.168.1.1 pool:[192.168.1.200-192.168.1.219]
2024/06/18 16:31:32.283 [PXE] Recover: HTTP port:16000 NBD port:10809 TFTP timeout:5 TFTP max-retransmit:3
2024/06/18 16:31:32.283 [PXE] Recover filter [deny] mode
2024/06/18 16:31:32.284 [PXE] [2] recover img data for <iso/Windows/Win11_23H2_English_x64_(UEFI).iso>
2024/06/18 16:31:32.284 [PXE] [2] recover auto script </app/scripts/W11/Win11_23H2_English_x64_(UEFI)/autounattend.xml>
2024/06/18 16:31:32.284 [PXE] [2] auto_default:0 auto_timeout:0 auto_count:1
2024/06/18 16:31:32.284 [PXE] [2] recover injection </app/injectionfiles/Windows/windows_injection.7z>
2024/06/18 16:31:32.284 [PXE] [3] recover img data for <iso/Windows/Win11_23H2_English_x64_(BIOS).iso>
2024/06/18 16:31:32.284 [PXE] [3] recover auto script </app/scripts/W11/Win11_23H2_English_x64_(BIOS)/autounattend.xml>
2024/06/18 16:31:32.284 [PXE] [3] auto_default:0 auto_timeout:0 auto_count:1
2024/06/18 16:31:32.284 [PXE] [3] recover injection </app/injectionfiles/Windows/windows_injection.7z>
2024/06/18 16:31:32.284 [PXE] [4] recover img data for <iso/Windows/Win10_22H2_EnglishInternational_x64v1(UEFI-BIOS).iso>
2024/06/18 16:31:32.284 [PXE] [4] recover auto script </app/scripts/W11/Win10_22H2_EnglishInternational_x64v1_(UEFI)/autounattend.xml>
2024/06/18 16:31:32.284 [PXE] [4] recover auto script </app/scripts/W11/Win10_22H2_EnglishInternational_x64v1_(BIOS)/autounattend.xml>
2024/06/18 16:31:32.284 [PXE] [4] auto_default:0 auto_timeout:0 auto_count:2
2024/06/18 16:31:32.284 [PXE] [4] recover injection </app/injectionfiles/Windows/windows_injection.7z>
2024/06/18 16:31:32.284 [PXE] [5] recover img data for <iso/Windows/Windows_7_AIO_(UEFI).iso>
2024/06/18 16:31:32.284 [PXE] [5] auto_default:0 auto_timeout:0 auto_count:0
2024/06/18 16:31:32.284 [PXE] [5] recover injection </app/injectionfiles/Windows/windows_injection.7z>
2024/06/18 16:31:32.284 [PXE] =============== PXE cofigure recovery finished ===============
2024/06/18 16:31:32.284 [PXE] ########## iVentoy auto running. #########