Does FOG work with iSCSI?

ManofValor · May 31, 2016, 8:34 PM

@Tom-Elliott What about it not showing up under my /images folder?

Wayne Workman · Jun 1, 2016, 1:59 PM

@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.

ManofValor · Jun 1, 2016, 1:59 PM

@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.

Wayne Workman · Jun 1, 2016, 2:14 PM

@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.

ManofValor · Jun 2, 2016, 7:11 PM

@Wayne-Workman Is it possible to edit my existing node or better to just create a new one?

Wayne Workman · Jun 2, 2016, 7:15 PM

@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.

ManofValor · Jun 2, 2016, 3:56 PM

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.

Wayne Workman · Jun 2, 2016, 4:17 PM

@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_FTP

The 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 example touch /images/NAS/.mntcheck and then the other too.

ManofValor · Jun 3, 2016, 2:19 PM

@Wayne-Workman I believe these are the logs you asked for. The second on just repeats itself through today.

[Thu Jun 02 16:29:26.973189 2016] [:error] [pid 6974] [client 10.10.1.40:51570] PHP Strict Standards:  Only variables should be passed by reference in /var/www/html/fog/lib/pages/schemaupdaterpage.class.php on line 46, referer: http://10.10.1.40/fog/management/index.php?node=schema
[Thu Jun 02 18:07:52.049146 2016] [autoindex:error] [pid 6978] [client 10.10.1.21:52158] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive

I will check on those other settings. Thx.

Wayne Workman · Jun 3, 2016, 2:21 PM

@ManofValor Also you should try updating again. For issues with FOG, it’s very very likely that Tom fixed it literally a minute after you posted. Updates are pushed all day long, most days.

Tom Elliott · Jun 3, 2016, 2:37 PM

@Wayne-Workman what error in the code base?

Wayne Workman · Jun 3, 2016, 2:38 PM

@Tom-Elliott FOG Configuration page in whatever version ManofValor is running throws a “Not Found” error.

Tom Elliott · Jun 3, 2016, 2:45 PM

@Wayne-Workman It’s not anything FOG is doing.

ManofValor · Jun 3, 2016, 9:42 AM

@Wayne-Workman Just updated again but still getting same error, though it did not go to the update page. I’m on version 7979.

Tom Elliott · Jun 3, 2016, 3:42 PM

@ManofValor What error?

THe 404 static/index.html?

ManofValor · Jun 3, 2016, 3:46 PM

@Tom-Elliott yes

Tom Elliott · Jun 3, 2016, 3:48 PM

@ManofValor well, why?

WHat’s int he apache error logs?

ManofValor · Jun 3, 2016, 4:06 PM

@Tom-Elliott This is from yesterday.

