Posts made by Quazz

I actually intended to make a thread about an apache error in relation to mysql (something about /nMySQL in line 40 and 52 of node.php if I remember accurately) I noticed popping up several times, but now I can’t access the logs on the WebGUI because of a server 500 error.

Upgraded to latest version a few minutes ago hoping it might fix it, rebooted server but still nothing.

I’ve used the search function on the forums to try and find out a bit more, ownership is set to www-data properly.

Any ideas on where I should start to look?

As for the error I mentioned earlier, I located the file manually, here it is:

7] PHP Warning: mysqli::select_db(): invalid object or resource mysqli\n in /var/www/html/fog/lib/db/mysql.class.php on line 40
[Wed Jan 20 13:50:44.021697 2016] [:error] [pid 1358] [client 192.168.1.29:51277] PHP Warning: mysqli::query(): invalid object or resource mysqli\n in /var/www/html/fog/lib/db/mysql.class.php on line 52

EDIT: Clients are now also unable to update the database when I upload an image.

@Sebastian-Roth I think I may have accidently misled you earlier.

What I meant with not working 10% of the time I meant 10% of clients (generally lower end consumer garbo). It seems to work fine on anything remotely professional or decent consumer stuff. I’m fairly certain the fault lies with the NICs at this point, but I’ll continue to monitor the situation and try a couple more times.

Created an imgur album if for nothing else but historic purposes

imgur link

@Sebastian-Roth Alright, there is indeed no next-server of filename info coming from the DHCP. And they properly receive the info (next-server and filename) from the proxydhcp as well. (it’s the only info it hands out). ProxyDHCP does refer to itself as to be the DHCP server but I’m guessing that’s normal.

All values are what we can expect, proper gateway, dns and so on.

@Sebastian-Roth Anything specific you want me to look for in the ipxe config menu?

As far as I understand, these options are all set as intended at the current stage of the boot process, is that correct?

@Sebastian-Roth I have indeed chosen for ProxyDHCP in the mean time. I will try the config thing tomorrow.

The clients now always say they get DHCP offerings from both the DHCP server and the DHCP proxy (after configuring net0), most solid clients are able to select the proper answer from the ProxyDHCP, but some are not (this usually professional vs consumer grade).

As far as I can tell from the packet dump, it does not send out a dhcp option 66 as you say, but it does specify for next-server to be 0.0.0.0 (not sure if that’s normal behavior or not though, I kind of thought if it didn’t send out the option then it shouldn’t even contain that information at all)

There’s definitely something going on, hopefully there’s still some way to improve the situation, I’ll let you know how it goes.

No luck on the logging in to modem/router thing. It’s going to continue to be a nuisance whether or not I use isc-dhcp-server or proxydhcp since it gives an empty next-server option to clients (from what I’ve read online this is because it gives a specific next-server and filename to the digital TV)

So in other words I have to choose between proxydhcp not working 10% of the time or isc-dhcp-server nearly always asking for tftp prompts and not working 10% of the time, ugh.

I’d like to thank you guys for helping me figure this out though, keep up the good work

@pugnacious Did you disable the firewall and SELinux on the CentOS one? From what I’ve read, they can cause a host of issues on that OS in relation to FOG.

@Sebastian-Roth The client in question that I captured traffic from was a VM, might that have something to do with option 175? I had finished prepping it for capture, shut it down, then started capture and booted the client. The client is in bridged mode (otherwise it wouldn’t even work if I’m not mistaken), so it should all work properly.

I think what happened with the two IP addresses is that the lease expired so the DHCP server had to correct itself? (the lease was 6 hours on the dot for the first offered IP).

As for the last point, there are indeed two dhcp servers, but unfortunately I can’t do much about that. (we are unable to login on the modem/router even with the login data provided by the ISP) I did try to get proxydhcp to work, but unfortunately some clients acknowledged the proxy, but then continued to request the file from 192.168.1.1 anyway, even though it doesn’t even offer a next-server option. (link here)

Yet, it seems to sometimes win the dhcp race after which it offers a empty next-server which would indeed force me to input me the address manually. The strange part is that this has only been happening recently, although I suppose it’s possible the ISP pushed a firmware update to the modem/router to make that happen.

Are there any solid alternatives I could look into? I’ve looked around a bit, but most attempts seem either kind of hacky or are in alpha stages of development.

EDIT: Talked to some people who know about more about that ISP and their modems (I use a different ISP at home who employ an entirely different system). I may have a way to login into the modem/router and disable DHCP, will test it out tomorrow, will let you know if this improves the situation as well.

0_1453128328572_pxeboot.pcap

I captured the DHCP traffic on the fog server when one of the clients was pxe booting (and had the tftp address prompt).

edit: The client that previously rebooted after ipxe initialization now claims it gets no filename (after server reboot), other clients working as before (tftp prompt and all)

I’m a bit busy today, but hopefully I’ll have some time for that later today.

I did notice some clients reboot right after loading the ipxe binary (and presumably before I have to or not have to enter the tftp address)

Also noticed that the sql backup is now 7mb as opposed to the 1mb I had before, not sure if that’s normal.

I have a feeling some of these are connected, but I could be way off.

Sorry for the glare, but the relevant info should be visible anyway.

I should note, I tested a Dell LatitudeE6410 with the exact same cable and everything which did not have this issue, no matter how many times I tried, which makes me think it has something to do with the NIC/drivers

I’ll check when I’m in at work tomorrow morning, but from what I recall it says something along the lines of “Configuring net0 (macaddress)…”

After which it will ask for tftp address.

@Wayne-Workman You can image unregistered computers using multicast with trunk. You just have to create a session for it specifying the amount of clients and such first.

What does it say when you try to manually install the libapache for php7?

I have been experiencing this as well since a few updates ago, no change in netwerk architecture (yet), so not sure why that’s suddenly occuring.

It clearly knows the tftp address as it loads the ipxe.kpxe file from it, but then it asks for tftp address anyway.

Also, this does not always happen, just almost always. (talking about the same machines here, it happens network wide, but sometimes the machines don’t ask, but most of the time they do)

@ManofValor What Ubuntu version do you have?

Updated to latest svn trunk version and this line showed up after setting up NFS server

It then went on to tell me the ip and such and said Setup Complete and nothing seems wrong.

I googled a bit on it and it has to do with # being used for commenting, so when used in a different context it produces stuff like this instead of what it’s actually supposed to do.

I don’t know what was supposed to happen, if anything, but it may be worth looking into just in case it messes with anything important.

I’m presuming there’s a syntax error in one of the setup scripts.

If there’s anyway I can help further, let me know.

@Wallae said:

I believe you have the EFI version of Ubuntu installed. I only really have experience with the regular (old style) one, since I experienced too many issues with it when I tried it out.

As far as I know, they changed the way they manage interfaces slightly, so I’m guessing there will be a file under /etc/network/interfaces.d that you need to edit instead.

@Wallae Can you do

sudo ls /etc/network

And tell us if there are any files there? There should always be an interfaces file there, but it may have been pushed to interfaces.bak in which case do…

sudo mv /etc/network/interfaces.bak /etc/network/interfaces