WebGui not available, so I reran the installer.
Everything appears to be working except reports.
Fog Version 1.5.2 on Ubuntu
Tried running Alter User in MySQL
No change.
Where to look next?
Latest posts made by TomcatKZN
-
HTTP 500 Internal Server Error - running user Tracking Report
-
RE: FOG Client: Athentication Error: Unable to get token
Hi Guys
Ran the install with -KY on FOG server. Completed Successfully.
Uninstalled the client on the Presysprepped image Virtual Machine.
Rebooted
Reinstalled the client pointing to FQDN of FOG server.
Rebooted
First iteration of authentication failed as before. A few minutes later when I checked the log again it had successfully authenticated and the client appears to be working correctly.
I have sysprepped this image and am busy capturing it. (For some reason the capture process always drops to about 300Mb/s, while Deploy always runs at full speed), will report back once I have done an install, in the morning. -
RE: FOG Client: Athentication Error: Unable to get token
Thanks for the response guys. I was at training workshop all day so haven’t been able to try this yet. Will do so first thing. Thank you.
-
FOG Client: Athentication Error: Unable to get token
Please can someone help. am going nuts.
On my presysprep image of win10 1709, I installed the client 0.11.12. (Fog server 1.5.0 RC10)
First off, I got the could not inatall Ca Certificate.
I changed the fogserver address to use the FQDN, and then the install worked.
Then I rebooted the client.
Fog log:--------------------------------Authentication-------------------------------- ------------------------------------------------------------------------------ 2018/01/22 21:08 Client-Info Version: 0.11.12 2018/01/22 21:08 Client-Info OS: Windows 2018/01/22 21:08 Middleware::Authentication Waiting for authentication timeout to pass 2018/01/22 21:10 Middleware::Communication Download: http://fogserver2.ehs.local/fog/management/other/ssl/srvpublic.crt 2018/01/22 21:10 Data::RSA FOG Server CA cert found 2018/01/22 21:10 Middleware::Authentication Cert OK 2018/01/22 21:10 Middleware::Authentication ERROR: Could not get security token 2018/01/22 21:10 Middleware::Authentication ERROR: Could not find file 'C:\Program Files (x86)\FOG\token.dat'. 2018/01/22 21:10 Middleware::Communication POST URL: http://fogserver2.ehs.local/fog/management/index.php?sub=requestClientInfo&authorize&newService 2018/01/22 21:10 Middleware::Response Private key path not found 2018/01/22 21:10 Middleware::Communication URL: http://fogserver2.ehs.local/fog/management/index.php?sub=requestClientInfo&configure&newService&json 2018/01/22 21:10 Middleware::Response Success 2018/01/22 21:10 Middleware::Communication URL: http://fogserver2.ehs.local/fog/management/index.php?sub=requestClientInfo&mac=00:15:5D:67:1F:1D|00:15:5D:67:1F:1E||00:00:00:00:00:00:00:E0&newService&json 2018/01/22 21:10 Middleware::Authentication Waiting for authentication timeout to pass 2018/01/22 21:12 Middleware::Communication Download: http://fogserver2.ehs.local/fog/management/other/ssl/srvpublic.crt 2018/01/22 21:12 Data::RSA FOG Server CA cert found 2018/01/22 21:12 Middleware::Authentication Cert OK 2018/01/22 21:12 Middleware::Authentication ERROR: Could not get security token 2018/01/22 21:12 Middleware::Authentication ERROR: Could not find file 'C:\Program Files (x86)\FOG\token.dat'. 2018/01/22 21:12 Middleware::Communication POST URL: http://fogserver2.ehs.local/fog/management/index.php?sub=requestClientInfo&authorize&newService 2018/01/22 21:12 Middleware::Response Private key path not found 2018/01/22 21:12 Middleware::Response Success 2018/01/22 21:12 Middleware::Communication URL: http://fogserver2.ehs.local/fog/service/getversion.php?clientver&newService&json 2018/01/22 21:12 Middleware::Communication URL: http://fogserver2.ehs.local/fog/service/getversion.php?newService&json 2018/01/22 21:12 Service Creating user agent cache 2018/01/22 21:12 Middleware::Response ERROR: Unable to get subsection 2018/01/22 21:12 Middleware::Response ERROR: Object reference not set to an instance of an object. 2018/01/22 21:12 Middleware::Response ERROR: Unable to get subsection 2018/01/22 21:12 Middleware::Response ERROR: Object reference not set to an instance of an object. 2018/01/22 21:12 Middleware::Response ERROR: Unable to get subsection 2018/01/22 21:12 Middleware::Response ERROR: Object reference not set to an instance of an object. 2018/01/22 21:12 Service Initializing modules
Mod edited to use code block.
-
RE: Deployed image boot loop - black screen & Press Ctrl Alt Delete
Okay. You have a point about backing up the original disk.
I’ll give that a bash and check if it works. -
RE: Deployed image boot loop - black screen & Press Ctrl Alt Delete
Understood. Thank you.
-
RE: Deployed image boot loop - black screen & Press Ctrl Alt Delete
@sebastian-roth said in Deployed image boot loop - black screen & Press Ctrl Alt Delete:
@TomcatKZN Ok thanks, I think Ich found what’s causing this. Just need a little more time to fix. Will get back to you soon.
Awesome. Much appreciated.
-
RE: Deployed image boot loop - black screen & Press Ctrl Alt Delete
I also ran Easus partition manager and posted the output.
Seems the 1st partition is fat16. perhaps thats the problem.
Wonder if I can change it to fat32 if it will still work.
What do you think? -
RE: Deployed image boot loop - black screen & Press Ctrl Alt Delete
GDisk -PreImage:
FDisk-PreImage:
Does this help identify the problem with capturing this image?
-
RE: Deployed image boot loop - black screen & Press Ctrl Alt Delete
@sebastian-roth said in Deployed image boot loop - black screen & Press Ctrl Alt Delete:
@TomcatKZN Thanks for the pictures. Although I am sure we have found the issue we still need to figure out what exactly is causing this. I need more information on where those pictures were taken. I’ve tried to replicate this in a test VM but was not successful yet. So I guess my assumptions are wrong.
Please let me know where and when exactly those gdisk and fdisk output pictures were taken. I surely see this is a FOG debug task but was this on a fresh untouched client before capture, after capture or on another machine before / after deployment?
What I am sure is that the partition start positions are moved at some point. And because of that Windows cannot boot. Though I am still not sure if the initial partition layout is crappy or if this is something FOG is causing.
The Gdisk and FDisk output is from a freshly deployed Client which failed.
The same client from which the image was taken.
The picture from windows is before the capture and deploy.
I will install an untouched disk and generate the same output from before the capture.