From: vic.thacker@fastmail.fm
To: "leimy2k via 9fans" <9fans@9fans.net>
Subject: Re: [9fans] PXE tftpload: file does not exist
Date: Sun, 23 Jul 2023 08:12:25 +0900 [thread overview]
Message-ID: <f6010be2-5612-43f4-97e3-7b8a1c6302a4@app.fastmail.com> (raw)
In-Reply-To: <3606FCBC-A925-4D16-8699-E6875461F712@germteig.com>
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 <marco@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 <steve@quintile.net> wrote:
>>>
>>> are you running the tftp server?
>>>
>>>
>>>> On 17 Jul 2023, at 4:38 pm, Marco Feichtinger <marco@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
prev parent reply other threads:[~2023-07-22 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 15:37 Marco Feichtinger
2023-07-17 18:47 ` Steve Simon
2023-07-17 20:25 ` Marco Feichtinger
2023-07-22 6:21 ` Marco Feichtinger
2023-07-22 23:12 ` vic.thacker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f6010be2-5612-43f4-97e3-7b8a1c6302a4@app.fastmail.com \
--to=vic.thacker@fastmail.fm \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).