• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. pmonstad
    3. Posts
    P
    • Profile
    • Following 0
    • Followers 1
    • Topics 65
    • Posts 284
    • Best 5
    • Controversial 0
    • Groups 0

    Posts made by pmonstad

    • Could there be some info on a client when "partition outside the disk!"?

      When cloning Windows 7 hosts there are sometimes problems with clients having too small harddisks. The deploy task completes without any warnings on host and the image has not been deployed.

      The only way to trouble shoot is to run the client info from the PXE menu. When checking for FOG compatibility a message is shown: “Error: Cant have a partition outside the disk!”

      I spent a lot of time finding the source of this problem: harddisk too small compared to the image. I suggest this “error” is shown during the deploy attempt, if possible.

      The solution fo me is to run Gparted on the “master” client and then resize the original disk before running a new upload. Could the Gparted package be put in as an option in the PXE menu?

      posted in Feature Request
      P
      pmonstad
    • The exports file

      Changing the standard image folder path in FOG requires you to change the file /etc/exports every time you update FOG. Is it possible to keep the file unchanged during an update process?

      Running Centos 5.7 and FOG latest svn.

      posted in General
      P
      pmonstad
    • RE: Some error checking when editing host name

      Hm, I did not notice it as I had to scroll down to access the Update button.

      posted in Feature Request
      P
      pmonstad
    • Some error checking when editing host name

      I have some hosts names host1, host2, host3 etc

      When I do a rename of one of the host, like changing host2 to host1 there is no warning/error telling the host name already exists. I click the Update button and all seams right (if the host name exists is is not really changed, but it is easy to not notice this).

      Could there be some kind of pop up box telling the host did not changed name: host name exists. ?

      Today I did some renaming and 6 hosts were not renamed because I did not notice the input field stayd unchenged after I hit Update.

      posted in Feature Request
      P
      pmonstad
    • RE: Problems after moving images-folder

      Thanks Tom, a restart solved the problem.

      posted in General
      P
      pmonstad
    • RE: Problems after moving images-folder

      Sorry but I still have problems after changing the location of my images folder. I have moved the folder from /images to /home/images. I have then altered the /etc/exports so it looks like this:

      /home/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure,fsid=1,)
      /home/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure,fsid=2,)

      I have run the command exportfs -a and thanges the path in Storage Management. The image is uploaded to /images/dev folder as a folder with mac address. It contains three files: d1.mbr, d1pa.img and d1p2.img (a win 7 disk).

      The folder is owned by fog and permissions are set to 755.

      I need some help to trouble shoot this one. Running latest svn version 1889 on Centos 7.

      posted in General
      P
      pmonstad
    • RE: Problems after moving images-folder

      I see, but then I do not understand why an upload did not complete before I edited the config file and then made another upload. Possibly something other which went wrong then. Anyway, it works as expected now.

      posted in General
      P
      pmonstad
    • RE: Problems after moving images-folder

      Thanks! Could this file be updated automatically when the path in Storage group is altered?

      posted in General
      P
      pmonstad
    • Problems after moving images-folder

      I have moved the image folder into the home folder. I have read the wiki which tells my I have to modify the config file found at /var/www/html/fog/commons/config.php

      I cannot find this file in FOG 1.1.1. I have done all other things described in the wiki. An image is uploaded but left inside the dev folder. I suppose one of the last bits it to move this one level up. Any suggestion about what is wrong?

      Running Centos 5.7 and latest svn version.

      posted in General
      P
      pmonstad
    • Release number -> release date

      I wish the release number could change from the counting number into a date, like release/build 140620

      This makes more sence as I have no clue what is the latest release or how old my installation is.

      posted in Feature Request
      P
      pmonstad
    • RE: Blank page after creating new Image

      [I][SIZE=12px]I had the same issue. I solved it by editing php.ini. Increase the value of the variable memory_limit = 32M (I set it to 32M, default on my server was 16M). Then restart your apache server.[/SIZE][/I]

      posted in FOG Problems
      P
      pmonstad
    • RE: 040ee119 error on boot

      The install/upgrade script fails on CentOS: Starting FOG Multicast Management Server…Failed!

      It is possible to start the service manualle by running “service FOGMulticastManager start”. Trying to stop it with “service FOGMulticastManager start” returns an error FAILED.

      posted in Bug Reports
      P
      pmonstad
    • RE: After Ver 1.0.0 update Blank Screen

      [quote=“ttricktt, post: 27031, member: 720”]Hi Fog Users,

      FOG is running on, CentOS release 5.10
      [FONT=arial][COLOR=#393939]Linux 2.6.18-371.6.1.el5 on i686[/COLOR][/FONT]

      After I upgraded to V 1.0.0 I have a blank screen when I browse to [url]http://<myhost>/fog/management/index.php[/url]

      Also I see an error in httpd logs,
      PHP Parse error: syntax error, unexpected T_FUNCTION, expecting ‘)’ in /var/www/html/fog/commons/init.php on line 33

      Anybody have any ideas how to fix this?
      Thanks,
      Rick[/quote]

      I had the same issue. I solved it by editing php.ini. Increase the value of the variable memory_limit = 32M (I set it to 32M, default on my server was 16M). Then restart your apache server.

      posted in General
      P
      pmonstad
    • RE: Bugs in FOG 1.0.0

      [quote=“pmonstad, post: 26961, member: 17422”]I am running as root and my server has been unchanged for years. Have done a lot up FOG updates (almost a couple of times each day) and this has never been a problem before. After a server restart I now get a new error Starting FOG Image Replicator Server…Failed![/quote]

      Hm strange. I ran the command
      service FOGMulticastManager restart

      Is respons with failed on stopping but OK on starting. Running the install script once again made it complete. Dont know was is wrong.

      posted in Bug Reports
      P
      pmonstad
    • RE: Bugs in FOG 1.0.0

      [quote=“Tom Elliott, post: 26958, member: 7271”]Have you tried:
      [code]service FOGMulticastManager restart[/code] To see if it reports any issues, cause I’m running CentOS 6.5 final on a few of my systems and have not had any issues installing.

      My best guess, maybe you tried installing as a local user, not as root?

      Could it also be you have a mysql password set for the root user?[/quote]

      I am running as root and my server has been unchanged for years. Have done a lot up FOG updates (almost a couple of times each day) and this has never been a problem before. After a server restart I now get a new error Starting FOG Image Replicator Server…Failed!

      posted in Bug Reports
      P
      pmonstad
    • RE: Bugs in FOG 1.0.0

      [quote=“pmonstad, post: 26951, member: 17422”]Error when installing/upgrading: I am upgrading to rev 1669 on my CentOS server. The install script fails with error: Starting FOG Multicast Management Server…Failed!

      No way I can get it to complete the install. Anyone?[/quote]

      I did a server restart and now it respons with error Starting FOG Image Replicator Server…Failed! I am not able to upgrade my installation.

      posted in Bug Reports
      P
      pmonstad
    • RE: Bugs in FOG 1.0.0

      Error when installing/upgrading: I am upgrading to rev 1669 on my CentOS server. The install script fails with error: Starting FOG Multicast Management Server…Failed!

      No way I can get it to complete the install. Anyone?

      posted in Bug Reports
      P
      pmonstad
    • RE: Bugs in FOG 1.0.0

      Hm, i fixed this by editing phpi.no memory_limit = 32M (was 16). This seems to have cured the broken GUI as well. Groups containing many hosts was the problem.

      Could there be some check or warning during FOG installation to warn the user about this? Not a problem when you know where to trouble shoot, but a pain when you dont.

      posted in Bug Reports
      P
      pmonstad
    • RE: Bugs in FOG 1.0.0

      Testing the problem with broken GUI. I deleted the group (not hosts) and recreated the group with the same name. Got the error (broken GUI as screenshot in another post shows). Did a new test adding som other hosts to a new group. Now I am not able to list all groups. Blank screen and an error in apache log:
      [Fri May 09 14:05:24 2014] [error] [client 172.20.0.45] PHP Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 82 bytes) in /var/www/html/fog/lib/db/MySQL.class.php on line 119, referer: [url]http://192.168.60.254/fog/management/index.php?node=group[/url]

      Now I am not able to either search nor list my groups.

      posted in Bug Reports
      P
      pmonstad
    • RE: Bugs in FOG 1.0.0

      Thanks! I’ll check the apache log file at work tomorrow. The strange thing is it only breaks the GUI in this particular group of 245 hosts, not my other groups. As mentioned in other threads there have been problems with the creation of groups in previous relewses. I’ll delete the group and recreate another one to eliminate fault possible been in previous releases of FOG.

      posted in Bug Reports
      P
      pmonstad
    • 1
    • 2
    • 8
    • 9
    • 10
    • 11
    • 12
    • 13
    • 14
    • 15
    • 10 / 15