Posts made by Joe Gill

@tom-elliott said in WIN10 Shutsdown After Host Reboots Post SysPrep:

CTRL+SHIFT+F5

Thanks Tom! I gave that a go.

@tom-elliott
@wayne-workman

Well, I pulled up the /var/log/apache2/error.log file…

I did find this…

[Tue Jul 24 12:38:38.255133 2018] [:error] [pid 43264] [client 172.16.101.30:42208] PHP Fatal error:  Call to undefined method ServiceConfigurationPage::service() in /var/www/html/fog/lib/pages/serviceconfigurationpage.page.php on line 1475, referer: http://fog-server/fog/management/index.php?node=snapin&sub=list

[Tue Jul 24 12:38:38.255133 2018] [:error] [pid 43264] [client 172.16.101.30:42208] PHP Fatal error:  Call to undefined method ServiceConfigurationPage::service() in /var/www/html/fog/lib/pages/serviceconfigurationpage.page.php on line 1475, referer: http://fog-server/fog/management/index.php?node=snapin&sub=list

Any thoughts?

@Wayne-Workman

I downgraded to the Working Branch. After I did this I went into Power Management settings on the Group that was giving me troubles. I deleted ALL power management entries. (None were shown.) So far we are working and nothing has rebooted.

Thanks for helping me think this one through.

@Wayne-Workman
@Tom-Elliott

The power management schedule portion of the GUI in 1.6 is not displaying properly on my server.

FOG Ver: 1.5.4.579
Host: Windows 10

I just recently noticed this issue. I have a group of hosts that will shutdown after I image them and the sysprep processes complete. They will check in with FOG and change their name / join the domain. Then they shutdown in about 4 minutes after being left be. I can turn the machine on, and in about 4 minutes from the time the log in screen appears, it shuts down. The odd thing about all of this is if they are not network attached, they do not shutdown. So it’s probable that the issue is coming from FOG.

@Wayne-Workman Any ideas here?

Thanks!

@wayne-workman
It most likely is. I was working in the Alpha 1.6 and had issues pushing more than one image at a time (both in multitask and unicast). So I tried to roll things back to the Working branch and noticed this message. The web GUI still works. I just can’t seem to get anything else working.

I did look through the Apache logs and did not notice any fatal errors. I also checked the multitask.log file and noticed that none of the multitask jobs were being posted.

Also, @Tom-Elliott logged into my system last week to try and resolve some Multi Tasking issues. At the time, it appeared to have worked. After that, I have not been able to do much.

Thanks!

Any idea what may have caused this to happen? I can go to:

http://fogserver/fog/management/ and update my database just fine but I have noticed a few services not functioning properly on my server since this.

• Starting and checking status of web services…Failed!
  root@fog-server:~/fogproject/bin#

Any suggestions are appreciated!

Thanks!

Joe

@Tom-Elliott
I can’t seem to get 1.6 to do a Wipe task. It will PXE boot the host but it never creates the task.

@tom-elliott

No problem! I’ll keep that in mind. I’m testing multicasting now.

I discovered a few things that could have been effecting multicasting performance. If this works, I’ll have to unicast most of the lab. Basically, we have some small low end consumer switches that some of these hosts are plugged in to. I had 4 hosts in that lab that are directly wired in to our smart switches (cisco). We did check to see if we had any packet loss during the previous multicast session and we did not and the cable checked out fine. So we’ll see.

@Tom-Elliott

One other feature that would be nice is when you check / un-check hosts from certain things, for instance groups, that it would recognize that as selecting the item. Right now you have to highlight the whole thing to select it.

Thanks!

@tom-elliott

/var/log/apache2/error.log?

What I am seeing is this… Yet I have tasks listed in tasks…

@tom-elliott

I agree. Less is more here. I like the idea of sort by associated first. That would certainly work.

Have you tested Multicast? I am testing that now. I get Attempted to check in failed.

Thanks!

@Tom-Elliott

I love the look and feel of the new interface. I can tell you and the group have put in a ton of effort in creating 1.6. Thank you!

One small thing I just noticed is the icon on the browser tab needs to be updated. Ha! I liked having the FOG icon to get to in my many open tabs. Small!

The next thing I noticed was when you open Groups/Associations/Hosts, it displays All hosts. It would be great if it showed just the hosts associated with the group with the option to display hosts that are not associated with the group. (like 1.5 did.)

I’ll put it to the test!

Again thanks!!

Cheers!

@Tom-Elliott

I like the new look! Where can we post requests / bugs?

Thanks!

@george1421
@Tom-Elliott

To update this issue… I had a network engineer look at this issue. He determined that we had our multicast setting set to flood all ports. So far disabling this has fixed the majority of our multicasting issues.

One thing we did notice is that we had one old switch going to one of our labs that seems to fail on multicast and not unicast. Multicast works everywhere else with that image. We will be replacing that switch at some point but I believe that switch is the culprit. It’s an older 10/100 “dumb” HP switch (commercial grade).

So far I have not experienced any other issues with that version of FOG.

Thanks again for all the help!

@george1421
The only switches we have on campus now are Meraki or dumb switches. Most things are on Meraki’s. The vendor turned “port flooding” off. I’m going to check but I believe I’ll still have the issue. I do not think that’s it. I’ll post back as soon as I know.

@george1421
It is set like that for the default stack.

@george1421
IGMP snooping is enabled.

@george1421 Thanks! I’ll check it out.