Does FOG work with iSCSI?

[Tom Elliott]

@ManofValor you didn’t do the commands as I typed them.

[ManofValor]

@Tom-Elliott ops, sorry bout that.

[root@localhost httpd]# systemctl status -l firewalld
● firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2016-06-02 16:22:09 CDT; 19h ago
 Main PID: 751 (firewalld)
   CGroup: /system.slice/firewalld.service
           └─751 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

Jun 02 16:22:08 localhost.localdomain systemd[1]: Starting firewalld - dynamic firewall daemon...
Jun 02 16:22:09 localhost.localdomain systemd[1]: Started firewalld - dynamic firewall daemon.

[Tom Elliott]

@ManofValor Well look at that. firewalld is still running. Also, what’s output of sestatus

[Tom Elliott]

To stop firewalld and see if things are any better:

systemctl stop firewalld

[ManofValor]

@Tom-Elliott

SELinux status:                 disabled

[ManofValor]

@Tom-Elliott said in Does FOG work with iSCSI?:

systemctl stop firewalld

Done. I wonder why that started?

[Tom Elliott]

@ManofValor Well, I don’t know.

It’s on be default with CentOS 7 install though.

To keep it from starting on reboot’s you can do: systemctl disable firewalld

[ManofValor]

@Tom-Elliott Cool.

[Tom Elliott]

@ManofValor Does this mean things are working?

[ManofValor]

@Tom-Elliott Sorry, no I got busy. I updated and am still getting the same error.

[Fri Jun 03 13:18:02.945120 2016] [mpm_prefork:notice] [pid 26225] AH00170: caught SIGWINCH, shutting down gracefully
[Fri Jun 03 13:19:34.014463 2016] [suexec:notice] [pid 1471] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jun 03 13:19:34.188721 2016] [ssl:warn] [pid 1471] 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
[Fri Jun 03 13:19:34.225594 2016] [auth_digest:notice] [pid 1471] AH01757: generating secret for digest authentication ...
[Fri Jun 03 13:19:34.226353 2016] [lbmethod_heartbeat:notice] [pid 1471] AH02282: No slotmem from mod_heartmonitor
[Fri Jun 03 13:19:34.227682 2016] [ssl:warn] [pid 1471] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
[Fri Jun 03 13:19:34.487960 2016] [mpm_prefork:notice] [pid 1471] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.6.22 configured -- resuming normal operations
[Fri Jun 03 13:19:34.487991 2016] [core:notice] [pid 1471] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Fri Jun 03 13:23:28.971718 2016] [mpm_prefork:notice] [pid 1471] AH00170: caught SIGWINCH, shutting down gracefully
[Fri Jun 03 13:24:15.348962 2016] [suexec:notice] [pid 6631] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Jun 03 13:24:15.351264 2016] [ssl:warn] [pid 6631] 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
[Fri Jun 03 13:24:15.393201 2016] [auth_digest:notice] [pid 6631] AH01757: generating secret for digest authentication ...
[Fri Jun 03 13:24:15.394852 2016] [lbmethod_heartbeat:notice] [pid 6631] AH02282: No slotmem from mod_heartmonitor
[Fri Jun 03 13:24:15.396369 2016] [ssl:warn] [pid 6631] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)
[Fri Jun 03 13:24:15.421332 2016] [mpm_prefork:notice] [pid 6631] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips PHP/5.6.22 configured -- resuming normal operations
[Fri Jun 03 13:24:15.421366 2016] [core:notice] [pid 6631] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Fri Jun 03 14:07:31.884310 2016] [autoindex:error] [pid 7430] [client 10.10.1.21:51157] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Fri Jun 03 14:07:32.009813 2016] [autoindex:error] [pid 6687] [client 10.10.1.21:51162] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Fri Jun 03 16:08:23.958816 2016] [autoindex:error] [pid 6689] [client 10.10.1.21:1278] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive
[Fri Jun 03 16:08:24.258954 2016] [autoindex:error] [pid 7496] [client 10.10.1.21:1279] AH01276: Cannot serve directory /var/www/html/: No matching DirectoryIndex (index.html,index.php) found, and server-generated directory index forbidden by Options directive

Last three hours.

[ManofValor]

@Wayne-Workman said in Does FOG work with iSCSI?:

@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

So, there is no way that I can find, including talking with Buffalo Tech, to access the CLI. They said there might be something on the web on how to enable SSH but can’t find anything on that either.

[Wayne Workman]

@ManofValor The interface name isn’t so important I guess. You could guess at it by just putting in eth0 which is a typical default name, but it could very well be something else. I did some Googling and couldn’t find any CLI stuff for the Terastation either. Best to not spend a lot of time on it I guess.

The important thing is to ensure the FTP credentials you have set in Storage Management for the storage node are correct, by trying them manually AND transferring a file to the terastation. That’ll be the proving point. There are examples of this in the wiki, in the “Troubleshoot FTP” article.

[ManofValor]

@Wayne-Workman Ok, thanks. Let you know how it goes.

[ManofValor]

@ManofValor I get the feeling that this particular NAS is not going to work. I can’t get into CLI and, I’m probably doing something wrong but, I can’t get FTP to work on the NAS side,it works on the windows and CentOS side. The firewall is disabled and vsftpd is enabled and active. Can you think of anything? I’m beginning to think that this NAS was not made for this. Any thoughts?

P.S. Still getting the error when trying to go to FOG Configuration.

[Wayne Workman]

@ManofValor If the NAS supports FTP and NFS, of course it can work. Those are the only two requirements for a storage node.

Have you created a user account for FTP access? Have you set a password for it? Have you given that account access to a directory? Have you shared that directory via NFS?

What do you mean FTP works on the windows and CentOS side? You should be testing FTP access to the NAS.

[ManofValor]

@Wayne-Workman I was talking with Buffalo tech and it does not support FTP and NFS. It is iSCSI only. I mentioned it before but I wasn’t thinking when we started talking FTP. This is why I’ve been trying to connect it iSCSI. I’ve got it connected I just figure out if I’ve got it right seeing that I can’t access CLI or, like most storage devices, even see what’s on the drives. Thoughts?

[Tom Elliott]

@ManofValor iSCSI means creating a target and establishing a mount using that target. I forget the terms please forgive me.

YOu will be using the FOG system to do the work, you just need to fstab the iscsi mount point on boot.

My guess, currently /images is not using anything correct?
https://help.ubuntu.com/lts/serverguide/iscsi-initiator.html
http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html

A couple links to hopefully help you along the way.

The interesting thing here is all this effort toward something you (or anybody really) are even sure will work. With all this time you have been using to try to get something working (and not succeeding) when this could’ve just been all done a LONG timeago by setting up a proper drive or giving the OS more space to begin with.

[Wayne Workman]

@Tom-Elliott And even if it can be mounted and read/writable in Linux, that doesn’t mean it can be re-exported. That part will likely fail.

[Tom Elliott]

@Wayne-Workman iSCSI shows up as if it’s a physical volume. iSCSI is block level so you can export it.

[Wayne Workman]

@Tom-Elliott Ah… See that’s why I hang around here lol. Learn new stuff all the time.