Open PaulMcF1987 opened 1 year ago
Please attach full logs (PHP/Apache/Nginx/Browser/CRM Logs)
@mariuszkrzaczkowski How do I obtain the CRM logs?
By browser logs, you mean console?
@mariuszkrzaczkowski How do I obtain the CRM logs?
https://yetiforce.com/en/knowledge-base/documentation/developer-documentation/item/debugging
By browser logs, you mean console?
Yes
@mariuszkrzaczkowski
I tried running the install again The only errors that are showing
MQSL Log
2022-07-12 10:13:09 4117 [Warning] IP address '172.23.0.2' could not be resolved: Name or service not known
2022-07-12 10:37:57 4266 [Warning] Aborted connection 4266 to db: 'YetiForce' user: 'YetiAdmin' host: '172.23.0.2' (Got an error reading communication packets)
2022-07-12 11:20:05 4721 [Warning] Aborted connection 4721 to db: 'YetiForce' user: 'YetiAdmin' host: '172.23.0.2' (Got an error reading communication packets)
2022-07-12 11:46:01 4990 [Warning] IP address '172.24.0.2' could not be resolved: Name or service not known
2022-07-12 11:46:01 4990 [Warning] Access denied for user 'YetiAdmin'@'172.24.0.2' (using password: YES)
2022-07-12 11:54:55 5019 [Warning] Aborted connection 5019 to db: 'YetiForce' user: 'YetiAdmin' host: '172.24.0.2' (Got timeout reading communication packets)
2022-07-12 11:56:36 5092 [Warning] Access denied for user 'YetiAdmin'@'172.24.0.2' (using password: YES)
2022-07-12 11:56:43 5095 [Warning] Access denied for user 'YetiAdmin'@'172.24.0.2' (using password: YES)
2022-07-12 11:56:50 5097 [Warning] Access denied for user 'YetiAdmin'@'172.24.0.2' (using password: YES)
2022-07-12 11:56:52 5098 [Warning] Access denied for user 'YetiAdmin'@'172.24.0.2' (using password: YES)
2022-07-12 11:56:52 5099 [Warning] Access denied for user 'YetiAdmin'@'172.24.0.2' (using password: YES)
2022-07-12 11:56:54 5100 [Warning] Access denied for user 'YetiAdmin'@'172.24.0.2' (using password: YES)
2022-07-12 11:56:54 5101 [Warning] Access denied for user 'YetiAdmin'@'172.24.0.2' (using password: YES)
2022-07-12 11:57:07 5103 [Warning] Access denied for user 'YetiAdmin'@'172.24.0.2' (using password: YES)
2022-07-12 12:03:30 5193 [Warning] IP address '172.27.0.2' could not be resolved: Name or service not known
2022-07-12 12:07:08 5195 [Warning] Aborted connection 5195 to db: 'Yetiforce' user: 'YetiAdmin' host: '172.27.0.2' (Got an error reading communication packets)
2022-07-12 12:26:37 5480 [Warning] IP address '172.28.0.2' could not be resolved: Name or service not known
2022-07-12 12:38:01 5485 [Warning] Aborted connection 5485 to db: 'Yetiforce' user: 'YetiAdmin' host: '172.28.0.2' (Got an error reading communication packets)
Nginx and Apache2 do not have any errors showing
When I navigate to cache/logs
there are no log files showing, only index.html which only has
<!DOCTYPE html>
<html><head><title></title></head><body></body></html>
I ran a fresh install on a fresh database to check console and got:
And this is the DB after
The only error that is highlighted during the setup is
However, this was also highlighted on my old server and it worked fine. Also, the file path mentioned does not seem to exist. I checked both the cloned repository on my server and the repository shown on Githib, it is not in either
@mariuszkrzaczkowski Ran the install on an incognito browser to get rid of all the mention of extensions in console...
All console shows in incognito is
@mariuszkrzaczkowski based on what I have provided above, have you any thoughts on what may be causing the error?
I have checked all of the error logs and that is all that there was.
I cleared Yetiforce from the system and reinstalled the docker container... not sure if these errors are relevant but the ones I noticed we...
Step 12/50
debconf delaying package configuration since apt-utils is not installed
step 43/50
warning package.json: License should be a valid SPDX license expression
warning ../../package.json: License should be a valid SPDX license expression
warning YetiForceCRM: License should be a valid SPDX license expression
warning " > vuex@3.6.2" has unmet peer dependency "vue@^2.0.0".
@mariuszkrzaczkowski should I assume that you dont know what might be causing the issue? Would I be better looking at an alternative CRM option?
@mariuszkrzaczkowski should I assume that you dont know what might be causing the issue?
We deal with github applications in our free time, now it is the holiday period so we have fewer possibilities. We publish Decker only for testing or development purposes, in order to work productively, it requires various changes.
Would I be better looking at an alternative CRM option?
You are free decide for yourself remember that it's open source and the community also builds it and creates it. And you want answers already, and sometimes you have to wait
@mariuszkrzaczkowski You asked for details yesterday morning and I provided the details asked for reasonably quickly. Nowhere did you ask for the details and say that you would get round to it when you have time. I was under the impression that you had asked for the details because you wanted to try and diagnose the issue
We deal with github applications in our free time, now it is the holiday period so we have fewer possibilities. We publish Decker only for testing or development purposes, in order to work productively, it requires various changes.
Does that mean that the docker published image is not fit to be used as a CRM for a business?
Also... Given that I cannot seem to connect the Docker version to a database, I would be weary of installing direct onto the server in case I have the same issue. If the docker image is for testing only then Id say, thus far, the testing hasnt went very well
Same issue for me. Are there some information? there is no apparently reason for this behavior. I've installed Yetiforce many times with no problem...
I installed YetiForce on my previous server with no issues, it installed fine and worked fine when trialing...
I followed the exact same steps for my new server and after the installation I get
I tried the process again but Yetiforce would not load, I kept getting the
504
error. I had to usedocker-compose down
followed bydocker-compose up -d
to bring it back online... I then tried to install Yetiforce again and got the following errorI checked the database that I created for Yetiforce It was an empty database but now has 710 tables and a size of 22.8 MB but apparently there has been no install...
I deleted the database and tried again and I get the same as above... again, I get the
504
error and theinstall unsuccessful
This time the db has been populated with 39 tables and 12.2 MB of data
Checked the Docker Logs for the container and Ill they say is
Apache Error log doesnt give anything for this time
MYSQL Error Log