@stiger Did you solve it by changing the stuff in the database?
Posts made by Sebastian Roth
-
RE: ipxe menu problem
-
RE: Location Plugin - enhancement of behavior
@Wayne-Workman Thanks for looking into this! About normalized DB structure: Usually one should move information to an extra table if it is redundant or used in various combinations. That’s not the case here because CIDRs won’t be redundant within one organization. So I think “the harder route” - as you call it - is not advisable anyhow. I am with you there.
-
RE: two clients same image
@trebor said:
The FOG server is a Debian 9 running headless with FOG 1.5.0-RC-10.
Which branch of FOG did you install?
dev-branch
orworking
? I just want to make sure we know which version exactly you have.As Wayne said, please check the MAC addresses of those two machines (boot up windows -> command prompt ->
ipconfig /all
).When I delete host FOG deletes the “client A” host and images.
FOG does not delete images when you delete a host! Are you sure this is happening?
-
RE: Cant PXE Boot = PXE-T01: File not Found
Interesting… the bug report just posted ends with stating that this is fixed in version
4.3.5-1
. In the logs posted I see version4.3.5-3
being installed. Possibly a regression?Edit: Here we go I think: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862680
Although I really like debian I am still not sure if this is something we should fix. Maybe we do and next time debian is doing something different again…?!
-
RE: Cant PXE Boot = PXE-T01: File not Found
@Wayne-Workman Yeah sure we can just force it. But I am wondering why this is the case. Searching more I found this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815319
So the issue has been around for a fair bit of time. But I still haven’t figured out if this is just an issue with the debian specific start scripts or if it’s actually a newer isc-dhcp-server version doing the env variable check… then fails if it’s not set - very poor I find.
-
RE: Cant PXE Boot = PXE-T01: File not Found
@wayne-workman Thanks heaps for looking into this! Reading through a couple of old posts on the internet I kind of came to the same conclusion that it’s an issue with a missing/wrong
/etc/default/isc-dhcp-server
parameter.Hmmmm, I am wondering how we are going to fix this. Why is it working in debian 8? I’d actually expect debian (dpkg) to generate
/etc/default/isc-dhcp-server
properly! -
RE: Cant PXE Boot = PXE-T01: File not Found
@404 No worries. Just trying to keep things a bit sorted.
In the same directory where you have the
installfog.sh
script a subdirectoryerror_logs/
is created… you should find two log files there. Upload both and we’ll have a look. -
RE: ipxe menu problem
@stiger Sorry for taking so long to look into this. I can confirm this being an issue but only if a number is used as first character in the name! If you name it
ape
or justpe
you don’t have that issue. I have looked through the JS and CSS code but as I am not an expert with that stuff I couldn’t come up with a quick fix yet.Playing with an example of
fadeToggle
(which we use in the web UI) I see that this is not generally impossible the way we use it - our code and example website. Maybe someone else has some time to play with this and can figure this out.So back to your problem of not being able to edit that entry. Till we find a fix in the web UI you can modify the entry in the database by hand.
shell> mysql -u root -p Enter password: ... mysql> use fog; ... mysql> UPDATE pxeMenu SET pxeName='fog.0pe' where pxeName LIKE '%0pe%'; ... mysql> quit; shell>
Then reload the
iPXE Menu Item Settings
page and you should be able to edit the menu entry. You can still have0pe
as Description to be seen by users in the FOG menu on boot. -
RE: Cant PXE Boot = PXE-T01: File not Found
@404 As you can see in Wayne’s message signature he’s got an automatic test environment that does daily installs on several different distros/versions (including debian 9) and we don’t see any issue there at the moment. If you are still keen to find the issue please post your install logs here.
For the other things like “what can FOG do/don’t do” I’d ask you to open a new thread and ask your specific questions. We try to keep things sorted a bit here so other people can follow if they have the same issue. For those people it’s not helpful if several different issues are being discussed in one thread.
-
RE: FreeNas FTP error
@lubo Carefully read through this to understand why this happens and how to solve it: https://forums.fogproject.org/topic/9850/freenas-ftp-command-question
-
RE: Uncompleted multicast
@kkroflin said:
I’ve checked master and storage nodes and md5 checksum is the same.
Can you please post a picture of that just to make sure we’re looking at the same things here.
Other than that… What network setting is used with those VMs? Is FOG running on the host itself? Where is the storage node, where the master node running?
-
RE: problem captures image
@NatLanis Have you deployed that image to a machine yet?
-
RE: Location Plugin - enhancement of behavior
@Wayne-Workman Yeah, interesting one! Thanks. I’d vote for that. Shouldn’t be too hard to add.
-
RE: Uncompleted multicast
@kkroflin The important error message here is
pigz: skipping: <stdin>: corrupted -- incomplete deflate data
It means that the image is somehow corrupt and cannot be extracted because of that. We had someone with that not long ago and in his case it turned out that he had a FOG storage node where the image hasn’t been transfered to properly. After he fixed that (re-transfer the image from master to storage) the deploy went fine.
Previously I haven’t used multicast with FOG so I don’t know if this is a new issue or an old one.
Multicast is one of FOG’s key features and it’s part of it since years.
Also, in case of an error like this, I would expect to receive some clear error state …
Tom changed that behavior not that long ago - see here. Though I don’t know why from the top of my head. I think there was an issue with some devices (maybe MS Surface) that would fail “lightly” and we wanted to make those work. Maybe see if you can find a discussion on this in the forum from around that date (4th of April 2017).
-
RE: problem captures image
@NatLanis Please post the pictures as JPEG or PNG instead of posting a proprietary DOCX file. Pictures will be displayed inline in the forum here.
-
RE: How do I change to order of the Location ID's?
@m-fitzgerald Thanks for opening a new one on this.
The problem is that if a PC has not been assigned to a node it will try and pull an image from the wrong node
But why don’t you assign the correct location as being asked when registering? Sorry, this might sound like a stupid question but I don’t get where exactly you are headed with this.
-
RE: FOG will not resize a hard drive after deployment.
@m-fitzgerald Good to hear this fixed the issue for you. Though from my point of view it’s only partly solved. If you capture the image again you will need to edit that file again. So question remains why it does not recognize your boot partition as such. Usually this happens if Windows is not installed as English version or partition labels have been modified by hand. As I said, take a screen shot of the disk management view in Windows and post here. I am fairly sure we can figure out why that is.
Follow on question though. How do I edit the order of Storage Nodes?
We try to keep topics separate. Please open a new thread for this! Won’t answer here.
-
RE: "Boot from local drive" menuitem is broken on HP ProLiant BL460c G6 (c7000 blade chasis)
@jones Ok, thanks for the picture. Did you read trough all the other things I mentioned?
-
RE: FOG will not resize a hard drive after deployment.
@m-fitzgerald Can you please edit
d1.fixed_size_partitions
and make it1:3
. Then re-deploy that image to a fresh machine and see what you get.As well can you take a picture of the disk management view in Windows on the source machine and post here?