Posts made by awellis

OK thanks! I really appreciate how active you guys are here!

@Sebastian-Roth It actually started working for us. I had it setup initially as “Only Assigned Printers” when it wasn’t working originally, save for 2 of the computers. The next day, I changed it to “FOG Managed Printers” though, and they all started showing up (without having to manually add a printer this time).

Driver was in the same place on every computer (the computers were imaged with it in place) so that shouldn’t be the issue. The logs may have been different because I have 12 computers, and each pair share 1 of 6 printers (which is why I’m wanting to use this vs AD). I wish I could figure out how to replicate the issue, but the lab is currently live and I can’t take it down for testing. If you want, I can try to work on it again when the labs are free in about a week though.

Alrighty Here’s a screenshot of the settings: https://imgur.com/a/BOFyJvG

Here’s a pastbin of the log for a computer that did have the printer added: https://pastebin.com/raw/WuyZYuc1
and here’s one for a computer that did not have it added: https://pastebin.com/raw/4Rb0Hzv6 - 3:10PM is where it looks like it added the printer, but it isn’t there.

For the second one (not added), I actually tried adding the computer first as I did with some of the others, and the fog client deleted it without actually adding the one I need.

I have what is a weird problem to me. I have a group of 12 computers (running windows 10 1903) that I have been using FOG to image, and the image goes fine. However, the printers I set up for them do not add right away. Fog is fully managing the printers, but the 1 printer I have added for each computer does not come up until I manually add a printer. The printer I add hasn’t mattered so far, but within 30 seconds of adding that printer, the FOG client removes it and adds the correct one. Is this normal/intended behavior? Should I add a random printer to my image? (does sysprep remove printers?)

Like I mentioned, FOG is fully managing printers. fog.log says the printer is already added before I’ve added the extra printer, even though it doesn’t show up.

I forgot to mention that I am still able to ssh into both boxes and the loads are well below 0.5

