(04-14-2018, 12:14 PM)monty Wrote:

(04-14-2018, 10:48 AM)tommiehansen Wrote: Same answer as my previous answer apply.

Thx, solved. Cause of problem is SchaffTrendCycle strategy.

(04-02-2018, 03:25 PM)PapoKarlo Wrote:

Quote:PapoKarlo

Can you show your nginx configuration for reference purpose?

server {
       listen 80 default_server;
       listen [::]:80 default_server;
       root /var/www/html;
       server_name _;
       location / {
               try_files $uri $uri/ =404;
       }
       location ~ \.php$ {
               include snippets/fastcgi-php.conf;

               fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
               fastcgi_read_timeout 900;
       }
}

(04-14-2018, 04:46 PM)tommiehansen Wrote: Major update

MySQL (InnoDB) is now an option that can be used instead of SQLite and code has been re-written to use this, if set, wherever possible.

Why? Because if running massive runs with 10+ threads etc SQLite simply is too prone to errors (and corruption) and isn't a great choice for say 30-100 000+  runs, something that is quite feasible when running 10+ threads and date ranges that span just 3-4 months.

So this became somewhat of a problem and has been solved by letting the user choose MySQL as the database.
Requires the user to set this up in its user.config.php (see new sample.config.php).

Using MySQL is also now the recommended way to run Gabby if you aren't just testing things out.

---

This also introduces a breaking change -- the naming scheme for the database names (SQLite as well) has changed.
This mean that any old runs/database you have for SQLite will now not show up at all since GAB will not recognize these as valid databases (or it will error out).

To solve this use the included tool Compatibility Fix. Currently this will rename your SQLite databases to the new naming scheme automatically.
You'll find it under <your install directory>/tools e.g. localhost:80/gab/tools

to update do:
git pull

or to install the new version to an entirely different dir create a new one and do:
git pull https://github.com/tommiehansen/gab.git

(04-14-2018, 08:12 PM)gekko2yuno Wrote:

(04-14-2018, 04:46 PM)tommiehansen Wrote: Major update

MySQL (InnoDB) is now an option that can be used instead of SQLite and code has been re-written to use this, if set, wherever possible.

Why? Because if running massive runs with 10+ threads etc SQLite simply is too prone to errors (and corruption) and isn't a great choice for say 30-100 000+  runs, something that is quite feasible when running 10+ threads and date ranges that span just 3-4 months.

So this became somewhat of a problem and has been solved by letting the user choose MySQL as the database.
Requires the user to set this up in its user.config.php (see new sample.config.php).

Using MySQL is also now the recommended way to run Gabby if you aren't just testing things out.

---

This also introduces a breaking change -- the naming scheme for the database names (SQLite as well) has changed.
This mean that any old runs/database you have for SQLite will now not show up at all since GAB will not recognize these as valid databases (or it will error out).

To solve this use the included tool Compatibility Fix. Currently this will rename your SQLite databases to the new naming scheme automatically.
You'll find it under <your install directory>/tools e.g. localhost:80/gab/tools

to update do:
git pull

or to install the new version to an entirely different dir create a new one and do:
git pull https://github.com/tommiehansen/gab.git

The database name is not required in     Example for mysql: '127.0.0.1:3306,TommieHansenIsTheBest,MySuperPassword' ?

(04-17-2018, 03:53 PM)gekko2yuno Wrote: Hi
I am getting error messages. It worked last time but after the pull its not working.I am on nginx with ssl.

Code:

Notice: Trying to get property of non-object in /var/www/gab/system/class.gab.php on line 113

Warning: Invalid argument supplied for foreach() in /var/www/gab/index.php on line 34
CLEAR CACHE
Notice: Undefined variable: dateFrom in /var/www/gab/index.php on line 165

Notice: Undefined variable: dateTo in /var/www/gab/index.php on line 166

(04-17-2018, 04:21 PM)tommiehansen Wrote:

(04-17-2018, 03:53 PM)gekko2yuno Wrote: Hi
I am getting error messages. It worked last time but after the pull its not working.I am on nginx with ssl.

Code:

Notice: Trying to get property of non-object in /var/www/gab/system/class.gab.php on line 113

Warning: Invalid argument supplied for foreach() in /var/www/gab/index.php on line 34
CLEAR CACHE
Notice: Undefined variable: dateFrom in /var/www/gab/index.php on line 165

Notice: Undefined variable: dateTo in /var/www/gab/index.php on line 166

This mean that
1. You have no Gekko UI instance running, thus it cannot get datasets since the source returns 0 (null) -- in this case everything fails.
2. You have failed to point your user.config.php to your Gekko server or have pointed it to somewhere that is no longer valid

Do note that in a couple of versions ago it looked like this: $server = "http://localhost:3000/api".
This has changed to "http://localhost:3000".

To solve
1. Check that you actually have Gekko UI running somewhere
2. Check your user.config.php file inside gab/system/user.config.php
3. Check the user.config.sample.php to see if you're missing something obvious
4. Run gab/tools/ and click 'Sanity check' to see if it complains about something
5. If everything fails create a new directory and git clone gab into that new directory and see if it works (you may have edited system files)

Good luck!

(04-17-2018, 08:44 PM)tommiehansen Wrote: You seem to have some problems with your Gekko install. Does it even work, does the regular Gekko UI even work for you?

All the errors you're talking about has to do with GAB communicating with the Gekko API endpoint.
This could have to do with something with your HTTPS (SSL) config that is doing something unknown that makes
the use of the function curl_cache() not work.

Without that working nothing will work.