Latest Development FOG
-
Here is what my apache error log states:
[SIZE=13px][COLOR=#555555]PHP Fatal error: require_once(): Failed opening required ‘…/commons/base.inc.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/service/servicemodule-active.php on line 2
[Thu Mar 26 09:19:18.242587 2015] [:error] [pid 4402] [client 172.28.21.104:49210] PHP Warning: require_once(…/commons/base.inc.php): failed to open stream: No such file or directory in /var/www/fog/service/servicemodule-active.php on line 2
[Thu Mar 26 09:19:18.242601 2015] [:error] [pid 4402] [client 172.28.21.104:49210] PHP Fatal error: require_once(): Failed opening required ‘…/commons/base.inc.php’ (include_path=‘.:/usr/share/php:/usr/share/pear’) in /var/www/fog/service/servicemodule-active.php on line 2
[Thu Mar 26 09:19:18.538766 2015] [core:notice] [pid 28619] AH00051: child pid 4535 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Thu Mar 26 09:19:43.585457 2015] [core:notice] [pid 28619] AH00051: child pid 4557 exit signal Segmentation fault (11), possible coredump in /etc/apache2
[Thu Mar 26 09:24:28.378500 2015] [core:notice] [pid 28619] AH00051: child pid 5262 exit signal Segmentation fault (11), possible coredump in /etc/apache2[/COLOR][/SIZE] -
I think I found the reason, or at least part of the reason for this. When I go to download the new client msi file from the fog webpage I get a ‘This Webpage cannot be found’ error from the web browser.
-
Check to see if the file is actually located @ URL <ipofserver>/fog/client/FOGService.msi
Then check Terminal:/var/www/fog/client/ to see if FOGService.msi exists
Edit: Check your install log. There is an entry specifically for the new client. If it failed then it will not be on your machine and the link will not work.
-
I get a not found when looking at <ipofserver>/fog/client/FOGService.msi and when I look in the client folder I only see FOGCrypt.zip FOGPrep.zip and FOGService.zip. No msi files are stored there.
-
Check your install log. There is an entry specifically for the new client. If it failed then it will not be on your machine and the link will not work.
[S]There was an error with r3162’s location of the file. A bit of a mistype.[/S] Tom should be correcting it now. BUT if you wish to force download it please use.
[CODE]sudo wget -O /var/www/fog/client/FOGService.msi https://github.com/FOGProject/fog-client/releases/download/0.7.2/FOGService.msi
[/CODE]OR
Download from [url]http://github.com/FOGProject/fog-client/releases[/url]
[COLOR=#ff0000]Edit:[/COLOR]
[COLOR=#ff0000]We were using curl method to download from github and some versions of ubuntu don’t install that package by default. This package has been added to the install script (r3163) and downloads of the new client will now work.[/COLOR][SIZE=4][COLOR=#339966]HAPPY BETA TESTING!!![/COLOR][/SIZE]
-
Moving to problems
-
Please post a thread in the Fog Problems section and we would be happy to help.
-
Tom,
I’m noticing on the latest build on 3180 that when you open list all hosts it takes forever to ping. Basically the GUI lags out and you cant do anything. Looking at your past comments on revisions, I saw you were addressing this. Not sure if you were still aware that its still an issue.
RZ
-
Tom,
Installing latest SVN and getting PHP Warning on the install couldn’t fetch mysqli in /var/www/fog/lib/db/MYSQL.class.php on line 90 and 120.
-
This isn’t necessarily an issue. If the messages are occurring during the update (and you have a browser open with fog trying to request information, when the services are restarted you will see these messages.
-
The issue I figured out is it has to do with my SQL password on config class. I have 3 $$$ in my password and normally i have to go into my configclass.php file and change password back when upgrading. I do this before schema update. Once I do this, I can proceed with database schema update and all works fine. So the issue now is in the install script writes to the SQL database during the kernel install before the schema update prompt . At this point, password isn’t changed yet and its throwing that error.
Hope that makes sense.Ray
-
It makes sense, but I have no means to know what your password is going to be and whether or not they’re going to contain technically illegal characters.
One of the way’s to help out I suppose is edit your/opt/fog/.fogsettings file and set the password so it’s escaping the $$$ with something like $$$
-
When i go to opt/fog/ there is no .fogsettings file.
-
can you run ls -lhart on the directory /opt/fog?
-
its a hidden file hence the . in the front of the file name. just do a nano .fogsettings or a vi .fogsettings or your favorite text editor
-
My bad i figured it out… hidden file.
-
Pinging issue is still present tho. I have 311 PCs and if I hit list all clients and its in the middle of pinging every client, I cant advance to another screen.
-
Do you require the host pinging?
-
Question… What was the last SVN revision released that didn’t use the new client? And how good of a build is it?
I’m thinking about upgrading but I’m not necessarily wanting to use the new client just yet, we have a lot of computers here running the old one.
Also, another question…
What happens to the old clients out in production when the new client is enabled on the FOG server?
-
[quote=“Tom Elliott, post: 44237, member: 7271”]SVN 3138 released. With this release comes many more things. Specifically the Beta FOG Client is available now and is downloadable from the FOG GUI as normal. There are two links. One for Legacy and one for New. Hopefully this is self explanatory.
[/quote]Both Clients are available still in the latest SVN. You will should not have to do anything using the old client at this point. If you wish to use the new client then you will need to change an option in Settings.
It is [B]NOT[/B] suggested to have both clients in the same environment.
