Posts made by cmcleod

@tom-elliott Hi Tom,

As my previous message stated, would you know what may cause the configuration page at: http://192.168.142.72/fog/management/index.php?node=about redirect to:
http://192.168.142.172/static/index.html

This happens every time and I can’t get into the configuration.

If you need further info, let me know. I appreciate all of your help.

Charlie

@Wayne-Workman @tom-elliott Here is an update:

The upgrade installations for trunk are now working. Maybe it was related to sourceforge being down?

Anyways, the remaining issue is when I click on the configuration page. If I hover my mouse over the configuration link, it shows the link:
http://192.168.142.72/fog/management/index.php?node=about

If I click on that link, it takes me there for a brief second and then it goes to:
http://192.168.142.72/static/index.html
That page is even outside of the fog site. I’ve looked at the php file. I’ve tried backing up and reinstalling to put the fog pages back in place. None of that seems to fix the issue.

I really need to get to the configuration site to make changes and I can’t do anything right now. Any help would be greatly appreciated.

Thanks!

Charlie

@Wayne-Workman I’m running CentOS 6.6. I ran yum update and then rebooted the system. There were only a few minor updates.

I then went to ~/trunk/bin/ and re-ran ./installfog.sh

Updating packages as needed still hung up at “Updating Packages as needed”. I had to ctrl+c to cancel and then the rest of the install went fine.

The configuration page is still not loading with the same error.

Thanks for your response @tom-elliott

1 - the webroot should be http://192.168.142.72/fog
All of the other pages seem to load fine except for the configuration page.

2 - I have not edited any files with regards to the installer.

3 - I’ve had FTP issues in the past and had them resolved. However, I can’t get to the configuration page to confirm the username and password entered for FTP.

Thanks for your help.

Charlie

When updating to the newest beta release of fog, some issues have come up that I haven’t been able to resolve.

1 - The configuration page within Fog no longer loads. It loads for a blink of an eye and then it redirects to: http://192.168.142.72/static/index.html
with the error: Not Found. The requested URL /static/index.html was not found on this server.

2 - When installing updates for the trunk release, it now is hanging up at “Updating Packages as needed.” I have let it sit on that screen for over 12 hours. If you press Ctrl+C it bypasses it and continues the installation/upgrade.

3 - When pushing a new image out to the server, it created the image in the /images/dev/0800272e575e folder. However, the image was not copied down to the /images/(new_image) folder. A Folder was never created. I had to create the folder and copy those files to it. Fog console then recognized the image and was able to push it out for deployment. Any ideas?

Any help with these issues would be greatly appreciated.

Thanks!

Charlie

@cml

That did it! DefaultMember storage node was not set to Master.

It immediately loaded up the page for creating a new image.

Thanks!!

@cml @Wayne-Workman
the Apache error log is listing this error several times:
PHP Fatal error: Call to a member function get () on boolean in /var/www/html/fog/lib/pages/ImageManagementPage.class.php on line 178, referer: http://192.168.142.72/fog/management/index.php?node=image&sub=add

I tried re-installing and that didn’t work

I tried restarting the server after upgrading.

I also tried restarting the FOG services and httpd.

I just refreshed and now I’m getting a HTTP 500: “The website cannot display the page”
Is it a permissions issues somewhere perhaps? or is there a file missing?

I upgraded to build 3570.

I was trying to add an image to the fog server. I click Add image and the page loads with just “Add New Image definition” headline across the top and that’s it.
Sometimes, it loads with an error “page cannot be found”.

I can list and search for images. I just can’t add any.

It appears to support it. I ran the command size but that appears to only work for file sizes. I ran the command:
size /mnt/array1/images/Win7Master/d1p1.img and it returned a response
213 8553337

So, here is how I resolved this issue.

First, on the Terastation, NFS was setup incorrectly. It was running in User Mode and it needed to be running in Kernel Mode. After this was set, we could then go back into the Fog server and removed the Terastation node. We changed the settings for the DefaultMember to point to the Terastation. After doing this, we were still receiving FTP errors. However, we could see the mount point and the files within.

We fixed the FTP issues by going to Fog Configuration, Fog Settings, TFTP server and changing the Fog account password. Also, the Terastation was joined to our Windows domain. After some research, we found out that if it is joined to the domain, FTP will not work. After unjoining from the domain, FTP started working immediately.

The only issue, and this may not be able to be solved, is that when we go to the Home page of Fog and look at the Disk Information, it just reports “No error, but no data was return.”
If you run df -h in the terminal, you can see the data returned for the total space and free space available. Is there a way to have this show up for the NFS mount in Fog?

Thanks so much for your help!

@cspence

I tried deleting fog from the forum instructions and I deleted the fog user. I re-installed following the same specifications I listed earlier and I’m still receiving the same error message.

Update - When I went back into Image Management after it failed, there was an error:
FOGFTP: Login failed. Host: 192.168.142.72, Username: fog, Password: (my password), Error: ftp_login(): Login incorrrect.

Ok, I’ll go back to my original NFS configuration and maybe I’m doing something wrong and you guys will be able to pick up on it.

On the Terastation - I have enabled NFS. I assigned the fog server as a client on nfs via it’s IP address. I’ve created a fog user with it’s UID set to match the UID of the fog user on the fog server - 1001. The NFS mount point on the terastation is //mnt/array1/images

