search

turnkeylinux / tracker

TurnKey Linux Tracker
https://www.turnkeylinux.org
68 stars 16 forks source link

Error Fetching Data #1907

Open skyfrost07 opened 3 months ago

skyfrost07 commented 3 months ago

Hi,

Could you please help to reviewing the current/latest version of SuiteCRM? It appears there's a recurring issue with the database connection, particularly after adding users, accounts, and opportunities. Once this error occurs, users are unable to sign out or sign in, as the system keeps prompting invalid credential or parameter errors. data display at dashboard also seems not accurate. Your assistance is greatly appreciated.

I'm a newcomer to GitHub and still unsure about the process for submitting requests. If there's anything specific I need to provide, please don't hesitate to inform me. thank you

JedMeister commented 2 months ago

Thank you for your report.

I'll aim to look into it ASAP.

JedMeister commented 2 months ago

Just following up on this. I can't reproduce, but I'm wondering if MySQL (actually MariaDB) is failing/crashing?

To check what it's doing, please run this:

systemctl status mariadb
skyfrost07 commented 2 months ago

hi Jeremy,

thank you for the update. please find below the mariadb status:

***@***.*** ~# systemctl status mariadb
* mariadb.service - MariaDB 10.11.3 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; preset:
enabled)
     Active: active (running) since Thu 2024-02-08 11:34:52 +08; 1 month 7
