Posts made by Kiweegie

@Wayne-Workman Hi Wayne, keeping an eye on all the scripting tweaks for removing old client and installing new one however I’m still facing issue with installing new client and getting error:

“Failed to download CA certificate”

This has happened to others and in this post it stated that the new client can only be downloaded and installed in conjunction with the new development versions of FOG. Another user had issue on the development version and Tom Elliot had to remote in and edit some files to get it to work - wondering if mine needs something similar?

Happy to edit the files needed if I can be given some guidance on what to look for.

regards Kiweegie.

@Sebastian-Roth @george1421

Hi both, thanks for the pointer to log, that showed me issue. Had reinstalled from trunk and while fog password was ok per my records in the below locations I had like a complete rookie forgotten to reset password on the server itseld post upgrade… d’oh!

Storage Management > All Storage Nodes > Default Member > Management Password
Fog Configuration > Fog Settings > TFTP Server > FOG_TFTP_FTP_PASSWORD

cheers all
Kiweegie.

Hi again

I upgraded to latest trunk to get past issue with 4501 not opening List Snapins page. List snapins now works a treat however Create New Snapin opens a blank page…

URL = http://<ip_of_FOG_Server>/fog/management/?node=snapin&sub=add

regards Kiweegie,

@Tom-Elliott Hi Tom, not an issue and had noticed the Nginx reference. Was more a heads up than anything else.

cheers. Kiweegie.

Hi fellow FOGgers

Noticed this on the home page this morning on latest trunk after updating yesterday.

Not a biggie from my perspective but getting the word out.

cheers Kiweegie,

@Wayne-Workman Hi Wayne, yes I edited fogserver variable to be my actua FOG server dns name…

Note the issue is not with the script per se. at least not in my case but one of the CA Cert not being found or downloaded for FOG new client.

regards Kiweegie.

@Wayne-Workman Hi Wayne

git log

shows as

git-svn-id: https://svn.code.sf.net/p/freeghost/code/trunk@4541 71f96598-fa45-0410-b640-bcd6f8691b32

However there are a couple of commits above that last of which is

commit f34289f60d81c9d95149e3bb78982ba017f6b932
Merge: 259e115 0918efb
Author: Tom Elliott <tommygunsster@gmail.com>
Date:   Mon Dec 14 21:58:04 2015 -0500

    Merge svn with dev-branch

The legacy client version on old machines is 3.0.29 - I can remove that manually or via script no problem. I don’t know what version the new client is as can’t install it and /var/www/html/fog/client doesn’t show a version number in text file etc.

I’ve also checked certmgr.msc on client machines in case there was already a new FOG client cert on there but nothing in evidence.

cheers, Kiweegie.

@Wayne-Workman Hi Wayne and co. Just trying these scripts now and have hit another hurdle in that the new client fails to install with error:

Failed to download CA certificate

I’ve searched the forum and can see that others have had this issue in the past but the solution was never made clear.

Suggestions? I’ve updated to latest git version this morning (15Dec15 around 1200 GMT).

regards Kiweegie

@Wayne-Workman HI Wayne, thanks for this. I’ve upgraded to latest trunk and can confirm this now works as expected. Please mark call as resolved.

regards Kiweegie.

Seeing this on latest trunk version

Fatal error: Call to a member function get() on null in /var/www/html/fog/lib/pages/snapinmanagementpage.class.php on line 47

The create snapin link works as expected

The line in the code affected is as follows so something storage group related

47                 'storage_group'=>$Snapin->getStorageGroup()->get('name'),

regards Kiweegie.

I have about 300 machines which were all imaged with an earlier FOG version (started using it back in late 0.2X days).

These machines have the legacy client on them and I’m keen to deploy the latest client in its place (0.9.9 I believe). I’ve searched the forums and can see that others have asked the question and can see some people mentioning GPO to remove the old one amongst other things. Is that the best accepted way or can the client update be done all through FOG itself?

I’m guessing the client itself is used during snapin deployment so we can’t snapin this? And I found the client updater within the FOG configuration window in the GUI can that be used in some way to update the client or is that just for things like GreenFOG etc?

When last I investigated this I think the client had to be built into the image itself though I’d prefer to just update the client rather than completely reimage.

regards, Kiweegie.

@Tom-Elliott Good morning Tom,

Confirm since upgrade to latest release Image Replication is working once more.

Couple of related quesions please if you don’t mind. Does this need to be updated (FOG version) on the storage nodes as well or just on the master node? I’ve only updated latter and seems to be working but double checking.

I noticed that in the FOG Log viewer when checking Image Replicator log that it shows the fog user password for the storage nodes in plain text. Is this by design?

[12-07-15 8:53:02 am] * Started sync for Image NewShinyImage
[12-07-15 8:53:02 am] | CMD:
			lftp -e 'set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; set net:limit-rate 0:64000;set net:limit-rate 0:64000;set net:limit-rate 0:64000; mirror -c -R --ignore-time -vvv --exclude 'dev/' --exclude 'ssl/' --exclude 'CA/' --delete-first /images/NewShinyImage /images/NewShinyImage; exit' -u fog,<FOG user pw in plain text> 10.223.40.15
[12-07-15 8:53:02 am] * Started sync for Image NewShinyImage

