Best posts made by mp12

@Timo

Did you reset the encryption data on the specific host? If not give it a try and report back.

@Lenain

/opt/fog/log/servicemaster.log
/opt/fog/log/fogscheduler.log
/var/log/apache/error.log

@Wayne-Workman I tried some scenarios (lots). With different number of max clients and different number of clients which get a deploy. See spreadsheet for details.

0_1455537297048_fog_testing.xlsx

Problem manually solved.
I also had a generated password with a “/”. When I tried to deploy a snapin, it failed with the same error @Hanz described.
A login with an an ftp-client redirected me into the users home directory. I changed “/” into a different character (passwd and GUI) and the ftp-client redirected me into /opt/fog/snapins.
Snapins now work without an error!

@theWizard try removing special characters and try again.

@Sebastian-Roth

Server

• FOG Version: RC-12 (42)
• OS: Ubuntu 14.04

Client

• Service Version: 0.11.5
• OS: Win 7

I am having the same problem. Can wake-up the clients in the console using wakeonlan *MAC*. When trying to wake-up a client or group in FOG GUI it creates the following error in the apache error.log

[Tue Oct 04 10:08:18.989990 2016] [:error] [pid 9838] [client x.x.x.x:35286] PHP Fatal error:  Uncaught Error: Access to undeclared static property: WakeOnLan::$_port in /var/www/fog/lib/fog/wakeonlan.class.php:70\nStack trace:\n#0 /var/www/fog/lib/fog/fogpage.class.php(1316): WakeOnLan->send()\n#1 /var/www/fog/lib/fog/fogpagemanager.class.php(230): FOGPage->wakeEmUp()\n#2 /var/www/fog/management/index.php(25): FOGPageManager->render()\n#3 {main}\n  thrown in /var/www/fog/lib/fog/wakeonlan.class.php on line 70

@Wayne-Workman first of all I am very thankful.

I am using FOG now for six-seven years. It’s a wonderful piece of software. Sure I want to help make FOG better. Thats why I am testing all these different configurations.

My only problem is that the imaging now takes twice the time.
I can handle this but I think a correct splitting would be great for the whole community.

Seems like the last client inside a group or inside the URL wakes up.

@Tom-Elliott
Running RC-12 Version 46
Tested URL with different MAC Addresses and different number of clients. We also changed the order of addresses.
Everytime we execute the URL, the last MAC in the row wakes up

@Wayne-Workman
We have different size of groups. Now we tested a group with two clients and the second client in the group woke up. First one still off.

@Wayne-Workman said:
I am working with the location plugin now. The splitting works fine.

@Tom-Elliott

switched to RC-14.

We tested the URL (also changed order) and the group wake-up directly in FOG. Each test was realized with three clients.
All clients woke-up! Great work @Tom-Elliott and @Wayne-Workman.

Thanks a lot!

@Tom-Elliott

Found the error. After creating a new snapin and enabling it on creation, I rechecked the snapin and found that the checkbox Snapin Enabled was empty. Set a check mark, restarted replication and it uploaded the snapisn to the nodes.

@Sebastian-Roth
Thanks for the reply! Did an update to 1.5.5.1 two weeks ago. Everything works fine so far!