Topics created by Kiweegie

@Tom-Elliott Hi Tom

I meant I manually removed the snapin from /opt/fog/snapins folder on the server, was looking for a way to remove reference to same in the DB/Web GUI.

It doesnt’ matter now though I’ve just rebuilt Fog having backed up image and snapins etc I need.

Mark this one as resolved, thanks for your efforts.

regards Kiweegie.

@Kiweegie said:

Thanks Tom,

I did move it myself. Uploading a new image ended with the same result though. I’m happy to continue manually moving from /images/dev/macaddress to /images/imagename if necessary just wondered if this was down to something I’d done wrong…

regards, Kiweegie.

The only reason that FOG wouldn’t move it itself would be due to FTP credentials…

Knowing now what credentials are set on the master storage node, try to connect via CLI using FTP with those credentials you have set. If it doesn’t work, there’s your problem.

I have the vm restored to the previous state and I’m able to login with version 4388 on the cloud. This vm has the access control, ldap and location plugins installed.

On the vm that was cloned, I renamed the folders for access control and ldap then restarted the httpd service. On this vm I’m now able to reach the schema update page. After the schema update was updated the version number on the cloud is 4652.

After I was able to login I removed the plugins access control and ldap and restarted httpd. I was able to login OK, so I added back in ldap, access control and restarted http. This time on the login page I noticed (as with version 4388) the estimated fog sites and latest version values weren’t displayed only the rotating circles. I was able to login OK. I then removed the ldap plugin again. At the login page the estimated sites just showed the rotating circles. And finally I logged in and removed the access control plugin. Now at the login page I get the values of 4199 and version 1.2.0 (?? since I though this was 1.3.0). I added back in the ldap plugin without issue.

So you guess that it was the access control modules is spot on. I’ll wait a day or two so we can get the images deployed on the production FOG server then attempt to upgrade that one again.

Oh ok I was able to get it back by copying the image the image management page.php file form the old verison I had before It was in the 3000s build and was able to get the page to load but now when i go to edit a image i get a basic page with no formatting lol

@Tom-Elliott absolutely, was looking for how I could mark resolved this side funnily enough,

@Wayne-Workman Success!

ok the latest snapin has worked as expected. Root cause I think was the locations and how I had set them up. Each host has a Location entry and each location points to a storage group.

I’d set the host I was testing this on to the only location I’d set up for head office and this was pointing to the wrong storage group.

I’ll do some further testing this week but hopefully others with same issue can at least learn from my mistakes…

Wayne, really appreciate the time and effort you put in to help me out with this one, greatly appreciated.

cheers, Kiweegie.

@Sebastian-Roth

sry haven`t found this thread before.

Thx for this.

My workaround works only randomly, i think rc.local is the best way.

Hi Tom/Wolfbane

thanks for the info and for getting documentation updated which will no doubt help others doing this. In our case the networking team have confirmed that STP is enabled but that portfast is not. We’re looking to roll this out again in a couple weeks but for now have gone back to 0.32.

Our network team have advised tha as well as configuring portfast they will also configure BPDU Guard to avoid network loops which could bring network down as discussed in [URL=‘https://learningnetwork.cisco.com/thread/3160’]this cisco thread[/URL].

I’ll confirm once we have this up and running and include any other gotchas we encounter.

thanks again, Kiweegie

Hi,

I know this is an old thread, but I just discovered this exact error today. I can’t remember that it’s ever done this before, but can’t be sure. Using FOG 0.32.

I apologize for the late reply! That is cool.