Posts made by Joe Gill

Joe Gill

Will do. I’ll tail those files and see what happens when I create a new task. I’ll report back! Thanks!

Joe Gill

Which files would you like me to pull for you?

Joe Gill

MariaDB [fog]> SELECT * FROM multicastSessionsAssoc;
+-------+------+-----+
| msaID | msID | tID |
+-------+------+-----+
|    57 |    0 |  87 |
|    56 |    0 |  86 |
|    55 |    0 |  85 |
|    54 |    0 |  84 |
|    53 |    0 |  83 |
|    52 |    0 |  82 |
|    51 |    0 |  81 |
|    50 |    0 |  80 |
|    49 |    0 |  79 |
|    48 |    0 |  78 |
|    47 |    0 |  77 |
|    46 |    0 |  76 |
|    45 |    0 |  75 |
|    44 |    0 |  74 |
|    43 |    0 |  73 |
|    42 |    0 |  72 |
|    41 |    0 |  71 |
|    40 |    0 |  70 |
|    39 |    0 |  69 |
|    38 |    0 |  68 |
|    37 |    0 |  67 |
|    36 |    0 |  66 |
|    35 |    0 |  65 |
|    34 |    0 |  64 |
|    33 |    0 |  63 |
|    32 |    0 |  62 |
|    31 |    0 |  61 |
|    30 |    0 |  60 |
+-------+------+-----+
28 rows in set (0.00 sec)

MariaDB [fog]>

Joe Gill

@Sebastian-Roth

[jgill@fogserver log]$ systemctl status FOGMulticastManager
● FOGMulticastManager.service - FOGMulticastManager
   Loaded: loaded (/usr/lib/systemd/system/FOGMulticastManager.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2019-06-12 09:22:41 MDT; 1h 31min ago
 Main PID: 5610 (FOGMulticastMan)
   CGroup: /system.slice/FOGMulticastManager.service
           ├─5610 /usr/bin/php -q /opt/fog/service/FOGMulticastManager/FOGMulticastManager &
           └─5613 /usr/bin/php -q /opt/fog/service/FOGMulticastManager/FOGMulticastManager &

Jun 12 09:22:41 fogserver.bhs.tn systemd[1]: Started FOGMulticastManager.
[jgill@fogserver log]$

Joe Gill

@Fernando-Gietz

Screenshot from 2019-06-12 10-51-45.png

Joe Gill

@Fernando-Gietz

MariaDB [fog]> SELECT * FROM multicastSessions;
Empty set (0.00 sec)

MariaDB [fog]> SELECT * FROM multicastAssoc;
ERROR 1146 (42S02): Table 'fog.multicastAssoc' doesn't exist
MariaDB [fog]>

Joe Gill

@Sebastian-Roth
@Fernando-Gietz

Here is the latest…

[jgill@fogserver log]$ ls -lar
total 80
-rw-r--r--. 1 root root  4056 Jun 12 09:22 servicemaster.log
-rw-r--r--. 1 root root  1433 Jun 12 09:31 pinghost.log
-rw-r--r--. 1 root root  3471 Jun 12 09:31 multicast.log
-rw-r--r--. 1 root root 28408 Jun 12 09:22 groupmanager.log
-rw-r--r--. 1 root root  7770 Jun 12 09:22 fogsnapinrep.log
-rw-r--r--. 1 root root  4559 Jun 12 09:22 fogsnapinhash.log
-rw-r--r--. 1 root root  1812 Jun 12 09:30 fogscheduler.log
-rw-r--r--. 1 root root  8714 Jun 12 09:22 fogreplicator.log
-rw-r--r--. 1 root root  4462 Jun 12 09:22 fogimagesize.log
drwxr-xr-x. 5 root root    67 Jun 12 09:23 ..
drwxr-xr-x. 2 root root   218 Jun 12 09:22 .
[jgill@fogserver log]$

06-12-19 9:22:41 am]
==================================
===        ====    =====      ====
===  =========  ==  ===   ==   ===
===  ========  ====  ==  ====  ===
===  ========  ====  ==  =========
===	 ====  ====  ==  =========
===  ========  ====  ==  ===   ===
===  ========  ====  ==  ====  ===
===  =========  ==  ===   ==   ===
===  ==========    =====      ====
==================================
===== Free Opensource Ghost ======
==================================
============ Credits =============
= https://fogproject.org/Credits =
==================================
== Released under GPL Version 3 ==
==================================


