Error Installing Fog - FOG Multicast Management Server Failed
-
Also, ensure selinux is disabled. You van also make sure iptables is off. When you disable selinux you’ll have to reboot the server, then try finishing the install.
-
Again, I’ll give more info when I get home.
-
Okay, great. I know that iptables and selinux are already disabled. Everything is being done as root. I tried again after editing the config.php file correctly and got same error. Thanks for your help by the way… editing the /etc/my.cnf file as root to allow me bind to be attached to my fog servers IP address rather than 127.0.0.1 is where I’m a bit lost. I will wait til you are home to explain. THANKS!
-
my.cnf is what MySQL uses to establish connections on the system. However, you’re right now stuck just trying to get FOG installed. What version are you attempting to install? FOG 0.32 or FOG 0.33?
I’ve never had problems install either on centos 6.4 but I’ll build a VM and install whichever version you’re trying to install just to try replicating your results. I’ll even follow the guide you’re following. Then I can be of more assistance, so it will be a couple of minutes while CentOS 6.4 installs as I just use netinstall.iso for doing this. Once we get a successful install on your side, we can work on the nitty gritty parts with /etc/my.cnf, selinux, iptables, etc…
-
This post is deleted! -
I am using FOG 0.32
-
I figured as I opened the wiki. I’m doing the first parts right now. I hope you don’t mind a slight delay.
-
Alright,
I’m about to start the install. I’ve disabled selinux and turned off iptables, just awaiting reboot so I can get fog installed.
I know this sounds weird, but I hope I get the exact problem you’re seeing.
-
Real quick question, when you’re doing the setup part (the choices you make) can you tell me the selections you’re making besides the entering of your IP information as mine is probably different.
Thank you,
-
Choosing option 1 for Redhat
Normal mode
Everything else is defaults except choosing to make FOG dchp server which is no. We are integrating our own network with fog -
That’s exactly what I did, it’s installing right now, will just be a few more minutes.
-
Alright,
Bad-news,
Multicast management server started up just fine on my install.
-
How familiar are you with log files within linux?
-
Did you make sure to update your sources/OS before installing FOG? On ubuntu, that’s apt-get update following by an apt-get upgrade.
This makes sure you have the latest info on the packages. This can solve many a tricky install problem.
-
She’s running centos 6.4, so:
[CODE]yum -y update[/CODE]
Would work much better (and yes I totally just learned how to use bb code element
) -
I’m starting to lean more towards this being a package issue.
Are you sure you’re system is updated to it’s fullest extent?
Also,
After you’ve performed an install, can you give the last 20 lines of the file:
/var/log/httpd/error_log
This may be telling us your exact issue which would be extremely helpful as FOGMulticastManager is a PHP file, so error’s should be written there.
-
You can open another terminal using ALT+F2, and do a [CODE]tail -f /var/log/syslog[/CODE] as you do the install.
Toggle between the screens using ALT+F1 for the installer and ALT+F2 for the log.
This might help us find what is happening.
The syslog may be in a different location for CentOS. I’m kind of spoiled to Ubuntu.
-
CentOS is:
[CODE]tail -f /var/log/messages[/CODE]
-
Everything is updated, i made sure to run the updates through yum at least three times today before starting the FOG installation. One thing I probably should mention is that i have another NIC on this VM which is disabled for now. This shouldnt interfere should it? Our plan is to run this on every vlan on our network, which will require multiples NICs.
As far as log files, no its been a while since I have used linux. I used to know bash shell really well bc of previous programming experience. Just been a while since ive utilized it. I will get you those lines as soon as I can.
-
Alright,
Is the nic you have available setup for bridged or NAT network?
If it’s NAT, that’s probably why you’re having an issue, outside traffic is allowed, but incoming traffic is not. Even if this isn’t the direct cause of the issue, it will cause issues down the road. When I setup my VM (I already deleted it) I had it set to NAT, and although everything installed fine on mine, I use virtualbox rather than VMWare, so it may be slightly different configurations in that regard. I’d try making sure your VM is using a bridged adapter versus the VM NAT network system.
