Posts made by pmonstad

same problem here. It has worked for months now but suddenly it fails (I have done a lot of svn upgrades and run 2145 now). Cannot imagine this has to do with ftp on my server as I have never changed anything lately.

I have run FOG 1.2.0 (svn 2145) with several hundred win 7 clients (Thinkpad T61, T500 etc). All is fine. Today I setup a Dell GX755 with Windows 7. Upload seems to succeed but a new client will not boot after deploy is finished. The screen is black without any warning or blinking cursor. It simply stops right after the FOG menu disappears.

My working client reports a disk with one partition (see screen shot) and the image folder on serves has the following files:
-rwxrwxrwx 1 fog fog 2 aug 4 10:51 d1.fixed_size_partitions
-rwxrwxrwx 1 root root 15 aug 4 10:51 d1.original.fstypes
-rwxrwxrwx 1 fog fog 259 aug 4 10:51 d1.original.partitions
-rwxrwxrwx 1 root root 0 aug 4 10:51 d1.original.swapuuids
-rwxrwxrwx 1 fog fog 8656638 aug 4 10:52 rec.img.000
-rwxrwxrwx 1 fog fog 11413661870 aug 4 11:25 sys.img.000

I cannot figure out why the second client fails after deploy as the hardware is identical and it has previously worked with Windows XP (FOG 0.32).

[url=“/_imported_xf_attachments/1/1255_IMAG0269.jpg?:”]IMAG0269.jpg[/url]

I had never this problem when I used the default location of the image folder (/images). When I moved it into the /home folder I get problems as the folders made inside dev folder is set to root:root

My /etc/exports file is correct, I thing:
/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,)

Servers has been restarted.

The folder inside the dev folder is never copied into /home/images as the ownership always seems to be root:root even if I manually set this to chown -R fog:fog /home/images and chmod -R 777 /home/images

Any idea about this problem? I am running svn 2145 on CentOS 5.7

In the GUI dates and times are shown in American standard (07-02-2014 2:02pm). Could there be an option to customize the layout of these strings using e.g. the [B]strftime [/B]function?

The config option could be an input where the user enters the format to be used, like e.g. %d.%m.%y %H:%M making the string looks like: 02.07.14 14:02

[quote=“Tom Elliott, post: 31956, member: 7271”]1983/1984 should fix this issue.

Thank you,[/quote]

I’ll give this a try tomorrow. Thanks again!

The files is not moved out of the dev folder and into its own folder. This was not a problem before I moved the /images folder into the /home folder. I have to do some more research tomorrow.

just a thought: could there be some hard coded stuff here referring to /images instead of the true path where the images are stored?

[quote=“Junkhacker, post: 31935, member: 21583”]why did you move it?[/quote]
Because my disk is full and my /home directory is located in a large storage group.

Installed svn 1982 and it is not possible to enter any menu. After logging in the dashboard is displayed. whatever menu I hit only dashboard is shown.

Running on Centos 5.7. Apache log says: PHP Warning: MySQL::sqlerror() [<a href=‘mysql.sqlerror’>mysql.sqlerror</a>]: Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 180, referer: [url]http://192.168.60.254/fog/management/index.php?node=tasks[/url]

I have moved the folder /images to /home/images. The export file is updated and everything works OK except one thing: The ownership of uploaded images are wrong. They changes to root:root

I have done chmod -R 777 /home/images and chown -R fog:fog /home/images but every new folder inside /home/images is then changed to root:root. I have to manually change this every time an upload is done.

I run CentOS 5.7 and 1.1.2 of FOG.

[LEFT]I have exactly the same problem on CentOS 5.7. [/LEFT]

[quote=“Jaymes Driver, post: 31691, member: 3582”]
You’re wanting an alert to display letting the user know that the image is not going to fit on the disk because of it’s size is that correct rather than just “fail” on the disks listing in the compatibility page is that correct?

Do you think that the compatibility page should be revamped to better depict this information? What ideas do you have?

Or are you wanting the alert to be on the main pxe menu screen with the “Host is registered” message? I think this is something that can only be done after registration though, as an image will need to be assigned to the host before it will know if the hosts disk is the correct size or not.[/quote]

Hi! The way it works now is the deploy starts as expected (single disk, multiple partitions, not resizable (win 7)). If the image is originally uploaded from a larger disk than the disk it now tries to deploy to, there are no warning on the client (I am not at work now so excuse me if I am wrong), except for some fast showing info about the “partition outside disk”. If you run this by remote it is not easy to cope with such an error. When I log into FOG gui the host is shown with the deploy date, and I think all went correct.

