Posts made by neodawg

This can be marked as solved.

Commenting out the lines on the file fixed it for me.

Reference:
https://forums.fogproject.org/topic/8576/upgrade-1-2-1-3-rc10-error-mysql/2

Yep, did yum update on the server too, was working fine on RC8, ran the installer for RC10, broke it, fixed it and redid the svn up command on the fog install folder and tried installing again. Got to the step above and died and listed the restart to show it was broken.

Here is the mysql.log file that might tell you more, i suspect it has something to do with the new performance tweaks you have made?

160909  4:01:05  InnoDB: Starting shutdown...
160909  4:01:07  InnoDB: Shutdown completed; log sequence number 3694098
160909  4:01:07 [Note] /usr/libexec/mysqld: Shutdown complete

160909 04:01:07 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
160909 04:01:07 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160909  4:01:07 [Note] /usr/libexec/mysqld (mysqld 5.5.52) starting as process 15752 ...
160909  4:01:07 [Note] Plugin 'FEDERATED' is disabled.
160909  4:01:07 InnoDB: The InnoDB memory heap is disabled
160909  4:01:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160909  4:01:07 InnoDB: Compressed tables use zlib 1.2.3
160909  4:01:07 InnoDB: Using Linux native AIO
160909  4:01:07 InnoDB: Initializing buffer pool, size = 128.0M
160909  4:01:07 InnoDB: Completed initialization of buffer pool
160909  4:01:07 InnoDB: highest supported file format is Barracuda.
160909  4:01:07  InnoDB: Waiting for the background threads to start
160909  4:01:08 InnoDB: 5.5.52 started; log sequence number 3694098
160909  4:01:08 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
160909  4:01:08 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
160909  4:01:08 [Note] Server socket created on IP: '0.0.0.0'.
160909  4:01:08 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
160909  4:01:08 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
160909  4:01:08 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
160909  4:01:08 [Note] Event Scheduler: Loaded 0 events
160909  4:01:08 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.52'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL) by Remi

In digging into the log some more, it looks like this error occured prior to me messing with RC10, part of my inital fixing was run the update like it says. Now I no longer see those performance_schema errors.

I can try test installing RC10 again if you like.

Updating from RC8 to RC10, getting this issue. CentOS 6.8

 * Configuring services

 * Setting up fog user.........................................Already setup
 * Setting up fog password.....................................OK
 * Stopping FOGMulticastManager Service........................OK
 * Stopping FOGImageReplicator Service.........................OK
 * Stopping FOGSnapinReplicator Service........................OK
 * Stopping FOGScheduler Service...............................OK
 * Stopping FOGPingHosts Service...............................OK
 * Setting up and starting MySQL...............................Failed!
[root@fog bin]# service mysqld restart
/etc/init.d/mysqld: line 103: syntax error near unexpected token `fi'
/etc/init.d/mysqld: line 103: ` fi'

yum reinstall mysql-server fixes the issue.

uname -r
2.6.32-642.4.2.el6.x86_64

Sorry for the delay, I ran out of time on this and just used multiple partition single disk method. It sounds like you guys are not able to replicate the problem, so it must be an issue with my server/client pc. If I get time again later I will try to replicate the issue with a new install of XP.

Thanks for the help

Sorry to bring this up again, but having the same issue. Different fog server however. using build 8179.

I created a small group of hosts ~25 and went to the group page, checked the box and it didn’t autofill the form, thought OK, remembering this thread that didn’t necessarily matter. Then went to a host and saw the box was checked to join and the old information that was in there was now gone. I then tried to update the individual host by clearing the fields and hitting the join box, still didn’t autofill, checked the defaults in Settings and that was still there and correct. I believe this was working on SVN5675.

Browser is Chrome 51. (Now that I think about it I think my chrome updated last week sometime)(perhaps chrome issue?)
Tried MS Edge, Works as expected.

Can someone verify my results?

@Tom-Elliott I was more so meaning that I had blown away any factory restore partitions. I have no idea why it doesn’t work, the whole upload process appears to work fine.

I wipe out the partitions and loaded XP from CD:

Using build 8088

Single partition upload: breaks source install
multi part upload: works

