Posts made by Josh Scoville

We have had some issues with name changing working after imaging. One particular machine, I checked in the gui to make sure the services were set properly. I was able to check the boxes and save on the services screen, but when on the Active Directory screen for the host, after clicking save, I get an error “page cannot be displayed” page. We have had issues with the name changer and domain join working on other systems even with all services checked, so I’m just trying to figure out what’s not working, but the error page is a new one.

No firewall is running on the machines.

Sorry for taking so long to get back to replying to this forum thread. We have just reuploaded the affected images from scratch and this worked like it should now, but the only thing is that the hostname changer and domain join parts are not happening.

The AD services are checked for this host as well as the hostname changer services. The fog.log on the client system drive shows that it has trouble connecting to the server, although it is connecting to the correct IP address and we can ping the server IP fine from the client. Not quite sure what’s going on here.

[quote=“neilm, post: 37138, member: 24150”]has this been resolved? i checked all settings and can login to ftp with broswer and filezilla. but images stay in /images/dev until manually moved[/quote]

Tom Elliott’s post above fixed it for me. You have to edit /etc/vsftpd.conf and then restart the ftp services.

Yes, it has an image set. Some just reboot when selecting quick image.

When we try and quick image a registered host, the system just kicks us directly back to the main menu with no apparent error message or anything. This is after we enter the username and password, not before. We updated a few weeks back to the 2203 mid distro version while trying to fix another issue.

I have also commented out the --picture line in the bootmenu file, but this did not help. Any ideas where to look to fix this?

Thanks! If it was a snake, I’d be less one nose right now!

OK, I must be a complete blind idiot today, because I can’t find that setting anywhere on the FOG settings page. What title should I look for? Thanks a lot!

Let me know if this is an unrelated issue and needs to be on its own thread, but ever since day 1 when we upload an image using the default partclone image, it crawls along at under 500 MB transfer rate on a Gigabit network. When we deploy an older image using partimage, it flys at 2-3 GB transfer rate. Just wondering if this is something that can be adjusted as it now takes forever to upload an image. Deploying the partclone image does seem faster, just the uploads are so slow.

Ah, OK now I can login to ftp via web and see the directory tree. So should I try uploading a new image and see what happens?

I just tried going to [url]ftp://10.10.100.218[/url] which is my server’s ip address and get the following error: v500 OOPS: priv_sock_get_int
.

Tried using web browser. Sorry I am not more familiar with the fog server’s ftp setup, but usually this works when logging into an internet ftp site.

I checked my settings: Have the username fog with my password in storage management for the defaultmember management username and password. It is the same in the TFTP settings in FOG settings. I don’t see a setting for FTP, only TFTP server. My username and password are the same in all areas that I know to check.

For me, when I copied the image over manually from /images/dev/macaddress to /images/imagename, it worked for deploying the image, but this should be an automatic process.

We use this server in a production environment almost daily, so this is very important to get fixed. thanks!

Thanks for that info. Any ideas on how to fix this permanently? I have several users who use this very often, but I am the only one with linux knowledge and the CLI, so a permanent fix is most needed. Again, thanks!

Yes and apparently they are the MAC addresses to the upload machine, because one I was uploading had it’s mac address there.

I am having an issue when we create and upload an image, the image seems to upload fine, but when we deploy it, we get the error “cannor find image store”. I see the image is in the folder named by the upload machine’s mac address in /images/dev, but my storage node is set to /images. Tom Elliot had me upgrade Fog to sub version 2203, but this hasn’t helped. I have ran chown -R fog /images and also set read/write/execute permissions on this folder and all sub folders just to make sure that wasn’t it.

We are running Fog on Ubuntu 13.10. We really depend on FOG to deploy images for our school system computers and right now we cannot deploy any new images. This was a new install on a vm, but we migrated images from our old 0.32 box.

Yes, I did comment out the --picture line and that got me working for this issue. Thanks for the explanation. That makes sense.

OK, I reuploaded the image from the client. The files are still showing in /images/dev/mac-address and nothing new has been added to /images. In other words, no LatitudeE5510 folder has been created. Any ideas?

Web UI says I am running version 2203. Is this correct?

OK, the script is done and I am logged back in now. Should I test an upload?

What should I see in the file system as concerning the /images and /images/dev folders?

Thank you!