• Wake-Up task

    23
    0 Votes
    23 Posts
    9k Views
    T

    sorted thank you

  • HP 4530s - PXE-E3B

    25
    0 Votes
    25 Posts
    9k Views
    R

    Yep, noticed that when I edited the original post - back up and running though. I’m still not sure what’s causing the issue with the 4530s. 4520s and 4540s work perfectly.

    I’ll just use a USB until I can figure out what’s causing it -

    Rob

  • Replicator Problem

    4
    0 Votes
    4 Posts
    1k Views
    W

    Try to ssh into your stroage nodes using the same username and password for the storage node in Storage Management --> <select node>–> [FONT=Ubuntu][COLOR=#555555]Management Username & [/COLOR][/FONT][FONT=Ubuntu][COLOR=#555555]Management Password. [/COLOR][/FONT]This will confirm that the password info is correct. As a reminder certain browsers will prefill info so make sure to disable prefill for your browser when looking at this information.

  • Fatal PHP Error when viewing Image Management page

    3
    0 Votes
    3 Posts
    1k Views
    A

    Well, you led me to the solution!

    We have four different storage groups with their respective master nodes. In our ‘main’ group, we were retiring our server “fog1” and replacing it with “fog2.” Last night, I made the switch: I disabled “fog1” from master and set “fog2” to master on the ‘main’ group.

    The issue wasn’t with those settings, but “fog2” still had “max clients” set to 0. Setting this to 10 fixed the issue. I had only looked at the configuration summary – which looked fine to me! (master node set correctly).

    Thanks!

  • 0 Votes
    13 Posts
    6k Views
    J

    correct

  • Cannot update schema after 0.32 --> 1.1.0 upgrade

    6
    0 Votes
    6 Posts
    2k Views
    S

    Hi Tom,

    Thanks for that! Adding the password to the correct config.php file was the ticket! I was able to do the schema update with only this (hopefully inconsequential) error:
    [CODE]The following errors occured
    Update ID: 36 - 5

    Database Error:

    Duplicate entry ‘400-28’ for key ‘gmHostID’
    Database SQL:

    ALTER TABLE fog.groupMembers ADD UNIQUE ( gmHostID, gmGroupID )[/CODE]

    Thanks again!

    Jeff

    [COLOR=#555555] [/COLOR]

  • FOG 1.1.0 Multicast stuck on "Please Wait"

    7
    0 Votes
    7 Posts
    2k Views
    S

    It was actually our image that was busted, so we’re good with imaging with multicast now! Sorry for the confusion, updating fog somehow made the image break.

  • Capone blank option

    26
    0 Votes
    26 Posts
    11k Views
    J

    I had a go on my failing system today, when I rename run.php to something else I get the problem back, i.e. no options for capone.
    I’ve tried clearing the browser cache, on both Firefox on the server and ie8 on xp, and it makes no difference.
    My home system is fine, I’ll try building a new one and see if I can reproduce the problem.

  • Adding Images Back in

    26
    0 Votes
    26 Posts
    11k Views
    Tom ElliottT

    Just the one time, because you will upload this “now good” image and push that to your other hosts.

  • Kernel Panic - Not Syncing(Lenovo ThinkPad Edge)

    24
    0 Votes
    24 Posts
    12k Views
    Tom ElliottT

    That’s correct, unless you tell it to image in raw format.

  • Hostname changer

    26
    0 Votes
    26 Posts
    14k Views
    Tom ElliottT

    If you imported hosts, then it is most likely because the host modules are not set.

  • Boot from USB instead of iPXE

    11
    0 Votes
    11 Posts
    7k Views
    D

    we have other systems that have a functioning ipxe environement. I’ll try to image the systems seperatly.

    will report back

  • After PXE FOG menu screen appears and then restarts

    11
    0 Votes
    11 Posts
    4k Views
    M

    Hi,

    When I changed the file to indionly.kkpxe it won’t start- doesn’t even get to the FOG menu…
    I solved this problem by changing the [FONT=Ubuntu][COLOR=#555555]FOG_PXE_MENU_TIMEOUT value in the fog configuration menu-> FOG boot settings…[/COLOR][/FONT]

    [FONT=Ubuntu][COLOR=#555555]Thanks for all the help[/COLOR][/FONT]

  • Printer error fog 1.1.0

    3
    0 Votes
    3 Posts
    1k Views
    beauvaisB

    hello,
    thank you for your quick response.
    Ok this has resolved to worry.
    I noticed that you could not change a field in printer management, host management, I feel that the update button does not work change.
    You can not add a printer to a group, this is not reflected in the host.
    thank you

    Hello from France

    apache error

    root @ fog: ~ # tail-f / var/log/apache2/error.log
    [Fri Jun 13 8:35:48 2014] [error] [client 192.168.1.68] PHP Warning: in_array () Expects parameter 2 to be array, null Given in / var / www / fog / service / servicemodule-active.php on line 41

    root @ fog: ~ # cat / proc / version
    Linux version 3.5.0-17-generic (buildd @ allspice) (gcc version of 4.7.2 (Ubuntu / Linaro 4.7.2-2ubuntu1)) # 28-Ubuntu SMP Tue 9 Oct 2012 7:31:23 p.m. UTC

    fog subversion 1813
    hello,
    merci de votre rapidité d’intervention.
    Ok cela a resolu se soucis.
    J’ai remarqué que l’on ne pouvais pas modifié un champ dans printer management , host management, j’ai l’impression que le bouton update ne fonctionne pas en modification.
    On ne peut pas non plus ajouter une imprimante à un groupe, ce n’est pas repercuté dans le host.
    merci

    Bonjour de France

  • Network fails on compatibility test

    66
    0 Votes
    66 Posts
    39k Views
    R

    I’m happy to test any of the kernels for the Dell 755/760/780 and provide feedback.

  • PXE Issue FOG Version 1.1.0

    2
    0 Votes
    2 Posts
    740 Views
    Tom ElliottT

    When you set the undionly.kpxe line up in dhcp, did you restart the dhcp service? This, of course, is assuming you’re using dhcpd.conf from linux, otherwise does you network use other DHCP information? Option 67 would likely be the culprit.

  • Scheduled cron tasks don't start

    13
    0 Votes
    13 Posts
    4k Views
    hariskarH

    Thank you Tom! with
    [CODE]sudo service FOGScheduler restart[/CODE]

    it works fine now!
    I had done it before but for some reason it did not work. Also I wonder why it did not work after many linux (different distros)/fog reinstallations.
    Anyway, not it is OK!
    Thank you again! 🙂

  • Tftp Pxe Problem after upgrade form 0.32 to 1.1.0

    4
    0 Votes
    4 Posts
    1k Views
    Tom ElliottT

    clear your browser cache

  • Unable to connect to database

    6
    0 Votes
    6 Posts
    18k Views
    J

    is the capacity on your hard drive is at 100% you should run this command to verify [B]df-h[/B] so if delete something to start mysql service[B] [/B]

  • Storage node issues

    5
    0 Votes
    5 Posts
    2k Views
    M

    Thanks for the quick feedback guys. Sorry I’m so delayed in responding, I’d already returned my test VM’s to snapshots and just hadn’t been able to return to this until yesterday.
    1.1 seems to have resolved the issue for me. The nodes now behave as expected with regard to the ‘master’ setting. I’m hoping that this is something that was fixed in 1.1 and I’m not just losing my mind…

    One other slight problem I’m seeing now:

    The disk information does not display for the SN. It does work correctly for the default member.
    If i click just below the ‘Failed to connect to’ text, I’m brought to a hardware info page which does contain the file system information I’d expect to see on the chart.

99

Online

12.2k

Users

17.4k

Topics

155.6k

Posts