As I see the situation there are at least two ways to make it more informative to the administrator: Either stop the process on the client by not rebooting it, showing the message and waiting for some interaction, or not send a “task completed” back to the FOG server. The “task completed” should only be sent if the deploy task really is completed which is not the case here.

I don’t think it is necessary to show a warning about this unless a deploy task is started. As the message “outside disk” exist there is probably already some error checking on the client, so perhaps it could be possible to either pause the client and not send the “task completed” back to the FOG server? Sorry for my rather bad explanation about this.

[quote=“Tom Elliott, post: 31568, member: 7271”]The images folder should be with permissions set as:
[code]chmod -R 777 /home/images[/code][/quote]
Thanks!

[quote=“Jaymes Driver, post: 31603, member: 3582”]
I’ll say it once more. I do not think that this will benefit anyone from including it, that was the point of both of these posts, not to attack you. You are the one that attacks us each time we explain to you, this doesn’t benefit the community. We have included steps as a community so that if you needed to run these tools from PXE menu, you could.

How about this, instead of asking us to do it, you add gParted to your PXE Menu and take notes on how you did it and post in the tutorials section. Then monitor that thread, how many visits you have and problems you have. When you notice a large amount of traffic for that idea, post it as a feature idea. I bet Tom realizes before you do the amount of traffic and implements a feature for it.

Stop reading my comments negatively they are never meant that way, they are meant to be informative.[/quote]

Here we go again… My feature request (or more like a wish) was to[B] have a warning when the disk is too small to fit the image[/B]. I know how to solve this when I am aware of the problem, and I mentioned I have used gParted to fix this. I did not request for this to be included in the PXE menu, and YES, I have put ISO things in there myself years ago. As this is a forum my intention is to have some inputs to questions and thoughts raised in the forum. This helps me a lot (and perhaps others as well) as a forum thread is often very helpful. Starting a discussion (that is what a forum is for, right?) does not necessarily mean me or someone else expect developers to shout “hurray” and start coding right away. It is yours choice: find the suggestion good, give some feedback (in a friendly way) or don’t answer at all. The worst thing that could happen is to frighten people to ask questions, telling them they are stupid, lazy etc. I have spent time in the Wiki, and sometimes it is helpful and sometimes it it confusing as the info is outdated compared to the current functionality in FOG. This is no criticism about anyone, it is the nature of a living project like FOG. That is why I (and probably a lot of others) ask a question in the forum: not found in the Wiki, not a clue about where to look, of most often; the nature of a forum - ask a question and hope someone will help you.

[quote=“Tom Elliott, post: 31591, member: 7271”]Another option to work with is to use the NTFS - Single Disk (Resizable) option. We’ve fixed it so you don’t even have to use Sysprep to use resizable images.[/quote]

Tom: will this work with Windows 7 now? If true I guess this is the ultimate solution as this was not a problem in the old Windows XP days. Thanks!

Dear Mr Driver,
I am fully aware of the solutions you suggests, and I have never ever had any problems fiddling around with FOG or other systems out there. I am not sure about this, but I sometimes feel every comment and suggestion I rise here in the forum seems to make you or other administrators quite upset, at least some of the answers you give are not very friendly. I don’t want to make a flame war about this, but this is how I sometimes read and understand your answers.

The idea about such a warning mentioned in the first post is to let newbies find FOG a little more user friendly. Of course I know it makes sense to have an image smaller than the smallest disk in use, but even if my computers are very much the same brands and models, there seems to always be a few computers with a smaller disk (e.g. replacement) than the others.

It took me a long time to find the reason why a computer did not successfully deploy, and when deploying a lot of hosts it is impossible to notice this as there are no warnings at all. The host is even marked as successfully deployed in the GUI. I have several times expected a range of computers to have completed a deployment just to find them back in my office a couple of days later as the user can’t boot the computer.

But of course, if there are no one else in the world who find this necessary I will not struggle much to convince anyone. And excuse me so much for rising the question in the first place.

This file does not exists anymore in latest releases. No need to worry about it at all.

I have set the path for images to /home/images. This works quite well, but not when I start an upload. The files are uploaded to the dev folder inside images, but the owner is set to root and not to fog. It then fails in last stage when tha mac-address folder inside dev is to me moved one step up. I have to do this manually after I have set correct ownership.

I have already set ownership like: chown -R fog:fog /home/images and chmod -R 755 /home/images but it still makes new images owned by root when I do an upload. Any suggestions?

Running latest svn on Centos 5.7.