database update failed after capture

[alansopro]

@george1421 The only users I have listed in my MySQL is fogstorage and root. I have no fog user. I looked in the web config directory where the login is defined and the DB is fog using the login root and the password.

[george1421]

@alansopro Ok then we need the error message from apache error log.

[Tom Elliott]

I’m oh so very lost in what’s happening here.

@alansopro, you’ve gone through the FTP steps, and NOW the pxe boot doesn’t work? How isn’t it working? Is there an error message, or something we can help you troubleshoot further?

That said, resetting your password would have 0 impact on the booting capability of PXE. So unless there’s something seriously misconfigured we need a lot more information please.

Preferrably, Apache error logs, Installation Error logs, pictures, and more details than “I did this, now that ain’t working”.

[george1421]

@Tom-Elliott Tom, in this post https://forums.fogproject.org/topic/8236/database-update-failed-after-capture/11 FOG is only filling out the top section of the iPXE menu when boot.php is called directly. My guess is that something is wrong with access the msql server, but that is only a guess.

The OP does have 2 issues. One was resolved with correcting the ftp (linux) user password.

[alansopro]

@george1421 The problem was the actual computer. I plugged in another one and it PXE boots fine but now the NFS server isn’t starting so i can’t capture image due to that.

[george1421]

@alansopro ?? Was the target computer ??, Um ok.

As for the nfs service, have you rebooted your FOG server since the upgrade.

You can check the status of nfs with the following command: showmount -e 127.0.0.1 That should list the exported shares from /etc/exports.

[phishphan]

I received the same error message on 1.3.0 RC5. Right when the image was just about to finish it said Update Database Failed and then rebooted. This thread is somewhat confusing. Was there a fix posted for this?

[george1421]

@phishphan You are correct the OP seems to have several issues, but in your case please follow the suggestion by @Quazz https://forums.fogproject.org/topic/8236/database-update-failed-after-capture/5 and see if your issue is the FTP user account

[Wayne Workman]

@george1421 it is an ftp issue. the storage management pass was changed, and a gui user wasn’t defined in .fogsettings, and the wrong pass defined in there too.

[george1421]

@Wayne-Workman said in database update failed after capture:

@george1421 it is an ftp issue. the storage management pass was changed, and a gui user wasn’t defined in .fogsettings, and the wrong pass defined in there too.

Is this a systemic issue with the 1.3.0-rcX upgrade script? We’ve seen quite a few of these exact issues in the last few days??

[Wayne Workman]

@george1421 said in database update failed after capture:

Is this a systemic issue with the 1.3.0-rcX upgrade script? We’ve seen quite a few of these exact issues in the last few days??

It’s systemic only because people don’t know that they really should define fog web ui user and pass inside of /opt/fog/.fogsettings exactly like the installer says. Additionally, people are changing the Storage Management DefaultMember password without realizing that they must too change the password setting in .fogsettings, and re-run the installer, or do it all manually.

You know what I think?
@Tom-Elliott I think if people change the Storage Management password, that the new password should be tried against that node before being stored in the DB. If an FTP connection fails with the new credentials, show a big fat message saying the credentials are bad and won’t be stored, and to first update .fogsettings and re-run the installer, and that they ought to have web ui credentials defined too so the installer can auto-update the node’s password FOR them.

[Wayne Workman]

IMHO, even requiring ui credentials inside .fogsettings creates an unnecessary complexity for fog. When I setup this initially using just BASH, it didn’t require any such ui credentials, but only access to the DB, which the main already has, and a remote node has because the user has to enter the fogstorage credentials. The new way Tom has it setup is php based, and requires valid web interface credentials.

I’ve discussed this with Tom at great length several times, he feels differently.

[alansopro]

@george1421 When running the showmount -e 127.0.0.1 in SSH it gives me a Port mapper failure - timed out error.

I did reboot the system but I mounted the external drive back using mount --bind /media/EXT /images/EXT

[Tom Elliott]

@alansopro Try:

service rpcbind restart; service nfsd restart

[alansopro]

@Tom-Elliott NFSD is an unrecognized service.

[Tom Elliott]

again, what information do we have?

What’s the OS you’re running?

[alansopro]

@Tom-Elliott Sorry I’m running CentOS 6.8 Final /w FOG 1.3.0 RC4 (Trying to upgrade to RC5 but fails on the NFS setting up/starting step.

[Tom Elliott]

@alansopro If you replace nfsd with just nfs does it work?

[Wayne Workman]

@phishphan 's issue was FTP credentials. I helped him get it sorted.

[alansopro]

@Tom-Elliott

This is what I get when trying to restart it.

service nfs restart
Shutting down NFS daemon: [ OK ]
Shutting down NFS mountd: [ OK ]
Shutting down NFS quotas: [FAILED]
Shutting down NFS services: [ OK ]
Shutting down RPC idmapd: [ OK ]
Starting NFS services: [ OK ]
Starting NFS quotas: kCannot register service: RPC: Timed out
rpc.rquotad: unable to register (RQUOTAPROG, RQUOTAVERS, udp).