Random 500 error Invalid connection

[lucableve]

• Gitea version (or commit ref): 1.7
• Git version: 1.8.3.1
• Operating system: Centos 7
• Database (use [x]):
  • PostgreSQL
  • MySQL (MariaDB 10.2)
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:

Description

Hi,
after gitea installation I have random 500 errors. The logs return this:
2019/01/15 01:59:48 [...itea/routers/home.go:138 RenderRepoSearch()] [E] SearchRepositoryByName: Count: invalid connection
2019/01/15 01:59:49 [...itea/routers/home.go:138 RenderRepoSearch()] [E] SearchRepositoryByName: Count: invalid connection
2019/01/15 02:00:25 [...itea/routers/home.go:138 RenderRepoSearch()] [E] SearchRepositoryByName: Count: invalid connection
2019/01/15 02:09:37 [.../gogits/cron/cron.go:92 Run()] [E] MirrorUpdate: invalid connection

I have this system: Nginx reverse proxy to gitea :3000 on Db mysql (engine : mariadb 12)

[lucableve]

I have reinstalled vps and before gitea installing check into verbose log, random return 404 :
[Macaron] 2019-01-15 12:26:16: Completed GET /user/login 404 Not Found in 3.923679ms

my config nginx is :
server {
listen 51.77.202.209:80;
server_name xxxxx.com www.xxxxx.com;
error_log /var/log/httpd/domains/xxxxx.com.error.log error;

# reverse proxy
location / {
     proxy_pass http://127.0.0.1:3000/;
}

location ~ /\.ht    {return 404;}
location ~ /\.svn/  {return 404;}
location ~ /\.git/  {return 404;}
location ~ /\.hg/   {return 404;}
location ~ /\.bzr/  {return 404;}

include /home/vps/conf/web/nginx.xxxxx.com.conf*;

}

[zeripath]

The http proxy isn't the connection that your errors are referring to. The problem appears to be with the communication between Gitea and the db. Does the xorm.log reveal anything?

[lucableve]

xorm.log not have errors.
I forgot to tell you I have installed vestacp panel but
I have configured manually reverse proxy and db.

I started server gitea and this is log before first error invalid connection:

2019/01/15 13:16:57 [I] Log Mode: File(Info)
2019/01/15 13:16:57 [I] XORM Log Mode: File(Info)
2019/01/15 13:16:57 [I] Cache Service Enabled
2019/01/15 13:16:57 [I] Session Service Enabled
2019/01/15 13:16:57 [I] Git Version: 1.8.3.1
2019/01/15 13:16:57 [I] SQLite3 Supported
2019/01/15 13:16:57 [I] Run Mode: Production
2019/01/15 13:16:57 [I] Listen: http://0.0.0.0:3000
2019/01/15 13:17:57 [...s/context/context.go:235 func1()] [E] GetUserById: invalid connection

this is my db config app.ini

[database]
DB_TYPE = mysql
HOST = ip:3306 //Same problem with localhost and 127.0.0.1
NAME = name
USER = usr
PASSWD = psswd
SSL_MODE = disable
PATH = data/gitea.db

[zeripath]

Ok your Gitea version doesn't make sense. We haven't released 1.8.3.1 that appears to be your git version which is quite old. I think that's the default version of git on centos 7 so it should be upgraded. If git has been upgraded Gitea doesn't appear to be using it. This was mentioned in another issue if you look for it.

The MariaDB version you're reported also doesn't quite make sense. There's also no version 12 of Maria dB.

[lucableve]

I'm sorry , I have confused version, have fixed first comment.
Try update git version

[typeless]

By 'random' errors, do you mean some queries work fine? Did it fail with some types of queries and work for others?

[lunny]

That's an error from mysql driver. Maybe we should upgrade the driver library.

[lucableve]

@typeless
on 10 attempts of the same query 2 return invalid connection randomly

[zeripath]

May be there are dead connections in the pool?

[typeless]

@lucableve I guess @lunny was right. You may try to upgrade the driver library and see if that works.
I am not sure where the driver library in question is though.

Edit: probably this

Edit2: also go-sql-driver/mysql#836

[lucableve]

Ok, I try this solution, update you

[lucableve]

I downloaded binary master to test fix @lunny @zeripath but error occurs again.
Do I have to try the source version?

[luxiaok]

The same error and situation kept a long time.

[samek]

With 1.7.1 is much better, but we still do get them.

[bobemoe]

I've been researching this over at #6804. I've tried Gitea 1.9-dev which should include the fix above, but still same issue.

I think @zeripath is right, dead connections in the pool. Watch mysql processlist, error happens straight after connection timeout (60s in my mysql.cnf)

But why did the update not work?

[zeripath]

Because I suspect the connections are timing out due to deadlocks