Posts made by Neil Underwood

@wayne-workman Thanks for that! I’ll play around with it and see what happens!

@wayne-workman I don’t need anything fancy like a gui tool in the dashboard. I just want to know which file I need to edit. Should be something in the source or config files somewhere that I can monkey with this. The old color scheme was much better when there were at least 4 or 5 different colors. The graph has to be picking from some arbitrary set of predetermined colors, no?

When I upload an image and replication kicks off I like to be able to look at this graph and at a glance determine whether or not bandwidth rules are being obeyed. When multiple nodes have the same exact color the graph, for me at least, is pretty useless.

Our latest update to FOG changed the color scheme on the bandwidth graph.

With 11 devices sending and receiving this becomes incredibly confusing now:

Where can I make a change to this color scheme?

Cool. Thanks Tom!

I don’t think there is an actual communication issue, but this is what I saw when looking through my logs for a completely separate issue:

I know all my nodes are online and the Dashboard shows the correct info on the graphs. Any ideas here?

@Joe-Schmitt helped me in a private chat just now. My bandwidth has returned to normal. Thanks for the awesome support as always guys.

@Tom-Elliott LOL no offense taken. Yes , I clicked save each time.

@Joe-Schmitt said in Fog Client is not updating:

@Neil-Underwood Are you sure you disabled the new client updating and not the legacy’s?

You can find the new client’s auto updater setting at : FOG Configuration -> FOG Settings -> FOG Client -> FOG_CLIENT_AUTOUPDATE. Once applied your network usage should return to normal very quickly.

Yep. I’ve toggled it and rebooted in between and it is having zero effect. See the screenshots:

I want to hop on here and add that I’m experiencing the same issue. Mine, however, is not responding when I disable the client updater. It’s still communicating with hosts and trying to push the client out. I came in this morning to find that FOG had tried to push out almost half a TB over the weekend. Take a look at my bandwidth usage:

@Joe-Schmitt said in Constant bandwidth suck:

Either re run your fog server installer or upgrade. The smart installer can’t be downloaded from your server. This means it wasn’t obtained properly when you last upgraded your server.

I moved .fogsettings to .fogsettings.old and ran the upgrade. Seems to have fixed all my remaining issues, including my broken replication. Thanks for that. I’ve been upgrading regularly for months now and I’m not sure now if it’s just coincidence that I moved .fogsettings and let it regenerate. In any case, looks like I’m back to normal here. Thanks again.

@Joe-Schmitt said in Constant bandwidth suck:

Need a fog.log from a host.

I do see some errors in the log:

------------------------------------------------------------------------------
 7/8/2016 10:14 AM Client-Info Client Version: 0.10.5
 7/8/2016 10:14 AM Client-Info Client OS:      Windows
 7/8/2016 10:14 AM Client-Info Server Version: 8215
 7/8/2016 10:14 AM Middleware::Response Success
 7/8/2016 10:14 AM Middleware::Communication Download: http://192.168.19.200/fog/client/SmartInstaller.exe
 7/8/2016 10:20 AM Middleware::Communication ERROR: Could not download file
 7/8/2016 10:20 AM Middleware::Communication ERROR: The operation has timed out.
 7/8/2016 10:20 AM Data::RSA FOG Project cert found
 7/8/2016 10:20 AM ClientUpdater Update file is authentic
