• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Axel
    3. Topics
    A
    • Profile
    • Following 0
    • Followers 0
    • Topics 12
    • Posts 40
    • Best 1
    • Controversial 0
    • Groups 0

    Topics created by Axel

    • A

      Is upgrading to trunk "back to normal" now?

      General
      • • • Axel
      3
      0
      Votes
      3
      Posts
      1.0k
      Views

      N

      SVN will look a bit odd at first glance since its revision number no longer matches the current software revision that you will receive.

      For example (numbers are made up for my time’s sake):
      SVN shows rev 3899, installed FOG shows 4591. This is okay and normal now.

    • A

      Solved FOG 3642 BFD: /var/www/fog/service/ipxe/bzimage warnings in apache2 logs client not imaging

      FOG Problems
      • • • Axel
      2
      0
      Votes
      2
      Posts
      780
      Views

      Tom ElliottT

      Those errors occur when you’re looking at the fog configuration pages base page. The come up because of the attempt to read the bzImage and bzImage32 files version.

    • A

      Solved Multiple instances of the same service running? ps -ef|grep FOG build 3642

      FOG Problems
      • • • Axel
      3
      0
      Votes
      3
      Posts
      1.0k
      Views

      A

      ok, thank you Tom!

    • A

      Solved Quick cron scheduling help needed

      General
      • • • Axel
      4
      0
      Votes
      4
      Posts
      1.4k
      Views

      A

      It was adding the * that helped get these going, thanks Deastrom!

    • A

      FOGScheduler needs started manually since upgrading to SVN 2912 from 1.2.0

      FOG Problems
      • • • Axel
      15
      0
      Votes
      15
      Posts
      5.1k
      Views

      Tom ElliottT

      I have not, but I’m constantly (as you can guess) on SVN so if there was some issue, I would have likely corrected on spot. That said, I don’t recall this being an issue. Thats not to say there isn’t one.

    • A

      Troubleshooting help needed: Upload task delayed scheduling not working correctly.

      FOG Problems
      • • • Axel
      12
      0
      Votes
      12
      Posts
      3.3k
      Views

      A

      I don’t want to get too far off track, but now that i’m squared away with 1.2.0 and things are working, do you recommend I move to the SVN?

    • A

      Scheduled tasks are not starting in FOG 1.2.0

      FOG Problems
      • • • Axel
      19
      0
      Votes
      19
      Posts
      7.1k
      Views

      JunkhackerJ

      [quote=“Wayne Workman, post: 47472, member: 28155”]So literally you just put in the host serial and mac address and the dev server’s IP and that’s it?

      That’s pretty sweet, I gotta say.[/quote]

      yep, that’s all you have to do

    • A

      FOG problems connecting to NFS share on NAS4FREE

      FOG Problems
      • • • Axel
      10
      0
      Votes
      10
      Posts
      6.2k
      Views

      L

      [quote=“Axel, post: 12528, member: 686”]So I spent 10+ hours today trying to get this to work. I’ve followed multiple tutorials on using an external NFS share and my results are not good. After I configure the NFS share in FOG the web GUI says unable to connect on the front page where usually the space free/used is displayed. I’ve created the NFS share, remade /images mounted my NFS share in FOG on /images, created the .mntcheck and then the /dev folder with .mntcheck inside it. I’ve made sure to chmod -R fog:root /images. When uploading an image once the process gets to send method-nfs I get an error of mount: 192.168.62.125:mnt/nfsdata/dev/ failed, reason given by server : Permission denied
      mount: mounting 192.168.62.125:/mnt/nfsdata/dev/ on /images failed bad file descriptor. I’ve even tried following posts on here where people had similar issues and i’ve had no luck. The fog server is a vm running in Proxmox with bridged networking. Any ideas?[/quote]

      hey Axel

      not sure if you resolved your issue, post is too long… didn’t read all of it…

      however, I have noticed two things that may be causing your issue…

      the first… you used chmod -R fog:root /images… when it should be chown -R fog:root /images (perhaps you meant to type that…)
      the second, in your screen shots for the storage node section, the password field should resemble the password in plain text, not the encrypted type… try changing to your normal password, save and try that…

      I always issue (right or wrong) the following commands on the /images folder…
      chmod -R 777 /images
      chown -R fog:root /images

      but that’s just me…

    • A

      Moving FOG install to Proxmox OpenVZ Container question about database and "schema"

      General
      • • • Axel
      1
      0
      Votes
      1
      Posts
      940
      Views

      No one has replied

    • A

      Snap In Deployment question

      FOG Problems
      • • • Axel
      1
      0
      Votes
      1
      Posts
      1.1k
      Views

      No one has replied

    • A

      Can't move images file

      General
      • • • Axel
      3
      0
      Votes
      3
      Posts
      1.5k
      Views

      C

      shut down nfs deamon, something like “sudo stop nfsd” or maybe looking in /etc/init.d/ for an nfsd related script, and calling it with the stop argument.

      Once you’re done, remember to turn nfsd back on.

    • A

      Adding local storage via external USB drive

      FOG Problems
      • • • Axel
      4
      0
      Votes
      4
      Posts
      2.5k
      Views

      C

      It should.

      Plug in the USB drive. See where it mounts, usually /media/something. You can cat /etc/mtab to get the device info also, just look for something being mounted to /media/something.

      Make a directory for the server image under /images, something like /images/Server1.

      Mount the device to the folder you just created: sudo mount /dev/usbhdd1 /images/Server1

      See if it works. If so, you can add it to the fstab so it mounts the folder on every boot up. You may also need to use the same usb port each time, but I’m not sure how Linux ID’s the external drive for mounting purposes.

    • 1 / 1