MySQL troubleshooting

[moses]

I’m trying to troubleshoot what appears to be a password mismatch between FOG/MySQL.

The MySQL password is blank, and I’m trying to check what FOG has.

According to the wiki, the password should be in:

/var/www/[html]/fog/commons/config.php
/opt/fog/service/etc/config.php

The first file doesn’t exist:

[admin@localhost bin]$ ls /var/www/html/fog/commons/
base.inc.php  index.php  init.php  schema.php  text.php

and the second file has only one line:

<?php define('WEBROOT','/var/www/html/fog/');

Am I missing something or does the wiki need to be updated?

[Sebastian Roth]

@moses The paths are different for different FOG versions. If I remember correctly you are using FOG trunk. So please take a look at /var/www/{html/,}fog/lib/fog/config.class.php

Guess we should update the #wiki!

[Wayne Workman]

wow that page is super old…

I’ll see what I can do.

[Wayne Workman]

@Moderators @Developers @Testers Check it out? https://wiki.fogproject.org/wiki/index.php?title=Password_Central

I totally re-wrote it.

[george1421]

@Wayne-Workman Looks great.

The only comment that I would make is to place a disclaimer at the top and somewhere in the middle about soon to be released version 1.3.0 since it has not been officially released yet. One might get the impression that 1.3.0 has been release already. I know its knit picking but we have quite a bit of confusion already with the trunk revisions.

And this is just a general comment, I wish we could either change the default web admin account from fog or change the linux fog account to something other than fog. I’ve seen admins get this mixed up and think they are changing the password for the web gui and end up changing the linux fog password and breaking image capture.

[Wayne Workman]

@george1421 about the “pending release”… you have no idea how many articles reference FOG 1.3.0 lol. I’m writing for the release, and when that happens, boom, all documentation becomes correct.

I’m all for changing the default local user and default interface user.

Make it admin or something. having it as fog just gets the Ubuntu folks locked out of their servers.

[george1421]

@Wayne-Workman said in MySQL troubleshooting:

I’m all for changing the default local user and default interface user.
Make it admin or something. having it as fog just gets the Ubuntu folks locked out of their servers.

admin seems to be a consistent default across most open source projects. What ever it is, it should just be different than what the back end service uses (could change the back end service account also). That way there IS a distinction for both the IT admin as well as when we discuss issues in the forum.

[Wayne Workman]

@george1421 webfog and localfog maybe… or webadmin and localadmin

Because, thinking now, probably a lot of Ubuntu people create an account on installation called admin

[Quazz]

Are you using Ubuntu 16.04 per chance?

[Tom Elliott]

@Wayne-Workman Most people use admin, like @george1421 said.

To all,

While I understand wanting a change, (which is very simple) I worry about the extent to which people seem to be “worried”.

No project, regardless of free, paid, or otherwise, will ever be able to appease everybody. The same thing goes that they can’t be expected to make adjustments for all use cases either.

Changing the username makes sense, but since it’s inception, it’s used fog as the main username. As I said, this is not normal, and adds to the confusion of since FTP uses this same methodology.

I don’t know if I “should” make the change for the username now though as I’m pretty confident FOG, as it currently stands, is very close to a release compared to even 3 months ago. Making this adjust is simple enough, but when a release is this close, and so many others are already (more or less) used to the GUI as it stands, making just a menial change seems rather moot to me.

What worries me (and I suppose this could go for many things) is the idea that people think we should make a full adjustment simple because one or two others ran into an issue once.

While I’m all for trying to make things simpler, making a “project” do this for you seems a bit out of order, at least in my eyes. For example:

This one time my system failed to upload. To fix this I had to check the disk. Please add disk checking to EVERYTHING because this happened once.

At what point should it be expected that the user actually make sure things are okay rather than rely on “source code” to make assumptions and fix things for you? (Then the reverse that we make those changes, and the admin didn’t want them?)

One of the things I dislike more than anything is people complaining about text as it’s read. I do understand trying to make things more readable, but to expect that a change “MUST” happen to something as pointless as text, because one person didn’t understand, is a waste of time.

I don’t know why I feel like adding this information here but do feel this needs to be stated.

[moses]

@Quazz Centos 7

[Tom Elliott]

@moses are you still looking for the config file?

[Tom Elliott]

@Sebastian-Roth said in MySQL troubleshooting:

@moses The paths are different for different FOG versions. If I remember correctly you are using FOG trunk. So please take a look at /var/www/{html/,}fog/lib/fog/config.class.php

Guess we should update the #wiki!

If you are here’s the info again.

[moses]

@Tom-Elliott No, I found it. Discovered underlying issues with Centos, not FOG, so I’m taking backups of config and images, and reinstalling.

Long story short, systemd got corrupted due to me being an idiot.