FOG 33b - installation - HP Elite 8300 SFF

[Alistair]

I have been using version 32 for a number of years on an old HP PC.

I installed 33b yesterday on a new HP Elite 8300 with 8 GB RAM.

Is it still necessary to change the bind-address= in /etc/mysql/my.cnf
I changed this to my fog server address.

I tried to update the database schema but could not until I had put in the mysql password with:
sudo gedit /var/www/fog/commons/config.php

Then database schema updating worked.
Then logged successfully into [url]http://10.0.1.40/fog/management[/url]
Then named a Linux image.

Server 2012 R2 already had DHCP scope options:
066 = fogserver
067 = undionly.kpxe

Then tried to register one old HP client (which I know had been registered before on the old FOG server)
Client obtained IP address and then waited for Tftp - timed out.
I had seen this years before on the old system, so I typed:
sudo stop tftpd-hpa
sudo start tftpd-hpa

Client still timed out.

I restarted the DHCP on the win server and rebooted the fogserver.
Then the real problems began: I got error messages from Nautilus and I could no longer log in on the fog management page, either on the fogserver or my PC. I could see that my password was accepted, but the next page was never opened. It just stayed at the login page.

xxxxxxxxxxxxxxxx

So now today I have reinstalled Ubuntu 12.04.4 and FOG 33b

Do I still need to change the bind-address in /etc/mysql/my.cnf ?
Yesterday when I did this, new copies of my.cnf were created: my.cnf~ and my.cnf~~.
Is this normal?

I’m really worried that the same thing is going to happen today again.

[Alistair]

Yesterday I was logged in as Root when I did the installation and file mods.

Today I have remained a normal user and installed fog with sudo.

[jbsclm]

I’ve installed various revision of 0.33 on ubuntu 12.04 lts, but now just install the new revision over the top. All I did on the install was to su - and cd to the bin directory under the fog source, and then ./installfog.sh
I don’t remember having to change anything, other than to answer the questions. I certainly didn’t do anything with the mysql config, just accept the prompt from the installer to set the password to null.
I let the installer download all the required packages, rather than installing, and configuring them beforehand.
hope this helps

[Alistair]

I urgently need help now. It’s happened again. I cannot log in to the fog management console.
It worked 10 minutes ago until I closed and opened firefox. The fogserver also went into screensave mode when it has to be unlocked. So I unlocked it.

If I try to log into the fog management console with fog and wrong password, then I see “invalid login”.
If I use the correct password then there is no “invalid” message, which means the password has been accepted, but the next main fog home page never appears. It just stays at the login.

I’m desperate now. I really need to get this working. I’ve spent hours re-installing everything.

[BPSTravis]

Have you tried clearing cache on firefox? You do not need to “unlock” the server terminal window every time it goes to sleep.

What do your apache error logs say? right after you try the correct login?

/var/log/apache2/error.log

[Alistair]

[Mon Apr 14 15:15:31 2014] [notice] Graceful restart requested, doing restart
apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName
[Mon Apr 14 15:15:32 2014] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.11 with Suhosin-Patch configured – resuming normal operations
[Mon Apr 14 15:15:36 2014] [notice] Graceful restart requested, doing restart
apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName
[Mon Apr 14 15:15:36 2014] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.11 with Suhosin-Patch configured – resuming normal operations
[Mon Apr 14 15:20:19 2014] [notice] caught SIGTERM, shutting down
[Mon Apr 14 15:20:20 2014] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.11 with Suhosin-Patch configured – resuming normal operations
[Mon Apr 14 16:47:56 2014] [notice] caught SIGTERM, shutting down
[Mon Apr 14 16:48:43 2014] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.11 with Suhosin-Patch configured – resuming normal operations
[Mon Apr 14 16:58:33 2014] [error] [client 10.0.1.39] PHP Warning: mysql_close(): 22 is not a valid MySQL-Link resource in /var/www/fog/lib/db/MySQL.class.php on line 45, referer: [url]http://10.0.1.40/fog/commons/schemaupdater/index.php?redir=1[/url]
[Mon Apr 14 16:58:33 2014] [error] [client 10.0.1.39] PHP Fatal error: Call to a member function debug() on a non-object in /var/www/fog/lib/db/MySQL.class.php on line 50, referer: [url]http://10.0.1.40/fog/commons/schemaupdater/index.php?redir=1[/url]
[Mon Apr 14 17:41:56 2014] [error] [client 10.0.1.39] File does not exist: /var/www/favicon.ico
[Mon Apr 14 17:41:56 2014] [error] [client 10.0.1.39] File does not exist: /var/www/favicon.ico
[Mon Apr 14 17:45:52 2014] [error] [client 10.0.1.39] File does not exist: /var/www/favicon.ico
[Mon Apr 14 17:46:01 2014] [error] [client 10.0.1.39] File does not exist: /var/www/favicon.ico
[Mon Apr 14 17:46:01 2014] [error] [client 10.0.1.39] File does not exist: /var/www/browserconfig.xml
[Mon Apr 14 18:08:19 2014] [error] [client 10.0.1.40] File does not exist: /var/www/favicon.ico
[Mon Apr 14 18:08:19 2014] [error] [client 10.0.1.40] File does not exist: /var/www/favicon.ico
[Mon Apr 14 18:09:29 2014] [error] [client 10.0.1.39] File does not exist: /var/www/favicon.ico
[Mon Apr 14 18:09:29 2014] [error] [client 10.0.1.39] File does not exist: /var/www/favicon.ico

[Alistair]

10.0.1.40 is the fogserver
10.0.1.39 is my work station

Clearing the cache did not help. Using firefox on fogserver did not work either.

[Alistair]

Why would it work for 10 minutes and then not? The same yesterday.

[Tom Elliott]

From what I can tell, it appears the username and/or password are not working for mysql.

Try commenting the bind-address part of the my.cnf file entirely and restart mysql and try again.

[Alistair]

how do I comment the bind-address

[Alistair]

By the way, is it best to stop mysql first before doing changes and then start?

[Alistair]

Oh yes # to comment

[Alistair]

Have put # in front of bind-address and saved.
then
sudo start mysql
running
Tried login - not work.

As I said it is easy to see that my correct password is being accepted because I do not get “invalid login”

[Tom Elliott]

Then the user you’re trying to login is flagged as quick image/mobile

[Alistair]

That’s correct. I selected that option believing that it gave me an extra option on the PXE registration page.
You need to put a better explanation of what it is on the initial user creation page.
I really did not know if I should tick it or not.
What do I do now to get access again. This is the one and only user I have called fog.

[Tom Elliott]

You have to unflag the user.
[code]mysql -u root -p fog[/code]

From the mysql shell run the command:
[code]UPDATE users SET uType=‘0’ WHERE uName=‘fog’;[/code]

[Alistair]

And could I have a definitive answer on if it is necessary with 33b to modify the bind-address= in /etc/mysql/my.cnf to my fogserver ip address? (as it was necessary with 32)

[Alistair]

Thanks so much Tom. It works again. And I will not tick that option again.
Can I suggest the following text in addition to that you have by that tick box:

Warning - if you tick this box, this user will not be able to log into this FOG Management Console in the future.

[Alistair]

I am trying to register 1 client, an old HP

PXE TFTP open timeout

It’s not finding the pxe boot file.

A few years ago I think I fixed this with
sudo start tftpd-hpa

But tftpd-hpa is already running.

Server 2012 R2 already has DHCP scope options:
066 = fogserver
067 = undionly.kpxe

So what’s the problem?

[Tom Elliott]

does your fog server have the file:
/tftpboot/undionly.kpxe