• Check in suddenly fails

    10
    0 Votes
    10 Posts
    3k Views
    J

    @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

  • MySQL troubleshooting

    14
    0 Votes
    14 Posts
    4k Views
    mosesM

    @Tom-Elliott No, I found it. Discovered underlying issues with Centos, not FOG, so I’m taking backups of config and images, and reinstalling.

    Long story short, systemd got corrupted due to me being an idiot.

  • Cannot PXE boot

    16
    0 Votes
    16 Posts
    5k Views
    Wayne WorkmanW

    @george1421 said in Cannot PXE boot:

    I have also seen that some projects actually have a service page that lists if the services are running or not, and gives the admin a choice to stop or start a service.

    I’ve got a DHCP plugin ready to be integrated into fog… just having a lot of trouble understanding the plugin system for such a large plugin.

    But, I can easily create a two-file + small DB change plugin that will detect the status of services and offer the ability to restart on a click.

    Again though, the one thing holding me back from going wild is a lack of understanding of the plugin system. People have attempted to explain it to me many times but it just doesn’t click. I need to be shown.

  • Snap-in Process

    4
    0 Votes
    4 Posts
    1k Views
    Wayne WorkmanW

    @adukes40 Sounds right.

  • Snap-in Replication

    Solved
    11
    0 Votes
    11 Posts
    3k Views
    Tom ElliottT

    @adukes40 no problem.

  • PXE boot issue on E6410

    3
    0 Votes
    3 Posts
    950 Views
    george1421G

    I can say for sure that the e6410 pxe boots just fine using the trunk (dev) build of 1.2.0.

    The e6410 is a bios only system that does boot with the undionly.kpxe. Since you said that you had an older version of FOG installed, can you tell me what you have defined for dhcp option 67?

    When iPXE boots, there is a series if hex values that indicate the build beyond the version number. What is the build number.

  • HP EliteDesktop 800 G2 SFF

    10
    0 Votes
    10 Posts
    5k Views
    S

    @Rwest Are you using FOG trunk or version 1.2.0. Please post a picture of the error you see when trying to deploy!

  • Wake On Lan With FOG on Debian

    3
    0 Votes
    3 Posts
    2k Views
    Tom ElliottT

    @fdrouard wol/wol.php path no longer exists.

  • FOG Multicast doesn't work

    14
    0 Votes
    14 Posts
    5k Views
    S

    @arnaudrigole As you can see there are no udp-sender processes running. So multicast just cannot happen. Those should be started by the FOGMulticastManager service (which seems fine on your server). So please check the logs as I suggested earlier.

  • VM Machine has download problems?

    Solved
    9
    0 Votes
    9 Posts
    3k Views
    S

    @MadsMagnus Great to hear that you found out what was causing the issue! Marking this for addition to the #wiki article on debugging boot problems.

  • Unable to create un image with upload (fog.upload)

    2
    0 Votes
    2 Posts
    870 Views
    Wayne WorkmanW

    You’re experiencing FTP related issues. There are a number of things that cause this, but greater than 90% of the time it’s simply bad credentials.

    This article contains everything you need to get it sorted:
    https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

  • Since the latest update, FOG seems to not be renaming.

    Solved
    31
    0 Votes
    31 Posts
    15k Views
    E

    @Tom-Elliott ok roger that. Thanks so much.

  • Very high CPU usage httpd, mysqld, FOGMulticastManager FOG trunk@5224

    29
    0 Votes
    29 Posts
    14k Views
    K

    @Quazz Hi Quazz yes main problem of high cpu usage appears to be much better - main server with most number of hosts is sitting at 5-30% CPU load roughly with no active tasks running. I’m testing now with images running to double check under load.

    cheers Kiweegie.

  • General Replication question

    3
    0 Votes
    3 Posts
    612 Views
    adukes40A

    That’s what I figured. thanks for clarification.

  • Dell PCs Can't Boot From Hard Drive - Press A Key to Reboot

    6
    0 Votes
    6 Posts
    1k Views
    RobTitian16R

    @george1421 Upgrading to trunk has resolved this issue - thank you! 🙂

  • Boot menu customization

    3
    0 Votes
    3 Posts
    518 Views
    O

    Hi, thanks for the reply.
    I had to update via git (https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk) in order for these options to appear. I was using version 1.2.0 but could not find this. 1.3 changed everything and so far seems to offer what I needed.
    Thanks.

  • Can't upload Dell Latitude 3440 image

    22
    0 Votes
    22 Posts
    11k Views
    P

    @Wayne-Workman
    That did Wayne, thanks again for the help. Updating passwords between storage node in gui, and .fogsettings, so they match, was the final answer.

  • Imaging issue with writing BCD after FOG update (1.2.0)

    5
    0 Votes
    5 Posts
    1k Views
    W

    @Wayne-Workman Thank you, I just finished imaging a machine with an older image, so it 100% was the image. No worries though, I’ll just build a new one. Thank you!

  • tsc : Fast TSC Calibration failed

    9
    0 Votes
    9 Posts
    6k Views
    george1421G

    @Rich-C Tom has also been telling us the newer trunk kernels will work with 1.2.0 stable. So if you backup your current kernels you can download the latest trunk version using the following commands on your fog server. Just navigate to /var/www/html/fog/service/ipxe , rename the files and then execute these commands.

    sudo wget https://fogproject.org/kernels/bzImage
    sudo wget https://fogproject.org/kernels/bzImage32

    These kernels are 4.5.3 as of today.

    I do have to say my personal recommendation is to just upgrade to the trunk release to take advantage if the new features (as long as you can tolerate a little instability of the dev releases).

  • Possible to view imaging history of Unregistered host?

    9
    0 Votes
    9 Posts
    2k Views
    phil_guyP

    @Tom-Elliott Alright thanks for the help.

149

Online

12.4k

Users

17.4k

Topics

155.9k

Posts