[Thu Jun 02 00:06:34.470996 2016] [autoindex:error] [pid 15228] [client 10.10.1.21:2098] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 00:06:34.559253 2016] [autoindex:error] [pid 15216] [client 10.10.1.21:2099] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 02:05:42.043059 2016] [autoindex:error] [pid 11055] [client 10.10.1.21:14026] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 02:05:42.159785 2016] [autoindex:error] [pid 11039] [client 10.10.1.21:14027] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 04:06:31.915010 2016] [autoindex:error] [pid 9665] [client 10.10.1.21:24864] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 04:06:31.986869 2016] [autoindex:error] [pid 9633] [client 10.10.1.21:24865] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 06:06:48.291935 2016] [autoindex:error] [pid 31077] [client 10.10.1.21:37320] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 06:06:48.518771 2016] [autoindex:error] [pid 11106] [client 10.10.1.21:37321] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 08:07:20.646876 2016] [autoindex:error] [pid 31078] [client 10.10.1.21:49911] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 08:07:20.721677 2016] [autoindex:error] [pid 17814] [client 10.10.1.21:49912] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 10:07:17.924190 2016] [autoindex:error] [pid 15228] [client 10.10.1.21:63580] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 10:07:18.027936 2016] [autoindex:error] [pid 15216] [client 10.10.1.21:63581] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 10:25:50.815385 2016] [autoindex:error] [pid 31077] [client 10.10.1.203:8400] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 10:25:51.190080 2016] [autoindex:error] [pid 11055] [client 10.10.1.203:8422] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 12:07:29.184297 2016] [autoindex:error] [pid 9665] [client 10.10.1.21:12356] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 12:07:29.270498 2016] [autoindex:error] [pid 9633] [client 10.10.1.21:12357] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 14:07:15.235994 2016] [autoindex:error] [pid 31077] [client 10.10.1.21:25815] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 14:07:15.319521 2016] [autoindex:error] [pid 11106] [client 10.10.1.21:25816] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 16:07:09.043076 2016] [autoindex:error] [pid 31077] [client 10.10.1.21:38978] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 16:07:09.132915 2016] [autoindex:error] [pid 17814] [client 10.10.1.21:38979] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 16:19:09.451677 2016] [mpm_prefork:notice] [pid 7052] AH00170: caught SIGWINCH, shutting down gracefully
[Thu Jun 02 16:22:21.397740 2016] [suexec:notice] [pid 2082] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Thu Jun 02 16:22:21.607225 2016] [ssl:warn] [pid 2082] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using localhost.localdomain. Set the 'ServerName' directive globally to suppress this message
[Thu Jun 02 16:22:21.652838 2016] [auth_digest:notice] [pid 2082] AH01757: generating secret for digest authentication ...
[Thu Jun 02 16:22:21.654022 2016] [lbmethod_heartbeat:notice] [pid 2082] AH02282: No slotmem from mod_heartmonitor
[Thu Jun 02 16:22:21.656084 2016] [ssl:warn] [pid 2082] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
[Thu Jun 02 16:22:21.863773 2016] [mpm_prefork:notice] [pid 2082] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.6.21 configured -- resuming normal operations
[Thu Jun 02 16:22:21.863805 2016] [core:notice] [pid 2082] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Thu Jun 02 16:26:36.730982 2016] [mpm_prefork:notice] [pid 2082] AH00170: caught SIGWINCH, shutting down gracefully
[Thu Jun 02 16:27:20.812912 2016] [suexec:notice] [pid 6925] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Thu Jun 02 16:27:20.815690 2016] [ssl:warn] [pid 6925] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
AH00558: httpd: Could not reliably determine the server's fully qualified domain name, using localhost.localdomain. Set the 'ServerName' directive globally to suppress this message
[Thu Jun 02 16:27:20.861329 2016] [auth_digest:notice] [pid 6925] AH01757: generating secret for digest authentication ...
[Thu Jun 02 16:27:20.863283 2016] [lbmethod_heartbeat:notice] [pid 6925] AH02282: No slotmem from mod_heartmonitor
[Thu Jun 02 16:27:20.864984 2016] [ssl:warn] [pid 6925] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
[Thu Jun 02 16:27:20.894536 2016] [mpm_prefork:notice] [pid 6925] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.6.22 configured -- resuming normal operations
[Thu Jun 02 16:27:20.894578 2016] [core:notice] [pid 6925] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Thu Jun 02 16:27:23.065603 2016] [:error] [pid 6974] [client 10.10.1.40:51408] PHP Fatal error:  Call to a member function getDB() on integer in /var/www/html/fog/commons/init.php on line 132
[Thu Jun 02 16:29:26.973189 2016] [:error] [pid 6974] [client 10.10.1.40:51570] PHP Strict Standards:  Only variables should be passed by reference in /var/www/html/fog/lib/pages/schemaupdaterpage.class.php on line 46, referer: http://10.10.1.40/fog/management/index.php?node=schema
[Thu Jun 02 18:07:52.049146 2016] [autoindex:error] [pid 6978] [client 10.10.1.21:52158] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 18:07:52.158440 2016] [autoindex:error] [pid 7231] [client 10.10.1.21:52159] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 20:07:22.142156 2016] [autoindex:error] [pid 6977] [client 10.10.1.21:64796] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 20:07:22.341320 2016] [autoindex:error] [pid 6973] [client 10.10.1.21:64797] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 22:07:16.232293 2016] [autoindex:error] [pid 6978] [client 10.10.1.21:12812] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Thu Jun 02 22:07:16.253132 2016] [autoindex:error] [pid 7231] [client 10.10.1.21:12813] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive

Tom Elliott · Jun 3, 2016, 4:07 PM

@ManofValor Who’s been playing with your http configuration information?

Yesterday isn’t any good either, though. Is this off the NAS or off the main server? Is SELINUX enabled on this CENTOS box? What about firewalls?

ManofValor · Jun 3, 2016, 4:31 PM

@Tom-Elliott It’s off the main server. More than likely I did something. I’ve been learning how to connect my NAS to my fog server and yesterday I setup a new storage node for the NAS. So somewhere in there I’m sure I screwed something up. If I did it I don’t know what.
SELinux is disabled and the firewall:

[root@localhost httpd]# service iptables status
Redirecting to /bin/systemctl status  iptables.service
● iptables.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

Does FOG work with iSCSI?

135

12.0k

17.3k

155.2k