@templink Please run:
sudo mysql -u root
Within mysql please run:
ALTER USER 'root'@'127.0.0.1' IDENTIFIED WITH mysql_native_password BY '';
ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY '';
exit;
Then you should be good to go.
Found out exactly what the issue was. It’s because of the damn WOL tasking son of a.
Sorry it was so hard to replicate/troubleshoot.
It is now fixed in RC-9 thanks for reporting.
As a meantime fix, so you don’t have to constantly run in to the problem.
Edit your /opt/fog/.fogsettings file.
Look for packages=' and remove sysv-rc-conf from the packages list.
More often than not, (unless you’re still using the legacy version of the fog client), the CPU usage starts to become high because of replication. This slows the CPU because it’s got to process the data, and read it from disk to send it where ever it needs to be distributed.
You could try:
service FOGImageReplicator stop
service FOGSnapinReplicator stop
I set one of my hosts to pending and I see what yo’re seeing.
I don’t know german very well so I didn’t know what was being said there. Now I see it says:
“Requires templates to process”
I fixed it. Will be fixed for RC-21.
The error comes after the partclone error? It seems to be telling you exactly what’s wrong. The drive wasn’t shutdown properly.
Found and fixed now. The text will be a bit smaller too, but Home is no longer displaying as:
Hom
e
@threeonesix As @sebastian-roth suggests, leave the locations default. /home/images /home/snapins is changing the default locations.
FOG defaults to put images on /images and snapins on /opt fog/snapins
If you are a beginner, why state where you want these things mounted instead of saying, I would like images on /dev/sdb and snapins on /dev/sdc. You have admitted to not knowing much about linux.
To understand:
/dev/sdb = /images
/dev/sdc = /opt/fog/snapins
That would get you where you need to be, all you need to learn is how to tell your server to mount /images and /opt/fog/snapins.
First things first, did you make sdb a single partition using all available space for the partition? How are you formatting the partition? xfs, ext2, ext3, ext4, ntfs, btrfs?
Same questions for sdc
The following instructions assume you are going to use /images and /opt/fog/snapins as the installer defaults to. It assumes the partition is formatted on both disks as ext4. Adjust as necessary.
sudo -i #enter sudo password
mkdir /images #creates /images if it does not exist already
mkdir -p /opt/fog/snapins #creates /opt/fog/snapins if it does not exist already
echo "/dev/sdb1 /images ext4 defaults 0 0" >> /etc/fstab # appends the quoted line into the /etc/fstab file
echo "/dev/sdc1 /opt/fog/snapins ext4 defaults 0 0" >> /etc/fstab # appends the quoted line into the /etc/fstab file
mount -a #attempts to mount /dev/sdb1 to /images and /dev/sdc1 to /opt/fog/snapins
Remoted in to help out. Issue to install the working-RC-24 with the new “items” which failed out was the code I added to try to ensure things were cleaned up had some issues. Now we wait, I suppose, to see if WOL is still doing the “additionals”.
Hey all,
Just trying to inform you.
I made a change to the installation that tries to set the fog username/password for you so it can be displayed during a node/system install.
This change is enforcing a password reset for the Linux System’s FOG User. You will probably have a few issues initially getting anything ftp related to work.
There are two ways you can fix this:
Way 1 (probably more work but ultimately allows you to edit your own info) :
The fix is to open up the /opt/fog/.fogsettings file and search for the storageftppass= line.
This line is what the new FOG User password is set too. You can change it to whatever you like. Edit this file to make the password set to whatever you want it to be so future updates don’t break it.
Save the file and on terminal enter sudo passwd fog
Set the password to whatever you want it to be, mostly likely what is currently stored in the storage node anyway.
Way 2 (Probably the simplest way)
Copy the value in the /opt/fog/.fogsettings storageftppass= line and edit your storage node to use this new password. You will also likely need to edit the FOG Configuration->FOG Settings->TFTP Server->TFTP_FTP_PASSWORD with this new password as well.
This should help you out.
@kondi Repushed RC-35 which should address this issue.
Thanks for reporting.
I confirmed this was a bug. It is now fixed in 3431. Thanks for reporting.
And a little more info:
When the client sends the self registration the, Invalid Host, message is how it knows to do this. Hopefully this helps clarify that, from the messages in the log, to the urls it’s sending, are showing there currently is no bug. The system is doing exactly what it’s supposed to be doing.
Of course, confirmation of the fact that the host registered itself and is now in “pending hosts” would be even further showing that this is indeed working properly.
@Polii123 This is because document root is looking at /var/www/fog (so you can access by simply http://localhost/) and still see fog. However, the FOG_WEB_ROOT setting is not reflecting this. So essentially it’s looking for the link:
http://localhost/fog/status/hw.php in: /var/www/fog/fog/status which I’m going to guess doesn’t exist.
https://github.com/FOGProject/fogproject/issues/149
Fixed in development. The post earlier is still valid to get things operational more immediately.
Chatted and found out the problem.
This was a two part problem.
Problem number one.
Location Plugin was installed, but no entries were made. I don’t know yet if there’s a bug specifically in this, but there was a location association at one point in time. This lost its association but made it so the default location was not set. This is why the http:///fog/service/ipxe/bzImage was display.
Problem number two.
The FOG Configuration->FOG Settings->TFTP Server->FOG_TFTP_PXE_KERNEL setting was literally set to /bzImage instead of bzImage
Any of the files being stated should not have a beginning precursor as such.
Hopefully we’ve helped out and helped figure out other means to troubleshoot.
Typically speaking, usernames don’t contain dashes and I’ve been working to improve checking of things so we have more suitable allowances for things.
I’ve updated the regex and this new regex should work for ldap and the main username now.
The regex I’m using is:
/(?=^.{3,40}$)^[\w][\w0-9]*[._-]?[\w0-9]*[.]?[\w0-9]+$/
What this translates too:
Must be at least 3 characters.
Must be no greater than 40 characters.
Must start with a word character (not number, character, etc…)
Can have up to two periods (non-contiguous) test.user.decimals is valid. test…userdecimals is not.
Only one underscore or - in the username.
Hopefully this will address the issues you saw and let you log back in.
You’ll likely find it simpler to just update to SVN/Trunk (if you can).
The problem is specific to what that NIC is expecting to download from. It is expecting a specific parameter to get the default.ipxe file.
Most systems work naturally when it is set to: /default.ipxe but there are a few quirks where the nic is EXPECTING tftp://${next-server}/default.ipxe
Basically it’s expecting the implicit direction of protocol and where to get the file.
Yes. The Host registration service was fixed for 1.3.1 I believe, it brought in a different bug which caused the release of 1.3.2, but yes it was fixed.