First, I logged into fog and tried to mount the storage server through NFS.
Name: Terastation
IP: 192.168.142.176
Max clients:10
Storage Group: default
Image path: /mnt/array1/images – path specified on the NAS
Interface: eth0
Username: fog user and same password as on the NAS
I add it and then I go to the home screen. I click under Disk info to change to Terastation. The response: No error, but no data was return. So, my guess is that means it didn’t work.

On the fog server, I ran the following commands:

1. mkdir /mnt/nfs/images
2. mount 192.168.142.176:/mnt/array1/images /mnt/nfs/images
3. mount - shows that it was mounted successfully. However, there is no rw after the mount. Does that mean it is not read/write?
4. vi /etc/fstab
5. line added:
   192.168.142.176:/mnt/array1/images /mnt/nfs/images nfs auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0
6. mkdir /mnt/nfs/images/dev
7. touch /mnt/nfs/images/.mntcheck
8. touch /mnt/nfs/images/dev/.mntcheck
9. reboot now
10. confirm the mount point was successful - output of the mount command is:
    192.168.142.176:/mnt/array1/images on /mnt/nfs/images type nfs (rw,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800,addr=192.168.142.176)
11. ls -alh /mnt/nfs/images - the .mntcheck file is there with the following permissions:
    -rwxrw-rw- fog:52
    /dev - drwxrwxrwx fog:52
    /images/dev/.mntcheck - same permissions as the other file
    **so I’m not sure if those permissions are correct or not
12. I login to fog. I go back to the Terastation storage I created earlier. This time I create a storage group called Terastation and change the storage node for terastation’s IP to the fog server. I change the Image path to: /mnt/nfs/images
13. I go back to the Home screen and change to terastation and I can now see the space available on the Terastation.
14. I go to Images and create an image:
    Name: Win7-64-Pre-Sysprep
    Storage Group: terastation
    OS: Windows 7
    Image Path: /images/Win764PreSysprep
    Image Type: Multiple Partition Image - all Disks (Not Resizable)
    I click Add
15. I boot up and register a host computer.
16. I go to the hosts in fog and choose to upload for the computer to upload an image to fog.
    I reboot the host and I get this error:
    mounting 192.168.142.72:/mnt/nfs/images/dev on /images failed: Permission denied.
    An error has been detected!
    Fatal Error: Failed to mount NFS Volume
    Computer will reboot in 1 minute.

Any ideas? Thanks so much for your help.

SSH does work… However, every user I have created can’t login. They didn’t provide the credentials for the root account.

No, the Buffalo Terastation supports NFS. However, you can’t change the owner of the /images folder or change settings at all for fog to access it. I’ve changed the UID for CentOS and for the terastation on the fog user. I still can’t access it.

I’ve researched it and others say they are having the same problem with this device. I saw recommendations to set the mount point within the /images folder for SMB and that will work. However, I’ve tried everything and it’s not working. The space updates within FOG for available space but I receive the error in my original post when trying to image to it.

My goal is just to be able to use my NAS device as external storage.

@ch3i
Initially I tried the NFS route with the Terastation. When I added it to the Storage Group as a second node, fog just showed an error on the Home page for that storage device.

I then mounted the NFS share within CentOS and pointed fog to the local mount point. Fog saw the additional storage with no problem. However, when I tried to upload the image, I received the same error I stated in my original post that I was receiving now with CIFS.

I’ve search the forums and can’t find any article that list specific steps for creating a SMB share and mounting it.

I tried using NFS. However, our external storage is a Buffalo Terastation. From the forums, I found out that NFS doesn’t work with this device. I read suggestions for setting up SMB connection to the external storage. However, there are not a lot of specific articles that say how.

I’m also running CentOS 6.5 with Fog version 1.2.0 on a Proxmox VM.

Here is what I have pieced together so far.

Prior to installing FOG, do this:

1. I setup a share on the Terastation called images. I assigned no file restrictions to it.
2. I created a password file called secret.txt in /root. I put in it:
   username=fog
   password=(my local fog user in linux password)
3. mkdir /images
4. sudo chmod -R 777 images
5. chown -R fog.root /images
6. vi /etc/fstab
   I added the following line:
   //x.x.x.x/images /images cifs credentials=/root/secret.txt,noperm,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
7. I installed fog
8. The home screen shows the full storage of my remote storage device.
9. I create an image in Image configuration
10. I registered a host computer
11. I assigned the image for upload
12. I booted up the host and I receive the following error message:
    mounting x.x.x.x:/images/dev on /images failed: permission denied
    Checking Mounted File System
    An error has been detected.
    Fatal error: Failed to mount NFS Volume
    Computer will reboot in 1 minute.

If I open the share in Windows explorer and attempt and on CentOS - I can see the directory structure. If I create a folder or file, I can see those folders and files appear in the Windows share. So, I believe I have the file permissions correct.

I also saw an article that you needed to create the .mntcheck file. I see this file in the dev directory already with 777 access for everyone. I read somewhere else that this file needs to exist in the /images directory as well. So, I copied the file from /images/dev to /images

So, why is Fog not able to connect and create the image?

Any help would be greatly appreciated!