@Tom-Elliott I don’t think it’s a mysql error but a php error, php for centos tends to be a little tricky and some things are missing on the redhat builds, the apache logs point out that same php error, maybe we could try an alternative for mysqli->query
Posts made by jdmg94
-
RE: Fog painfully slow with plenty RAM left
-
RE: Fog painfully slow with plenty RAM left
@Tom-Elliott just updated, installation went fine but, home page is still not loading, and when trying to deploy an image I get a new error
-
RE: vsftpd configuration not compatible on centos 6.x
@Tom-Elliott updated to the latest trunk, vsftpd is working now
-
RE: Fog painfully slow with plenty RAM left
@Sebastian-Roth tried that, same results
-
RE: vsftpd configuration not compatible on centos 6.x
@Wayne-Workman same error, apparently the configuration is overwritten by the installer
-
RE: Fog painfully slow with plenty RAM left
@Wayne-Workman Apache error logs state the following
[Wed Apr 13 03:39:58 2016] [error] [client 10.54.0.203] PHP Warning: mysqli::query(): invalid object or resource mysqli\n in /var/www/html/fog/lib/db/mysql.class.php on line 49, referer: http://fogserver.collective.lan/management/index.php?node=home
and I guess this error is the one preventing the home folder from loading completely
-
Fog painfully slow with plenty RAM left
I recently updated to the latest trunk and I noticed that fog became painfully slow,
I checked the RAM usage on the server and it was over 80% freenow the CPU is being taken over by the apache server, which wasn’t happening before
the home screen is not displaying all the data, but its done loading
and when I try to schedule a task I get a php error
Long story short, I updated my fog installation and everything went south
-
vsftpd configuration not compatible on centos 6.x
The current configuration uses
allow_writeable_chroot
which is no supported on vsftpd versions below 3.x
edit: I’m running the latest trunk
-
RE: wget failure on client's image
@Wayne-Workman BTW, vi is as buggy as it can get on the debugging interface on the clients side, could you guys consider switching to nano instead?
-
RE: wget failure on client's image
@Wayne-Workman so here’s my setup
I have a server with 2 nics, eth0 is on a vlan that has all the test computers on it, this vlan has no internet connection nor has it access anywhere else but its own computers.
eth1 is on a vlan that has internet and access to my desktop, which is the one I do ssh on.
when I run the script you sent on a server outside the test vlan I get a “7013” response
but when I run the same file on a client computer on the test vlan I just get a blank response.
I can ping the server, but I don’t really know what could be causing the trouble here.I just realized I have a typo, my bad it works on both vlans, response is 7013
-
RE: wget failure on client's image
@Sebastian-Roth my document root is /var/www/html/fog/
so usually I get
fogserver/management
instead of
fogserver/fog/management
-
RE: wget failure on client's image
@Tom-Elliott well my virtual host is set to have the fog folder as document root, maybe that’s causing a conflict there?
-
RE: wget failure on client's image
I tried running that line from a different server to check on the syntax
this is what I got
-
wget failure on client's image
Hello guys,
I’m currently on the latest trunk, and i’m trying to register my hosts/send inventory and I always get stuck on this point
This wget line is the one that causes the trouble, I can ping my fog server, but this line here won’t get through
Here’s the error message:
sorry for the potato quality, I’m on a temporary phone right now
-
RE: FOGUpdater.sh is not compatible with the latest trunk
@Wayne-Workman Just trying to get this working, I have a couple other bugs to report but I’m no longer at my office now, I’ll get to bug-squashing tomorrow morning
-
FOGUpdater.sh is not compatible with the latest trunk
Hello again guys!
On line 10 of the mentioned file above I found the following:
[[ ! -f ${docroot}${webroot}config.class.php && ! -f ${docroot}${webroot}Config.class.php ]] && handleError " No config file found" 4
The updater is looking for the config file on /
but the file in the latest branch is in /lib/fog/
I changed the lines here and it worked just fineOkay maybe it needs some work I’m getting an error now
-
RE: no default.ipxe
@Sebastian-Roth yay contributing! Thanks guys! It’s working now
-
RE: no default.ipxe
no worries I checked the error log, and it may have been a typo the error is the following:
Starting dhcpd: ^[[60G[^[[0;32m OK ^[[0;39m] status: unrecognized service
so I’m assumming someone typed
sudo service **dhcp** status
instead of
sudo service **dhcpd** status
I’ll check the install script and get back to you guys.