Okay. So here’s what’s happening for me and what I suspect is happening for @AndersonJ as well. @tom-elliott was right, the setting was wrong under “storage management”>“DefaultMember”>“interface”. So the udp-sender would start, then end itself when it realized it was started with an invalid interface. Thanks for the help, everyone.

What’s the name of the image you’re trying to deploy?

What’s the name of the image you’re trying to deploy?

Didn’t know that button existed. Thanks. That did it, but now the clients are trying to update to 0.9.5 automatically, and all they succeed in doing is uninstall the old version. I’ll probably have to push out 0.9.5 in an image, but I thought I’d let you know

I’m running the lastest git build as of today maybe a half hour ago. I uninstalled the old client service from the client, removed the FOG certificate, downloaded the latest one from the server, and installed it, but I’m still having an issue with the hostname changer, as you can see in the fog.log

@Wayne-Workman 1.2.0 (it’s one of the tags)

Okay. So here’s what’s happening for me and what I suspect is happening for @AndersonJ as well. @tom-elliott was right, the setting was wrong under “storage management”>“DefaultMember”>“interface”. So the udp-sender would start, then end itself when it realized it was started with an invalid interface. Thanks for the help, everyone.

@Wayne-Workman I checked that, but I’ll check @tom-elliott’s suggestion next time I’m working with it.

@Tom-Elliott

Where else is there besides that setting in the web interface that you just said is not used anymore, and in .fogsettings? Both of those are right.

I forget. I’m not at work right now. Whatever the latest git version was at about 1800 UTC-6 yesterday.

Hello. I’ve noticed an issue where FOG is not using the correct interface when starting udp-sender, which results in it quitting right away and not running the multicast task. My interface name, as specified in fog_udpcast_interface is “enp4s0” but FOG appears to keep trying to use “eth0”, as shown in the log below

[09-08-15 11:37:49 pm]  * No tasks found!
[09-08-15 11:37:59 pm]  | Sleeping for 10 seconds to ensure tasks are properly submitted
[09-08-15 11:38:09 pm]  | Task (48) abc is new!
[09-08-15 11:38:09 pm]  | Task (48) abc has been cleaned.
[09-08-15 11:38:09 pm]  | Task (48) /images/OldAcer image file found.
[09-08-15 11:38:09 pm]  | Task (48) 1 client(s) found.
[09-08-15 11:38:09 pm]  | Task (48) abc sending on base port: 62188
[09-08-15 11:38:09 pm]  | CMD: cat /images/OldAcer/d1p1.img | /usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 660 --portbase 62188 --full-duplex --ttl 32 --nokbd --nopointopoint;cat /images/OldAcer/d1p2.img | /usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 660 --portbase 62188 --full-duplex --ttl 32 --nokbd --nopointopoint;
[09-08-15 11:38:09 pm]  | Task (48) abc has started.
[09-08-15 11:38:19 pm]  | Task (48) abc is no longer running.
[09-08-15 11:38:19 pm]  | Task (48) abc has been cleaned as complete.
[09-08-15 11:38:29 pm]  | Task (48) abc is new!
[09-08-15 11:38:29 pm]  | Task (48) abc has been cleaned.
[09-08-15 11:38:29 pm]  | Task (48) /images/OldAcer image file found.
[09-08-15 11:38:29 pm]  | Task (48) 1 client(s) found.
[09-08-15 11:38:29 pm]  | Task (48) abc sending on base port: 62188
[09-08-15 11:38:29 pm]  | CMD: cat /images/OldAcer/d1p1.img | /usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 120 --portbase 62188 --full-duplex --ttl 32 --nokbd --nopointopoint;cat /images/OldAcer/d1p2.img | /usr/local/sbin/udp-sender --interface eth0 --min-receivers 1 --max-wait 120 --portbase 62188 --full-duplex --ttl 32 --nokbd --nopointopoint;
[09-08-15 11:38:29 pm]  | Task (48) abc has started.
[09-08-15 11:38:39 pm]  | Sleeping for 10 seconds to ensure tasks are properly submitted
[09-08-15 11:38:49 pm]  | Task (48) abc is no longer running.
[09-08-15 11:38:49 pm]  | Task (48) abc has been cleaned as complete.

Additionally, the log file for that task “multicast.log.udpcast.48”

Udp-sender 20120424
No suitable network interface found
The following interfaces are available:
        lo      127.0.0.1
        enp4s0  10.255.6.20
cat: write error: Broken pipe
Udp-sender 20120424
No suitable network interface found
The following interfaces are available:
        lo      127.0.0.1
        enp4s0  10.255.6.20
cat: write error: Broken pipe

@Wayne-Workman I have been working with him a little and looking at his logs and I think I see something. Where does fog pull the interface to use for udp-sender from? Because for me it keeps using the wrong interface name when starting udp-sender and I suspect it’s doing the same for him.