Tested the partimage image i have been using:

single partition upload: breaks source install
multi partition upload: works

I pushed out the good image
Then boot it
then rebooted to debug upload
I am obviously uploading to a different image on fog as to not wipe out my working image.
The pictures are of before and after, I noticed that they matched as well.

So to further clarify, I pushed down an old partimage of xp i have, then i change the image on the host to the new one, rebooted client after successful boot, then scheduled the upload-debug, ran sfdisk took a pic, imaged it all the way, then ran sfdisk again and took a pic. after rebooting the client it no longer booted and hung on the GRUB screen, doesnt matter if I skip PXE or not, it will no longer boot.

I hooked up the failed booting drive to another pc and could see and read the files on the hard drive just fine.

What sort of logs or information would you like from me? video of my actions and the image process?

EDIT: I will try a multiple partition image upload tonight and see if that works. I guess the next step would be to try a new xp install and upload that.

Resizeable - forgot to mention that

Here is the info, listed in the order you requested.

Here is 2 definitions that I attempted an upload to:

[root@fog images]# ls -al Optiplex740/
total 3504244
drwxrwxrwx 2 root root       4096 Jun  4 01:09 .
drwxrwxrwx 8 root root       4096 Jun  6 00:23 ..
-rwxrwxrwx 1 root root          1 Jun  4 01:03 d1.fixed_size_partitions
-rwxrwxrwx 1 root root      32256 Jun  4 01:04 d1.mbr
-rwxrwxrwx 1 root root        132 Jun  4 01:04 d1.minimum.partitions
-rwxrwxrwx 1 root root         15 Jun  4 01:03 d1.original.fstypes
-rwxrwxrwx 1 root root          0 Jun  4 01:03 d1.original.swapuuids
-rwxrwxrwx 1 root root 3588280852 Jun  4 01:09 d1p1.img
-rwxrwxrwx 1 root root        132 Jun  4 01:03 d1.partitions
[root@fog images]# ls -al Opti740/
total 3251564
drwxrwxrwx 2 root root       4096 May 15 23:28 .
drwxrwxrwx 8 root root       4096 Jun  6 00:23 ..
-rwxrwxrwx 1 root root          1 May 15 23:21 d1.fixed_size_partitions
-rwxrwxrwx 1 root root      32256 May 15 23:23 d1.mbr
-rwxrwxrwx 1 root root        132 May 15 23:23 d1.minimum.partitions
-rwxrwxrwx 1 root root         15 May 15 23:21 d1.original.fstypes
-rwxrwxrwx 1 root root          0 May 15 23:21 d1.original.swapuuids
-rwxrwxrwx 1 root root 3329538183 May 15 23:28 d1p1.img
-rwxrwxrwx 1 root root        132 May 15 23:21 d1.partitions
[root@fog images]# 

[root@fog Opti740]# cat d1.partitions 
label: dos
label-id: 0x0003307f
device: /dev/sda
unit: sectors

/dev/sda1 : start=          63, size=   156249937, type=7, bootable
[root@fog Opti740]# 

0_1465271179541_d1.mbr

Before picture

After picture

If you need anything else let me know.

Trying to upload an XP image from a Dell Optiplex 740 to fog (7981). The whole upload process goes perfect and no issues.

After its done the original source computer doesn’t boot back to windows. I have tried loading the XP disk and doing a fixmbr
and fixboot. That didn’t fix the installation either. I think also tried redeploying the just uploaded image and that didn’t work either.

I have an old partimage image that I am able to successfully deploy.

I understand that XP is no longer supported and if you choose not to fix this I understand, just passing the information along.

EDIT:
Doing further testing, I am able to view the files on the non booting drive just fine. So the data is still readable, the MBR must be what is getting goofed.

Not sure if that is possible, but if a guy is using SVN to download the trunk, then needing to roll back to a previous version of trunk its confusing and you pretty much have to guess the SVN version from the fog version.

Thought it would be convenient to have those versions match the fog version in the cloud.

I am not an expert in SVN/GIT, but I usually use SVN because of the easy downloading of a specific revision.

EDIT: Or list both version numbers in the cloud if it isnt possible.
Fixing the fog/management/index.php?node=about page to list the SVN version would work as well

