The new options for service sleep times (FogPingHosts and such) is not setting correctly when changed and applied, it is reverting to original settings.
Posts made by Hanz
-
New options for Service Settings for Linux Sleep times not sticking.
-
RE: Multcasting - Hosts Do Not Contain the Same Image Assignments
@Tom-Elliott I just messaged you that SVN 6138 is still throwing this error
-
RE: Ipxe boot Marvel/Yukon nic to FOG successfully
@KKTwenty101 I finally got this to work by updating the bios on my marvel/yukon nic machines.
PXE took off immediately afterwards. Just an option to try. -
RE: Multicast Works from Server, but not from storage node...
@ch3i yes it is the master node. I have one at each school that doesn’t have gigabit service to speed imaging along.
-
Multicast Works from Server, but not from storage node...
The multicast works when the clients are instructed to go to server (via location), and this is from remote location. Just had network team setup WOL and multicast for me (although not sure of specifics with the multicast).
The problem is when the clients are set (via location) to run the multicast from the local storage node (where unicast works, and which is the group (location-based) master node.
It gets to the Partclone screen and hangs, nothing else. Reboots, killall udpsender, and clearing from mysql do not resolve the issue. I’m hoping it’s something in the way FOG “directs” the mutlicast to the storage node and on, since multicast originates from the server itself, or on my end with the multicast settings themselves.
Routers, switches, VLANS all included in topography.
- When directed from both the server and local master storage node i noticed there is no mention of 10.72.216.50 which is storage node IP.
| 1 task found [01-19-16 1:25:25 pm] | Task (8) Multi-Cast Task is new! [01-19-16 1:25:25 pm] | Task (8) Multi-Cast Task has been cleaned. [01-19-16 1:25:25 pm] | Task (8) /images/X131Feb15 image file found. [01-19-16 1:25:25 pm] | Task (8) 2 client(s) found. [01-19-16 1:25:25 pm] | Task (8) Multi-Cast Task sending on base port: 52814 Udp-sender 20120424 Using mcast address 234.72.3.50 UDP sender for (stdin) at 10.72.3.50 on enp0s25 Broadcasting control to 224.0.0.1 [01-19-16 1:25:25 pm] | CMD: cat /images/X131Feb15/d1p1.img | /usr/local/sbin/udp-sender --interface enp0s25 --min-receivers 2 --max-wait 300 --portbase 52814 --full-duplex --ttl 32 --nokbd --nopointopoint;cat /images/X131Feb15/d1p2.img | /usr/local/sbin/udp-sender --interface enp0s25 --min-receivers 2 --max-wait 300 --portbase 52814 --full-duplex --ttl 32 --nokbd --nopointopoint;
But then nothing happens…Any ideas or suggestions ??
-
RE: FOGUserService Net Framework error 64 bit machines
@Jbob I’ll have to try tomorrow and let ya know.
-
RE: Cannot Image HP Stream 11 Netbook
@drc0nc ok I see the part about changing the host disk, but which format are you using ? (Multi part, single part-resize…etc)
-
RE: FOGUserService Net Framework error 64 bit machines
@george1421 That I’m not sure about honestly…What version should I be using ? I’ll have to work on adding a package to update .NET I guess. If I update the .Net framework after FOG, will this fix the issue ?
-
RE: Cannot Image HP Stream 11 Netbook
@mwbutler I’m currently working with this same machine… I did get it to pxe boot after changing option 67 to ipxe.efi. I think I left the legacy support disabled and it took off. Unfortunately my normal images won’t work due to there not being MBR apparently and it doesn’t find the hard drive, so I’m still in testing, but I will let you know.
-
RE: FOGUserService Net Framework error 64 bit machines
@Jbob I am installing the client via gpo as stated above. And I’d like to also mention that this issue only presents itself sometimes.
-
FOGUserService Net Framework error 64 bit machines
I’m getting an error on 64 bit machines that have the new client installed.
Error Parsing C:\Windows\Microsoft.NET\Framework\v4.030319\config\machine.config Parser returned error 0x80070005.
FOGUserService.exe-Configuration Parser Error is the name on the popup box.
I know this is an issue with permissions, but not sure why it’s only happening on these 64 bit machines.
The client is being installed via gpo if that helps. The error pops up immediately upon login.
-
RE: [git 5736] Snap-in installation failes when using sfx files
@Brian-David What was it exactly that was stopping the sfx, but not regular exe 's
-
RE: CentOS 7 - Storage Node installation fails
@Wayne-Workman UPDATE Apparently disabling firewalld.service didn’t stick. Working now
my apologies for assuming it was set correctly. -
RE: CentOS 7 - Storage Node installation fails
@Wayne-Workman That’s odd as all my other existing storage nodes, after update, have the packages= " " empty.
-
RE: CentOS 7 - Storage Node installation fails
@Wayne-Workman when I tried ftp’ing to the server it said ftp wasn’t installed on new node.
this is from /opt/fog/.fogsettings
packages = "httpd php-process";
Other nodes don’t have anything listed here
-
RE: CentOS 7 - Storage Node installation fails
@Wayne-Workman Triple checked all passwords and such along with selinux and firewalld
-
RE: CentOS 7 - Storage Node installation fails
I have a new issue now after this…I had this particular node disabled (old node) when I ran installer for server to update to SVN 5700. After logging back into web UI the storage node is no longer listed…After editing database for storage node, it will not "sync"with server for some reason. Is it ok to delete the node in database and recreate ? Is this what I should do as solution ?
-
RE: CentOS 7 - Storage Node installation fails
I had the same issue as @Wayne-Workman on NEW node install only…Per Wayne I ran installer as "N"ormal mode up to php-fpm installation said OK. Then re-ran installer as "S"torage and it worked fine.
-
SVN 5680 Error log from Server
SVN 5680 verified with client v9.9 Error log from Server
Fedora 22[Tue Dec 08 17:10:56.109763 2015] [:error] [pid 7243] [client 10.72.146.88:57403] PHP Warning: Cannot modify header information - headers already sent in Unknown on line 0
Seems to be functioning normally, but not really sure what this error might cause.