database update failed after capture
-
@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??
-
@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/.fogsettingsexactly 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. -
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
fogstoragecredentials. 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.
-
@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
-
@alansopro Try:
service rpcbind restart; service nfsd restart -
@Tom-Elliott NFSD is an unrecognized service.
-
again, what information do we have?
What’s the OS you’re running?
-
@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.
-
@alansopro If you replace nfsd with just nfs does it work?
-
@phishphan 's issue was FTP credentials. I helped him get it sorted.
-
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). -
Yet this morning I restarted it and everything is fine. So I’m really confused. Let me try capturing an image again…
EDIT:
I was able to get it working and I searched the apache logs and found an error on on a fogmanagement file which someone else had a topic on and had to remove a & symbol. Everything seems to be good and the image was captured. Thank you.
-
@alansopro Why not use CentOS 7? It is free, and newer. We even have this spiffy tutorial for it: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7
Clearly the build you have has issues. These would likely be resolved in CentOS 7.