Lastly the fogstorage password which is used on the main server for nodes to connect back to. That can be edited in the GUI under FOG Configuration > FOG Settings > FOG Storage Nodes > FOG_STORAGENODE_MYSQLPASS. What config file if any does this password sit in and is amending in the GUI sufficient? Wondering if a new server has to be provisioned if we can just edit the fogstorage password here on new machine to match what was set during storage node setup. Or on the other hand can the new fogstorage password be added to a config file on the storage nodes?

Thanks again for the help and (exceedlingly) quick fix/reply.

regards Kiweegie.

Updated to latest trunk and all looking good apart from image replication. I have the Location plugin installed on one Normal node in head office plus a storage node (also in head office) and storage nodes at 7 remote sites.

I have 2 storage groups defined - “default” and “local”.

I have a storage node configured for each actual storage node. The head office storage node (called “localstorage”) points to the “local” group - this is for images at head office which don’t need to replicate to other sites.

The remote storage nodes are all set with the “default” storage group.

The “DefaultMember” and “localstorage” nodes are both set as Master Node so should replicate to any storage nodes within the same storage group, correct?

Log viewer shows:

[12-06-15 10:22:37 pm] * Starting Image Replication.
[12-06-15 10:22:37 pm] * We are group ID: #1
[12-06-15 10:22:37 pm] | We are group name: default
[12-06-15 10:22:37 pm] * We have node ID: #1
[12-06-15 10:22:37 pm] | We are node name: DefaultMember
[12-06-15 10:22:37 pm] * Not syncing Image between group(s)
[12-06-15 10:22:37 pm] | Image Name: MyNewShinyImage
[12-06-15 10:22:37 pm] * | I am the only member

The image itself has the Replicate? check box checked and is associated with the default storage group. Oddly if I associate the image with the “local” group replication starts to work.

The correct fog username and password has been added to each storage node under Management Username and Management Password and I tested I could ftp to the nodes with these credentials.

The correct IP is set on each node as well. Permissions on the /images directory look ok too - I’ve manually set as fog:root.

It would appear the master fog server knows its the master, can see the correct image but cannot see any other nodes within the same storage group for some reason.

Ideas anyone?

thanks, Kiweegie.

Thanks as always Tom for the quick fix - all good now, this can be marked as solved.

Ref the Apache and php files error - think that was an additional symptom of the sed missing character.

Installed latest git version tonight 04Dec GMT and on install (of storage node) got this error

sed: -e expression #1, char 34: unterminated `s' command

It sets the fog username and password and then fails at this point

* Setting up Apache and PHP files.............................Failed!

Regards Kiweegie.

@Tom-Elliott Hi Tom, updated to latest git release now and indeed its working again. I did only update a few days ago after your last fix re the flashing issue.

regards Kiweegie.

@Tom-Elliott Hi Tom, flashing was indeed solved however I now seem to have another niggle with regards the plugins. I managed to enable WOL, Location and Pushbullet plugins and they show on the toolbar fine, however the plugin icon itself has disappeared.

If I navigate to Fog Configuration > Fog Settings > Plugin System I can see that the checkbox is not ticked. No problem, tick box and click Save. Still no icon. Go back to Fog Configuration > Fog Settings > Plugin System again and once more it’s unchecked.

@jbob thanks for confirming pushbullet not working. Is a fix in the works? If so I’ll leave it enabled for now and wait on that. If not I can just remove it - assuming i can get the plugin system itself showing again

thanks, Kiweegie

@Wayne-Workman Hi Wayne, I could get past the issue and have the plugins installed now but it may throw off new users hence reason I flagged up.

Additionally the pushbullet plugin does not seem to be accepting tokens. Not a deal breaker for me but again just pointing it out to add to the snagging list.

Cheers, Kiweegie.

Just a heads up re some visual/browser issues in the plugins section of latest release.

I’m updated to latest release 4340 as at Friday 13th Nov 15 to get around an issue with snapin removal and a small bug with the location plugin which Tom Elliot kindly resolved.

Clean reinstall of FOG and am in process of adding in plugins. I can enable the plugins system but as soon as I try and activate one of the plugins - I’m interested in the Locations, WOL and Pushbullet specifically - the browser just flashes.

Example GIF can be seen here:

I’ve found it is possible to click on the plugin and have it activate but takes a few tries to get right. This is happening on Chrome and Firefox. I tried looking at it in IE too (ugh) and in there IE12 on Win 8.1 the front page of FOG web GUI is blank with just a series of bullet points down left hand side. Moving cursor over the page does highlight clickable content (cursor changes to hand icon and the URL shows in popup at bottom of page).

regards Kiweegie.

Ninja-Edit:

Some issues on the WOL plugin also

I can add new entries but cannot display the entries once added. Also the menu (see URL below) for “List all broadcasts” reads as “List all s”

http://FOG_Server_IP/fog/management/index.php?node=wolbroadcast&sub=list

@Tom-Elliott Hi Tom

I meant I manually removed the snapin from /opt/fog/snapins folder on the server, was looking for a way to remove reference to same in the DB/Web GUI.

It doesnt’ matter now though I’ve just rebuilt Fog having backed up image and snapins etc I need.

Mark this one as resolved, thanks for your efforts.

regards Kiweegie.