Topics created by jamesb

Is your fog server behind a proxy server or does the fog server have direct access to the internet?

This was weird but I think it’s solved now. It didn’t matter which method I chose it would always give me the SAN error. I decided to reboot the server after current images finished. Then the error messages started to change. This now works with the REFINED_EFI method. I’m not sure why it didn’t want to update the method I chose but updating the server seemed to have kick what was stuck in it’s settings.

@jamesb Well, if you have ruled out the patch cable, gunk in the chips, RAM, and know that all the other exact-same models work fine, you’re left with just the problematic computer. It could be a bad power supply, giving out too much or too little voltage, or unsteady voltage. Or it could be a bad motherboard.

You could try to update the firmware on the motherboard to see if it helps.

@Tom-Elliott

Here is the latest in my error logs:

BFD: /var/www/html/fog/service/ipxe/bzImage32: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage32: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
[Fri May 27 12:04:35.841463 2016] [:error] [pid 26076] [client 172.52.8.7:58657] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 105, referer: http://172.28.2.21/fog/management/index.php?node=report&sub=host-list
BFD: /var/www/html/fog/service/ipxe/bzImage32: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage32: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
BFD: /var/www/html/fog/service/ipxe/bzImage: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss
[Fri May 27 12:03:19.508898 2016] [:error] [pid 22082] [client 172.52.8.7:58558] PHP Strict Standards: Only variables should be passed by reference in /var/www/html/fog/lib/pages/schemaupdaterpage.class.php on line 46, referer: http://172.28.2.21/fog/management/index.php?node=schema
[Fri May 27 12:03:19.218924 2016] [:error] [pid 25953] [client 172.24.8.30:50751] PHP Warning: array_walk() expects parameter 1 to be array, boolean given in /var/www/html/fog/lib/client/servicemodule.class.php on line 21
[Fri May 27 12:03:19.218895 2016] [:error] [pid 25953] [client 172.24.8.30:50751] PHP Warning: array_combine(): Both parameters should have an equal number of elements in /var/www/html/fog/lib/fog/fogbase.class.php on line 262
[Fri May 27 12:03:19.133697 2016] [:error] [pid 22091] [client 172.24.8.30:50750] PHP Warning: array_walk() expects parameter 1 to be array, boolean given in /var/www/html/fog/lib/client/servicemodule.class.php on line 21
[Fri May 27 12:03:19.133666 2016] [:error] [pid 22091] [client 172.24.8.30:50750] PHP Warning: array_combine(): Both parameters should have an equal number of elements in /var/www/html/fog/lib/fog/fogbase.class.php on line 262
[Fri May 27 12:03:19.030185 2016] [:error] [pid 22084] [client 172.24.8.30:50749] PHP Warning: array_walk() expects parameter 1 to be array, boolean given in

Remoted in and fixed.

Issue is ubuntu had docroot of /var/www/ but really the files existed in /var/www/html. So the current was placed in /var/www/fog, but web was looking at /var/www/html/fog.

Fixed by removing /var/www/html/fog, moving /var/www/fog /var/www/html/fog, and creating a link from /var/www/html/fog to /var/www/fog.

I found out what the issue was. Somebody on my team removed option 66 and 67 from our dhcp servers. So the network boot didn’t know where to look for any files.

I don’t know what you mean timeout?

Can you provide some screenshots?

My other guess is the webroot issue. Maybe try rerunning the install with, after updating to latest pull please:
./installfog.sh -y -D /var/www/html

Team viewer and I helped fix the issue described in this thread. The issue was mcrypt was not loaded properly. Copying the needed ini file to the mods available folder and enabling the module helped correct this. I’ve now added checking to the installer to further prevent these types of cases hopefully.

I just fixed a handful of issues with the apache vhosts configuration. If you’re daring, you can grab the latest github commit on dev-branch if you don’t want to wait for the next SVN.

Win 7

@Junkhacker Didn’t even notice that.

This isn’t really a feature request. It’s a bug. I’ve since corrected for this. The only thing you can’t do is set multiples for the same time, but you can set how ever many of any kind. It was only allowing one greenFog entry at all and this was incorrect.

I created a workaround in 3224

The latest svn fixed the issue.

3199 should fix this issue.

It should (hopefully) fix the weirdness that was ubuntu/debian and get new client stuff.

3189 should address the mobile user logging in as well as remove the warnings about the headers sent and the random display of 1 or 0 on the mobile login page.

The notification GUI your are referring to was not ready for the initial public beta. See [url]http://portal.fogproject.org/work_packages/24[/url] for the workpackage.

That fixed it. Thanks Tom.

It’s always wanted to grab all the MAC Addresses. That’s exactly what its purpose is.

Just remember, hostnames cannot contain spaces as @jamesb found out.