|06:49||antaresgades has joined IRC (email@example.com)|
Good morning. I am having an issue booting raspberries pi. The server was working OK two weeks ago, hoever yesterday none of the raspberry pi 3b+ (no SD card) boot anymore.
I've found two problems so far and some information about on Channel log from 16 May 2022 (dnsmasq error 0 related issue)
However, I'm trying to apply what alkisg suggested there but no success, providing pxe-service-tag line at ltsp-dnsmasq.conf is unused
Additionally, output of ltsp ipxe shows that the system is looking for 192.168.67.1 as server address but server is installed at 192.168.1 and working without issues until yesterday (well, last working boot was about 2 weeks ago, just in case the problem could be package updates or something)
A gist with dnsmasq log output and ltsp ipxe is available at
Udpate: I forgot to restart dnsmasq service so I did and it look that sudo mkdir -p /srv/tftp/srv.... etc command stated by alkisg works as a solution.
However, I can't figure out how the issue happened... package update seems the most probable thing, because it has happened also with another server under the same conditions.
So maybe disable all automatic updates of the servers could be a good idea.
|08:38||jgee8 has joined IRC (firstname.lastname@example.org)|
|08:40||jgee has left IRC (email@example.com, Ping timeout: 252 seconds)|
|08:40||jgee8 is now known as jgee|
Nah I don't think package updates can cause such issues
But where could it be providing it's been working for a year and suddenly it stop working in two different servers for the same cause?
|10:39||shored1 has joined IRC (shored1!~shored@user/shored)|
|10:40||shored has left IRC (shored!~shored@user/shored, Ping timeout: 244 seconds)|
Is there anythng that people who have suffered this issue could do to help improving/solving the issue (provide logs, package versions, installation details...)?
antaresgades: I'm on vacations; I suggest that you create a github discussion about this issue, add as much info as you can, so that we can troubleshoot there
Most probably it will be related to an administrative action, not to software updates
Ok sorry I din't know you were on vacation. Enjoy it as possible. I'll try to open an issue ASAP
|13:12||eu^host-5-154-17 has joined IRC (firstname.lastname@example.org)|
|13:50||antaresgades has left IRC (email@example.com, Quit: Client closed)|
|14:55||Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)|
|14:55||Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)|
|15:38||woernie has joined IRC (woernie!~werner@2001:9e8:e24a:4500:9184:1095:82e9:5b1d)|
|16:12||eu^host-5-154-17 has left IRC (firstname.lastname@example.org, Quit: Client closed)|
|17:51||oh207 has joined IRC (email@example.com)|
|18:03||oh207 has left IRC (firstname.lastname@example.org, Ping timeout: 256 seconds)|
|20:18||Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds))|
|20:31||Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)|
|21:13||woernie has left IRC (woernie!~werner@2001:9e8:e24a:4500:9184:1095:82e9:5b1d, Remote host closed the connection)|
|21:51||Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 240 seconds)|
|22:05||Cueball has joined IRC (Cueball!~quassel@2001:8b0:ffb3:0:ac6a:aaff:fe7e:9c3)|
|22:15||Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)|
|23:26||Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)|
|23:36||Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)|