@ch3i said:
@Scott-B said:
Still not working with 3735
Have you some errors in your apache error.log ?
I’m seeing could not connect to database errors.
@ch3i said:
@Scott-B said:
Still not working with 3735
Have you some errors in your apache error.log ?
I’m seeing could not connect to database errors.
Still not working with 3735
Just updating, same result on 3726.
I am on the latest as of 9:30AM 070715, v3713. It been happening for the past few revisions.
I ended up copying the .fogsettings file from a fresh test FOG install and changing the needed IP addresses. Then I could get past the repository failing issue, but would not update/install any needed software. I found that when manually running the installs I needed to say okay to installing to an untrusted resource. After that everything is up and how it should be.
Well, the issue is back again with a new install on Ubuntu 14.04.2. Currently svn 3658.
When going to FOG Configuration >> Configuration Save >> Export Button all I get is a page cannot be found. Suggestions?
@Tom-Elliott Update FOG itself or if you make changes in the web GUI? For example going from eth0 to bond0 for default network or enabling or disabling donation.
I’ve noticed since moving to the SVN when choosing Quick Image from the PXE menu I now get a list of possible images. Can this option be removed and just take the default image assigned to that device.
Could it have something to do with the settings stored in the /opt/fog/.fogsettings file? Wondering if anything in that file which could have changed since the install could cause an issue.
@Developers
Is the .fogsettings file ever updated after the initial install?
How or where do I find out what the password would be for the fog user that manages the fog DB created during install?
@Tom-Elliott said:
f I can get 15 and higher working properly.
V/R
Tom Elliott
I was starting to think the same thing actually. We have a 2nd FOG server (Ubuntu 14) as a storage node. Could that just be promoted to the main FOG server? The fog DB is on the old server. OR could I just rebuild the old server and under fog config and upload a backup of the DB? Recommendations?
I’m trying to update our FOG install to the newest version and I’m getting “failed” when it tried to add the needed repository. What repo is it adding? Server is FC12.
[quote=“Wayne Workman, post: 46964, member: 28155”]If permissions are set recursively to 777, then ownership and group doesn’t matter.
But, I think that a stock install is fog/root.[/quote]
Okay thanks. I just noticed that my image upload isn’t getting moved from /images/dev to its correct /images/imagename folder upon completion.
I have two fog servers, but on each /images/pcimagename have different rights. One is fog/root and the other is fog/fog. Are either of these correct or should it be something else?
Thanks for the info. Just thought I would throw it out there. We really appreciate all the work the FOG team does for this project.
When adding or removing a printer from a fog group the group’s fog page only lets you add or remove. It would be helpful if we could see what printers are already assigned to that group. Currently we have to go into one of the workstations in the group then printers to view the device print options.
[quote=“Tim618, post: 37267, member: 25256”]Scott- could you elaborate on this a little bit please? I’m getting the same error after moving to a new server. What folder did you manually create??? And what permissions? Thanks.[/quote]
We manually made the directory in /images to match the name of the image. So uploading an image called “HP1234” meant we had to make a folder in /images called HP1234 and grant 777 rights to that folder.