Posts made by need2

Are these systems part of any kind of Domain?

Since the database never appears to have been successfully modified by the installer, I just reran the 1.1.1 installer after deleting all of the FOG pieces except images and the database.

As far as I can tell, MySQL is running. It just doesn’t like some part of the schema update. The .log and .err files appear to be empty when viewed by nano. I also did a partial uninstall (deleted everything except my DB and images) and reinstall, and still got stuck on the schema update.

I have now reverted back to 1.1.1, and everything is working normally, but I cannot test the fixes introduced in the newer revisions.

Yes, I still can’t get past the schema update step.

Yes, that did not do anything for it. There appears to be either a problem with a table or a command being fed to that table.

Received a database error from the web GUI schema update while upgrading to SVN 1880 from 1.1.1 . I did not see a specific error, so here is the output:

See attached.

EDIT: So now I’m stuck in a limbo of sorts. I can’t get past the schema update. I’ll keep fiddling.

When the following is entered manually:
[CODE]Update ID: 1 - 10

Database Error:

Database SQL:

INSERT INTO fog.users VALUES (‘’,‘fog’, MD5(‘password’),‘0000-00-00 00:00:00’,‘’)[/CODE]

I get:

[CODE]Column count doesn’t match value count at row 1[/CODE]

[url=“/_imported_xf_attachments/1/1023_schema_output.txt?:”]schema_output.txt[/url]

Excellent, thanks for your quick work on this. I’ll update to that branch tomorrow and give it a shot.

I have not tested every one, but I know that everything related to imaging and disk check shut down afterwards if scheduled.

A Wake task still requires an image, which honestly it shouldn’t.

If scheduling a shutdown after completion of a donate task, the client reboots rather than shuts down.

Present in the FOG 1.x.x branch since the donate task has been implemented, and verified as still present in 1.1.1 .

If you have the FOG Client installed on the workstations, you can specify sleep/shutdown times.

That will teach me to do conversions before coffee. Yes I should have come out with MB.

The old version of FOG does not have as much in the way of compression, so it will consume bandwidth much more quickly.

If I read correctly that the server is a P4 with 4GB of RAM, then you are dealing a lot with processing speed, onboard bandwidth (speed of communication within the motherboard), RAM speed, drive speed, most likely a 10/100 network card, and the speed of the cache on almost every component previously mentioned all before the information can even leave the server.

Then it has to transmit over the network. Networks are measured in bps, or bits per second. A Gigabit network could transmit in the absolute best case scenario 125 gigaBYTES per second. HOWEVER, there are almost no cases where this happens. You have to deal with line quality (quality of the insulation and lines of the ethernet cable), distance degradation, switch performance, outside interference and other clients passing information before you even get to the workstation.

Finally, on the workstation, it has to process all of this information coming in over its ethernet card (also likely 10/100). The information has to go through a similar series of steps as to what it went through on the server but in reverse before it is committed to the drive, which most consumer class drives to not have amazing write speeds.

In conclusion, if you were to put FOG on a faster server, and/or upgrade to FOG 1.1.1, you should see a performance improvement.

The NFS that works is on a Windows server, and the one I haven’t gotten working yet is on the FOG server. And I do have it in the exports file, but come to think of it I should take another look at the settings it has.

Just touching base on this one. I continued to have difficulties with the NFS share, so I just cheated and used the Windows Server NFS share I used way back when I was using a hijacked WDS server for my PXE server. Its working like that, but I would like to be able to stop relying on that server before it goes end-of-life. So any suggestions on what permissions and such I should have on the NFS share for the TRK boot folder would be appreciated.

Obligatory SVN rev number request.

No… so I am not familiar with what a FAI server does. Does it behave like FOG where it will replace its standard menu with a chainload if you give a task for a workstation that is registered to it? Or does it only supply a menu during its PXE boot every time no matter what?

Does the FAI server change its PXE boot for clients like the FOG server does if there is a task for said client?

I needed to do:

[CODE]chmod -R 755 /var/www/fog/service/ipxe/trk[/CODE]

I’m getting an access issue now within the TRK kernel. That is probable an issue with my NFS share… either I didn’t mount it right or there are some other places that permissions reside for NFS shares. Doing some digging of my own, but I always appreciate freebies.

By previous menu, I meant the default FOG menu. It would step me back out of the Advanced Menu and back to the Default FOG Menu. I think that part is fixed now, and it looks like my problems are all permissions now. I’m still a bit linux-tarded, so that might take me a bit to get right.