Posts made by pmonstad

@Tom-Elliott

@Wayne-Workman Here is the log file:0_1470662623979_fog.log

@pmonstad Did a reinstall (svn) to make sure all client files are downloaded. Checked the global option is turned on, then moved all hosts to a new group and forced a client update setting to yes on all hosts. Still no update on my clients, and no errors in the fog log: client version : 0.11.4 client os: windows. server version: 1.3.0-rc-7 Middleware::Response Success

@Tom-Elliott Both options are turned on.

@Tom-Elliott Double checked: it is on. This client ran the update from 0.12 to 0.14 a couple of days ago. This is not an one-client problem. None of my clients have got 0.15 after installing rc7.

@Tom-ElliotIs says: client version : 0.11.4 client os: windows. server version: 1.3.0-rc-7 Middleware::Response Module is disabled globally on the FOG server

The last line indicate some setting is turned off ? All checkboxes are one, and I have not changed anything tha last couple of months concerning this. It did update from 0.12 to 0.14 some days ago.

No such error in log file. Says it communicates with the rc7 FOG server. Are there any info in FOG gui telling which client version is available on the server? Could be useful to have this info available…

I updated FOG from RC6 to RC7 but the client will not auto update from 0.11.4 to 0.11.5. Anywhere in FOG gui to give a hint on which client version is installed on FOG server?

I finally figured out what was the problem: The Management password under Storage Management has been changed to some random text string. I never did it. All I did was running av svn update and this password seams to have changed. A bug?

Hm, back again. Still problem. I have this error in apache error log:
[Mon Aug 08 12:35:09 2016] [error] [client 192.168.68.41] PHP Fatal error: Uncaught exception ‘Exception’ with message 'Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 108, Message: ftp_login(): Login incorrect., H$
[Mon Aug 08 12:35:12 2016] [error] [client 192.168.68.41] PHP Warning: ftp_login(): Login incorrect. in /var/www/html/fog/lib/fog/fogftp.class.php on line 108

I have set fog user password with command passwd fog and it does not help. This worked last time I did an capture task, some weeks age in then latest svn version. Now I am on RC7 and still a problem. I have not touched the server other than running the update svn procedure. Any suggestion how to solve this?

I did an update today to RC7 and it now works again. Have no idea what caused the database error.

Deploy works OK

@george1421 I know this has been an issue and I ran passwd fog to reset the password. No effect

Updated from a month old svn to rc6. Capturing an image fails when database record is to be updated (I guess) after upload is completed. Centos 6 and mysql (no changes have been made since my last svn was up and running.

Running very latest svn 5829, client 0.11.2 on Win 7 32 bits. Framework 4.0.

I have a client which fails when I try to install the client. I get an error "Unable to create settings file: Error reading JObject from JsonReader. Path ‘’, line 1, position 421.

Works again after updating to svn 7713

After updating to svn 7687 I’m no longer able to deploy hosts. During PXE booting host reports failed to check in. Running on a Centos server.

@Tom-Elliott From a user point of view it is a bug when things suddenly act different then it used to be, when there are no signs of changes in the way a function is meant to work.

I have done an update to latest svn and things suddenly fails. That’s way I assume this MIGHT be a bug. Client 0.9.12 gives me an error telling “could not get security token” and “invalid security token”. The function is meant to do an client update automatically, which it now suddenly fails to do. You can of course make a statement this is not a bug, but it still act like a bug. According to the wiki this might be a problem if I uninstall/reinstall the client. This is not the case.

Putting hosts into a group and then running the suggested procedure is probably good, but how can I know which client works and which fails?

But if this is not a bug, but the way things are meant to work these days I will have to live with it. By the way, I reported a similar problem months back and then it was a bug which was fixed.

@ITSolutions This is a problem on most hosts. How/were do I reset this?