Fog 0.33b Snappin deployment


  • Senior Developer

    Yeah,
    I’m starting to think it’s returning the error because it can’t find the address, like you have a different /var/www/fog dir (maybe /var/www/html/fog?)


  • Testers

    R1165
    should I kill the pre-existing snapin task and start a new task?

    [CODE]1/30/2014 4:48 PM FOG::PrinterManager Waiting for tray to load…
    1/30/2014 4:48 PM FOG::UserTracker Record processed by server!
    1/30/2014 4:52 PM FOG::SnapinClient Attempting to connect to fog server…
    1/30/2014 4:52 PM FOG::SnapinClient Module is active…
    1/30/2014 4:52 PM FOG::SnapinClient The remote server returned an error: (500) Internal Server Error.
    1/30/2014 4:52 PM FOG::SnapinClient at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
    at System.Net.WebClient.DownloadString(Uri address)
    at System.Net.WebClient.DownloadString(String address)
    at FOG.SnapinClient.startWatching()
    [/CODE]


  • Senior Developer

    r1165 being released to address this.

    It’s good to know the validation stuff was working though, even if it was “too” much.


  • Senior Developer

    That’s because it’s looking for a snapin task from the tasks page, I’ll take a look though, give me a minute or two.


  • Testers

    Permissions issue in apache?


  • Testers

    snapin is not loading…
    Here is a snippet from the log.
    [CODE]1/30/2014 3:41 PM FOG::ClientUpdater Checking Status : UserTracker.dll
    1/30/2014 3:41 PM FOG::ClientUpdater Zero byte response returned
    1/30/2014 3:41 PM FOG::ClientUpdater Checking Status : config.ini
    1/30/2014 3:41 PM FOG::ClientUpdater Zero byte response returned
    1/30/2014 3:41 PM FOG::ClientUpdater The remote server returned an error: (500) Internal Server Error.
    1/30/2014 3:41 PM FOG::ClientUpdater at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request)
    at System.Net.WebClient.DownloadString(Uri address)
    at System.Net.WebClient.DownloadString(String address)
    at FOG.SnapinClient.getAllPublishedModules()
    at FOG.SnapinClient.startUpdate()
    1/30/2014 3:41 PM FOG::ClientUpdater Client update will be applied during next service startup.
    1/30/2014 3:41 PM FOG::ClientUpdater Client update process complete, exiting…
    1/30/2014 3:42 PM FOG::SnapinClient Attempting to connect to fog server…
    1/30/2014 3:42 PM FOG::SnapinClient Module is active…
    1/30/2014 3:42 PM FOG::SnapinClient No Tasks found for: 00:25:64:BD:7D:1A[/CODE]


  • Testers

    ok all is good! it imaged fine, I am waiting to see if the snapin loads or not.


  • Testers

    [quote=“Tom Elliott, post: 22256, member: 7271”]There is a way to kill them, just your icon’s not showing.[/quote]
    mysql
    truncate activeTasks;


  • Senior Developer

    There is a way to kill them, just your icon’s not showing.


  • Testers

    I did however come accross another bug, If the machine does not image for some reason or another and you have snapins associated with the PC, active snapins start to pile up with no way to kill/cancel them.

    [IMG]http://imagizer.imageshack.us/v2/800x600q90/191/rjum.png[/IMG]


  • Testers

    Good news! as soon as I upgraded to R1164 the PC that was setting here already images rebooted twice. once for the hostname and once for the domain.
    I am now trying to re-image it and see how that goes.


  • Senior Developer

    r1164 released. Hopefully fixes ntfsresize for xp, specifically does ntfsresize for win7. Also changes from throw exception, to print in hostname.


  • Testers

    [quote=“Tom Elliott, post: 22243, member: 7271”]That’s why you knew something wasn’t working right.

    It does make me wonder though, should I through exception, or just print that the system isn’t going to join the domain?

    I’m guessing, based on this, a print is what’s needed. I’ll make that change and release as well.[/quote]
    ok, let me know, I am ready to pull the trigger on the next release.


  • Testers

    This post is deleted!

  • Senior Developer

    That’s why you knew something wasn’t working right.

    It does make me wonder though, should I through exception, or just print that the system isn’t going to join the domain?

    I’m guessing, based on this, a print is what’s needed. I’ll make that change and release as well.


  • Testers

    [quote=“Tom Elliott, post: 22237, member: 7271”]And you have the system setup to join the domain as well, don’t you?[/quote]
    Yes I do.

    Cool, trying to get free’d up to test!


  • Senior Developer

    “Fix issue on hostname changer where if something was true, it continued on where it shouldn’t have. Add base elements for the Loation plugin (NOT READY YET). Add openssh to init.gz, mostly for me, but could prove useful.”

    r1163 releasing as we speak.


  • Senior Developer

    And you have the system setup to join the domain as well, don’t you?

    I, again, made a mistake.

    The line with the checks and balances for this is supposed to read (in plain English)

    If the host is not to use AD, print er: BLAHBLAHBLAH
    Otherwise continue on your merry way.

    I forgot the not part of it.

    So it was reading:
    if the host is to use ad, print er: BLAHBLAHBLAH

    I’m sorry I’m such an idiot.


  • Testers

    [quote=“Tom Elliott, post: 22230, member: 7271”]Did r1162 fix the Hardware issue you were seeing, if you use the available init.gz (the one I packed, not the one I packaged for you specifically)?[/quote]
    I have yet to try it, today is Hectic for me, I have had circuits to our remote locations dropping all day.
    I will try and see if I can test when things calm down.


  • Testers

    [quote=“Tom Elliott, post: 22229, member: 7271”]So the changing hostname before restart after imaging probably isn’t happening because you disabled HOSTNAME_EARLY in the FOG Settings, if I recall correctly.

    What does the fog.log say in regards to the hostname changer?[/quote]

    I set HOSTNAME_EARLY back to 1
    Here is the Log.
    [CODE]1/29/2014 11:56 AM FOG::HostnameChanger Attempting to connect to fog server…
    1/29/2014 11:56 AM FOG::HostnameChanger Module is active…
    1/29/2014 11:56 AM FOG::HostnameChanger General Error Returned:
    1/29/2014 11:56 AM FOG::HostnameChanger #!er: Join domain disabled on this host.
    1/29/2014 11:56 AM FOG::HostnameChanger Host name was not found in the database.[/CODE]


Log in to reply
 

234
Online

7.2k
Users

14.4k
Topics

135.6k
Posts