Posts made by fry_p

@george1421 Is pushbullet integration obsolete now? I am just curious.

@Julianh You can take credit for inspiring me to do this myself. I have not tested yet, but there are a couple of quirks. Here is what I did:

1 - Activated plugins by going to Fog Configuration>Fog Settings>Plugin System and checked the box for “PLUGINSYS ENABLED”
2 - Went to the newly appeared Plugins tab at the top of the Web GUI
3 - Activated Pushbullet
4 - Chose Install plugins on the side column
5 - Installed Pushbullet Plugin
6 - Created a free Pushbullet account at https://www.pushbullet.com/
7 - In Pushbullet, went to Settings>Account>Create Access Token
8 - Copied the token to the clipboard
9 - Back in the FOG GUI, chose the new Pushbullet accounts tab at the top and chose “Link Pushbullet Account”
10 - Pasted token code and hit save

The only thing that is strange is that in the list of accounts, the entry is there but the Name and Email are blank. Testing the functionality this morning.

Correct me if I am wrong, but doesn’t FOG have a pushbullet plugin? This may satisfy your needs.

“Pushbullet
Receive notifications on devices with Pushbullet installed when events occur such as imaging completion.”

If you are interested, I or someone who uses the plugin may be able to provide instructions.

If I may interject with a very hypothetical statement. If you end up using the fog client portion of this solution on more than say a few hundred hosts, you may think about making the server a bit beefier. Here is my setup

For my 1500 hosts that check in with the client:

4 vcpu’s
8GB RAM
250GB storage (we use model specific images)

May be overkill but it works pretty well for me

@Sebastian-Roth my issue may have been a fluke. I sat down and set up the same scenario as in my first reply twice and the image expanded perfectly. I will certainly make a new post if it happens again, but it did happen on a production machine so it was corrected manually so the user could utilize all of the space. I also was not the one working on it. I will pay closer attention if it happens again.

@Fernando-Gietz May I ask what port the host returns the call to port 445 on the client? I ran the command:

tcpdump -i ens192 dst port 445

for the destination port of 445. I saw that it seemed FOG was calling out to each host in alphabetical order about 1 per second. If I understand correctly, is this plugin supposed to check real time/on the fly when I bring up the host edit page? It does not seem to be doing that. Please see the below mockup of what is happening:

1 - TCP dump started for destination port 445.

2- I see the following happening
fogserver.domain.org—> Middleschoolroom1
fogserver.domain.org—> Middleschoolroom2
fogserver.domain.org—> Middleschoolroom3
and so on

3 - I open the host edit page for my PC (HS218-fry)

4 - I check the tcp dump and I see that it never calls out to 445 on my pc and continues with:

fogserver.domain.org—> Middleschoolroom4
fogserver.domain.org—> Middleschoolroom5
fogserver.domain.org—> Middleschoolroom6
and so on

It seems to never be attempting to contact my PC when I bring up the host edit page.

Here is a real example. I brought up the host edit page for my PC right in the middle of this tcpdump pictured below.

Another oddity is that the built in host pinging on the host list page is working properly and even detecting these are windows clients. If I am not mistaken from what you said, this also uses port 445 on the client, no? I am just thinking out loud

@Sebastian-Roth I want to chime in that I just had an issue with expansion as well. I don’t have the specific partition info at the moment, but I can tell you that I have FOG 1.5.6, the image (win10 x64 1903) was built on a 128 GB drive and deployed to a 256 GB drive. It followed the same pattern as the OP, the drive did not expand at all. I can make a new topic if you would like and I can do some testing later

@Fernando-Gietz Do you want me to edit line 114 or 110 (what you just listed in your last reply)? I accidentally changed “Unknown” to $val in line 114 and it came up with a value of 6 with the red exclamation. I realized my error and went to line 110 and put in $val instead of FOS and it is showing up red exclamation and “unknown” still.

