@Aur3l Ok, this is fixed in dev-branch and will be in the next release as well. The fix is fairly simple and you might want to add this on your own FOG server by hand to not have to wait for the next official release.

@sgennadi ok the SX6000 IS the the PCIE/NVMe M.2 storage card, gotcha.

I did a quick google search and only found one post where they were talking about getting crc errors in their drive. There is also an ssd toolbox created by adata that can inspect the drive. I’m wondering if there is a firmware update for the drive that might address this error. Lastly since this drive is so new, there may not be a linux driver available yet to properly manage this drive so its using the generic nvme controller driver that is giving you that error.

@Sebastian-Roth
Thanks for the reply! Did an update to 1.5.5.1 two weeks ago. Everything works fine so far!

@tian Trying to catch up with older bug reports. Sorry for the late reply.

As we moved to bootstrap this is just how those progress bars look like. Probably not as easy to change.

I am marking this solved - won’t add.

@bretfred Trying to catch up with bug reports, sorry for the late response. I just tested creating multicast tasks with names like 123 and 2. Creating the task as well as multicasting worked like a charm. Possibly Tom has fixed that already. Marking as solved.

@nextechinc Thanks for posting! Sorry we have lost track of this. I just added your suggested change to the dev-branch. Will be in the next release.

@Sebastian-Roth awesome, thanks! I’ll give it a while on my VM’s tonight.

This is fixed

I can confirm that works fine

@Sebastian-Roth Yes it is working now - thank you !!

@falko said in Creating group, members add themselves.:

When I have experienced the issue in the past I have always found that the phantom hosts added to new groups were only the most recent hosts that were registered. Whether that be 2 hosts or 5 phantoms

Running the SQL maintenance commands from the wiki (as mentioned I think updates also helped) seemed to resolve

I was also having this issue, finding that when my co-workers created a group from the hosts page with even just 1 selected computer, it would add over 200 computers to the new group! I was able to avoid this issue by going to groups, creating a new group there, then adding members from the groups screen.

A couple of weeks ago a came across the SQL management commands and that fixed the issue for me! I can now create groups again from the hosts screen (at least until it breaks again). For those wondering about the commands they can be found here: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Database_Maintenance_Commands

Fixed in working branch. Will be in the next release.

@Sebastian-Roth I actually forgot to grab the df -h output before resizing things, but after resizing and re-capturing, it seems to be deploying correctly without consuming all the free space. So this can be closed now I think, at least as far as it affects me. Thanks for the assistance.

@george1421 @Sebastian-Roth
Thank you gentlemen. That fixed it for me as well. Registration is working again.

Works fine adding the remi-php70 repository! Please close the ticket

@yrubdarb Fixed this issue in working, thanks for reporting.

If you see any other issues, are you familiar with GIT? Can you put in a Pull Request against the working branch? (If you could look at working-1.6 that would be great too).

Sorry if I seem a bit distant lately. I had to make a bunch of life decisions very recently and it has greatly impacted my availability for the time being.

I am still here, I just may not be anywhere near as active as I once was until I am settled a bit more.

Thank you,

I’m getting this now on Ubuntu 18.04.1. Fresh install on VirtualBox VM. git checkout working-1.6:

PHP Fatal error: Uncaught Error: Call to undefined method Host::getMasterStorageNode()

While trying to create a task.

Version 1.5.4.586

Not solved in 1.5.4. Problem is still there.

I finally had a chance to update our server (1.5.4). Image History is now reporting the correct previous image as expected. Thanks guys!

@tom-elliott Tom, I just got around to installing a fresh CentOS 7.5 minimal server with FOG 1.5.4. I used the wiki instructions to install this system to the letter and it appears to be fixed. Sorry for the delay. I have another issue with 1.5.4 which I will detsil in a separate post. Thanks for your help and this post is indeed solved.