Host ID was not set, or unable to be created

[Sebastian Roth]

@Zaarin AFAIK this should be fixed in version 7430 already. Kind of strange. Is this Ubuntu 16.04? Fresh install?

[klaron]

I am running 7484 and am having the same problem.

[Tom Elliott]

@klaron os and version of fog server?

[klaron]

@Tom-Elliott Ubuntu 14.04 LTS. Fog 1.2.0 svn 7484. It was working fine with 7274.

[Sebastian Roth]

I am unable to reproduce the issue on Ubuntu 14.04 (FOG 7484). Please enable mysql logging so we actually see the full mysql query and error you get. Edit the file /etc/mysql/my.cnf (14.04 - different file on 16.04 AFAIK) and uncomment the following two lines:

general_log_file        = /var/log/mysql/mysql.log
general_log             = 1

Then restart the mysql daemon (sudo service mysql restart) and watch the mysql log via tail -f /var/log/mysql/mysql.log. You’ll see lot of queries and results. Try adding a host and post the query and error here in the forum. Don’t forget to disable (comment) the log settings later on.

[Zaarin]

Hi,

Problem fixed with the version 7492 but I dropped the database in order to update the schema. Is this normal?

Is there a possibilities to force the update during the installation? Because no update when I see in the installation “You still need to update the database schema…” and go to /fog/management

Thanks for your hard work,

Zaza.

[Zaarin]

Hi,

The database upgrade is working now (version 7522).

This topic can be closed.

Thank you,

Zaza.

[Sebastian Roth]

@Zaarin Thanks for letting us know!

[oscar]

I have the same problem with version 7593 and ubuntu 14.04.
Attachment contents of files mysql.log and error.log:
0_1463053791792_fog_mysql.log
0_1463053977262_fog_mysql_error.log

any idea how to fix it?
THX.

[Wayne Workman]

@oscar Is this a new fog build or existing?

[Sebastian Roth]

@oscar From the logs it doesn’t look like the SQL INSERT is failing… ?!?

[oscar]

@Wayne-Workman this is a existing fog build. The first time I update trunk version had errors in the database. When upgrading a second time seems to fix. I think the problem is in the database update. Is there any way to leave it clean?

[Wayne Workman]

@oscar Seeing as your problem is a month old, my first suggestion is to update.