@Fernando-Gietz Would you like me to test this with the $ping variable in the php file? If so, I did a deploy to a laptop. It is still showing a red exclamation with no text when hovered over. If not, I can try again with the original syntax.

I have roughly 1500 hosts registered to my fog server. I ran another tcpdump and I am seeing pairs of what appears to be “calls” and “replies” from hosts to and from the server. It is pretty steady 1-2 popping up per second. I do not believe our firewall touches internal traffic but I can verify. I am also checking Antivirus at the moment.

@Fernando-Gietz For your first suggestion of modifying the PHP file with the $ping variable in the place of “Unknown”. When I hovered over the red exclamation after doing that, nothing appeared.

For the second suggestion of a tcpdump, there is quite a bit of chatter on that port for hosts all over our district. Is it possible fog is using this port for other purposes? I ran it for a 30 seconds and opened the host page and saw a lot of traffic, but none from the host I was working with.

@Fernando-Gietz I am able to telnet from the fog server to the host on port 445 if that means anything. I will test these other suggestions over the next few hours.

Thanks!

@Fernando-Gietz I may actually have an issue here. It is still displaying the red exclamation with the message “Unknown” for my computer which is on. I verified that Windows Firewall is completely disabled on my machine.

I ran a packet capture from my FOG server with the following display filter:

tcp.port eq 445 && ip.addr == (my host IP address here)

I am basically looking for packets sent from the fog server with the destination of my PC and the destination port of TCP port 445. I started the capture and went to the host page for my PC in FOG. I waited there for a few moments and stopped the capture. There were no packets sent from the fog server during this time that fit the criteria.

Perhaps I am mistaken, but it appears that the problem lies on FOG plugin side of things and not my host denying TCP port 445 as it appears the server is not sending the packet in the first place.

Not that it matters, but all outbound traffic on my server should be allowed because I have firewalld disabled and off.

What are your thoughts? I’d love to test suggestions if you have any!

@Sebastian-Roth I used 1803 up until last week. We are making new images with 1903 and the behavior is still normal for me. Very strange

@Fernando-Gietz Thank you for this! I just updated to 1.5.6 recently and am very interested in using this. I made sure TCP 445 is open on my hosts. Currently showing unknown and a red exclamation on the host pages of online hosts, but I will give it time to do its thing.

Hi All,
Just had a lovely experience with sysprepping a 1903 image that may be a bug and how to fix it. I made 3 model specific images prior to this and just ran into this on my 4th.

I attempted to run the command: sysprep /generalize /oobe /shutdown /unattend:unattend.xml

I instantly received a sysprep error regarding the dll located at C:\Windows\System32\spopk.dll. The error is found in the C:\Windows\System32\Sysprep\Panther\setupact.txt and the C:\Windows\System32\Sysprep\Panther\setuperr.txt logs. I do not remember the specific error.

My workaround is to copy the C:\Windows\System32\spopk.dll file from a working 1903 PC and replace the existing spopk.dll file on the computer you are trying to sysprep. You will need to take ownership and give full control of the existing spopk.dll file in order to modify it. Once permissions were set and I copied the “good” dll to my desktop, I ran the following command:

xcopy "C:\users\fry_p\Desktop\spopk.dll" "C:\Windows\system32" /y

I was able to successfully run sysprep after that. Once uploaded, the PC went into OOBE mode and failed. I redeployed the just captured image and it seems to be working now.

EDIT: Microsoft Forum post about similar situation: https://social.technet.microsoft.com/Forums/en-US/0dcbdf32-05a1-4edc-8f22-287998d30de5/sysprep-problem-audit-mode-canamp39t-be-turned-on-if-there-is-an-active-scenario?forum=win10itprosetup

@george1421 I found this when I initially did the search for the ini’s. I increased the amount and it is reading the new amount in the error log.

@Sebastian-Roth I am finding that my entries in this table don’t actually date back that far.

Yet my count for

SELECT COUNT (*) FROM userTracking;

