Posts made by PomonaIT

[quote=“MRCUR, post: 40217, member: 25116”]I know this is an older thread, but I just got a few Surface Pro 3’s that I’d like to image through Fog. I installed the latest SVN build of Fog onto Ubuntu 13.10 this morning. I have the DHCP server set to ipxe.efi.

After disabling secure boot on a Surface, I was able to get it to the iPXE menu. Entered the server’s IP when prompted and after about 20 seconds received a timeout message.

Any ideas Tom?[/quote]

I’d like to know if there are any solutions for this as well? I don’t get any sort of connection. We may be implementing this as a standard tablet and it would be a bummer if I can’t create and deploy an image to them. I will add, I am only on version 1.2.1, because of the XP deployment bug (something to do with PartClone?) that a few of us encountered (yes , we still deploy XP to older systems).

[quote=“Tom Elliott, post: 36573, member: 7271”]Quotes are not needed, nor will they hurt.

I found out the issue.

The file you need to add the date.timezone on Ubuntu 14.04 (and possibly others?) Is in:

(Drumroll please)
.
.
.
.
…
…
[code]/etc/php5/cli/php.ini[/code][/quote]

Oh well, I edit the setting on both php.ini’s with and without quotes with no success.

[quote=“Tom Elliott, post: 36573, member: 7271”]Quotes are not needed, nor will they hurt.

I found out the issue.

The file you need to add the date.timezone on Ubuntu 14.04 (and possibly others?) Is in:

(Drumroll please)
.
.
.
.
…
…
[code]/etc/php5/cli/php.ini[/code][/quote]

Great. I guess we have something like a 1 in 3 chance to have got it right…haha. I will give that a try.

[quote=“PomonaIT, post: 36554, member: 24658”]Let me check that out and see what is set. Thanks.[/quote]

I am using Ubuntu, so I found the php.ini at /etc/php5/apache2/. The date.timezone setting was blank, so I added “date.timezone = America/Los_Angeles”. I restarted server for good measure, uploaded image and time is off by 7 hours. Any other ideas?

[quote=“Tom Elliott, post: 36547, member: 7271”]“If it isn’t broken, don’t fix it.”

It isn’t “broken” persay. It’s not even a “problem” persay.

Your /etc/apache2/php/php.ini? Maybe needs the date.timezone?[/quote]

Let me check that out and see what is set. Thanks.

I have noticed of late (not sure how long it has been like this) that the image upload time is off several hours, appears to be mostly ahead 4-5 hours. I have check my VM and the FOG server time and all are correct. What else might be causing the time to be off? This isn’t a priority fix, but just an observation I wanted to bring forward.

[quote=“Tom Elliott, post: 36493, member: 7271”]How do you mean it said you were still on 1.2.0?[/quote]

Ok, I ran 1.1.2 install again and now I have the 1.1.2 version on the cloud graphic and the prompt that I don’t have the latest version under Fog Configuration. I assume since I didn’t upgrade, I wasn’t supposed to see the database schema update page?

[quote=“Tom Elliott, post: 36493, member: 7271”]How do you mean it said you were still on 1.2.0?[/quote]

I think I realized what I did. I mis-read ‘latest version’ to be what version I am on, even though I noticed the cloud showed I was on 1.1.2. I have since reverted my vm snapshot. Looks like I will run the installer again and give an update. Thanks.

[quote=“Tom Elliott, post: 36490, member: 7271”]Reinstall fog, only with the 1.1.2 package.[/quote]

If you mean to download and run installer for 1.1.2 over the top of 1.2, I did that. It stated I was on 1.2 after the install completed. Is there other steps to take?

I seem to have the XP deployment bug after updating to 1.2.0, like others have been posting of late. We still have to re-image some XP machines, so I can’t have it not work. I have looked at the few suggestions that have been posted but they either don’t pertain or vague. What is the easiest way to go back to 1.1.2 without losing my data (ie. images, db)?

[quote=“Tom Elliott, post: 30601, member: 7271”]Moving to iPXE isn’t necessarily causing issues, rather, it’s showing issues that you haven’t seen quite yet. PXE was old and slow, and probably didn’t care about many things as much as iPXE does. While I understand this is unexpected, I would go out on a limb and say the PRO’s completely outweigh the CON’s of this change.[/quote]

Ok, thanks for the follow-up. I guess we either do further testing or possibly move to another switch.

[quote=“Junkhacker, post: 30582, member: 21583”]my 7010’s have no issues at all with fog. the problem is your network[/quote]

I am not going to completely rule that out from the standpoint that there is some sort of issue with iPXE and our older cisco switches, but never had one issue on .32. If moving to iPXE is causing issues, then why would I need to change our network settings to allow FOG to work. Maybe portfast on our 10 year old switches aren’t responding the same as the newer switch OSes? So is the consensus that it is fixed now as for as FOG or is there still known issues among other users and is still being looked into?

We thought to stick another switch between the computer and the main cisco switch (wall jack) and there is now no problems. I am not sure we are going to want that as a final solution, but that does narrow it down to 7010 NIC/iPXE/Cisco combo. I assume a solution is still being worked on from the iPXE side?

I am on 1.1.1. I checked with network admin and all ports that we use are set to Portfast.

I was able to capture there error and I believe there is a another thread on it. The error is 040ee119. So far, we have only imaged a few models since upgrading. I just know as of now, the 7010 isn’t working.

After updating to 1.x, we seemed to have lost the ability to connect (no fog menu) to 7010. I have tried the latest kernel, down to 3.6.9. There is a quick error after the ipxe configuration…progress indicator but I can’t catch it in time (it looked alpha numeric). It will just continue on to the next boot device. I have also updated to the latest bios version A18. The bios is set to legacy mode out of the box. I saw on another thread that we might have to manually wipe the HDD, but not sure if this is the same issue? I hope not, because it’s like taking a step backward.

Thanks.

[quote=“madskillz23, post: 30493, member: 8206”]Yes, that will get you the official version. It depends on how you installed it, but I typically download fog to /usr/fog_NEW and I upgrade fog, then I delete the /usr/fog_OLD directory. So if you just downloaded fog to the fog user’s home directory, you should be able to just delete the old files.[/quote]

Thanks. I will follow that way of doing it.

[quote=“PomonaIT, post: 30487, member: 24658”]Aww, I see. Let me give that a try and I will update you. Thanks.[/quote]

Looks like that worked. So in the future, I can use that command with the latest version number to get the official build? Another question; What directories are the server files stored? Am ok to delete any folder starting with Fog_xxx or x.x.x under the foguser home folder? I assume these are just installation folders?

[quote=“madskillz23, post: 30486, member: 8206”]So I think you are actually ahead of the tagged 1.1.1 revision. If you install from trunk, you get the latest commit. Download the stable branches using the following code:
[CODE]svn co https://svn.code.sf.net/p/freeghost/code/tags/1.1.1 /INSTALL_DIR[/CODE][/quote]

Aww, I see. Let me give that a try and I will update you. Thanks.

I just used SVN to download from trunk and installed 1.1.1 over 1.0.1. No errors occurred and I updated DB Schema from management page. I still get the message ‘you are not running the most current version…’. I seemed to recall finding another post on this but not sure what I searched for last time. Any clues? Thanks.

Going forward, what is the easiest way to obtain the latest update and install? I am not familiar with SVN, but it appears that may be what I need to learn how to use?