Upgraded ubuntu from 13.04 to 14.04 now Web console will not come up

[darkxeno]

Ok So I’m lost I upgrade my Ubuntu from 13.04 ti 14.04 and now i get a 404 error when I goto fogserver/fog/management. Well I copy www/fog folder to var/www/html/ and upgraded fog to 3713 and I get the update schema page but when I click upgrade schema it just sits there and does nothing.

does anyone know what I can do to get my fog back up?

[Wayne Workman]

Move to FOG Trunk.

This is a well known issue with Ubuntu 14.04 and FOG 1.2.0. Several people have experienced this issue, I’d imagine several more will too until the next version of FOG is released (version 1.3.0).

The problem, specifically, is that 1.2.0 uses 127.0.0.1 to access it’s database locally and Ubuntu 14.04 does not like this for some reason.

Here is how you update to trunk: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

[darkxeno]

thats how i upgraded to 3713 lol

[ch3i]

@darkxeno please post your apache error.log.

[Wayne Workman]

@darkxeno Ah… didn’t see that part.

See if your DB is running…

Some things to try:

service mysql restart
tail -f /var/log/mysql/error.log
mysql
use fog
exit
./installfog.sh -y

[darkxeno]

@ch3i

I uploaded the fail since when I copy and paste it tells me it’s spam

[darkxeno]

[Wed Jul 08 08:30:04.533150 2015] [:error] [pid 22878] [client 10.0.10.146:51962] PHP Warning: mysqli::poll(): No stream arrays were passed in /var/www/fog/lib/db/MySQL.class.php on line 67, referer: http://10.0.0.22/fog/management/?node=schemaupdater

This is whats in my apache error log this one line repeated a lot of times lol

[darkxeno]

@Wayne-Workman db is running

[cml]

Is the document root in /etc/apache2/sites-available/001-fog still set to /var/www ?

[darkxeno]

for some reason the fog site isnt there

[darkxeno]

i have also notice that when i do the ./installfog.sh -y it hangs on the updating database

[Wayne Workman]

@darkxeno said:

i have also notice that when i do the ./installfog.sh -y it hangs on the updating database

Sure the database is running?

service mysql status

[darkxeno]

@Wayne-Workman
yup it says running

[darkxeno]

ok so I went back to 2659 and I’m able to get back into the web console now when i try to up grade to 3713 i’m not able to update the schema

[Wayne Workman]

@darkxeno Can you try something in the middle?

instead of typing “svn up”, you’d use this to get a specific revision:

svn co -r 3186 https://svn.code.sf.net/p/freeghost/code/trunk

[darkxeno]

@Wayne-Workman

so 3347 worked

[Wayne Workman]

@darkxeno if you can determine - closely or exactly - where it breaks, that’d help the devs a lot.

[darkxeno]

so i went from 3347 to 3726 and with no issues it looks like I had to upgrade in steps for some reason it was the sql database would not update.

[Wayne Workman]

@darkxeno that’s an issue… it means that the latest schema updater code can’t update something in earlier revisions to the current revision…

Look at your MySQL logs and Apache logs to try and see what it is… What time did the schema updater fail? Your original post was 3 hours ago.

[darkxeno]

@darkxeno said:

Wed Jul 08 08:30:04.533150 2015] [:error] [pid 22878] [client 10.0.10.146:51962] PHP Warning: mysqli::poll(): No stream arrays were passed in /var/www/fog/lib/db/MySQL.class.php on line 67, referer: http://10.0.0.22/fog/management/?node=schemaupdater

this is whats in the apache logs repeated a bunch of times