Returns 217,893 entries.

The furthest back i can find is roughly January 30th 2019. Do you guys think that 217,893 is still too high? I can maybe try to prune anything older than two months as I really don’t need anything older.

By the way, here is the error I am getting.

/var/log/php-fpm/www-error.log

[26-May-2019 05:53:59 America/New_York] PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 8192 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 622

I set the memory to 1 GB for troubleshooting purposes only. I find it odd that it is only trying to use 8192 bytes but I still get a white screen when I am running the report. Specifically I am putting in myself as the username and my desktop as the PC.

@EduardoTSeoane I have restarted both services and also restarted the entire server. Since it is reading the new memory limit, I think it is trying to read too much data since we have had FOG for a long time. Years of user data that predates me at this job. I will try another restart of services though.

EDIT: Same issue after restarting services again.

@EduardoTSeoane and @Sebastian-Roth you are both correct as always! I am running into the same error, but it is reading my new memory limit of 1024M. In particular, I am interested in the user tracking report. I am wondering if my table is much too large for the report to handle. Is there a way I may wipe the table up until 5/24/2018, or a year before today? I can open another thread as this is not particularly a fog issue.

Hi All,
I am running 1.5.6 on CENTOS7. I am running into an issue with setting the php memory limit so I can view reports on the web interface.

Please see below for my log

/var/log/php-fpm/www-error.log
[24-May-2019 12:25:22 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 8192 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 622
[24-May-2019 12:17:46 America/New_York] PHP Warning: Error while sending QUERY packet. PID=6597 in /var/www/html/fog/lib/db/pdodb.class.php on line 591
[24-May-2019 12:17:46 America/New_York] PHP Warning: Error while sending QUERY packet. PID=6484 in /var/www/html/fog/lib/db/pdodb.class.php on line 591
[24-May-2019 12:09:11 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 936 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[24-May-2019 11:57:21 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 89 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[24-May-2019 11:36:52 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 89 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[24-May-2019 11:28:24 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 89 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[24-May-2019 11:23:22 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 89 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[24-May-2019 11:17:20 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 89 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[24-May-2019 11:08:25 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 89 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[24-May-2019 10:57:13 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 81 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[24-May-2019 10:52:53 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 89 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[24-May-2019 10:25:38 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 84 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[23-May-2019 14:18:39 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 78 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[23-May-2019 14:14:13 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 78 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[23-May-2019 10:35:22 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 85 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[23-May-2019 08:18:28 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 99 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[22-May-2019 09:15:31 America/New_York] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 24 bytes) in /var/www/html/fog/lib/db/pdodb.class.php on line 602
[22-May-2019 08:46:46 America/New_York] PHP Warning: Invalid argument supplied for foreach() in /var/www/html/fog/lib/fog/fogcontroller.class.php on line 1100
[22-May-2019 08:46:46 America/New_York] PHP Warning: array_diff(): Argument #2 is not an array in /var/www/html/fog/lib/fog/fogcontroller.class.php on line 1080

No matter where I change the memory limit (in the web UI under Fog Settings --> General or /etc/php.ini, or a couple of other places that are probably wrong) the error appears in my log saying the memory maxed out at roughly 256M. I was trying on 1.5.5 too (I upgraded to 1.5.6 as of this afternoon as a last ditch effort to get it to read my parameter). I am attempting to set it to anything that will allow reports to run.

Thanks!
fry_p

@ckasdf This is very strange you are getting an “Access is denied” because setupcomplete.cmd runs in the local system permission context. This is indeed the issue I think. So in my eyes, the hostname changer in the fog service is running fine, but the service is failing to start with the setupcomplete.cmd script thus causing your issue. The screenshots that I asked for pretty much mirror my setup.

So unfortunately I myself cannot recommend anything but to rebuild the image as it seems the local system account is borked. @Sebastian-Roth @Wayne-Workman @george1421 may have other ideas because they are actual wizards.