days ago
       Docs: man:mariadbd(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 542 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d
/var/run/mysqld (code=exited, status=0/SUCCES>
    Process: 567 ExecStartPre=/bin/sh -c systemctl unset-environment
_WSREP_START_POSITION (code=exited, status=0/SUCCE>
    Process: 574 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ]
&& VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/g>
    Process: 741 ExecStartPost=/bin/sh -c systemctl unset-environment
_WSREP_START_POSITION (code=exited, status=0/SUCC>
    Process: 747 ExecStartPost=/etc/mysql/debian-start (code=exited,
status=0/SUCCESS)
   Main PID: 681 (mariadbd)
     Status: "Taking your SQL requests now..."
      Tasks: 21 (limit: 2312)
     Memory: 291.6M
        CPU: 11min 43.296s
     CGroup: /system.slice/mariadb.service
             `-681 /usr/sbin/mariadbd

Feb 08 11:34:51 suitecrm mariadbd[681]: 2024-02-08 11:34:51 0 [Note]
InnoDB: Loading buffer pool(s) from /var/lib/mysql>
Feb 08 11:34:51 suitecrm mariadbd[681]: 2024-02-08 11:34:51 0 [Warning]
'innodb-file-format' was removed. It does nothi>
Feb 08 11:34:51 suitecrm mariadbd[681]: 2024-02-08 11:34:51 0 [Warning]
'innodb-large-prefix' was removed. It does noth>
Feb 08 11:34:51 suitecrm mariadbd[681]: 2024-02-08 11:34:51 0 [Warning] You
need to use --log-bin to make --expire-logs>
Feb 08 11:34:51 suitecrm mariadbd[681]: 2024-02-08 11:34:51 0 [Note] Server
socket created on IP: '127.0.0.1'.
Feb 08 11:34:52 suitecrm mariadbd[681]: 2024-02-08 11:34:52 0 [Note]
/usr/sbin/mariadbd: ready for connections.
Feb 08 11:34:52 suitecrm mariadbd[681]: Version: '10.11.3-MariaDB-1'
 socket: '/run/mysqld/mysqld.sock'  port: 3306  De>
Feb 08 11:34:52 suitecrm systemd[1]: Started mariadb.service - MariaDB
10.11.3 database server.
Feb 08 11:34:52 suitecrm /etc/mysql/debian-start[829]: Triggering
myisam-recover for all MyISAM tables and aria-recover>
Feb 08 11:34:53 suitecrm mariadbd[681]: 2024-02-08 11:34:53 0 [Note]
InnoDB: Buffer pool(s) load completed at 240208 11>
lines 1-28/28 (END)

It appears that there's an intermittent connection issue with the database. When the connection is stable, everything operates smoothly and all data is retrieved successfully.

[image: image.png]

Screenshot 1 froze while attempting to sign out, prompting me to refresh the browser and sign out again.

[image: image.png]

Screenshot 2 typically displays this error predominantly after refreshing the browser. When this occurs, the data display also appears incorrect, as shown in screenshot 3.

[image: image.png]

Screenshot 3 shows a filter applied for sales stages set to "Proposal," but it's also displaying other stages alongside it.

Even after installing a fresh suiteCRM, the problem arises once I create a user or add opportunities.

hope to hear from you soon.

thank you and have a nice day~

Regards, Karma

On Thu, Mar 14, 2024 at 12:56 PM Jeremy Davis @.***> wrote:

Just following up on this. I can't reproduce, but I'm wondering if MySQL (actually MariaDB) is failing/crashing?

To check what it's doing, please run this:

systemctl status mariadb

— Reply to this email directly, view it on GitHub https://github.com/turnkeylinux/tracker/issues/1907#issuecomment-1996460146, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGRNZLMSAMSPCNPX4ID4FOLYYEUZDAVCNFSM6AAAAABD7D6M6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJWGQ3DAMJUGY . You are receiving this because you authored the thread.Message ID: @.***>

JedMeister commented 2 months ago

Not sure why, but the MariaDB output wasn't rendering as a code block?! Anyway, I've reposted it below because that makes it easier to read.

Regardless, nothing wring with the MariaDB service and it looks fine!? It has been running for ~5 weeks and no additional log entries since it was started! I also note that it's not using a significant amount of memory or CPU. So my guess was completely wrong!

Despite no issues with MariDB, perhaps it's worth running a package upgrade on your server? Do that like this:

apt update
apt upgrade -y

Unfortunately, your screenshots aren't visible. I'm guessing your replied via email and it seems that GH doesn't handle that well? If you get a chance could you please try logging into GH and reposting them?

Also I've just had a quick look at SuiteCRM docs and there should be a couple of log files to check for errors. They are /var/www/suitecrm/public/legacy/suitecrm.log & /var/www/suitecrm/logs/prod/prod.log. If they are really big, then perhaps just give me the last 50 lines like this:

tail -50 /var/www/suitecrm/public/legacy/suitecrm.log

And

tail -50 /var/www/suitecrm/logs/prod/prod.log

Also, have you updated the SuiteCRM software itself? I notice that there is a newer version that what our appliance ships with (v18.0 ships with SuiteCRM v.8.4.0, latest is v8.5.1. Before updating, be sure to create a backup first - just in case something goes wrong!

You should be able to update via the web UI:

https://docs.suitecrm.com/admin/installation-guide/using-the-upgrade-wizard/

There is also a CLI update path:

https://docs.suitecrm.com/admin/installation-guide/upgrading/#_update_from_command_line

MariaDB service status repost:

***@***.*** ~# systemctl status mariadb
* mariadb.service - MariaDB 10.11.3 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; preset: enabled)
     Active: active (running) since Thu 2024-02-08 11:34:52 +08; 1 month 7 days ago
       Docs: man:mariadbd(8) 
             https://mariadb.com/kb/en/library/systemd/
    Process: 542 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCES>
    Process: 567 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCE>
    Process: 574 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/g>
    Process: 741 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCC>
    Process: 747 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
   Main PID: 681 (mariadbd)
     Status: "Taking your SQL requests now..."
      Tasks: 21 (limit: 2312)
     Memory: 291.6M
        CPU: 11min 43.296s
     CGroup: /system.slice/mariadb.service
             `-681 /usr/sbin/mariadbd

Feb 08 11:34:51 suitecrm mariadbd[681]: 2024-02-08 11:34:51 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql>
Feb 08 11:34:51 suitecrm mariadbd[681]: 2024-02-08 11:34:51 0 [Warning] 'innodb-file-format' was removed. It does nothi>
Feb 08 11:34:51 suitecrm mariadbd[681]: 2024-02-08 11:34:51 0 [Warning] 'innodb-large-prefix' was removed. It does noth>
Feb 08 11:34:51 suitecrm mariadbd[681]: 2024-02-08 11:34:51 0 [Warning] You need to use --log-bin to make --expire-logs>
Feb 08 11:34:51 suitecrm mariadbd[681]: 2024-02-08 11:34:51 0 [Note] Server socket created on IP: '127.0.0.1'.
Feb 08 11:34:52 suitecrm mariadbd[681]: 2024-02-08 11:34:52 0 [Note] /usr/sbin/mariadbd: ready for connections.
Feb 08 11:34:52 suitecrm mariadbd[681]: Version: '10.11.3-MariaDB-1'  socket: '/run/mysqld/mysqld.sock'  port: 3306  De>
Feb 08 11:34:52 suitecrm systemd[1]: Started mariadb.service - MariaDB 10.11.3 database server.
Feb 08 11:34:52 suitecrm /etc/mysql/debian-start[829]: Triggering myisam-recover for all MyISAM tables and aria-recover>
Feb 08 11:34:53 suitecrm mariadbd[681]: 2024-02-08 11:34:53 0 [Note] InnoDB: Buffer pool(s) load completed at 240208 11>
lines 1-28/28 (END)