[06-12-19 9:22:41 am] Interface Ready with IP Address: 127.0.0.1
[06-12-19 9:22:41 am] Interface Ready with IP Address: 127.0.1.1
[06-12-19 9:22:41 am] Interface Ready with IP Address: 172.16.1.19
[06-12-19 9:22:41 am] Interface Ready with IP Address: fogserver.bhs.tn
[06-12-19 9:22:41 am]  * Starting MulticastManager Service
[06-12-19 9:22:41 am]  * Checking for new items every 10 seconds
[06-12-19 9:22:41 am]  * Starting service loop
[06-12-19 9:22:41 am]  * No new tasks found
[06-12-19 9:22:51 am]  * No new tasks found
[06-12-19 9:23:01 am]  * No new tasks found
[06-12-19 9:23:11 am]  * No new tasks found
[06-12-19 9:23:21 am]  * No new tasks found
[06-12-19 9:23:31 am]  * No new tasks found
[06-12-19 9:23:41 am]  * No new tasks found
[06-12-19 9:23:51 am]  * No new tasks found
[06-12-19 9:24:01 am]  * No new tasks found
[06-12-19 9:24:11 am]  * No new tasks found
[06-12-19 9:24:21 am]  * No new tasks found
[06-12-19 9:24:31 am]  * No new tasks found
[06-12-19 9:24:42 am]  * No new tasks found
[06-12-19 9:24:52 am]  * No new tasks found
[06-12-19 9:25:02 am]  * No new tasks found
[06-12-19 9:25:12 am]  * No new tasks found
[06-12-19 9:25:22 am]  * No new tasks found

Nothing is showing up in the logs at all.

And from the web interface…

Screenshot from 2019-06-12 09-34-06.png

Joe Gill

@Fernando-Gietz
@Sebastian-Roth

Well the problem persists on the new server… Multicast.log shows no new tasks and zero multicast.log.udpcstxxxx files in the /opt/fog/log directory. I’m betting the database issues persist on. I’ll be in first thing tomorrow morning. (7AM MST)

Cheers!

Joe Gill

@Sebastian-Roth

Yes I did. It didn’t help any.

Joe Gill

@Developers

Any ideas here?

Thanks!

Joe Gill

@george1421
@Tom-Elliott

Well I removed .fogsettings file and re-ran the installer. This made no difference on the FOG settings. I removed FOG entirely (minus my images). Re-ran the installer and re-migrated my DB over to the new install and my storage node came back. As a test, I tried adding a new storage node (not as a master) and it still would not allow me to add any new storage nodes or make changes to my existing storage node.

Any suggestions is greatly appreciated!

Thanks!

Joe Gill

@george1421

Thanks George! I’ll give that try and re-post results. I know it has to be something simple. I just can’t wrap my head around it.

Joe Gill

@Fernando-Gietz

What shows up in the UDP log is from over a year ago when I messed with multi-cast last. I am working on building a new server.

Thanks!

Joe Gill

FOG Ver. – 1.5.6.4
OS – CentOS Linux release 7.6.1810 (Core)