150708 8:29:15 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150708 8:29:15 [Note] Plugin ‘FEDERATED’ is disabled.
150708 8:29:15 InnoDB: The InnoDB memory heap is disabled
150708 8:29:15 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150708 8:29:15 InnoDB: Compressed tables use zlib 1.2.8
150708 8:29:15 InnoDB: Using Linux native AIO
150708 8:29:15 InnoDB: Initializing buffer pool, size = 128.0M
150708 8:29:15 InnoDB: Completed initialization of buffer pool
150708 8:29:15 InnoDB: highest supported file format is Barracuda.
150708 8:29:15 InnoDB: Waiting for the background threads to start
150708 8:29:16 InnoDB: 5.5.43 started; log sequence number 2579942
150708 8:29:16 [Note] Server hostname (bind-address): ‘127.0.0.1’; port: 3306
150708 8:29:16 [Note] - ‘127.0.0.1’ resolves to ‘127.0.0.1’;
150708 8:29:16 [Note] Server socket created on IP: ‘127.0.0.1’.
150708 8:29:16 [Warning] Found invalid password for user: ‘timesheet@localhost’; Ignoring user
150708 8:29:16 [Warning] Found invalid password for user: ‘sa@localhost’; Ignoring user
150708 8:29:16 [Warning] Found invalid password for user: ‘timesheet1@localhost’; Ignoring user
150708 8:29:16 [Note] Event Scheduler: Loaded 0 events
150708 8:29:16 [Note] /usr/sbin/mysqld: ready for connections.
Version: ‘5.5.43-0ubuntu0.14.04.1’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 (Ubuntu)
150708 8:37:22 [Note] /usr/sbin/mysqld: Normal shutdown

150708 8:37:22 [Note] Event Scheduler: Purging the queue. 0 events
150708 8:37:24 [Warning] /usr/sbin/mysqld: Forcing close of thread 1554 user: ‘root’

150708 8:37:24 [Warning] /usr/sbin/mysqld: Forcing close of thread 1465 user: ‘root’

150708 8:37:24 InnoDB: Starting shutdown…
150708 8:37:25 InnoDB: Shutdown completed; log sequence number 2593161
150708 8:37:25 [Note] /usr/sbin/mysqld: Shutdown complete

150708 8:37:25 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150708 8:37:25 [Note] Plugin ‘FEDERATED’ is disabled.
150708 8:37:25 InnoDB: The InnoDB memory heap is disabled
150708 8:37:25 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150708 8:37:25 InnoDB: Compressed tables use zlib 1.2.8
150708 8:37:25 InnoDB: Using Linux native AIO
150708 8:37:25 InnoDB: Initializing buffer pool, size = 128.0M
150708 8:37:25 InnoDB: Completed initialization of buffer pool
150708 8:37:25 InnoDB: highest supported file format is Barracuda.
150708 8:37:25 InnoDB: Waiting for the background threads to start
150708 8:37:26 InnoDB: 5.5.43 started; log sequence number 2593161
150708 8:37:26 [Note] Server hostname (bind-address): ‘127.0.0.1’; port: 3306
150708 8:37:26 [Note] - ‘127.0.0.1’ resolves to ‘127.0.0.1’;
150708 8:37:26 [Note] Server socket created on IP: ‘127.0.0.1’.
150708 8:37:26 [Warning] Found invalid password for user: ‘timesheet@localhost’; Ignoring user
150708 8:37:26 [Warning] Found invalid password for user: ‘sa@localhost’; Ignoring user
150708 8:37:26 [Warning] Found invalid password for user: ‘timesheet1@localhost’; Ignoring user
150708 8:37:26 [Note] Event Scheduler: Loaded 0 events
150708 8:37:26 [Note] /usr/sbin/mysqld: ready for connections.
Version: ‘5.5.43-0ubuntu0.14.04.1’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 (Ubuntu)
150708 8:48:45 [Note] /usr/sbin/mysqld: Normal shutdown

150708 8:48:45 [Note] Event Scheduler: Purging the queue. 0 events
150708 8:48:45 InnoDB: Starting shutdown…
150708 8:48:46 InnoDB: Shutdown completed; log sequence number 2593161
150708 8:48:46 [Note] /usr/sbin/mysqld: Shutdown complete

this is my mysql logs