Posts made by saistrop

Well I ended up doing a fresh install of FOG (wiped existing FOG files and set it up again) and during setup I provided the password for MySQL this time. I have a GUI, so I’m going to continue testing and see if I hit any other issues.

Will try that and report back. Thanks guys, you’re always incredibly helpful with issues like this (even if it is likely user error)

Where in the setup process would I tell it to use that? I didn’t see it earlier, may have overlooked it.

I can log in as root with password, should I create a fog user and set it to the same password as the fog user and give that user full access to the DB? My current svn version is 4256 if that gives you any further help.

Well I tried giving full access to the fog user, but no dice. What would I need to remove in order to attempt another fresh install? And should I upgrade to the newest SVN if one has been released since then?

I created a user ‘fog’ for the DB, do I need to give it full access? If so I’ll try that and report back once it finishes.

Hey again guys,
I got a second staging machine set up just to test more recent SVN channels, and when I installed the newest one, I keep running into an issue where once I run the install script and go to the Database Updater page, it just navigates to a blank page. Did some digging in the error_log file in httpd, came across an issue with the MySQL database not being able to be access by root using no password. I did run the secure install and removed root access and such, do I need to re-enable that or is there a way to work around it? Thanks.

Hey guys,
I was working on some image uploads when I found out that the default location for images had gotten full in the root directory so I tried moving the images to a new location. Ever since then, I’ve been unable to get images to load, with the message ‘/usr/share/fog/lib/partition-funcs.sh: line 124: local: /images/mac address: not a valid identifier’. I’ve tried making a new storage node and group, and I’ve made sure that the FOG GUI is pointing to the right location. Is there some other configuration I need to do to get this working? Thanks.

Well after fighting with this thing for the better part of a week, I think I’ve finally got it stabilized. I’m on revision 3526, and I ended up creating a new image from scratch. Uploading and downloading finally work correctly, and while I do have an issue with the image, that’s a Windows issue not a FOG issue. Thanks to @Wayne-Workman for all his help, hopefully now you guys can move on to more important things, like a stable release.

This is a brand new image uploaded with the current version of FOG, so it’s already set to Partclone. I’m creating a new image from scratch to see if that will fix the issue, should have it ready later on this afternoon. I’m really at a loss as to why it isn’t cloning the second partition at this point.

Well I just uploaded an image from another machine, and I created the image as a Single Disk. It downloaded the first partition fine, however when I got to the second partition I got an error stating “this is not a partclone image”. So I’m at least halfway to getting things working. Going to go through the debug download again to see what comes out, will update shortly.

That’s the error I get when I reach the second partition on the image now.

Just a quick update, I can upload an image from another client correctly, so it looks like the old image could be the issue. Will try with new image and see.

While I appreciate the advice Wolf, it’s not a permission issue in the directory so far as I can tell. It seems to be looking for a file that doesn’t exist.

[root@localhost /]# ls -laR /images/Win7Prox64/
/images/Win7Prox64/:
total 9226228
drwxrwxrwx 2 root root 49 May 27 11:58 .
drwxrwxrwx 5 fog root 75 Jun 5 10:04 …
-rwxrwxrwx 1 root root 512 May 27 14:00 d1.mbr
-rwxrwxrwx 1 root root 8478104 May 27 14:00 d1p1.img
-rwxrwxrwx 1 root root 9439173435 May 27 14:18 d1p2.img

I’ll try it with single disk and see how it goes. In the meantime, here is a picture of the error I’m getting, which make sense given that the file doesn’t exist because it was never part of 1.2.0’s image setup as far as I could tell.

Those all appear to be good, I’m getting an error something along the lines of “unable to location partition” when I try to do the clone. Do I need to change the image settings to only copy the MBR and partition table, or is there some other configuration I still need to do that I’m missing? It’s currently setup as a single disk-multiple partition, using Partclone. You guys really are saints for taking so much time to try and help me figure this out, if I haven’t pointed that out already.

Well, minor update. I got the current SVN version from updating (3526 is what’s listed), and it seems to be having an issue with the old image I had from 1.2.0. Is there a known way to work with old images on the current SVN?

That’s strange, since I’ve already got MariaDB installed. Maybe I’ll try to remove it and install it again, though I don’t think that would have much effect at this point. I still haven’t found a good resolution for the issue, at this point I may just end up having to start FOG over from scratch, which would be unfortunate, but it may fix it.

MariaDB is already installed and updated, would it be worth trying to remove it and let FOG install it? And that got me farther, now it’s failing on the Plugins. Unfortunately it’s about closing time here so I’ll have to get back to this on Monday. I really appreciate the help, hopefully a new stable build is coming soon that’ll work better with CentOS 7’s weird setup.

@Wayne-Workman I would certainly appreciate it, I know it’d likely be easier if I rolled back to CentOS 6.6 but my company is trying to push everything up to the most modern version, and they don’t always realize new isn’t always better.