I just migrated over from Debian 9.9 on a new FOG server build to CentOS. Everything is up and running except for multicasting. I was getting an error stating “Fog Server not Master Node”. I went through all of the config changes and updated all instances of username and password found in /opt/fog/.fogsettings file. When doing so, I noticed that the Fog Storage Node would not let me change the IP Address or username. It would say it updated but when I refreshed things it was not updating. I tried a different browser and the problem persisted. So I decided to delete the FOG storage node and re-add it. When I re-added it, the storage node never appeared in the list. I have rebooted the server and restarted all services with no luck in getting my storage node back.

I don’t know if this is the appropriate place to post this or not. Please move this if it is not.

Thanks!

Cheers,

Joe

Joe Gill

@Sebastian-Roth

Yeah I would rather not re-build my DB from scratch if at all possible. I have fewer hosts now than when I started with FOG but it’s still a large number. I am in the process of setting up another FOG server to do a fresh install and go from there. I do need to clean some things up in there so it may be the time to do this. I did run through the Troubleshoot MySQL Database Maintenance Commands and didn’t get real far with it. I"ll look at that once more before I bite the bullet on starting over.

I’ll post back to the other thread I started. Hopefully I can figure something out without having to re-do the entire DB…

Thanks for all of your help! I know you guys put in a ton of time with FOG and it’s very appreciated!!

Cheers!

Joe

Joe Gill

@Sebastian-Roth

Yes. It shows up there like normal. Just nothing in the log.

Joe Gill

@george1421
@tandersb

I agree with George… I had one setup for a bit when I first started with FOG… It was a nightmare. I had nothing but issues. I switched to just using the server as the storage node. Works great!

Joe Gill

@Sebastian-Roth Any ideas here?

Joe Gill

FOG Version – 1.5.6.3
FOG Server OS – Debian 9.9

Hi all,

I ran into a problem Multi-Casting machines. I get the following message on my HOST.

Here is /opt/fog/log/multicast.log

[06-06-19 11:11:14 am]
==================================
===        ====    =====      ====
===  =========  ==  ===   ==   ===
===  ========  ====  ==  ====  ===
===  ========  ====  ==  =========
===      ====  ====  ==  =========
===  ========  ====  ==  ===   ===
===  ========  ====  ==  ====  ===
===  =========  ==  ===   ==   ===
===  ==========    =====      ====
==================================
===== Free Opensource Ghost ======
==================================
============ Credits =============
= https://fogproject.org/Credits =
==================================
== Released under GPL Version 3 ==
==================================


[06-06-19 11:11:14 am] Interface Ready with IP Address: 127.0.0.1
[06-06-19 11:11:14 am] Interface Ready with IP Address: 127.0.1.1
[06-06-19 11:11:14 am] Interface Ready with IP Address: 172.16.1.17
[06-06-19 11:11:14 am] Interface Ready with IP Address: fogserver
[06-06-19 11:11:14 am]  * Starting MulticastManager Service
[06-06-19 11:11:14 am]  * Checking for new items every 10 seconds
[06-06-19 11:11:14 am]  * Starting service loop
[06-06-19 11:11:14 am]  * No new tasks found
[06-06-19 11:11:24 am]  * No new tasks found
[06-06-19 11:11:34 am]  * No new tasks found
[06-06-19 11:11:44 am]  * No new tasks found
[06-06-19 11:11:54 am]  * No new tasks found

I also tested Multicast in debug mode on a particular machine I was having issues getting FOG to start multicasting to and the test worked just fine. It appears that FOG doesn’t recognize that an event has started. I have tried killing all multitask sessions, killing the multicast session PID, stopping and restarting multicast, restarting the server, running an update on the FOG server, clearing any flags in the SQL database, nothing has worked.

Any help is greatly appreciated!

Thanks!

Cheers,

Joe

Joe Gill

@phishphan

I have had this happen before. Usually it’s a setting issue within Windows 10 that has to be addressed. I had a lot of issues imaging the latest version of the Windows 10 kernel. I ended up having to run sysprep and make some modifications to my unattend.xml file. Once I did that it worked well.

I’m sure @Wayne-Workman will have some ideas.