------------------------------------------------------------------------------

 7/8/2016 10:20 AM Bus {
  "self": true,
  "channel": "Update",
  "data": "{\r\n  \"action\": \"start\"\r\n}"
}
 7/8/2016 10:20 AM Bus Emmiting message on channel: Update
 7/8/2016 10:20 AM Service-Update Spawning update helper
 7/8/2016 10:20 AM UpdaterHelper Shutting down service...
 7/8/2016 10:20 AM UpdaterHelper Killing remaining processes...
 7/8/2016 10:20 AM UpdaterHelper Applying update...
 7/8/2016 10:20 AM Process ERROR: Unable to run process
 7/8/2016 10:20 AM Process ERROR: The specified executable is not a valid application for this OS platform.
 7/8/2016 10:20 AM UpdaterHelper Starting service...
 7/8/2016 10:20 AM Main Overriding exception handling
 7/8/2016 10:20 AM Main Bootstrapping Zazzles
 7/8/2016 10:20 AM Controller Initialize
 7/8/2016 10:20 AM entry Creating obj
 7/8/2016 10:20 AM Controller Start

 7/8/2016 10:20 AM Service Starting service
 7/8/2016 10:20 AM Service ERROR: Could not clear last session data
 7/8/2016 10:20 AM Service ERROR: Access to the path 'FOGUpdateHelper.exe' is denied.
 7/8/2016 10:20 AM Bus Became bus server
 7/8/2016 10:20 AM Bus {
  "self": true,
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 7/8/2016 10:20 AM Bus Emmiting message on channel: Status

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 7/8/2016 10:20 AM Client-Info Version: 0.10.5
 7/8/2016 10:20 AM Client-Info OS:      Windows
 7/8/2016 10:20 AM Middleware::Authentication Waiting for authentication timeout to pass
 7/8/2016 10:20 AM Middleware::Communication Download: http://192.168.19.200/fog/management/other/ssl/srvpublic.crt
 7/8/2016 10:20 AM Data::RSA FOG Server CA cert found
 7/8/2016 10:20 AM Middleware::Authentication Cert OK
 7/8/2016 10:20 AM Middleware::Communication POST URL: http://192.168.19.200/fog/management/index.php?sub=requestClientInfo&authorize&newService
 7/8/2016 10:20 AM Middleware::Response Success
 7/8/2016 10:20 AM Middleware::Authentication Authenticated


 7/8/2016 10:20 AM Bus Registering ParseBus in channel Power
 7/8/2016 10:20 AM Middleware::Communication URL: http://192.168.19.200/fog/management/index.php?sub=requestClientInfo&mac=F8:BC:12:6D:FB:43||00:00:00:00:00:00:00:E0&newService&json
 7/8/2016 10:20 AM Middleware::Response Success
 7/8/2016 10:20 AM Middleware::Communication URL: http://192.168.19.200/fog/service/getversion.php?clientver&newService&json
 7/8/2016 10:20 AM Middleware::Communication URL: http://192.168.19.200/fog/service/getversion.php?newService&json

 7/8/2016 10:20 AM Service Creating user agent cache
 7/8/2016 10:20 AM Middleware::Response Module is disabled globally on the FOG server
 7/8/2016 10:20 AM Middleware::Response No Printers

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 7/8/2016 10:20 AM Client-Info Client Version: 0.10.5
 7/8/2016 10:20 AM Client-Info Client OS:      Windows
 7/8/2016 10:20 AM Client-Info Server Version: 8215
 7/8/2016 10:20 AM Middleware::Response Success
 7/8/2016 10:20 AM Middleware::Communication Download: http://192.168.19.200/fog/client/SmartInstaller.exe
 7/8/2016 10:25 AM Middleware::Communication ERROR: Could not download file
 7/8/2016 10:25 AM Middleware::Communication ERROR: The operation has timed out.
 7/8/2016 10:25 AM Data::RSA FOG Project cert found
 7/8/2016 10:25 AM ClientUpdater Update file is authentic
------------------------------------------------------------------------------

 7/8/2016 10:25 AM Bus {
  "self": true,
  "channel": "Update",
  "data": "{\r\n  \"action\": \"start\"\r\n}"
}
 7/8/2016 10:25 AM Bus Emmiting message on channel: Update
 7/8/2016 10:25 AM Service-Update Spawning update helper
 7/8/2016 10:25 AM UpdaterHelper Shutting down service...
 7/8/2016 10:25 AM UpdaterHelper Killing remaining processes...
 7/8/2016 10:25 AM UpdaterHelper Applying update...
 7/8/2016 10:25 AM Process ERROR: Unable to run process
 7/8/2016 10:25 AM Process ERROR: The specified executable is not a valid application for this OS platform.
 7/8/2016 10:25 AM UpdaterHelper Starting service...
 7/8/2016 10:25 AM Main Overriding exception handling
 7/8/2016 10:25 AM Main Bootstrapping Zazzles
 7/8/2016 10:25 AM Controller Initialize
 7/8/2016 10:25 AM entry Creating obj
 7/8/2016 10:25 AM Controller Start

 7/8/2016 10:25 AM Service Starting service
 7/8/2016 10:25 AM Service ERROR: Could not clear last session data
 7/8/2016 10:25 AM Service ERROR: Access to the path 'FOGUpdateHelper.exe' is denied.
 7/8/2016 10:25 AM Bus Became bus server
 7/8/2016 10:25 AM Bus {
  "self": true,
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 7/8/2016 10:25 AM Bus Emmiting message on channel: Status

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 7/8/2016 10:25 AM Client-Info Version: 0.10.5
 7/8/2016 10:25 AM Client-Info OS:      Windows
 7/8/2016 10:25 AM Middleware::Authentication Waiting for authentication timeout to pass
 7/8/2016 10:25 AM Middleware::Communication Download: http://192.168.19.200/fog/management/other/ssl/srvpublic.crt
 7/8/2016 10:25 AM Data::RSA FOG Server CA cert found
 7/8/2016 10:25 AM Middleware::Authentication Cert OK
 7/8/2016 10:25 AM Middleware::Communication POST URL: http://192.168.19.200/fog/management/index.php?sub=requestClientInfo&authorize&newService
 7/8/2016 10:25 AM Middleware::Response Success
 7/8/2016 10:25 AM Middleware::Authentication Authenticated


 7/8/2016 10:25 AM Bus Registering ParseBus in channel Power
 7/8/2016 10:25 AM Middleware::Communication URL: http://192.168.19.200/fog/management/index.php?sub=requestClientInfo&mac=F8:BC:12:6D:FB:43||00:00:00:00:00:00:00:E0&newService&json
 7/8/2016 10:25 AM Middleware::Response Success
 7/8/2016 10:25 AM Middleware::Communication URL: http://192.168.19.200/fog/service/getversion.php?clientver&newService&json
 7/8/2016 10:25 AM Middleware::Communication URL: http://192.168.19.200/fog/service/getversion.php?newService&json

 7/8/2016 10:25 AM Service Creating user agent cache
 7/8/2016 10:25 AM Middleware::Response Module is disabled globally on the FOG server
 7/8/2016 10:25 AM Middleware::Response No Printers

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 7/8/2016 10:25 AM Client-Info Client Version: 0.10.5
 7/8/2016 10:25 AM Client-Info Client OS:      Windows
 7/8/2016 10:25 AM Client-Info Server Version: 8215
 7/8/2016 10:25 AM Middleware::Response Success
 7/8/2016 10:25 AM Middleware::Communication Download: http://192.168.19.200/fog/client/SmartInstaller.exe
 7/8/2016 10:30 AM Middleware::Communication ERROR: Could not download file
 7/8/2016 10:30 AM Middleware::Communication ERROR: The operation has timed out.
 7/8/2016 10:30 AM Data::RSA FOG Project cert found
 7/8/2016 10:30 AM ClientUpdater Update file is authentic
------------------------------------------------------------------------------

@Junkhacker said in Constant bandwidth suck:

what version of client? automatic updating enabled?

The 2 I checked appear to be running 0.10.5

Client updater is enabled globally

Lately I’ve noticed there’s been constant activity on the bandwidth graph on the FOG Dashboard. I didn’t realize how bad it was until I looked at the stats for the past week in our firewall:

I’m taking a constant 5M+ hit from the FOG server on our MPLS network. Checking jnettop I see this:

It looks as if every client is constantly trying to download the SmartInstaller.exe, over and over.

I’m on version 8215; Ubuntu 14.04

That’s good news. That video pretty much answered all my questions. Thanks a bunch.

I have 10 nodes, 9 and a master, all in different geographic locations. For the longest time everything has worked fine with all the clients PXE booting to the master node. We’ve recently started having some issues, one of them being bzImage getting stuck at 99% any time a task is attempting to run. Another issue started with the introduction of a wireless bridge that I don’t think is passing the DHCP request properly.

I’m wondering if it’s possible to make each site PXE boot to the local FOG node, rather than the master. I think this will eliminate the DHCP request issue over the wireless bridge.

I’m also wondering about the option here:

Will enabling this option force the client to download bzImage from the local node? If so, that should probably solve my other issue. Is it really that simple?

@Tom-Elliott said in FOGImagereplicator not working:

@Neil-Underwood DHCP Server if FOG is to be the dhcp server.

It defines the start and end range of DHCP.

Got it. So this does not apply to my setup then. Must have been defined a long time ago when I was playing with that. Thanks!

OK so I’m updated to 8215 now and everything seems to be able to see each other. It looks like the main server is pushing our the smartinstaller.exe to all the clients and that’s the activity I’ve been seeing on the graph. Hard to catch that using jnettop at first.

Thanks for all the assistance with this. I’ll open a separate thread for the log issue and another for the bzImage problem.

One more quick question though. What are these values used for?

startrange='192.168.19.10'
endrange='192.168.19.254'

@Wayne-Workman said in FOGImagereplicator not working:

@Neil-Underwood said in FOGImagereplicator not working:

w do I fix this? And how in the heck did it break in the first place?

Probably the server is only allowing local connections. There’s stuff about that in here:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL

“Enable Remote MySQL Access”

I must have overlooked the part about remote access because I visited this page earlier this morning. I fixed the remote permissions and now everything is able to see the DB. Thanks for that. I did do an OS upgrade that probably changed mysql versions. I’m betting that’s what screwed it up.

The mystery of where my log info is going still remains, however.

Also, on the dashboard the replicator appears to be working, based on the graph. But running jnettop from the master storage node doesn’t show any replication activity. If I can get my logs working again I’m certain I can figure out what the problem is.

OK, so now I’m seeing that I can’t connect to the master storage node DB from the remote storage nodes. I know as much about SQL commands and permissions as my left shoe. How do I fix this? And how in the heck did it break in the first place?

@Wayne-Workman said in FOGImagereplicator not working:

Looking at that picture, this issue is possibly related: https://forums.fogproject.org/topic/7825/db/17

You know, that prompted me to look at class.config.php and I think the DATABASE_HOST value is wrong, but I really don’t know. Can you verify this is correct? Should the “p:” be in there proceeding the IP address?

define('DATABASE_HOST','p:127.0.0.1');

I tried changing it and removing the “p:” and nothing seemed to change (after restarting php, mysql & apache just to be sure)