@Tom-Elliott I am willing in a heartbeat. The problem right now may be my “history” of the old trunk builds causing some headaches in the past. I have some convincing to do for my boss, but having solid things that are fixed/improved helps the case. I am also probably going to need to take a medical leave soon and want to have FOG be stable while I’m gone. I will look at the features 1.6 and see if I can’t earn that tester badge again 😄

@isaiah658 Fixed in dev-branch on github - will be in the next release.

@Cheetah2003 I know it’s been a long time. Sorry this has gone lost! I only got to look into this and fixed it.

@markbam I started to implement that but need to push this further down the list. We need to focus on bugs of the core FOG code before that.

Note to myself: I have saved a diff of the current work in my workspace.

@Fernando-Gietz Just found this. Hope you got to test this at all. I am going to mark this fixed now.

@cromag Thanks for bringing this topic up again. Indeed there was an issue in the scripts. I just pushed a fix to dev-branch. Should be fine in the next release.

Though I still have no idea where the macvtap0@ thing came from reported in the first place.

Nevermind.
It’s working again.

@brakcounty Using FOG with more than one NIC is not officially supported. While it can be setup this way and mostly works it can still cause trouble as we see.

I probably won’t find the time to set this up myself and test but you are more than welcome to investigate in which case it works or fails. If you need assistence on debugging this feel free to ask here.

I returned XD thanks for all @Sebastian-Roth

@george1421 I had to use *.pushbullet.com and *.api.pushbullet.com for web filtering url in Lightspeed setup

Adding a comment:

Currently we are using false nodes to change the multicast tasks. I mean

To make multicast tasks on desired vlan we are creating a second master node to the location’s storage group, with nic an ip assigned on the vlan that we want to do the task and with false user/password to avoid a redundant synchronization.

By the moment, this solution is working with version 1.5.6 of Master and Nodes.

The node must be precedent on alphabetic order to the real node.

@Rivybeast @Raymond-Bell Thanks for testing and letting me know! I will work on fixing the other reports and merge this into dev-branch in the next weeks.

Thank you. yes, you are right the problem is NOT the “//” but SPT on the switch that caused “udhcpc failed”. the solution is posted here:
https://forums.fogproject.org/topic/12248/udhcpc-failed/4

Tested imaging with a dumb switch, and everything worked.

@faresalandlos Yes right, the filesize shown as zero doesn’t cause any problem. You can still deploy the image and the image files are not gone.

The information is located and updated in the database.

@fractal13 Nice to see you around! Hope things are going well for you.

Thanks for the hint on the downloads page. Depending on the tools you use to download you get a different filename. Just click the download link in Firefox and you end up with a file called fogproject-1.5.7.tar.gz. Use wget and you have 1.5.7.tar.gz…

@Quazz Thanks heaps for digging into this even more. I guess it will be very hard to actually track down when and how this was introduced.

This problem is rare enough on its own already (personally haven’t come across it at all)

I would have said so myself a day or two ago. But then I even ran into the same issues when debugging a different partition layout problem for another user in my VM test setup (VirtualBox).

@jmeyer Sorry for the late reply. Couldn’t get to this any earlier. Is this still an issue for you? I have had a look at the code but can’t make sense of this yet. I suppose we’d need the start of the output - the first “Attempting to check in” output line to understand this.

But looking through it I have a feeling that maybe one of the settings is wrong in your setup. Please connect to the database and run the following query:

shell> mysql -u root -p Password: ... mysql> use fog; ... mysql> SELECT * FROM globalSettings WHERE globalSettings.settingKey IN ('FOG_DEFAULT_LOCALE', 'FOG_HOST_LOOKUP', 'FOG_MEMORY_LIMIT', 'FOG_REAUTH_ON_DELETE', 'FOG_REAUTH_ON_EXPORT', 'FOG_TZ_INFO', 'FOG_VIEW_DEFAULT_SCREEN'); ...

Get the full output and post here (as text or picture).

@Tom-Elliott Happy to help ! 😉

@Sebastian-Roth
I make new install of Fog under Debian.
I was using Ubuntu years ago so it’s old install (3 years old).

I have been testing Fog version since years with Tom.
And as i work with VM, i can revert change easily.

In a remote session we figured out that the database schema version was kind of oddly set. Still not sure why that was. Fixed that and applied the last couple of schema changes. That fixed a couple of odd issues including the Storage Node setting changes that can be done now again.