• Fog 1.0.1 and Ubuntu 14.04 network printers

    5
    0 Votes
    5 Posts
    2k Views
    Tom ElliottT

    [quote=“zacharylewis07, post: 29144, member: 24431”]Having Printer Issues Also…
    I’ve installed FOG 1.1.0 with patches from svn version 1780, yet I’m still having issues with PrinterManager adding and removing printers. I have “Add and Remove” selected for all hosts under “Printers” in Host Management.

    Experiencing the following…
    [LIST]
    []Random comments in the FOG log: PrinterManager Service is disabled and I get no printers deployed at all.
    []When printers do finally decide to deploy, I can’t remove them afterwards without cleaning up the registry.
    [/LIST]
    Any help is greatly appreciated.

    User since FOG 0.26 (Love the software)[/quote]

    Did you upgrade from 0.32 or is this a “fresh” install of 1.1.0?

  • FOG 1.0.1 - client doesn't get the FOG boot menu.

    27
    0 Votes
    27 Posts
    14k Views
    D

    Can i try both? Or does it have to be a undionly.kpxe?

    Also, after restarting my server every time to try these new files, when trying to hit the web GUI i get an unable to connect to database error - although i’ve put the password in the commons/config.php folder…it was workign previously

  • Snapin client Module is active...

    3
    0 Votes
    3 Posts
    1k Views
    A

    Okay…They are “In Progress” now.

    Thanks,

    Andy

  • Fog 1.0.1 image creation

    8
    0 Votes
    8 Posts
    3k Views
    T

    All errors were related to FTP, realized my FTP client was connecting on port 22, not 21. VSFTPD would not connect on 21. I removed VSFTPD and installed ProFTP and it is working now! Images created!

  • FOG 1.0.1 and older NICs

    32
    0 Votes
    32 Posts
    15k Views
    Scott BS

    [quote=“Junkhacker, post: 29161, member: 21583”]if you run
    [FONT=Consolas]tftp x.x.x.x get default.ipxe[/FONT]
    does it download the file?[/quote]

    I see what I did. When updating the tftboot files I accidentally moved default.ipxe. Thanks!

  • Web interface problems after upgrading to 1.01

    6
    0 Votes
    6 Posts
    2k Views
    Tom ElliottT

    You don’t need to wallow or anything. It happens, thats why you ask questions.

  • FOG 1.0.1 FOGMulticastManager service won't start

    10
    0 Votes
    10 Posts
    4k Views
    R

    [quote=“Tom Elliott, post: 29051, member: 7271”]Change the document root of your apache information to /var/www[/quote]

    I’ve changed the documentroot, but there’s no difference.

    [CODE][Wed Jun 04 12:15:10.484125 2014] [:error] [pid 7062] [client 10.4.30.43:49221] PHP Warning: require(…/commons/base.inc.php): failed to open stream: No such file or directory in /var/www/fog/service/servicemodule-active.php on line 2
    [Wed Jun 04 12:15:10.484155 2014] [:error] [pid 7062] [client 10.4.30.43:49221] PHP Fatal error: require(): Failed opening required ‘…/commons/base.inc.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/service/servicemodule-active.php on line 2
    [Wed Jun 04 12:15:13.479323 2014] [:error] [pid 7091] [client 10.4.30.43:49220] PHP Warning: require(…/commons/base.inc.php): failed to open stream: No such file or directory in /var/www/fog/service/servicemodule-active.php on line 2
    [Wed Jun 04 12:15:13.479352 2014] [:error] [pid 7091] [client 10.4.30.43:49220] PHP Fatal error: require(): Failed opening required ‘…/commons/base.inc.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/service/servicemodule-active.php on line 2
    [Wed Jun 04 12:26:44.439631 2014] [:error] [pid 7157] [client 10.4.30.174:49235] PHP Warning: require(…/commons/base.inc.php): failed to open stream: No such file or directory in /var/www/fog/service/servicemodule-active.php on line 2
    [Wed Jun 04 12:26:44.439661 2014] [:error] [pid 7157] [client 10.4.30.174:49235] PHP Fatal error: require(): Failed opening required ‘…/commons/base.inc.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/service/servicemodule-active.php on line 2
    [Wed Jun 04 12:26:47.437465 2014] [:error] [pid 7121] [client 10.4.30.174:49234] PHP Warning: require(…/commons/base.inc.php): failed to open stream: No such file or directory in /var/www/fog/service/servicemodule-active.php on line 2
    [Wed Jun 04 12:26:47.437494 2014] [:error] [pid 7121] [client 10.4.30.174:49234] PHP Fatal error: require(): Failed opening required ‘…/commons/base.inc.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/service/servicemodule-active.php on line 2
    [Wed Jun 04 12:33:39.110303 2014] [:error] [pid 7199] [client 10.4.30.174:49184] PHP Warning: require(…/commons/base.inc.php): failed to open stream: No such file or directory in /var/www/fog/service/servicemodule-active.php on line 2
    [Wed Jun 04 12:33:39.110333 2014] [:error] [pid 7199] [client 10.4.30.174:49184] PHP Fatal error: require(): Failed opening required ‘…/commons/base.inc.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/service/servicemodule-active.php on line 2
    [/CODE]

    Could these errors be made by clients with the old fog client installed?

  • Fog Upgrade from 0.3.2 to Fog - 1.0.1 - PHP Errors - CentOS 6.5

    11
    0 Votes
    11 Posts
    4k Views
    R

    Ahh thanks for that, I have another question but I’ll create a new thread for that 🙂

  • 0 Votes
    9 Posts
    3k Views
    R

    To add, actually it seems almost 100% stable with this modification, no crashes today…

    Maybe the one crash after I made this change was a fluke and/or I had not rebooted yet, I cannot remember with all the different testing that I’ve been doing…

  • Customize the Background Image behind the menu.

    8
    0 Votes
    8 Posts
    5k Views
    JunkhackerJ

    does each site have it’s own tftp server as well?

  • IPXE PHP boot files not found

    8
    0 Votes
    8 Posts
    6k Views
    Tom ElliottT

    The MySQL Issues could play into account as much of the data Polled comes out of the database. So it’s not too surprising to see the issue. This may also explain why a reinstall seems to help fix some of the issues. Not a complete reinstall from scratch, just simply rerunning the installer in place.

  • IPXE "Could not boot" error after upgrade to 1.0.1

    8
    0 Votes
    8 Posts
    4k Views
    D

    Our network engineer is out today so we’re not sure about the details. All we could see was that a “no internet” policy was applied to that port via our NAC, and when we disabled it, FOG suddenly worked fine. The box was booting from the FOG server via IPXE so it seems that internal network access wasn’t blocked, but again, we don’t know any specifics.

  • NFS problems

    5
    0 Votes
    5 Posts
    2k Views
    Tom ElliottT

    I have an nfs shared through cifs, but not the other way.

  • Error:Undefined index: currentUser

    1
    0 Votes
    1 Posts
    834 Views
    No one has replied
  • Power Outage caused Management Login problems?

    3
    0 Votes
    3 Posts
    962 Views
    P

    Thanks for the reply Tom, I will try this out and see what I get

  • Fog 1.0.1 - Can't deploy image

    18
    0 Votes
    18 Posts
    6k Views
    M

    I am certain - the disk’s have all come from the same place - and I have NEVER had to partition them first before I can download the image from FOG.

  • FOG 1.0.1 PXElinux.cfg Doesnt Exist

    12
    0 Votes
    12 Posts
    5k Views
    W

    So it comes down to preference…

    To SYSPREP or To FOG PREP…it doesn’t really matter if you do or not just get to FOGGING!!!

  • PXE Boot Problems after upgrade to 1.0.1

    10
    0 Votes
    10 Posts
    4k Views
    Jaymes DriverJ

    [quote=“Tom Elliott, post: 28975, member: 7271”]No, but it’s good to have so people aren’t staring at code thinking the problem is missing text.

    In programming, typically it’s syntactically incorrect to have dhcp-boot=,[/quote]

    In some systems when using DNSMASQ you have to leave that field blank, like novell. If you supply the FOG host server name, the file will fail to resolve. I should have left a place holder in the documentation that explained that the blank is for the host name but I didn’t know it was going to drive you insane lol

  • Multicast issue 1.01

    2
    0 Votes
    2 Posts
    707 Views
    Tom ElliottT

    [quote=“Broach75, post: 28756, member: 24433”]Hi, New FOG user. Setup is working great for unicast, but I am unable to get multicast working. I have installed several times on both physical and virtual servers with same results. I do not see any multicast troubleshooting info like in the .32 version. Does it still exist?

    Thanks
    Bill[/quote]

    More or less, the same troubleshooting document is still valid for 1.0.1.

    That said there were some known quirks depending on the setup of your fog server with Multicast.

    If you’re interested, install the svn version of FOG and see if that can help you.

  • Host Stuck in Database?

    2
    0 Votes
    2 Posts
    857 Views
    Tom ElliottT

    If you know the information such as the host ID you can remove with an sql statement. Why you can’t now is probably because the hostID is currently set to 0 which FOG can’t recognize. That said, normally the host wouldn’t even appear to the system, so the only other guess is maybe and image isn’t set to this host?

    To remove the host:
    [code]mysql -u root -h’<YOUR FOG IP HERE>’ [-p’<YOUR MYSQL ROOT PASSWORD>’ #ONLY IF SET]
    DELETE FROM hosts WHERE hostName=‘HOSTNAMEOFSYSTEMTOREMOVE’;
    [/code]

173

Online

12.4k

Users

17.4k

Topics

155.9k

Posts