• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Raymond Bell
    3. Topics
    • Profile
    • Following 0
    • Followers 0
    • Topics 44
    • Posts 369
    • Best 22
    • Controversial 0
    • Groups 2

    Topics created by Raymond Bell

    • Raymond BellR

      Lenovo M70a Pxe boot

      FOG Problems
      • • • Raymond Bell
      12
      0
      Votes
      12
      Posts
      2.1k
      Views

      george1421G

      @raymond-bell said in Lenovo M70a Pxe boot:

      And i have never used the FOS Linux

      You have, but you’ve never directly interacted with it.

      The concepts are here: https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image Understand your caveats and why this isn’t the first choice.

      The concept here is that you will boot bzImage and init.xz from the USB stick and bypass iPXE and its interaction with your hardware. Look at the chat bubble in the upper right corner of this page for a few more hints.

    • Raymond BellR

      Image Replication Deletes and starts over

      FOG Problems
      • • • Raymond Bell
      5
      0
      Votes
      5
      Posts
      420
      Views

      Raymond BellR

      @sebastian-roth
      Yes one of the storage nodes is the master
      But i am working on changing that as we speak and creating a new master 64bit then the others will be changed to 64 bit also

      as of right now i have
      server 64 bit 16.04 xubuntu not storage node
      1 Ubuntu 16.04 32bit storage node master
      1 Ubuntu 16.04 32bit storage node
      1 ubuntu 20.04 64 bit storage node

      I am going to just use the 64bit as master after i get the images all copied over, then disable the other 2 32 bit nodes, upgrade them to 64 bit and re-enable them to see if that fixes some of the issues i am having since the 1.5.9 upgrade

    • Raymond BellR

      Unable to Image Since 1.5.9 Update

      FOG Problems
      • • • Raymond Bell
      7
      0
      Votes
      7
      Posts
      414
      Views

      Raymond BellR

      @sebastian-roth Checked on the storage node that was giving issues and it done fine i am going to just move everything to new master SN and test

      fog@Fog-Main-Storage:/images$ cp Win1064Bit4-15-21/d1p2.img test_extract.img.gz fog@Fog-Main-Storage:/images$ file test_extract.img.gz test_extract.img.gz: gzip compressed data, last modified: Thu Apr 15 12:45:14 2021, from Unix, original size modulo 2^32 3448112244 gzip compressed data, reserved method, ASCII, has CRC, extra field, has comment, encrypted, from FAT filesystem (MS-DOS, OS/2, NT), original size modulo 2^32 3448112244 fog@Fog-Main-Storage:/images$ gunzip test_extract.img.gz
    • Raymond BellR

      Lenovo E15 Gen 2 Issues

      FOG Problems
      • • • Raymond Bell
      9
      0
      Votes
      9
      Posts
      1.5k
      Views

      S

      @x23piracy said in Lenovo E15 Gen 2 Issues:

      Is reading the SLIC from Bios still in the current releases of FOG? I have a nice customisation from Tom running in my current installation:

      Sorry, but I don’t know what this is about. Probably best of you open a new topic on this.

    • Raymond BellR

      chainloading failed after image

      FOG Problems
      • • • Raymond Bell
      1
      0
      Votes
      1
      Posts
      187
      Views

      No one has replied

    • Raymond BellR

      Fog Upgrade (Backing up database.. Failed!)

      FOG Problems
      • • • Raymond Bell
      8
      0
      Votes
      8
      Posts
      869
      Views

      Raymond BellR

      @sebastian-roth UPDATE
      I ran 1.4.4 installer
      then ran 1.5.5 installer
      then ran 1.5.9 installer
      and everything worked fine this time it asked me to set a password for MySql this time

    • Raymond BellR

      Solved Inventory Report 1.5.7

      FOG Problems
      • • • Raymond Bell
      5
      0
      Votes
      5
      Posts
      684
      Views

      Raymond BellR

      @Sebastian-Roth Yes this fixed the issue…

      @Sebastian-Roth said in Inventory Report 1.5.7:

      @Raymond-Bell As the person in the other topic has not replied yet I would ask you to test the first fixes I mentioned there. Would be great to get some feedback if the new search pattern thing is working in the wild (on your system).

    • Raymond BellR

      Unsolved Image List under PXE Boot

      FOG Problems
      • • • Raymond Bell
      2
      0
      Votes
      2
      Posts
      159
      Views

      No one has replied

    • Raymond BellR

      Solved TFTP Server

      FOG Problems
      • • • Raymond Bell
      30
      0
      Votes
      30
      Posts
      6.3k
      Views

      george1421G

      @Raymond-Bell said in TFTP Server:

      It was that ATA… Sorry for all the trouble guys

      That is why we are here to help. I’m glad you have it worked out. Something simple, but it caused you so much problems. On the plus side you are now on 1.5.5 with all of the fixes, so you are in a better place than when you started the day.

    • Raymond BellR

      Unsolved HostnameChanger Not Working

      FOG Problems
      • • • Raymond Bell
      2
      0
      Votes
      2
      Posts
      220
      Views

      S

      @Raymond-Bell Can you please post a picture of the host’s AD settings?

      The log message says a user is logged in. Is that true? Did you try with and without a user being logged in?

    • Raymond BellR

      Unsolved FOG 1.5.4 Replication Issue

      FOG Problems
      • • • Raymond Bell
      4
      0
      Votes
      4
      Posts
      418
      Views

      J

      @Raymond-Bell @Tom-Elliott You had me update to the working-1.6 branch and it fixed the issue in that it would go the next node even if it says there is a non-match file on the first node. The issue of it constantly thinking image files (usually the largest .img) don’t match still has not been fixed. I have been too busy with other issues in our school district to continue testing at the moment though and have been manually updating images using rsync if we ever upload a new version, seeing as how it doesn’t seem to delete non-matching files and /or thinks matching files don’t match. I am able to replicate the issue on VM’s at home and with multiple test machines and our servers at work. However until the work orders slow down I am unable to keep digging into the issue and the rsync has been working as a temporary solution.

    • Raymond BellR

      Unsolved Slow web Interface 1.5.2

      FOG Problems
      • • • Raymond Bell
      2
      0
      Votes
      2
      Posts
      289
      Views

      S

      @Raymond-Bell Anything in apache error logs?

    • Raymond BellR

      Solved Backing up database failed!

      FOG Problems
      • • • Raymond Bell
      8
      0
      Votes
      8
      Posts
      918
      Views

      Raymond BellR

      @george1421 I had downloaded the 6077 again and not 6078 🙂
      END USER ERROR 🙂

    • Raymond BellR

      remove reference to old snapin file

      FOG Problems
      • • • Raymond Bell
      1
      0
      Votes
      1
      Posts
      328
      Views

      No one has replied

    • Raymond BellR

      Solved Backing up database failed!

      FOG Problems
      • • • Raymond Bell
      7
      0
      Votes
      7
      Posts
      2.6k
      Views

      Raymond BellR

      ISSUE RESOLVED By following this

      TLDR; Rerun the fog installer if you have lost “Database Connectivity” to your fog server, or run the ALTER USER syntax shown below.

      So Ubuntu 16, among others I suppose, enable a “security updates” to be applied automatically as a “default” to things. Why, well it makes it simpler to ensure your Ubuntu systems are in compliance and patched for any potential exploits. This causes unknown and unexpected issues.

      I figured it’d be a safe thing to express that there could be problems (as many of you have already experienced) that when these updates go up (with or without your knowledge) it can break functionality in unexpected and inopportune ways.

      The quickest fix is to simply rerun the fog installer which should correct the problem.

      As a note, it seems this problem is specific only when the mysql account is the ‘root’ user AND the password is blank.

      The “fix” if you must do it manually is to open a terminal and obtain root:
      Super (Windows Key) + T then sudo -i (in most cases).

      From there, open mysql with mysql -u root

      NOTE: MySQL MUST be run with ROOT.

      Run:

      ALTER USER ‘root’@‘127.0.0.1’ IDENTIFIED WITH mysql_native_password BY ‘’; AND
      ALTER USER ‘root’@‘localhost’ IDENTIFIED WITH mysql_native_password BY ‘’;

      It’s okay if one of them fails. This is going to fix Most people’s issues.

      I would highly recommend removing the unattended-upgrades as many of these “sudden” issues came as a security patch ubuntu pushed out. By default Ubuntu typically set’s this for you as enabled and it can cause havoc on you as you (the admin) may not have “done” anything.

      To prevent this problem from happening in the future you could run:

      apt-get -y remove unattended-upgrades (AS Root again).

    • Raymond BellR

      Solved FOG Imaging Log Not Working

      Bug Reports
      • • • Raymond Bell
      17
      0
      Votes
      17
      Posts
      5.8k
      Views

      Tom ElliottT

      So the reason the date selector was not being seen was because I am grabbing the minimal date.

      Some entries, for this field, might have ‘0000-00-00 00:00:00’ as the date time stamp, which is invalid.

      So the original way it worked, if the date was invalid (start time will always be earlier than end time) it would present “invalid”.

      The updated method should work for this for all of you having this problem. I’m correcting this behaviour by adjusting the start date to 2 years before the current date.

      Hopefully this is sufficient. The reason I don’t want to go back further is the amount of time it would take to generate the selector. (I’m not guessing the selector based on max end date any more. I’m just giving a date range based on the earliest time found and forward (as it’s not really a selector otherwise right?))

      I’m also changing the way things are displayed a little bit.

      Instead of showing logs of tasks that have either an invalid start OR end date, both start AND end must be invalid to no longer show. It may make some strange readings for things, but shouldn’t hurt anything otherwise.

    • Raymond BellR

      Solved Stopping web service.............Failed!

      FOG Problems
      • • • Raymond Bell
      10
      0
      Votes
      10
      Posts
      6.1k
      Views

      S

      I got below error during installation:

      Stopping web service………………………………….Failed!

      I installed apache/httpd service then re-run installation and everything was perfect.

      If anyone gets error during apache/httpd installation then open epel.repo from below location and change https –> http in mirrorlist link.
      vi /etc/yum.repos.d/epel.repo

      Hope this helps everyone.

    • Raymond BellR

      Solved Release 1.3.0-RC-6 install error

      Bug Reports
      • • • Raymond Bell
      2
      0
      Votes
      2
      Posts
      661
      Views

      Tom ElliottT

      @Raymond-Bel
      it’s from line endings not being read properly.
      ^M translates to (Native) mode line endings (but it confuses installers).
      fix hopefully in SVN now.

      It’s not something I can tell when submitting either. It’s only when one informs me like this, so thanks.

    • Raymond BellR

      Solved Printer not showing in Devices - Fixup to 1.3.0-RC-5

      Bug Reports
      • • • Raymond Bell
      22
      1
      Votes
      22
      Posts
      6.5k
      Views

      Raymond BellR

      All is good to go now…

    • Raymond BellR

      Solved SVN Revision: 5846 Unable to remove printer

      Bug Reports
      • • • Raymond Bell
      2
      0
      Votes
      2
      Posts
      849
      Views

      Tom ElliottT

      Should be fixed in latest, sorry about causing the issue.

    • 1 / 1