Topics created by sapeurorca

@sapeurorca Try to reset encryption for that host, try to re-install the fog client on that host.

The Fog Client and Fog Server are up to date and database is fixed.

Now the Fog Server working properly now.

Thank You for your help.

It does not matter, I fully understand. But it helped me a lot, thanks again and congratulations to all the FOG team

@ch3i
Okay, I’ll test that and let you know. Thank you for your help.

OK thank you, i tried install fog 1.3.4-RC2.
I would come back to keep you informed.

@osandag said in no such device or address:

Hi, Was this issue resolved?
I have a same or similar issue where the host status is green for about the first ten minutes till i register the host image it, but after a while fog says ‘no such device or address’

Given the age of the issue, has it been fixed or I have to follow the SQL edit procedure?

I just had the same issue that you are describing. The way I fixed it was to ensure that my interfaces file (Ubuntu server) was configured correctly. In my case, I was using search [domain] instead of dns-search [domain]. Once I fixed that, all was well.

For all to see and understand what’s happening.

1.3.0 had some strangeness I was unaware of. This things were:

It had no error reporting on schema updates. Because of no error reporting, even a bad schema (bad sql) would appear as if all ran ok.

1.3.1 corrected these issues. Apparently at schema version point 136 and 140 there was an issue in creating the primary fields. These two schema versions handled the creation of imageGroupAssoc and snapinGroupAssoc.

These issues have been corrected for in 1.3.1 (and are of course present in 1.3.2). If you’re running into these issues, please open mysql and run:

ALTER TABLE `fog`.`imageGroupAssoc` ADD COLUMN `igaPrimary` ENUM('0','1') NOT NULL; ALTER TABLE `fog`.`snapinGroupAssoc` ADD COLUMN `sgaPrimary` ENUM('0','1') NOT NULL;

This would only pose a problem for those that were running on trunk builds that had a schema after these points. If either of them error on the command line (or in phpMyAdmin if that’s what you’re using) please just let me know. If you’re getting the Database ID 236 issue though, I’m pretty sure at the least the alter table of the igaPrimary above will work without any errors.

I’m solving this thread as 1.3.2 apparently fixed the issues that was seen for this thread to have been started.

Now I don’t think anything was wrong, but the installation was started with specifying the php version causing the rest of the system to try to use that versioning. This made it try install incompatible packages on 16.04.

@sapeurorca highly recommend updating to the RC builds. You may not want to but I’m confident it will improve your chances of success.