yes that is a good point, regarding the socket, which kind of configuration do you usually use when setting up Suite 7?
Regarding the log. Please check on public/legacy/suitecrm.log.
The install command after adding the Suite 8 side configuration, calls the silent install on legacy. Legacy is handling the bulk of the install process and it should log to suitecrm.log, if I’m not mistaken.
Welcome to the community and thank you for trying out Suite 8.
Also, sorry for the delay in replying, we are on a quite busy period at the moment.
Regarding the above question, Suite 8, at the moment still relies on Suite 7 for many things.
More details
just a bit of context:
For several reasons among them backwards compatibility reasons, Suite 8 still relies for a good part of the backend on the Suite 7. Suite 8 “contains” an Suite7 within it on the public/legacy folder and it uses a concept called “Legacy Handlers” to call suite 7 for whatever it needs.
Though the only place I see we are using the mysql_connect is in public/legacy/include/database/MysqlManager.php. Though preferably we should be using MysqliManager instead.
Do you have mysqli php module installed?
More details
The code on legacy is doing the following: public/legacy/include/database/DBManagerFactory.php
if (empty($config['db_manager'])) {
// standard types
switch ($type) {
case "mysql":
if (empty($sugar_config['mysqli_disabled']) && function_exists('mysqli_connect')) {
$my_db_manager = 'MysqliManager';
} else {
$my_db_manager = "MysqlManager";
}
break;
Check that the db config is correct on legacy config config.php
Check that the db config is correct on env.local on Suite8 root folder
If the above don’t work, could you please send a screenshot of the graqhql requests on the network tab that have an error (either a 500 or an error on the response body)? that can help in finding the root cause.
was looking into the code that outputs the above message.
Its on public/legacy/include/database/MysqliManager.php (Suite 7 code)
if (empty($this->database)) {
$GLOBALS['log']->fatal("Could not connect to DB server " . $dbhost . " as " . $configOptions['db_user_name'] . ". port " . $dbport . ": " . mysqli_connect_error());
As you can see from the above, the following message comes from the mysqli_connect_error().
It looks like mysqli is not able to reach the database.
I was looking into this issue and found this stackoverflow thread, which may help:
The link you’ve mentioned is the zip generated from github. This raises a good point and something we could make more clear on the release page on the documentation site.