No Log Files r4914 Version: 6517
-
@Tom-Elliott
Yes on the Master NodeAnd i will work on it some more tomorrow…
[Tue Mar 01 19:12:49.296118 2016] [:error] [pid 14800] [client 10.24.28.18:50081] PHP Warning: mysqli::query(): invalid object or resource mysqli\n in /var/www/html/fog/lib/db/mysql.class.php on line 52 [Tue Mar 01 19:12:49.296772 2016] [:error] [pid 14800] [client 10.24.28.18:50081] PHP Warning: mysqli::select_db(): invalid object or resource mysqli\n in /var/www/html/fog/lib/db/mysql.class.php on line 40 [Tue Mar 01 19:12:49.296808 2016] [:error] [pid 14800] [client 10.24.28.18:50081] PHP Warning: mysqli::query(): invalid object or resource mysqli\n in /var/www/html/fog/lib/db/mysql.class.php on line 52 [Tue Mar 01 19:12:49.297457 2016] [:error] [pid 14800] [client 10.24.28.18:50081] PHP Warning: mysqli::select_db(): invalid object or resource mysqli\n in /var/www/html/fog/lib/db/mysql.class.php on line 40 [Tue Mar 01 19:12:49.297491 2016] [:error] [pid 14800] [client 10.24.28.18:50081] PHP Warning: mysqli::query(): invalid object or resource mysqli\n in /var/www/html/fog/lib/db/mysql.class.php on line 52 [Tue Mar 01 19:12:49.298141 2016] [:error] [pid 14800] [client 10.24.28.18:50081] PHP Warning: mysqli::select_db(): invalid object or resource mysqli\n in /var/www/html/fog/lib/db/mysql.class.php on line 40 [Tue Mar 01 19:12:49.298174 2016] [:error] [pid 14800] [client 10.24.28.18:50081] PHP Warning: mysqli::query(): invalid object or resource mysqli\n in /var/www/html/fog/lib/db/mysql.class.php on line 52 [Tue Mar 01 19:12:49.298819 2016] [:error] [pid 14800] [client 10.24.28.18:50081] PHP Warning: mysqli::select_db(): invalid object or resource mysqli\n in /var/www/html/fog/lib/db/mysql.class.php on line 40 [Tue Mar 01 19:12:49.298851 2016] [:error] [pid 14800] [client 10.24.28.18:50081] PHP Warning: mysqli::query(): invalid object or resource mysqli\n in /var/www/html/fog/lib/db/mysql.class.php on line 52```
-
@Raymond-Bell when restarting the image replicator service, can you just do it with stop and start instead of just restart?
Maybe first get some output
ps -ef | grep FOG
-
@Tom-Elliott said:
@Raymond-Bell when restarting the image replicator service, can you just do it with stop and start instead of just restart?
Maybe first get some output
ps -ef | grep FOG
I do it with stop / start I never use restart
-
@Raymond-Bell more info gathering: does the image you uploaded exist on the other node
-
@Tom-Elliott said:
@Raymond-Bell more info gathering: does the image you uploaded exist on the other node
No i have to ftp download it to drive and upload it to the other node. And it worked fine before the update
-
@Raymond-Bell what were you on before you updated?
Could you run a mkdir for the image folder name on the receiving nodes? Ensure the /images folder is chowned for the fog user recursively and chmod 777 recursively? Then restart fogimagereplicator again?
-
@Raymond-Bell said:
No i have to ftp download it to drive and upload it to the other node. And it worked fine before the update
I have just confirmed that the replication service works without any changes in the latest trunk.
-
@Tom-Elliott
So i spent all day installing new fog server Ubuntu 14.04 / Fog 1.2.0 / then updated to latest SVN
Same on a new storage node…Import database (had to change size in php.ini to 200MB) but got it imported and all stuff is the
Uploaded a Image from backup drive i had it on, made sure name and eveything was the same, made sure all passwords matched
tried to deploy image and i get this again
-
@Raymond-Bell Checked the image settings? Does the image show up (size on server?). And is the image properly configured for the host you are trying to deploy?
-
@Sebastian-Roth Yes it shows size And yes i have used this image on this host many times.
-
I created a new image via web and i am uploading it now called it test 3-2-16
Going to try to deploy it when i get done uploading this one let you know -
So i can upload a new image just fine and it moves from dev to it’s folder just fine
But when i try to deploy it i get this error again…Failed to create
Also i still have the IP Passed is incorrect error under view logs
-
@Raymond-Bell I don’t know your timezone and all, but my timezone is Eastern Standard Time (I live in the state of New York). I wonder if it may be faster and more beneficial to run a teamviewer or remote connection with you to try helping track this down.
-
@Tom-Elliott I am central time
-
@Raymond-Bell maybe we can teamviewer now? I have a little time.
-
Remoted in and found issue was due to ftp changes recently. Had an isdir ? dirname of file : dirname to pass. When logically it should’ve been !isdir ? Dirname of file : dirname to pass
-
@Tom-Elliott I’m more impressed that it hasn’t been noticed more often, but glad it was simple enough find and fix.
-
@Tom-Elliott said:
@Tom-Elliott I’m more impressed that it hasn’t been noticed more often, but glad it was simple enough find and fix.
Thank you for your time.