When upgrading I get this message.

* Setting up fog user.........................................Already setup
* Setting up fog password.....................................Failed
# The fog system account password includes characters we cannot properly
# handle. Please remove the following character(s) from the password in
# your .fogsettings file before re-running the installer: 283332

it seems that it doesn’t like any numeric characters in the password in /opt./fog/.fogsettings

Thanks that worked!

I am having issues with the server replicating to the remote nodes over and over again.

[01-28-19 2:15:32 pm]  | Started sync for Snapin 11a - SimplifyPrinting - Resource id #21838
[01-28-19 2:15:40 pm]   # 11a - SimplifyPrinting: File does not exist optfogsnapinsSimplifySuite.sfx.exe (11Storage)
[01-28-19 2:15:40 pm]   # 11a - SimplifyPrinting: File does not exist on master node, deleting SimplifySuite.sfx.exe on 11Storage
[01-28-19 2:15:53 pm]  | CMD: lftp -e 'set xfer:log 1; set xfer:log-file /opt/fog/log/fogsnapinrep.11a - SimplifyPrinting.transfer.11Storage.log;set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; set net:limit-rate 0:128000; mirror -c --parallel=20 -R -i "SimplifySuite.sfx.exe" --ignore-time -vvv --exclude ".srvprivate" "/opt/fog/snapins" "/opt/fog/snapins"; exit' -u fog,[Protected] 10.11.40.39

I notice that the snapin name is including the path without the / in its name. “optfogsnapinsSimplifySuite.sfx.exe”
also its not adhering to the speed limits set.
all nodes are on the same version 1.5.5
I have to disable all replication on the server or it saturates our 100mb mpls connections
Any help would be great.

Thanks!

@tom-elliott
Thanks Tom

I am having issues with the UEFI boot order being changed to Windows Boot Manager after successfully imaging a PC.
I have to manually enter BIOS and change the boot order back to LAN
This makes imaging PC at remote sites very difficult, I would have to drive to the remote site and change the BIOS settings and that’s just not going to happen.

Does anyone know of a workaround for this issue?
I am using Lenovo ThinkCentre PC’s

does anyone have a cleanup query to cleanup hosts in the database that haven’t reported back in a specified amount of time?

@tom-elliott said in Data missing from the database after host is imaged.:

Fixed in working.

Basically what was happening was the other1 field is used to send emails. That part still can happen (as any value that’s not an email will just not receive an email), but it was clearing the field after it sent the email out.

I just commented out the line as I cannot remember exactly why I was clearing it to begin with.

Thanks Tom!

@tom-elliott said in Data missing from the database after host is imaged.:

Found it.

WOW that was fast

@tom-elliott said in Data missing from the database after host is imaged.:

@greg-plamondon I’ve yet to hear of imaging causing a change on the other tags. Only during registration does this happen. I’ll take a look at the inventory update script, maybe I missed something?

I have found a work around using the “Other Tag #2” for now.
Thanks!

@george1421 said in Data missing from the database after host is imaged.:

@greg-plamondon So just for clarity, if you disable your fog post install script from running (from the master script) the Othertag data is removed from the database?

I could see if you might have altered Othertag data it might happen.

Yes, the othertag is removed. Interesting enough I am able to use the “Other Tag #2” ie “iOtherTag1” field fine.

I also reverted back to fog 1.5.2 and I am having the same issue.