Posts made by Dan Dillard

I am getting this when selecting “Full Host Registration” form the boot menu. No reason is given. Also, I’d like to add that it is intermittent. If I persist and try another time or two it will let me register.

On imaging tasks quite often I am also getting a blinking cursor in the bottom left-hand corner of the screen at the moment before it would usually start PartClone. This cursor will stay there blinking indefinitely.

I have done some searches on this forum and haven’t been able to find a solution. I am willing to jump in, provide logs, and hopefully get this figured out. I hope someone out there can help me!

Just let me know what other information is needed, please.

I haven’t tested on 32 bit clients (we only have a few), but I am having an issue with this as well.

Have tried restarting FOG Service to prompt them to reach out and make a connection to the server, in the past this had worked.

I am running build 2098

Just wanted to know if this was a known issue, or if it is something more specific with our setup.

Thanks

Would it be possible to create a symbolic link from the standard location “/images” to the alternate location that you are using?

Or, it might be possible to set the mount point as “/images” for the alternate volume/location.

Can’t be for certain, but I think I might have ran into a similar (or the same) issue last week. We had our domain information disappear. One of my coworkers also noticed the autofill issue when using Chrome.

We also had another possibly related issue where settings were lost from the “Fog Settings” page. Not only the AD credentials but also things like the “web root” setting. If it happens again I will send any relevant info you might need. Friday of last week I had to get started on a group of 360 netbooks so didn’t have time to troubleshoot. I just reinstalled OS and everything.

Some new info on this, we found out that it doesn’t seem to have anything to do with the server itself.

When the deployment slows down and seemingly grinds to a halt on the client, the server has finished all disk and network activities. Monitoring the disk read rate and the network transfer rate from the terminal confirms this.

The only thing I could think of was that on a single image deployment the image is decompressed after it is transferred on the client itself. Does this sound right? Any way to confirm?

Anybody have any other ideas regarding this? Bump

I haven’t done system/package updates in about a month, normally it is an every two month or so thing.

We do have two new models of laptops (HP ProBook 6565b & 6570b) that have come along since a year ago but strangely enough those are the two that have the least issues. We used to just switch the kernel (or define it in host info) when we had issues and usually we could find a kernel that would work with problematic models, this however seems different. When it would be a kernel issue we would either see the “snow screen” or just really slow transfer speeds but they would be consistent. This new issue seems to be random aside from the fact that there are a few models that it happens less of the time on.

I have rebooted the server a couple of times in the past few weeks.

I am having a rather weird issue. I have a problem where my clients either freeze while imaging or the transfer speed becomes very slow at around 80%. The displayed speed on the screen is still usually around 2GiB/min, however this is not the actual speed as the transfer has slowed significantly. I will be imaging a computer that starts out saying it will take 8 min to image and once it gets to about 2 min remaining it will take about 14 minutes to complete. This means 20 minute imaging times if it doesn’t freeze during that time.

For those computers that do freeze, strange as it may sound, they will work if I put them in a group by themselves and send a multicast to the single computer. The only reason I could think that this works is that it is using different network protocols/methods to send the image.

When I first setup the server (August 2012) I was able to consistently image computers (Windows 7/20-25GB) in 4-5 minutes. I was wondering whether there is any general maintenance I should be performing on the server?

There are roughly 2000 computers registered in the database, I have it backed up and was about ready to do a rebuild of the server but I wanted to exhaust some other options first.

Anybody have a clue what is going on? Need me to post some logs? Hope someone can help!

Hello,

I am glad someone is working on and keeping an updated kernel!!

I know what to do with the bzimage, but am not entirely sure what to do with your .config file. Does it need to be put into the bzImage file?

That might be a good plan, I would really appreciate it, when would be a good time? (I am on Central Daylight Time) [url]http://en.wikipedia.org/wiki/Central_Daylight_Time[/url]

Oh yeah, I think I have memorized large chunks of the wiki, LOL (oops, didn’t realize that was in your signature, did find the donate link though ;))

I had another storage node up and running after I followed the advice in this thread along with a few others (MySQL IP binding, etc). It had a software RAID though which kept becoming degraded so I decided to go with a different box that wouldn’t need a software RAID.

The first one I had running I was using Linux Mint 13, now I have switched to using Ubuntu Server. The fact that it uses tftp instead of FTP might be helpful as I wasn’t aware of that.

Since this is a login issue, are there other places (configuration files) that contain the username and password? Also, is there a file similar the the “ftpusers” file for tftp protocol? Or should I just try to start from scratch again?

I am in somewhat the same pickle as the poster above. I am receiving the “530 Login Incorrect”

I have checked the password in the config.php, .fogsettings, and also made sure that the user account “fog” on the storage node has the same password. Also that it has permissions on the /images/ folder, although I am not getting a permission error (yet).

This is the fogreplicator.log from my fog server:

[CODE][07-25-12 3:31:24 pm] * [07-25-12 3:31:24 pm] Starting service loop.
[07-25-12 3:31:24 pm] * [07-25-12 3:31:24 pm] Checking if I am the group manager.
[07-25-12 3:31:24 pm] * [07-25-12 3:31:24 pm] I am the group manager.
[07-25-12 3:31:24 pm] * [07-25-12 3:31:24 pm] Starting Image replication.
[07-25-12 3:31:24 pm] * [07-25-12 3:31:24 pm] Determining my group ID number.
[07-25-12 3:31:24 pm] * [07-25-12 3:31:24 pm] Looking up my node ID number
[07-25-12 3:31:24 pm] * [07-25-12 3:31:24 pm] NODE ID# 1
[07-25-12 3:31:24 pm] * [07-25-12 3:31:24 pm] We are group ID: #1
[07-25-12 3:31:24 pm] * [07-25-12 3:31:24 pm] Finding group members.
[07-25-12 3:31:24 pm] * [07-25-12 3:31:24 pm] Found: 1 other member(s).
[07-25-12 3:31:24 pm]
[07-25-12 3:31:24 pm] * [07-25-12 3:31:24 pm] Getting my image root.
[07-25-12 3:31:24 pm] * [07-25-12 3:31:24 pm] My Root: /images
[07-25-12 3:31:24 pm]
[07-25-12 3:31:24 pm] * [07-25-12 3:31:24 pm] Starting Sync.
[07-25-12 3:31:24 pm] * [07-25-12 3:31:24 pm] Syncing: fogstorage1
[07-25-12 3:32:00 pm] * [07-25-12 3:32:00 pm] SubProcess -> mirror: Login failed: 530 Login incorrect.

[07-25-12 3:32:00 pm] * [07-25-12 3:32:00 pm] SubProcess ->
[07-25-12 3:32:00 pm] * [07-25-12 3:32:00 pm] SubProcess -> Complete[/CODE]

I am having this issue, however I don’t believe that it in the location or a permissions issue. It is a Storage Node that is reporting this error, and that Storage Node also gives a message about its RAID being degraded at boot.

Can this message (NFS Mount/Bad File Descriptor) be caused by the degraded RAID?

If I choose to start the degraded raid it mounts fine and I can browse the contents.

Edit: I have since fixed the issue, but not figured out what caused it. We just ended up backup up and starting from scratch, which has definitely had its benefits, we are seeing much better speeds now!