@Developers

Seems to be a typo on the Database Update page. Server is CentOS 6.5

http://fog/fog/management/index.php?node=schemaupdater

cd ~;mysqldump --allowkeywords -x -v fog > fogbackup.sql

Should be

cd ~;mysqldump --allow-keywords -x -v fog > fogbackup.sql

I am also seeing this issue, however when I look in the fog.log file it says that all modules are disabled on the server, even through i checked both the host and server level settings. I am using the old fog client (I assume this is supposed to work yet).

I also noticed the hostname didnt change when the machine started up, so the early hostname change didnt work, the image is a Windows 7 image. Fog ver 7597

Anything I can provide to assist in fixing this issue?

@Tom-Elliott

Thanks, seems to be working great now, the update fixed the issue with setting the All group AD settings. Now running 7591.

On a side note I was able to fix the install issues by getting rid of the webtastic repo and using remi and replacing PHP from webtastic to remi.

Yep, checked that several times and checked several hosts. Here is a video clip of what I am doing:

Video

I dont see any errors related to trying to update the group infomation, this is what I have:

[Mon May 09 15:21:35.303216 2016] [:error] [pid 13319] [client 10.0.10.188:51225] PHP Warning: array_map(): An error occurred while invoking the map callback in /var/www/html/fog/lib/fog/fogcontroller.class.php on line 197
[Mon May 09 15:16:32.934303 2016] [:error] [pid 13452] [client 10.0.10.188:51217] PHP Warning: array_map(): An error occurred while invoking the map callback in /var/www/html/fog/lib/fog/fogcontroller.class.php on line 197```

@Wayne-Workman

Fresh install of CentOS 7 x64

Also on that note, the installer doesnt seem to install PHP 5.6 from webtastic repo instead just uses PHP from base/epel. Thus I just modified the packages it was looking for be php56w* instead of php*

Anything you need from me?

Right,

Thats what I remember and have experienced with groups. But in this case those AD settings are not being applied to the hosts.

I will work on a video for you.

@Wayne-Workman

I have no need to set any host individually, they all need to join the same domain. Other than checking or unchecking ‘join domain’ box.

Would you like me to gather a video or some screen shots?

Thanks replying @Wayne-Workman
Some background on me, I have been dabbling with 1.3.0 as you guys have been working on for the last year.

1 . Yep, got it, thats where I am setting the correct passwords. Took me a little clicking around to realize the new client was using a AD password yet.
2. yep, got it.
3. yep, used it many times.
4. Ok, so your saying that no matter what the host fields have in them it will just use the defaults from the Fog Settings page? Previously it would autofill these ‘placeholders’ in so that you know it was set.
5. This, make sense, as each time I clear fields on a host and then check the box and watch the autofill, the new AD password changes its encrypted form. Default=6da1956736 HostField1=64a7977 HostField2=d0506078 (All truncated for security)
6. I have experienced this issue around the site, I am aware of it the issues and use the private/incognito modes when needed.

I am only checking in the web interface, however I did just install phpMyAdmin and checked the newly registered host(at bottom) and that shows the same as the web interface.
My work flow is this:
Make a group with All the hosts.
Goto the ‘All’ group I just created
Goto the AD page of the group
Check the Join Domain box
I see today its pulling everything from the defaults.
It auto-filled, the domain, domain username, and both new AD password (different again) and the legacy
Hit update
Page refreshes in about 1 second and says Group Info updated at the top of the page
Goto any host
Goto the AD settings page for said host
see that the box is checked to join, domain is there, domain username is wrong, its ‘fog’ and should have either been ‘fogadd’ or now ‘fogjoin’ (never used the username fog, this was changed when i updated from 1.2.0)
The new AD password field has the old legacy password in it (daa5c) which was used with the ‘fogadd’ account
the legacy password field is blank. This password is NOT set anywhere on the defaults page.

If I look at a host I registered and uploaded an image from on the new version 7498, this is what I see on that hosts AD settings page:
join box is not checked
all other boxes are blank

Hopefully this helps, there is 1700+ hosts on here so maybe there is too many to update all at once?