Posts made by cklemm

Ok, the file is pretty big, so if you want i can upload the whole thing. That said, this is what i picked out from it:

---

The following packages will be REMOVED:
curl libcurl4 php7.1-curl
The following NEW packages will be installed:
libcurl13

---

The following additional packages will be installed:
libcurl4
The following packages will be REMOVED:
libcurl3
The following NEW packages will be installed:
libcurl4 php7.1-curl
0 upgraded, 2 newly installed, 1 to remove and 145 not upgraded.

---

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libcurl3 : Conflicts: libcurl4 but 7.58.0-2ubuntu3.2 is to be installed
libcurl4 : Conflicts: libcurl3 but 7.58.0-2ubuntu2 is to be installed
E: Broken packages
ii apache2 2.4.33-1+ubuntu17.10.1+deb.sury.org+1 amd64 Apache HTTP Server
ii bc 1.07.1-2 amd64 GNU bc arbitrary precision calculator language
ii build-essential 12.4ubuntu1 amd64 Informational list of build-essential packages
ii cpp 4:7.3.0-3ubuntu2 amd64 GNU C preprocessor (cpp)

---

So, maybe i have too new a version of curl installed? I’m not sure how that would happen, we don’t use this server for anything but fog. Would that cause the installer to fail this way?

I’m running Ubuntu 18.04.

Hello,
I’m trying to upgrade from 1.5.2 to 1.5.4 to address some issues we’ve been having deploying and capturing images. When i try to run the installer, it seems to go fine until it gets to here:

• Confirming package installation

• Checking package: apache2…OK

• Checking package: bc…OK

• Checking package: build-essential…OK

• Checking package: cpp…OK

• Checking package: curl…Failed!

At that point it quits out. The web GUI still shows version 1.5.2 is active. I have installed curl separately and that has not seemed to make a difference.

If I should just be making tickets about the other issues before upgrading, please let me know.

@sebastian-roth Just an update, i was able to get this to work even in another building. Apparently this was a problem specific to the random old switch i was using to test this stuff. Thanks so much Sebastian and George.

So i still don’t have the packet info from the hub, but i restarted the computer while it was hooked into the hub, and just for kicks i decided to try to register the client. It worked.

A month of restarting the client and as soon as i plug it into a hub of all things it works. Right now it is capturing the image (at least, i’m pretty sure that’s what it’s doing). Does that give you any information? it makes me think it is a network configuration issue. I’m still going to try to capture the packets, but i thought this was worth posting.

@george1421 I did not change the IP after FOG was installed. Is there something i can check that would show which IP FOS is pointing at so i can be sure that is correct?

@sebastian-roth Ok, i’m working on it. I’m finding it hard to get a working hub, but i’ll post here when i have it.

@george1421 You seem to understand the problem exactly. You are also correct that the server itself, the client, and the DHCP server are all on different vlans. This is important to the way our network is set up, and i really need this to be able to work across vlans. If it matters, i could move the fog server to the same vlan as the DHCP server, but the client absolutely will not be on that vlan.

I don’t think that the fog server is running dhsmasq, unless it automatically installed when i install fog.
ps -ef | grep dnsmasq
The above only shows the command itself. I’m not an expert (obviously), but i think it isn’t running. If there is something else you’d like me to check, just let me know.

@sebastian-roth So, this is my first time setting up a fog server, but apparently there used to be one that covered all our clients. It should work.

Both the server and the client are connected to the same switch already, would that matter as far as capturing the packets?

As far as the network, the DHCP server isn’t even in the same building. Sorry i didn’t mention that, i didn’t know it was important.

@sebastian-roth Here’s the file:
https://drive.google.com/open?id=1a7o5ylngM3ixO1wgzXZh9Mt0v_4o5NmS
We’ll definitely have to try what we can without touching the DHCP server before i go playing around with it. You’re also right that the file was less than a third the size this time.

The client MAC address is 40B0.341C.FB6D.

Also thanks for sticking with this, i’d be really stuck without the help.

@sebastian-roth We have a separate DHCP server running server 2012. I have options 66 and 67 setup for the scope in question. There are also the various vendor classes and such that i can’t remember the specifics of, but were mentioned in a FOG Wiki entry about running a separate DHCP server. Those were set up as well. Is there some specific information from this server that you need?

@sebastian-roth The file came out to be, well, bigger than i was expecting. Anyway, here it is:
https://drive.google.com/open?id=1S-O-TSydukduMd6CKs04595qYTBW8I99
If it’ll help, i’m running Ubuntu 17.10.

After doing this a few more times, it looks like there isn’t anything that shows up during the time that the client is trying to register. kadath-fog-test is the hostname of the client, in case that isn’t clear.

@sebastian-roth Yes, i have no problems getting into the web page.

So, i realize i made the mistake of posting this on a Friday afternoon, but i’m still as stuck as i was previously. Has anyone else run into this?

@tom-elliott Sorry about the confusion. I’m having some trouble with video, but there really only are a few screens. Also, sorry, for imgur, but apparently the images are too big to be uploaded directly.

https://imgur.com/udh3Id2
This shows the basic booting to the NIC.

https://imgur.com/2yqCPc3
This is the computer at Fog OS, showing not registered.
I selected ‘Perform Full Host Registration and Inventory’ though the same thing happens with quick registration.
Then the computer reboots and shows this:

https://imgur.com/GK018fn
This is where it gets stuck.

Does that help?

EDIT: And the images aren’t showing up anyway. Added links.
Also, apparently if i leave it at that screen long enough it moves to this screen:
https://imgur.com/YMgMfzT

@tom-elliott Yeah, it loads into Fog OS, but when it reboots to register with the server is when it gets caught. On the DHCP server i’ve set up options 66 & 67, as well as every option mentioned on this page: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

Is there anything else that I might need?

I made sure that that was configured. As it happens, both the server and the clients I’m testing are plugged into the same switch right now, however, nothing seems to be different.

I did manage to get into a limited command space where it let me put in a number 1-7 for different options. That showed that i wasn’t able to ping the server (or anything else) and that the device itself didn’t have an IP.

The specific way it gets stuck looks like this:

udhcpc: started, v1.26.2
udhcpc: sending discover (x3)
udhcpc: no lease, failing
Either DHCP failed or we were unable to access <fog server> for connection testing.

It repeats all that three times, then says:

No DHCP response on interface eth0, skipping it.
Failed to get an IP via DHCP! tried on interface(s): eth0
Please check your network setup and try again.

Does that make sense? Is there a way i could just give it an IP at this screen, or is there something that i should have configured on the DHCP server that is missing?

The short version is that i have a server running and i can PXe boot into FOS, but when i try to register the device it restarts and says that it fails to get an IP address via DHCP.

If i register manually, through the web page, it appears to work, but when i try to capture an image it gets caught in a loop where it keeps restarting and says ‘chainloading failed’.

We have a separate DHCP server here, and options 66 and 67 are configured. I feel that i should point out again that the DHCP server works when just booting to Fog OS or just booting period, only in the odd restart environment when trying to register (full or quick, both have the same issue) does it not appear to work. I’ve been searching around, but i haven’t found anyone else with this issue, despite how apparently thorough and responsive this forum is (seriously, the timestamps here are crazy).