@george1421 said in Change the boot order automatically:

But we do it this way to make sure we don’t reimage the CFOs computer by accident (again) if everything was automatic.

That must have been a bad day.

Sebastian,

I was able to Register Windows10 Host and it is working. What a fantastic jobs, all of you people are doing.

Thank you for all your hard work.

Olduser.

@Sebastian-Roth

Hi,

Thanks works better with TCP port 445. I was referring this wiki :

https://wiki.fogproject.org/wiki/index.php/Troubleshooting_Host_Management_Showing_Hosts_as_Down

It’s solved.

@Scott-B Pleas run find /var -type f -name "*fpm*log*" and post results here.

Ahhh, forget about that. Ubuntu has the errors in apache error log as far as I remember. Please take a look at /var/log/apache2/error.log and maybe paste the whole log messages from yesterday and today here.

Hello
we changed the rights for the /images folder as followed
root@fogserver:/datastore/images/dev# chown -R fogproject:www-data /datastore/images/
Now it works :)))
Greets
JT

@Quazz Such a simple mistake and yet so hard to see. Thanks for seeing it for sure.

the php dont request the needed memory, it request for the next block. So:
When i has 256M it request another ±20M.
Then I increase to 512M. Then the system claims for another 20M.
Then I increase to 1024M and then the system claims for another 20M

I repeat the actions to accure memory size to 1536M.

If it’s necesary to increase the memory a lot then maybe it’s necesary increase the TimeOut and ProxyTimeout httpd.conf paramenters.

@george1421 Trying to read up on this topic I figured that this is not new. Samsung itself has been involved since March 2017!! But seems like this is still the case even with newer kernel versions and other Samsung drives: https://bugzilla.redhat.com/show_bug.cgi?id=1624611

As far as I understand it the lower you set the value of default_ps_max_latency_us the more power is consumed. Not sure if we want to set this by default for everyone.

@jlthompsonpsd Can you please post the exact machine model you have as well as run smartctl -i /dev/nvme0 in a debug capture task console and post a picture of the output here?

Promised Example:

## Elevate to admin the current Script Execution If (-NOT ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")) { $arguments = "& '" + $myinvocation.mycommand.definition + "'" Start-Process powershell -Verb runAs -ArgumentList $arguments Break } ##Create credentials $password = ConvertTo-SecureString 'MySecretPassword' -AsPlainText -Force $user='useradmin' $credential = New-Object System.Management.Automation.PSCredential ($user, $password) ##Execute wusa.exe with parameters and useradmin credentials. Start-Process -FilePath <path wusa.exe> -ArgumentList <arguments for wusa.exe> -Credential $credential -LoadUserProfile -PassThru

This maybe works

With New-PSDrive you can mount samba and nfs shares if you have the nfs-infrastructure installed.

@Whitespire-tech @Taspharel Yeah, this is kind of strange. I checked to fog-client code and it definitely uses the domain information and shouldn’t need “domain/username” notation. Hmmmmmm. Maybe that depends on the OS you have? Which client OS is this?

Also, sometimes an organization’s web filter / web proxy / content firewall really messes with this step. Be sure that fogproject.org is whitelisted in any of those.

@tgidwani Wow. Really glad you figured that out. I have done a lot of networking but I wouldn’t have expected the gateway setting to cause such an error. In theory the gateway information is only ever used when the host tries to connect to a machine that is not within it’s own subnet. So gateway shouldn’t play a role here as long as both were in the same subnet.

Are you able to replicate the issue when putting the GATEWAY= line back into the config??

@michaeloberg Did you ever solve this?

@VijayBomble Any news on this?

@DeRo93 said in Database connection unavailable - Login incorrect on FTP and Ubuntu:

But maybe you can tell me if this happened because the Ubuntu Server did an Upgrade or something?

Probably yes. But you may check the update log in /var/log/apt/history.log…

@Landy_Dan The FOG CA was introduced to secure the connection between fog-client software and the FOG server. We use certificate based state of the art encryption for that. But you need to know that it is a self signed CA and not derived from an official authority.

Not sure if it’s wise (and even possible) to use that for your RADIUS project. Give it a try and see how far you get. Start by taking a look at all the certificate stuff in /opt/fog/snapins/ssl/ on your FOG server.

Make sure your firmware is up to date in this hardware. Its failing between the UEFI PXE rom hand off and iPXE starting. Typically when we’ve seen this in the past it was related to cruddy early generation firmware.

Weird, disregard. It just suddenly started working now. No idea what fixed it. Maybe it took a while for something to register.

@Sebastian-Roth

I did not found the option in FOG configuration -> fog settings , but I just found the faulty host had as primary MAC the Windows vNIC mac. I put the MAC of the physical NIC as primary and then everything back to normal.

I don’t have a idea to make the research better as I just had to search in the host section of FOG the MAC addresses found in the client log to see what was going on.