FOGProject / fogproject

An open source computer cloning & management system
https://fogproject.org
GNU General Public License v3.0
1.14k stars 222 forks source link

[DEV-BRANCH] PHP7 1.5.9.138 snapins do not seem to work #467

Closed jessegit closed 2 years ago

jessegit commented 2 years ago

ubuntu 20.04 (PHP7), dev-branch 1.5.9.138 (and 137)

(I think) I know ~what I'm doing (worked previously for the past 5-7 years), and I've gone through the newbie mistakes (and with this, all the un/re/install, reset things, add deploy etc. things, and googled if there are any new gotchas since the last time I did imaging with fog).

Snapins do not work for me. I can add them, edit them, assign them to groups and hosts, make tasks for groups and hosts for all or single snapins and they appear in task list but the client will just say there are no snapins. I can do other things through the client link, like reboot and memory check, so that should not be a problem.

The only half-suspicious thing is is that I transplanted certificates from another fog installation on a PHP8 system (also 138/139, /opt/fog/snapins/ssl and /var/www/html/fog/management/other/ssl/srvpublic.crt) with all the required reboots and blahs.

The biggest problem here is not really the fact that it's not working, it's the fact that it's not debuggable. Client logs just say 'no snapins' and the server just waits for the client to act. No real reason why things do not work, and not documentation how it should work or how to debug it.

Unfortunately I only have till Saturday to debug this (and even at that, only random stints to test with a fog client)

Sebastian-Roth commented 2 years ago

@jessegit Anything in the apache / PHP-FPM logs on the FOG server while the fog-client queries the information?

jetbalsa commented 2 years ago

I'm experiencing the same issue, No errors in the FPM Logs, and the clients are reporting there are no snapins to download. Let me know of any logs you need to diag this.

Sebastian-Roth commented 2 years ago

@jessegit @JRWR Figured it out and pushed a fix (FOG 1.5.9.139). Thanks for using dev-branch and reporting this issue here!!