Topics created by Deimos

@sebastian-roth

true story.
Ubuntu 20.04 and FOG 1.5.9 get along quite well.

@Wayne-Workman said in Installation stops during setting up fogproject password:

own projects, I opt for very long passwords made from upper & lower case letters and numbers randomly. I’m talking 32, or 64 characters long. Typically I look up the maximum length supported password, and generate one of that length, just letters and numbers.

I tried another installation on an other, identical notebook fujitsu lifebook with fedora server 30, but allowed special characters in the function.sh and it works also.

do [[ -z $password || $ret -ne 999 ]] && password=$(head /dev/urandom | '0-9a-zA-Z!#$%&()*+,-./:;<=>?@[]^_{|}~' | fold -w12 | shuf -n1) echo -e "$password\n$password" | passwd $username >>$workingdir/error_logs/fog_error_${version}.log 2>&1 ret=$? let cnt+=1 done

@Deimos From what you are saying I am wonder if you aware of the fact that FOG does not have persistent group settings. It’s more or less just a tool to push a setting to several hosts at once but it does not stick to the group itself.

Yes they are assigned

ftp_proxy=http://10.andsoon.:1234
same with http and https
and
noproxy=10.fog_ip

So, the mysql-fix postet by Tom Elliot helped. No need to rerun the fog installer.

@tom-elliott said in Ubuntu is FOG’s enemy:

TLDR; … or run the ALTER USER syntax shown below.

As a note, it seems this problem is specific only when the mysql account is the 'root' user AND the password is blank.

The “fix” if you must do it manually is to open a terminal and obtain root:
Super (Windows Key) + T then sudo -i (in most cases).

From there, open mysql with mysql -u root

NOTE: MySQL MUST be run with ROOT.

Run:

ALTER USER 'root'@'127.0.0.1' IDENTIFIED WITH mysql_native_password BY ''; AND
ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY '';

It’s okay if one of them fails. This is going to fix Most people’s issues.

I would highly recommend removing the unattended-upgrades as many of these “sudden” issues came as a security patch ubuntu pushed out. By default Ubuntu typically set’s this for you as enabled and it can cause havoc on you as you (the admin) may not have “done” anything.

To prevent this problem from happening in the future you could run:

apt-get -y remove unattended-upgrades (AS Root again).

So I looked at the file with my wireshark at home (forbidden in office)
There´s no data.

I will set up a new fog from scratch and try to WOL the devices. I will report later.

I think the hostname policy of our company is the problem. We use year numbers and consecutive numbering as names for the hosts. And exactly in the query with one of the consecutive numbers results in several results of the query. Just there.
If I enter the entire name, it will only display that one host.
The case can be marked as solved.
Thank you for your cooperation.

@Deimos Ok, great to hear this is fixed! I am marking this solved then. Feel free to open new threads in case you run into new issues.

@Deimos Sure, all fine. Take your time and thanks in advance!

We should be able to collaboratively work on this here: https://demo.firepad.io/#6XlP080kbJ

Would be great if you open a new “German Translation” thread anyway. I am sure it’s good to post it there and discuss things.

@Deimos Update to trunk and adding choices is MUCH simpler, as well as “cancelling” other tasks.

https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk