Unable to register and inventory new Dell PCs
-
On my previous thread I laid out the details:
Running FOG 1.2 on Ubuntu 12.04LTS. This server has worked flawlessly for several hundred machines until this new batch of Dells. The BIOS is so current it’s not even listed on the Dell website. We also tried rolling back to an older version of BIOS, no difference. I’ve run updates on the FOG server to ensure that all the requisite software is current (MAP). The only update I haven’t performed is on Ubuntu itself and I don’t intend to do that.I’ve attempted compiling my own Linux kernel with the current 4.4.1 and adding in my own modules. I was successful except for the last part and am out of time to try to learn compiling in order to solve my own problem.
So I’m back. I have Dell XPS8900s and Dell Latitude laptops (NIC Realtek PCIe GBE Family Controller RTL8167). In the last thread, mods assumed that it was the NIC given the errors I was receiving when trying to PXE these machines.
I’ve also tried a known working USB NIC that is compatible with Linux to bypass the onboard NIC when registering with FOG.
Any new suggestions?
-
@Tom-Elliott You are fired.
-
@Wayne-Workman don’t lie, there most certainly is completely random in the computer world.
-
@Tom-Elliott said:
@Wayne-Workman not pseudorandom it’s completely random
No such thing in the computer world. :-)
-
@Wayne-Workman not pseudorandom it’s completely random
-
@mattyb It is clear text, FOG generates a 32 character long pseudorandom password for this.
-
@Wayne-Workman Agreed, but what’s not clear is that the default password in this field is not actually my password, encrypted. The management password needs to be in this field in clear text. The same applies to other config sections on the management web interface. I should have just tried it earlier.
-
@mattyb said:
That was it. Same headache as this OP: Point #3. Registering and uploading!
Just going to point out that those steps from that post are also in the Wiki article you said you went through ;-) Glad you got it working.
-
That was it. Same headache as this OP: Point #3. Registering and uploading!
-
I think my issue is in Storage Node / DefaultMember / Management Password. I updated that to match all other configs and now I get actual log choices. Trying to upload now.
-
@Wayne-Workman There’s nothing to expand. Below the pause button it says ‘invalid folder’ and nothing else.
-
@mattyb The error should show you what it tried for the username and password. navigate back to the log viewer and pay attention to the error.
-
@Wayne-Workman Interesting. Navigating to fog Configuration / Log Viewer straight away says there’s an error with the Fog “ftp_login(): Login incorrect.”
In my Fog Configuration / TFTP Server, the username and password are correct, as are the fog config files on the server.
-
@mattyb It wouldn’t hurt.
Anything in the apache error logs?
FOG Configuration -> Log Viewer -> Apache Error Log
-
@Wayne-Workman Logging in to ftp://<IP> works fine, I can read and write. Do I need to test at the specific image directory?
-
@mattyb said:
Username ‘Root’ has seems to have the proper system access to the image directory that it needs based on the result of the ls -laR /images command.
The username that is used in all of the credentials you checked must have system access to the image directory.
Can you try to log into the server via FTP using the credentials you confirmed? There are examples of how to do this towards the top of that article. Do it from a remote computer - not from the fog server.
-
I’m getting the Trunk-specific database error when uploading an image (same as referenced in the WIKI here. I’ve checked all four locations for the correct username/password combination and it’s correct. I’ve checked the filesystem of the new FOG server that Sebastian walked me through, and it’s the correct EXT4. Username ‘Root’ has seems to have the proper system access to the image directory that it needs based on the result of the ls -laR /images command.
-
@Sebastian-Roth I would like to thank Sebastian for his time in helping me diagnose this issue. We spent a substantial amount of time working through the issue and I learned a lot through the process! We are working through uploading images for these two machines as I type and all appears to be going well now that I’m on the Trunk version.
-
@Sebastian-Roth said:
The best thing to do would be to get together two or three people and do some kind of review. Do you think we could get together with @Tom-Elliott on a chat and start sorting through the wiki?
We need to. It needs to be organized like a book - everything in the contents. The search engine is the index.
Old stuff needs to be labeled “OLD” or even removed. I started a list in our secret area already.
-
@Wayne-Workman said:
main problem with all these other articles is that I’m not sure if they are sound or not.
Good point! As well there is a lot of pre 1.2.0 stuff in some of the articles which I suspect is more confusing than helping anyone (people who still run 0.32 either know what they do or just don’t care anyway). The best thing to do would be to get together two or three people and do some kind of review. Do you think we could get together with @Tom-Elliott on a chat and start sorting through the wiki?