I’m having a strange issue where I can’t get a storage node working. My goal is to be able to do multicast for a remote lab, so my thought was to setup a second fog server (running centos 7) as a storage node and set that up on the switch in that room. I then wanted to setup locations and put those computers in a location with the remote node. So I did that (following https://wiki.fogproject.org/wiki/index.php/Managing_FOG#Storage_Management) and suddenly I was no longer able to connect to the web interface on the master node due to a “Service Unavailable” error page. I figured out that I can get to it if I shut down the storage node, but if I bring it back up the error pages come back. I also get a large Service Unavailable in the image replicator log. Does anyone know what is causing this, and if fog actually works the way I’m hoping (I saw something saying storage nodes were used for speeding up unicast, but those were older messages so I’m not sure if that’s true or not anymore). Thanks in advance!

@george1421 Didn’t see any packets except for a single UDP packet every 2 seconds or so after the client checked in and loaded up into partclone. Turned out there’s some hardware issue with the server I had been using. Thanks for your help!

So I went ahead and installed fog and centos on a different (much older) machine and it worked fine. Looks like there’s some hardware issue with the original server I had been using, but that issue is not the NIC because I also tried a new one of those to no avail. Thanks for all your help @george1421!

Correct on all counts. Its running on a single switch on the same subnet. I did hook up wireshark and saw all the messages go back and forth with the initial test, but when running fog, the server just sends the one packet out and nothing else happens

@george1421 Did another full reinstall with a different NIC just in case and still nothing. Any chance the type of image taken matters? Partclone vs partimage? compression?

@george1421 No it’s bare metal ATM. I’m going to just do a reinstall and see if that fixes it, since at this point I don’t know what else could be going wrong. Did you do anything special with the install or just basically fog installer on the fresh install?

@sebastian-roth said in FOG Multicast Not working:

It was scheduled for 3 clients and all 3 opened up partclone. That said, shouldn’t the timeout kick in after 10 minutes and go off anyway?

I did check for the udp process and it is running after starting it. I’ve also tried running it immediately after a server restart and no udp processes running and no tasks scheduled.

edit: FOG does start up 2 separate udp-senders with the task… is that normal?

edit 2: looks like there’s 1 task for each partition

It actually does join the session, the session just never starts. I left it running overnight yesterday and all the computers got to the blue partclone screen and just sat there. I don’t recall if I did the same thing with just 1 multicast host but Ill give that a shot tomorrow morning when I get back to the office

@george1421 Yes they are all on the same subnet

@george1421 I don’t think the firewall should be an issue for FOG (just udp-sender/udp-receiver), as I don’t see any traffic hitting any port but 59106 and the ones after that, but I did disable the firewall and am still seeing the same issue.

@george1421 Sure. On the Centos 7 Wiki Installation page (https://wiki.fogproject.org/wiki/index.php?title=CentOS_7#Continue_pre-config) the instructions say “Open UDP port 49152 through 65532” and don’t mention port 9000 at all

Some More testing.

I ran the 2 host file test and the 2 host partclone test. The file test seemed to work fine, but the partclone manual multicast test did not. Got this on the server:

Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
Timeout notAnswered=[0,1] notReady=[0,1] nrAns=0 nrRead=0 nrPart=2 avg=10000
Dropping client #0 because of timeout
Disconnecting #0 (192.168.0.187)
Dropping client #1 because of timeout
Disconnecting #1 (192.168.0.169)
bytes=                re-xmits=0000000 (  0.0%) slice=0130 -   0
Transfer complete.

Getting a bit farther…

I realized the problem with my test previously was the udp-sender command runs on 9000/udp, whereas the initial firewall setup did not allow that port so I changed the port and that worked fine. Going back to the multicast log file, I get this when I try running the multicast restore:

[03-27-18 6:25:11 pm]  | Task (7) Multi-Cast Task is new!
[03-27-18 6:25:11 pm]  | Task (7) /images/3450_lab_img image file found.
[03-27-18 6:25:11 pm]  | Task (7) Multi-Cast Task 3 clients found.
[03-27-18 6:25:11 pm]  | Task (7) Multi-Cast Task sending on base port: 59106.
[03-27-18 6:25:11 pm]  | Command: /usr/local/sbin/udp-sender --interface em2 --min-receivers 3 --max-wait 600 --portbase 59106 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/3450_lab_img/d1p1.img;/usr/local/sbin/udp-sender --interface em2 --min-receivers 3 --max-wait 10 --portbase 59106 --full-duplex --ttl 32 --nokbd --nopointopoint --file /images/3450_lab_img/d1p2.img;
[03-27-18 6:25:11 pm]  | Task (7) Multi-Cast Task has started!
[03-27-18 6:25:21 pm]  | Task (7) Multi-Cast Task is already running with pid: 12616.
[03-27-18 6:25:31 pm]  | Task (7) Multi-Cast Task is already running with pid: 12616.
[03-27-18 6:25:41 pm]  | Task (7) Multi-Cast Task is already running with pid: 12616.
[03-27-18 6:25:51 pm]  | Task (7) Multi-Cast Task is already running with pid: 12616.
[03-27-18 6:26:01 pm]  | Task (7) Multi-Cast Task is already running with pid: 12616.
[03-27-18 6:26:11 pm]  | Task (7) Multi-Cast Task is already running with pid: 12616.
[03-27-18 6:26:21 pm]  | Task (7) Multi-Cast Task is already running with pid: 12616.

Still going to keep going with the tests on the multicast page but just wanted to update my situation

I’ve tried it with both a Netgear Prosafe JGS516 and an Asante GX5-2400W (factory settings)

I’ve been trying to get Multicast working with FOG but I’m stuck. Unicast works fine, but multicast just stops at preparing. I went through the troubleshooting steps at https://wiki.fogproject.org/wiki/index.php?title=Troubleshooting_a_multicast#Troubleshooting, but when I try testing with 1 client, I don’t get the .fogsettings file listed (or anything at all). I’ve also tried specifying the interface on the server, and the address on the receiver, but still nothing. multicast log file only shows this:

10:04:18.973480 Using mcast address 232.168.0.100
10:04:18.973604 UDP sender for /opt/fog/.fogsettings at 192.168.0.100 on em2 
10:04:18.973621 Broadcasting control to 192.168.0.255

Server is on 1.5.0, CentOS7. Right now, there is only a simple switch between the server and the client, and the client does boot fine. Anybody know what I’m doing wrong here?