Just a hunch, but perhaps you haven't added the cpu server kernel to /lib/tftpd to be loaded.
-vic On Sat, Jul 22, 2023, at 15:21, Marco Feichtinger wrote: > The error was caused by a misconfigured ndb. > Thanks to Frank D. Engel Jr., which gave me the hint in a separat email. > > So I played around with my ndb files, and concluded,… that I don’t quit > understand how the ndb works. > Given following basic ndb configuration: > ; cat /lib/ndb/local > > # > # files comprising the database, use as many as you like, see ndb(6) > # > database= > file=/lib/ndb/local > file=/lib/ndb/common > > # > # because the public demands the name localsource > # > ip=127.0.0.1 sys=localhost dom=localhost > > # > # main network for home.csr.germteig.com > # > ipnet=main ip=10.0.0.0 ipmask=255.0.0.0 > ipsubmask=255.255.0.0 > > # > # server subnetwork > # > ipnet=srv ip=10.0.0.0 ipmask=255.255.0.0 > fs=fs.main.com > auth=auth.main.com > authdom=servers.main.com > > sys=auth > ip=10.0.0.3 ether=<mac address> > dom=auth.main.com > > sys=cpu > ip=10.0.0.4 ether=<mac address> > ip=10.0.0.5 ether=<mac address> > dom=cpu.main.com > bootf=/386/9boot > > sys=fs > ip=10.0.0.10 ether=<mac address> > ip=10.0.0.11 ether=<mac address> > dom=fs.main.com > ; > > With that, the cpu server boots just fine. > It reads its config file under /cfg/pxe/ and loads the kernel. > > Now if I change the ip address of that cpu server to following: > sys=cpu > ip=10.0.1.4 ether=<mac address> > ip=10.0.1.5 ether=<mac address> > dom=cpu.main.com > bootf=/386/9boot > > Then I get the error "tftpload: file does not exist”. > But why? > > -marco > >> On 17.07.2023, at 22:25, Marco Feichtinger <ma...@germteig.com> wrote: >> >> yes, ip/dhcpd and ip/tftpd are running on the file server >> >> -marco >> >>> On 17.07.2023, at 20:47, Steve Simon <st...@quintile.net> wrote: >>> >>> are you running the tftp server? >>> >>> >>>> On 17 Jul 2023, at 4:38 pm, Marco Feichtinger <ma...@germteig.com> wrote: >>>> >>>> I have a standalone file server, and a separate standalone auth server. >>>> >>>> I tried to pxe boot a cpu server. >>>> It gets the /386/9boot to load fine, but then it seems, that it can’t >>>> retrieve the file /cfg/pxe/<mac address> from my file server. >>>> >>>> here is the screen output during bootup: >>>> 9boot gz…starting protected-mode loader at 0x900020 >>>> >>>> Plan 9 from Bell Labs PXE boot loader >>>> cpu0: 1800MHz GenuineIntel Atom (cpuid: AX 0x106CA DX 0xBFEBFBFF) >>>> ELCR: CC80 >>>> #l0: i82598: 10Gbps port 0XFE980000 irq 11: <mac address> >>>> #l0: i82598: 10Gbps port 0XFE980000 irq 10: <mac address> >>>> 498M memory: 498M kernel data, 0M user, 18M swap >>>> pxe on ether0 . >>>> <sysname> (10.0.10.1!69): /cfg/pxe/<mac address> >>>> .T.T.T.T.T.T.T.T.T.Ttftpread1st: failed to connect to server (10.0.10.1!69) >>>> >>>> failed. >>>> tftpload: file does not exist >>>> >>>> Which is strange, because I did create the file on my file server. >>>> It looks like following: >>>> bootfile=ether0!/386/9pccpuf >>>> nobootprompt=tcp >>>> readparts=1 >>>> mouseport=2 >>>> monitor=vesa >>>> vgasize=1024x768x8 >>>> user=bootes >>>> sysname=<sysname> >>>> >>>> Does anyone know what might be the problem? >>>> Thanks. >>>> >>>> -marco >>>> ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T8484142ec51acbb7-Md540f99a0c436e51a04217a8 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
