FOG 33b - installation - HP Elite 8300 SFF



  • I have been using version 32 for a number of years on an old HP PC.

    I installed 33b yesterday on a new HP Elite 8300 with 8 GB RAM.

    Is it still necessary to change the bind-address= in /etc/mysql/my.cnf
    I changed this to my fog server address.

    I tried to update the database schema but could not until I had put in the mysql password with:
    sudo gedit /var/www/fog/commons/config.php

    Then database schema updating worked.
    Then logged successfully into [url]http://10.0.1.40/fog/management[/url]
    Then named a Linux image.

    Server 2012 R2 already had DHCP scope options:
    066 = fogserver
    067 = undionly.kpxe

    Then tried to register one old HP client (which I know had been registered before on the old FOG server)
    Client obtained IP address and then waited for Tftp - timed out.
    I had seen this years before on the old system, so I typed:
    sudo stop tftpd-hpa
    sudo start tftpd-hpa

    Client still timed out.

    I restarted the DHCP on the win server and rebooted the fogserver.
    Then the real problems began: I got error messages from Nautilus and I could no longer log in on the fog management page, either on the fogserver or my PC. I could see that my password was accepted, but the next page was never opened. It just stayed at the login page.

    xxxxxxxxxxxxxxxx

    So now today I have reinstalled Ubuntu 12.04.4 and FOG 33b

    Do I still need to change the bind-address in /etc/mysql/my.cnf ?
    Yesterday when I did this, new copies of my.cnf were created: my.cnf~ and my.cnf~~.
    Is this normal?

    I’m really worried that the same thing is going to happen today again.



  • Have now connected everything to the school VLAN again.

    Rebooted after fixing sleep 30.
    Checked multicast log - no log for the last 3 hours
    Multicast to 2 HP
    TFTP is now running after reboot (problem fixed)
    Multicast failed as expected
    Stop and start multicast
    Multicast to 2 HP
    Multicast worked as expected
    Checked multicast log - it is running now, BUT, the log shows 7:30 PM when it is actually 9:30 PM on the Ubuntu clock as it is in reality here in Norway. I just mention it in case it has significance.

    This multicast problem is now predictable and fixable for me. I’m heading home.



  • Very helpful explanation.

    Actually I haven’t given up. It’s just that I MUST get the staff system running in 2 days time. And that’s impossible. That’s the real source of my frustration. I’m happy to keep working at this for the sake of others in the future who might have similar problems and helping with 0.33b, but not for at least a week until I’ve got the school system up and running. I will keep you very briefly updated on anything I discover, but nothing time-consuming for the time being. I’m in the middle of what is, for me, a big migration and huge learning curve. All new PCs, Server, printers, VLANS, Firewall, multimedia systems. Going from XP to Win 8.1 is a big jump. I’ll be using SYSPREP for the first time and answer files, ADBA etc…


  • Senior Developer

    When the Client systems are loading, they load two files. First one is bzImage, second is init.xz.

    The bzImage is a linux kernel, the init.xz file is the “OS” layer of the FOG System on the host.

    The kernel Jaymes is referring to is the bzImage that’s loaded onto the client systems. There are no particular issues on the FOG Server itself. This is the kernel I’ve been maintaining as much as possible. It has NOTHING to do with the fog server, besides it is stored under /var/www/fog/service/ipxe/bzImage.

    The fact that the FOGMulticastManager service is stopped leads me to think there is some problem, just not one that I can pinpoint without trying to get more information. If you’re willing to work forward I can try to help with this. I realize your not being paid for this and I feel the pain. Which is why I’m frustrated with you, from my eyes, seemingly just giving up.



  • Ohhh


  • Developer

    the kernels he is talking about are the ones that the fog server sends to clients when they network boot



  • I’ve fixed the sleep 30 syntax.



  • Yes every 10 seconds there are 6 items/lines

    But the log stopped for 1 hour from 1230 to 13:30.
    It also stopped 2 hours ago and has not recorded anything since then.

    The following is Chinese to me. I know nothing about kernels.
    [I]Errors with units normally leads to kernel issues, you can try one of the updated kernels Tom provides, or you can build your own, there is a fabulous guide on the forums that will walk you through creating a kernel with specific drivers, but the ones Tom puts out are normally all inclusive.[/I]

    Are you saying that a part of the OS is corrupted and needs fixing? Or can I use the system temporarily as it is and just stop and start the FOGMulticastManager if I want to multicast?

    [I][/I]


  • Developer

    [quote=“Alistair, post: 25706, member: 1830”]I have spent weeks trying to sort out issues with these new HP PCs.
    I’ve tried to get photos of the old HP PC screen output but school camera batteries go flat. Forget to take my camera with me.
    The relevant error messages go by really fast. Cannot read them to write them down. I have been trying.
    I have teachers coming in 3 days and no system ready. I have a crisis. I must move on.
    I’m also not getting paid for my time here at all. I have done hundreds of hours in extra voluntary hours.

    Firewall is now disabled.

    How do I access the sleep timer details to see if they are 10 seconds?[/quote]

    Errors with units normally leads to kernel issues, you can try one of the updated kernels Tom provides, or you can build your own, there is a fabulous guide on the forums that will walk you through creating a kernel with specific drivers, but the ones Tom puts out are normally all inclusive.

    I don’t think there is an option to change this setting, but if you check /opt/fog/log/multicast.log you will see every 10 seconds the multicast manager logs. Is it getting updated every 10 seconds? If so then it is working properly.



  • It’s obvious now that there is something wrong in my fogserver. Either firmware, hardware, linux, fog or a combination.



  • I have spent weeks trying to sort out issues with these new HP PCs.
    I’ve tried to get photos of the old HP PC screen output but school camera batteries go flat. Forget to take my camera with me.
    The relevant error messages go by really fast. Cannot read them to write them down. I have been trying.
    I have teachers coming in 3 days and no system ready. I have a crisis. I must move on.
    I’m also not getting paid for my time here at all. I have done hundreds of hours in extra voluntary hours.

    Firewall is now disabled.

    How do I access the sleep timer details to see if they are 10 seconds?


  • Senior Developer

    [quote=“Alistair, post: 25701, member: 1830”]Jaymes - Thanks for those final tips on stopping and starting multicast.
    I’ll try that. I’m not going back to 10.04.[/quote]

    I have a feeling there’s more here than meets the eye. The FOGMulticastManager service is what handles the starting and killing (once complete or timedout) of the multicast imaging types. What’s the sleep timer set to on your system? It’s usually defaulted to every 10 seconds, which worries me a little bit here. Is the firewall disabled on the FOG Server? [code]sudo ufw disable[/code]

    [quote=“Alistair, post: 25701, member: 1830”][FONT=Times New Roman]I can’t spend any more time on this. I’m kicking a dead horse. I’m running with unicast. I know it’s slower and only 10 at a time.[/FONT][/quote][FONT=Times New Roman][/FONT]
    [FONT=Times New Roman]What makes you think it’s slower? You can also adjust the number you want to queue. You just need to find the right balance. At home I do around 20 systems at a time just to test things out. As I stated earlier, multicast breaks my network but unicast sails just fine. It’s just as fast, if not faster than multicast even if I test from my work place.[/FONT]

    [FONT=Times New Roman][quote=“Alistair, post: 25701, member: 1830”][/quote][/FONT][quote=“Alistair, post: 25701, member: 1830”]
    [FONT=Times New Roman]I have no more time to use on this multicast problem. I’m usually good at fault finding, but here I have failed to find any pattern of success and failure. [/FONT][/quote][FONT=Times New Roman][/FONT]
    [FONT=Times New Roman]Based on what I’ve obtained from the information, it seems that something is changed between the reboots that allows multicast to “suddenly” appear to work. Your restarting of the server shows that it’s another issue in whole. You restarted to do fault finding, but your restarting of the system was, seemingly, causing the failure in the first place.[/FONT]
    [FONT=Times New Roman][/FONT]
    [FONT=Times New Roman][quote=“Alistair, post: 25701, member: 1830”][/quote][/FONT][quote=“Alistair, post: 25701, member: 1830”][FONT=Times New Roman]One time in another school I had 50% of students who could print to a particular printer and 50% who could not. I eventually discovered that all those who had domain user names longer than 15 characters, could not print out on that particular printer. No problem in printing to other printers. Go figure. Over 20 years I’ve seen [U]many[/U] examples of 1 program creating a problem in another on various platforms. Drivers for smartboards screw up LibreOffice.[/FONT][/quote][FONT=Times New Roman][/FONT]

    [FONT=Times New Roman][quote=“Alistair, post: 25701, member: 1830”][/quote][/FONT][quote=“Alistair, post: 25701, member: 1830”][FONT=Times New Roman]I suspect there is a problem in fog, maybe connected with firmware on my new HP Elite 8300 SFF and USDT clients.[/FONT][/quote][FONT=Times New Roman][/FONT]
    [FONT=Times New Roman]What problem do you suspect? Didn’t you state that imaging works fine on these clients? Multicast (when working) and Unicast works perfectly fine?[/FONT]
    [FONT=Times New Roman][quote=“Alistair, post: 25701, member: 1830”][/quote][/FONT][quote=“Alistair, post: 25701, member: 1830”][FONT=Times New Roman]I’m running fog 33b on one of the new SFF. But I also think it is strange and disappointing that I cannot unicast or multicast to my old HP DC7100 clients that I imaged many times from my old fogserver version 0.32.[/FONT][/quote][FONT=Times New Roman][/FONT]
    [FONT=Times New Roman]What exactly happens on these systems? Is there a kernel panic, can you test the systems for compatibility? I can rebuild a kernel fairly quick, but I can’t fix a problem without information. All I’ve gotten from these DC7100’s is, they don’t work, but no messages showing what or why they may NOT be working in the firstplace.[/FONT]
    [quote=“Alistair, post: 25701, member: 1830”]Thank you Tom, Jaymes and JunkHacker for all your input and time.
    I will only give further comments in this thread if I discover something significant that you should know about.
    [/quote]
    I wish one wouldn’t just give up so quickly. I’ve spent a lot of time, as well as the rest of us trying to help. While I realize it’s frustrating, giving up is not the right approach. At least not in my eyes.


  • Developer

    [quote=“Alistair, post: 25703, member: 1830”]Jaymes has found the problem!

    sudo /etc/init.d/FOGMulticastManager stop
    Stopping fog imaging solution: FOGMulticastManager
    start-stop-daemon: warning: Failed to kill 1157: no such process

    sudo /etc/init.d/FOGMulticastManager start
    Starting FOG solution: FOGMulticastManager

    Multicast worked !!!

    “no such process” !!!
    It wasn’t running.[/quote]

    You may want to add an upstart job to start the multicast manager at a reboot.



  • Jaymes has found the problem!

    sudo /etc/init.d/FOGMulticastManager stop
    Stopping fog imaging solution: FOGMulticastManager
    start-stop-daemon: warning: Failed to kill 1157: no such process

    sudo /etc/init.d/FOGMulticastManager start
    Starting FOG solution: FOGMulticastManager

    Multicast worked !!!

    “no such process” !!!
    It wasn’t running.


  • Developer

    [quote=“Alistair, post: 25701, member: 1830”]Jaymes - Thanks for those final tips on stopping and starting multicast.
    I’ll try that. I’m not going back to 10.04.

    [FONT=Times New Roman]I can’t spend any more time on this. I’m kicking a dead horse. I’m running with unicast. I know it’s slower and only 10 at a time. I have no more time to use on this multicast problem. I’m usually good at fault finding, but here I have failed to find any pattern of success and failure. One time in another school I had 50% of students who could print to a particular printer and 50% who could not. I eventually discovered that all those who had domain user names longer than 15 characters, could not print out on that particular printer. No problem in printing to other printers. Go figure. Over 20 years I’ve seen [U]many[/U] examples of 1 program creating a problem in another on various platforms. Drivers for smartboards screw up LibreOffice. [/FONT]

    [FONT=Times New Roman]I suspect there is a problem in fog, maybe connected with firmware on my new HP Elite 8300 SFF and USDT clients.[/FONT]
    [FONT=Times New Roman]I’m running fog 33b on one of the new SFF. But I also think it is strange and disappointing that I cannot unicast or multicast to my old HP DC7100 clients that I imaged many times from my old fogserver version 0.32.[/FONT]

    Thank you Tom, Jaymes and JunkHacker for all your input and time.
    I will only give further comments in this thread if I discover something significant that you should know about.

    [/quote]

    I don’t know what your fear of 10.04 is, you could do so as a test, then install latest fog and try multicasting, if multicast works then there may be a problem with something installed on FOG server A (The one with the broken multicast).

    You can increase the number of clients that can unicast at once, you can change this number under the fog settings of the web gui, click on General Settings and then edit the que size.

    but WHAT gives you the impression that it is slower? Unicast images the machines one at a time and decompresses the data AT the host. with multicast you decompress at server and send ALL information across the network, and then you wait for all multicast hosts to get to the same spot then they move forward. Multicast is slower than unicast… AND has the potential to leave you without an OS should you choose to leave while Multicast is performing.

    You can continue to blame FOG if you want, but the issue is specific to your server at the moment, there are many of us that use FOG for multicast, I do not I find more faults in the system than good, and they are not reporting this issue.

    I HAVE in the past 30 minutes, multicasted a number of machines without any problems, the biggest problem I faced was sitting at PLEASE WAIT and I was able to solve this by restarting the Multicast Manager after I changed the Multicast Max sessions on the fog web GUI to another number and back again and saving the page.

    I wish you the best of luck. You can still unicast to groups and deploy snap-ins you are not at a total loss because multicast is not working properly.



  • Jaymes - Thanks for those final tips on stopping and starting multicast.
    I’ll try that. I’m not going back to 10.04.

    [FONT=Times New Roman]I can’t spend any more time on this. I’m kicking a dead horse. I’m running with unicast. I know it’s slower and only 10 at a time. I have no more time to use on this multicast problem. I’m usually good at fault finding, but here I have failed to find any pattern of success and failure. One time in another school I had 50% of students who could print to a particular printer and 50% who could not. I eventually discovered that all those who had domain user names longer than 15 characters, could not print out on that particular printer. No problem in printing to other printers. Go figure. Over 20 years I’ve seen [U]many[/U] examples of 1 program creating a problem in another on various platforms. Drivers for smartboards screw up LibreOffice. [/FONT]
    [FONT=Times New Roman][/FONT]
    [FONT=Times New Roman]I suspect there is a problem in fog, maybe connected with firmware on my new HP Elite 8300 SFF and USDT clients.[/FONT]
    [FONT=Times New Roman]I’m running fog 33b on one of the new SFF. But I also think it is strange and disappointing that I cannot unicast or multicast to my old HP DC7100 clients that I imaged many times from my old fogserver version 0.32.[/FONT]

    Thank you Tom, Jaymes and JunkHacker for all your input and time.
    I will only give further comments in this thread if I discover something significant that you should know about.

    [FONT=Times New Roman][/FONT]


  • Developer

    [quote=“Alistair, post: 25695, member: 1830”]With firewall off:

    “Transfer successfull”[/quote]

    This is not an issue of tftpd-hpa.

    If you are interested in getting rid of the tftpd-hpa upstart as being a POSSIBLE issue you can install an older version of Ubuntu, I recommend 10.04

    I tested multicast on the latest FOG revision, Multicast works.

    you can try turning off multicasting service and turning it back on you can do so with the following command

    [code]
    sudo /etc/init.d/FOGMulticastManager stop
    sudo /etc/init.d/FOGMulticastManager start
    [/code]

    Then try multicasting.


  • Senior Developer

    This post is deleted!


  • [I]now we are trying to eliminate it as a possibility of the errors, so eliminate extra switch gear use only the router.[/I]
    I have been ONLY using one router, no other switches or firewall.

    [I]if the router worked yesterday for multicast, then it will work today, we just have to figure out what is failing and why.[/I]
    It is totally unpredictable. This is the problem.

    [I]Why are you rebooting the server after you get it working are you a glutton for punishment?[/I]
    This is an important principle of technical fault finding. Always try to reproduce exactly the same circumstances under which something happened or didn’t happen. A fresh reboot gives you that.



  • With firewall off:

    “Transfer successfull”


Log in to reply
 

401
Online

39.3k
Users

11.0k
Topics

104.6k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.