• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. SneakR
    S
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 3
    • Best 0
    • Controversial 0
    • Groups 0

    SneakR

    @SneakR

    0
    Reputation
    189
    Profile views
    3
    Posts
    0
    Followers
    0
    Following
    Joined Last Online
    Age 48

    SneakR Unfollow Follow

    Latest posts made by SneakR

    • Database Schema Update Loop

      I’ve updated to the latest trunk 7647 and now am stuck with the database schema update loop. Attempting to update then clicking “login” on the success screen takes me right back to the screen to update the DB schema.

      On 14.04 and have been through the .fogsettings file and the config.class.php file and thought I had edited one of those before to match it up on a previous update to get by this but maybe I missed something. Brain is fried today and trying to get a new batch going…

      Appreciate a smack in the back of the head on this one if anyone has the tip. I’ve searched and searched and nothing tried resolves.

      posted in FOG Problems
      S
      SneakR
    • RE: Changed kernel name on client page, will not revert.

      Chad,

      Thanks, that took care of it, deleted the old pxe boot file and voila’

      posted in FOG Problems
      S
      SneakR
    • Changed kernel name on client page, will not revert.

      Ubuntu 12.04
      Fog .32

      We tried to specify a kernel for some netbooks (x131e) after we downloaded and saved as the name Kitchen. Put that in the field after we had manually registered a client to test, but now it ALWAYS looks for that original name we put in the field to specify. I can even change it to FUZZ or something and update and when the client boots it says “cannot find kernel kitchen”. We’ve rebooted the FOG server, deleted the client and re-registered and it still looks for that kernel name we first typed in. We’ve used FOG just fine on a bunch of deploys, this is the only hiccup we’ve had so far.
      Thanks!

      posted in FOG Problems
      S
      SneakR