Does FOG work with iSCSI?
-
@Wayne-Workman said in Does FOG work with iSCSI?:
@ManofValor I managed a Tera station at my last job. They certainly support more than just iSCSI.
Actually, I called Buffalo tech and they said that particular NAS is iSCSI only.
-
@ManofValor Ok then, progress. We have to use iSCSI then. Calling them was good - that’s part of digging into this.
-
-
So now I have iSCSI enabled and connected to FOG/NAS device and should all be ready to go. I ran another image to see if it is working. Do ya’ll know if there’s something else I need to do to push it through or is it supposed to start backing up automatically? I haven’t seen anywhere yet that I need to but maybe ya’ll know something I don’t.
-
I don’t know if I follow?
-
@Tom-Elliott Basically, I’m not sure what to look for to know if the images are being sent to the NAS device. I’ve never used one so I’m not sure if there’s a delay before it starts, or if I have everything in order, or what? Is there something I have to do to push it to the NAS every time I image or Is it automatic, if I did it right? I’ve done everything I can find on this and it seemed pretty simple after figuring it all out so not sure if I’m missing anything.
-
Can anyone help me with my last question?
-
@ManofValor Is this your main storage node? Do images upload/replicate to it? Also - if properly setup everything will be automatic.
-
@ManofValor NAS = Network Attached Storage, in simple terms means a storage device (you know storage could be disk, USB key, SD card, CD, …) that is connected over network - compared to all the others being connected on an internal system bus. The data being written to any of those devices (be it the normal ones or NAS) should end up on the device without any extra “push” or something. But maybe I got your question wrong?!?
-
Where is the iSCSI device located on the FOG server? What does your Storage Node setup look like?
-
[root@localhost /]# cd /opt/fog/images [root@localhost images]# ls dev MCWP77 MCWP82 MCWPL54 postdownloadscripts
I did another image,MCWPL25, after connecting to the NAS, via iSCSI, and it is not showing up with the others. Either it worked and is on the NAS or something else happened. I also noticed this under image management:
One thing I am trying to figure out though is how to check the NAS. The interface I have doesn’t show me what’s on the disk’s. Just the size of the disk’s. I’m still learning how to use it but haven’t got much time on it. This is what I’m working on now.
-
@ManofValor No Data, under that field, just means the last known date to when that image was uploaded is not available (there’s no data to show).
-
@Tom-Elliott What about it not showing up under my /images folder?
-
@ManofValor What happens when you try to upload to that node? Screenshots please. Or are you just trying to replicate to it? If replicating, we need the replication log. It’s in the log viewer.
-
@Wayne-Workman When I ran an image for that one it worked as normal, I didn’t see anything different. It even shows up in fog management. Do you need me to do again? Here is the replicator log file if it helps. The one I’m looking for is not there, MCWPL25.
Did I need to create another storage node for the NAS. I could have swore in the process I was just pointing it the /images dir, but I could have misunderstood.
-
@ManofValor Yes, everything in fog must be defined in one place or another in the DB, which means creating it in the Web Interface. You must create a storage node definition for the NAS.
-
@Wayne-Workman Is it possible to edit my existing node or better to just create a new one?
-
@ManofValor said in Does FOG work with iSCSI?:
@Wayne-Workman Is it possible to edit my existing node or better to just create a new one?
I don’t know how you have it setup. Anything you delete in the web gui, you can remake. You’re using a iSCSI which is not locally on your fog server. This means you’d create a new node. If that’s all you will be using, this can be your only node.
It’s pretty simple. You create a new node, type in the image path, FTP images path, the IP address, and FTP credentials, set a storage group, enable it… We have probably over 100 threads about this in the forums, there are articles on it in the wiki too.
You do not have to wait to be told what to do, please feel free to try different things very, very rapidly. You can’t break anything that can’t be fixed too.
-
So I went in to FOG management and created a new storage node for my NAS.
Once I did that I ran yum update -y, git pull, rebooted, and then ran ./installfog.sh. At the end of the install I got this:######################################################################################## FOG has adjusted to using a login system to protect what can/cannot be downloaded We have detected that you don't have credentials defined to perform the backup If you would like the database to be backed up during install please define in your /opt/fog/.fogsettings file fogguiuser='usernameOfFOGGUI' fogguipass='passwordOfFOGGUIUser' You can also re-run this installer as: fogguiuser='usernameOfFOGGUI' fogguipass='passwordOfFOGGUIUser' ./installfog.sh -y ######################################################################################## * You still need to install/update your database schema. * This can be done by opening a web browser and going to: http://10.10.1.40/fog/management * Press [Enter] key when database is updated/installed.
Also When I click on the FOG Configuration button (the little wrench) in FOG management, I get this:
I also created a NAS directory (/opt/fog/images/NAS/) for the new storage node.
What is going on?
Thanks. -
@ManofValor The interface you’ve set is not correct. On the tera-station, get into CLI and issue
ip addr show
and read the right interface with that IP. More details on the interface are here: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTPThe bad request when going to FOG Configuration is likely a php syntax error in the code base, which I am sure will be fixed soon - but we need the apache errors.
In Fedora/CentOS/RHEL they are here:
/var/log/httpd/error_log
and in debian/ubuntu I think they are here:/var/log/apache2/error_log
The error should generate right after trying to access that page. Please copy/paste the relevant errors. They will have timestamps to help. Going to ping @Tom-Elliott about this one.The message from the installer is something added last week, a security measure to further protect the DB. If you do what the instructions say, you won’t see it anymore and the DB will backup automatically when you run the installer from that point onward.
And I don’t think it was necessary to make a
/opt/fog/images/NAS
on the server. Also, I’m wondering about your image path you have set. You can use that above FTP article to test FTP to the NAS and verify that path to be sure it’s correct. Also, if that’s what you’re going with, make sure you have/images/NAS/.mntcheck
and/images/NAS/dev/.mntcheck
present. You can use the touch command to make these, for exampletouch /images/NAS/.mntcheck
and then the other too.