Invalid FOG/MySQL Password Character: ";"

christopherJames

Well that could be a problem, that file doesn’t exist. Got a copy?

Wayne Workman

@christopherJames Files in linux that begin with a . are hidden. Open up terminal, and issue ls -la /opt/fog and you’ll see it. Additionally, via CLI you can issue vi /opt/fog/.fogsettings to edit the file with a text-based editor. Here’s basic instructions on Vi: https://wiki.fogproject.org/wiki/index.php?title=Vi

christopherJames

@Wayne-Workman

Thanks, I guess it’s obvious I lack some fundamentals when it comes to administering Linux, eh? Thank you for educating me, I’ve read and added that link to my ever-growing list of references.

christopher@NUC001:~$ ls -la /opt/fog
total 20
drwxr-xr-x 5 root     root 4096 Feb 17 18:07 .
drwxr-xr-x 4 root     root 4096 Feb 17 18:06 ..
drwxr-xr-x 2 root     root 4096 Feb 17 18:07 log
drwxr-xr-x 6 root     root 4096 Feb 17 18:07 service
drwxr-xr-x 2 www-data root 4096 Feb 17 18:06 snapins

Wayne Workman

@christopherJames Well that output is concerning. Have you ever gotten through the installer completely? You know that when you go to update the database via web browser, that you need to come back to the installer afterwards to continue right? I believe 1.2.0 doesn’t write the .fogsettings file unless installation completes.

christopherJames

@Wayne-Workman

No, I’ve never gotten through it successfully. I get to this

You still need to install/update your database schema.
  This can be done by opening a web browser and going to:

      http://192.168.1.101/fog/management

  Press [Enter] key when database is updated/installed.

Follow the link but always get this in the browser:

The website encountered an error while retrieving http://192.168.1.101/fog/management/. It may be down for maintenance or configured incorrectly.

I can’t do anything else in the terminal until I press enter so… I press enter. Is that where I cocked it all up?

The rest of the install log (done tonight):

  * Configuring Fresh Clam...OK
  * Setting up storage...OK
  * Setting up and starting NFS Server...OK
  * Setting up and starting DHCP Server...OK
  * Setting up and starting TFTP and PXE Servers...OK
  * Setting up and starting VSFTP Server...OK
  * Setting up sudo settings...OK
  * Setting up FOG Snapins...OK
  * Setting up and building UDPCast...OK
  * Installing init scripts...OK
  * Setting up FOG Services...OK
  * Starting FOG Multicast Management Server...Failed!

Script done on Wed 17 Feb 2016 06:07:08 PM EST

So is this a chicken-or-the-egg problem? I need to edit .fogsettings before I can re-install successfully but .fogsettings is not there because I never really had a successful installation in the first place.

Additionally, (and hopefully not to muddy the water any further) this evening when I ran the FOG installation script I tried, while still paused at

You still need to install/update your database schema.
  This can be done by opening a web browser and going to:

      http://192.168.1.101/fog/management

  Press [Enter] key when database is updated/installed.

to navigate according to your instruction to:

/opt/fog/.fogsettings

however

/opt/fog/

didn’t even exist until I pressed enter. The only one in existence was

/opt/fog-setup

If you think this is a lost cause just let me know, this isn’t a production machine that anyone is depending on, I can nuke/pave and try again from scratch.

No big.

Seriously.

george1421

Ok lets see if we can get you going here. The easiest may be to have you acutally deploy the trunk version of fog over 1.2.0. There are so many changes in 1.3.0 (a.k.a trunk version, understanding that 1.3.0 hasn’t been released yet) that there may be little benefit in rolling out 1.2.0.

But where you are at in the process. You are installing fog 1.2.0, you probably have to answer a bunch of questions every time you run the installer, those answers are saved in the .fogsettings file we keep talking about. Wayne mentioned that those values are only saved if the installer completes correctly.

