Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
 iventoy crash randomly after client connects
#1
Hey,

just found out about iventoy, and wanted to try it out.

Setup:

Host: Debian 12. iventoy 1.0.10

Client: Various Notebooks from various Vendors.

DHCP managed by opnsense.

Configuration:

(cant post picture, because forum says: "The message is too long. Please enter a message shorter than 65535 characters (currently 176356).")



Log.txt:

(cant post log.txt. because this forum says its to long, so here pastebin: https://pastebin.com/s5eBPP4z )


Sometimes the Menu shows up, and i could choose a iso, but than nothings happens, because iventoy crashed (its annoing too that the websites always says: "iventoy crashed, exiting the site!" or something like that instead simply let it open and only to give a warning)
Reply
#2
Did different ISO files make difference?
Try only put one standard Windows ISO or an linux (ubuntu) iso.
Reply
#3
(07-10-2023, 03:18 PM)longpanda Wrote: Did different ISO files make difference?
Try only put one standard Windows ISO or an linux (ubuntu) iso.

no. it didnt matter wich isos. tried few "standard" ones like debian, arch, etc.
Reply
#4
The latest Release, x.x.16 have exact the same problem.

Didnt matter wich ISOs or Hardware installed.

Log:https://pastebin.com/v99Arbme
Reply
#5
Currently I have no idea about it.
There is nothing special in the log.
Many other peoples use iVentoy linux version and work fine.
Maybe something with the OS environment?
Try to run iVentoy in a CentOS 7 OS (you can use VM for test) and test.
iVentoy was built under CentOS 7.X OS, so if you run it in CentOS 7.X it should have no compatible problem.

PS: When iVentoy crash, did you check that the process really exit ?(by ps -ef)
Or maybe you can turn on the coredump flag in the OS and make it to generate a core file for debug.
Reply
#6
lol ok?

Yes. the process exits.

Its crash everytime, didnt matter on wich Distro, with that:

2023/07/20 12:18:50.221 [PXE] ===========================================================
2023/07/20 12:18:50.221 [PXE] iVentoy 1.0.16 [Linux 64] is running now ...
2023/07/20 12:18:50.221 [PXE] ===========================================================
2023/07/20 12:18:50.222 [HTTP] NBD service is running on 192.168.2.5:10809 ...
2023/07/20 12:18:50.222 [DHCP] DHCP service is running ...
2023/07/20 12:18:50.222 [TFTP] TFTP service is running ...
2023/07/20 12:18:50.222 [TFTP] TFTP write thread is running 29 ...
2023/07/20 12:18:50.222 [HTTP] HTTP PXE service is running on 192.168.2.5:16000 ...
2023/07/20 12:18:50.225 [HTTP] API request: <{"method":"query_status"}>
2023/07/20 12:18:50.241 [HTTP] API request: <{"method":"sys_ip_list"}>
2023/07/20 12:18:50.255 [HTTP] API request: <{"method":"get_dhcp_mode"}>
2023/07/20 12:18:57.729 [DHCP] Snooping 74-56-3c-68-bf-65 MSG:<DISCOVER> ARCH:<EFI BC> (nil)
2023/07/20 12:18:57.729 [DHCP] snopping add client 74-56-3c-68-bf-65
2023/07/20 12:19:00.841 [DHCP] Snooping 74-56-3c-68-bf-65 MSG:<REQUEST> ARCH:<EFI BC> 0x7f76307ca740
2023/07/20 12:19:00.842 [TFTP] Parse tftp option(tsize,0)
2023/07/20 12:19:00.842 [TFTP] Parse tftp option(blksize,1468)
2023/07/20 12:19:00.842 [TFTP] Unsupported tftp option windowsize 4
2023/07/20 12:19:00.842 [TFTP] TFTP RRQ client 192.168.2.247:1720 download <iventoy_loader_16000> start ...
2023/07/20 12:19:00.842 [DHCP] snooping record found 192.168.2.247
2023/07/20 12:19:00.842 [PXE] Client 74-56-3c-68-bf-65 start PXE install in UEFI X64 mode.
2023/07/20 12:19:00.842 [TFTP] DHCP External client 192.168.2.247 should use loader ipxe.x64.ipxe.efi.0
2023/07/20 12:19:00.842 [TFTP] Start send file iventoy_loader_16000 to 192.168.2.247:1720 with blksize 1468, has oack 1
2023/07/20 12:19:00.843 [TFTP] Recv an ERROR opcode pkt from client 192.168.2.247:1720.
2023/07/20 12:19:00.848 [TFTP] Parse tftp option(blksize,1468)
2023/07/20 12:19:00.848 [TFTP] Unsupported tftp option windowsize 4
2023/07/20 12:19:00.848 [TFTP] TFTP RRQ client 192.168.2.247:1721 download <iventoy_loader_16000> start ...
2023/07/20 12:19:00.848 [DHCP] snooping record found 192.168.2.247
2023/07/20 12:19:00.848 [PXE] Client 74-56-3c-68-bf-65 start PXE install in UEFI X64 mode.
2023/07/20 12:19:00.848 [TFTP] DHCP External client 192.168.2.247 should use loader ipxe.x64.ipxe.efi.0
2023/07/20 12:19:00.848 [TFTP] Start send file iventoy_loader_16000 to 192.168.2.247:1721 with blksize 1468, has oack 1
2023/07/20 12:19:00.958 [TFTP] Finished send file to 192.168.2.247:1721 with blksize 1468 blks 766
2023/07/20 12:19:05.532 [DHCP] Snooping 74-56-3c-68-bf-65 MSG:<DISCOVER> ARCH:<EFI BC> 0x7f76307ca740
2023/07/20 12:19:06.591 [DHCP] Snooping 74-56-3c-68-bf-65 MSG:<REQUEST> ARCH:<EFI BC> 0x7f76307ca740
user@iventoy:~/iventoy-1.0.16$

Maybe it is that?

2023/07/20 12:19:00.843 [TFTP] Recv an ERROR opcode pkt from client 192.168.2.247:1720.

The only thing i didnt tried, is to use iventoys own dhcp server (because it isnt possible, because i have already one r unning)

i would click on detail, but isnt possible, because everytime iventoy crash, this  message pop ups and force close the tab

https://i.postimg.cc/pT98CnDW/grafik.png

(wich is reaaaaaaally annoying for debugging)
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)