@Wayne-Workman Oh ok. Cool.

Posts made by ManofValor
-
RE: Does FOG work with iSCSI?
@Tom-Elliott Oh is that what that means…lol. Thanks, I really didn’t know that.
-
RE: Does FOG work with iSCSI?
@Tom-Elliott Thank you Tom. I’ve done some of the stuff in the links, I am connected to my NAS, but this is the first I’ve seen of some of this. I guess I need to learn how to search better. As I said I am connected I just haven’t been sure if it was working yet, mostly because this NAS doesn’t support CLI or the ability to go in and see what’s on the drives. I’ve never seen a storage unit that doesn’t let you see what’s on it.
I agree about it taking a long time but I don’t think either of us, my boss and I, expected it to take this long either. It doesn’t bother him though because he it’s a good learning experience. In the beginning he wanted to use FOG because it was free and he’s heard good things about it. Also, we have this old NAS, that I now hate, that he is wanting to utilize, but again we didn’t think it would take this long. I have enjoyed learning about Linux, mostly, so I guess there’s that. I really appreciate you guys helping me, I know I ask a lot of dumb questions. With this experience I’ve been to other sites and asked for help with other stuff and there is nobody else I’d rather learn this stuff, even FOG aside, than you guys. Y’all have been awesome.
-
RE: Does FOG work with iSCSI?
@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?
-
RE: Does FOG work with iSCSI?
@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.
-
RE: Does FOG work with iSCSI?
@Wayne-Workman Ok, thanks. Let you know how it goes.
-
RE: Does FOG work with iSCSI?
@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_FTPSo, 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.
-
RE: Does FOG work with iSCSI?
@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.
-
RE: Does FOG work with iSCSI?
@Tom-Elliott said in Does FOG work with iSCSI?:
systemctl stop firewalld
Done. I wonder why that started?
-
RE: Does FOG work with iSCSI?
@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.
-
RE: Does FOG work with iSCSI?
[root@localhost httpd]# systemctl status -l firewall ● firewall.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
-
RE: Does FOG work with iSCSI?
@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)
-
RE: Does FOG work with iSCSI?
@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
-
RE: Does FOG work with iSCSI?
@Wayne-Workman Just updated again but still getting same error, though it did not go to the update page. I’m on version 7979.
-
RE: Does FOG work with iSCSI?
@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.
-
RE: Does FOG work with iSCSI?
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. -
RE: Does FOG work with iSCSI?
@Wayne-Workman Is it possible to edit my existing node or better to just create a new one?