So you run the installer and then it stops at the use the url …/fog/management. On that page you will run the schema install that will create the missing FOG database entries. Without those tables being created the reset of the install will fail, spectacularly. If you can’t access the management page then ensure that th httpd server is running on your FOG server (it should be by default). If it is running but you can’t access the web page, then I would have to ask if you disabled the firewall (and disabled selinux) like you were instructed.

To see if your web server is only you can use the following command sudo netstat -an|grep :80 which should return lines if your web server is listening on port 80 (standard http). You could also use the command ps aux|grep http to report if there are any processes in memory with the name http.

george1421

If you want to upgrade to the pre 1.3.0 release then you can follow the instructions in this: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

For my purposes I create a directory in /opt/fog_trunk and download the trunk installer files there. Then I run the setup program found in /opt/fog_trunk/bin

christopherJames

@george1421 said:

But where you are at in the process. You are installing fog 1.2.0, you probably have to answer a bunch of questions every time you run the installer

Affirmative.

So you run the installer and then it stops at the use the url …/fog/management. On that page you will run the schema install that will create the missing FOG database entries. Without those tables being created the reset of the install will fail, spectacularly. If you can’t access the management page then ensure that th httpd server is running on your FOG server (it should be by default). If it is running but you can’t access the web page, then I would have to ask if you disabled the firewall (and disabled selinux) like you were instructed.

Yes, I did

sudo ufw disable

and received confirmation if I remember correctly.

To see if your web server is only you can use the following command sudo netstat -an|grep :80 which should return lines if your web server is listening on port 80 (standard http). You could also use the command ps aux|grep http to report if there are any processes in memory with the name http.

Just now:

christopher@NUC001:~$ sudo netstat -an|grep :80
[sudo] password for christopher: 
tcp6       0      0 :::80                   :::*                    LISTEN     
christopher@NUC001:~$ ps aux|grep http
christo+ 14436  0.0  0.0  13692  2136 pts/19   S+   19:39   0:00 grep --color=auto http

That’s what we’re looking for, right?

the reset of the install will fail, spectacularly.

Amen, hallelujah, testify.

Tomorrow I will follow the instructions at the link you posted and report back.

“In for a penny, in for a pound” as they say.

Thanks so much.

george1421

Interesting, it appears that you http server is listing on an ipv6 interface (not sure I understand the netstat output at this second.) I can say that the web server IS running. Did you remember to disable selinux? Because you have all of the bits in place to have FOG running. Selinux may/will block the web server from accessing the web pages as well as cause other annoying access blockages.

[edit] Ignore the tcp v6 reference, I just confirmed my prod FOG server has the same results [/edit]

Wayne Workman

Ubuntu doesn’t come with SELinux by default. Unless he installed the Debian package for SELinux (which pales in comparison to the Red Hat implementation), then he doesn’t have it.

And I agree - just go with FOG Trunk, please. Getting 1.2.0 working on newer Ubuntu seems to work for some (how I don’t know) but not for others obviously. FOG Trunk just works.

And if you’re new to Linux and just learning, I might even suggest CentOS 7 instead of Ubuntu. Red Hat has a plethora of very, very, very respected certifications that are very, very, very expensive and are not, not, not a joke that will, will, will get you a good job.

christopherJames

@Wayne-Workman said:

Ubuntu doesn’t come with SELinux by default. Unless he installed the Debian package for SELinux (which pales in comparison to the Red Hat implementation), then he doesn’t have it.

I didn’t install it.

And I agree - just go with FOG Trunk, please. Getting 1.2.0 working on newer Ubuntu seems to work for some (how I don’t know) but not for others obviously. FOG Trunk just works.

Weeeeelllll… I finally got to the log in screen. Next time I run into a problem i’ll do as recommended.

And if you’re new to Linux and just learning, I might even suggest CentOS 7 instead of Ubuntu. Red Hat has a plethora of very, very, very respected certifications that are very, very, very expensive and are not, not, not a joke that will, will, will get you a good job.

I’ll check it out, thanks.

Thank you to the three of you for the help!

PS - I couldn’t find a way to mark this as SOLVED.

Invalid FOG/MySQL Password Character: ";"

126

12.1k

17.3k

155.3k