Error Login

Use search.

There is no information in the search for this case, I am having connection problems in mysql, when setting these connections, increasing the timeout, the system issues another error which is to generate a large log file, knocking down the server, ie because of one problem, another was caused. And I have not been able to heal either, see the log file off, and tell me if this is correct, if it is, I would like you to explain to me why the file is still being generated.

<!--
<entry key='logger.enable'>false</entry>
<entry key='logger.level'>all</entry>
<entry key='logger.file'>./logs/tracker-server.log</entry>
-->
    
<entry key='logger.level'>off</entry>

Anton Tananaev6 years ago

I know that it has been discussed numerous times before, so there's definitely information on how to fix "too many open files".

P.S. please stop marking logs as "java" code.

Track-trace6 years ago

You might try to set the open file limit to 50000 instead of 100000

http://www.befirstcode.com/2017/10/increase-open-files-limit-for-traccar.html

smsoousa6 years ago

I was using this configuration as per the official Traccar configuration page:

soft nofile 50000
hard nofile 50000

but I saw now that it was not working, after I changed it to the one you informed:

root soft nofile 50000
root hard nofile 50000

It worked perfectly, I will do some tests after this and return to say if solved, thank you in advance.

smsoousa6 years ago

Anton and friends, even with mysql configured, I still see the timeout error, if it was not uncomfortable for you, could you checkmey my.cnf file that I posted earlier to see if it is configured properly? Or help me by saying which file to change and what information to put in order for this error to be remedied, I've researched a lot, made several attempts, but all without success. Because it returned the same error now of 30000ms

Track-trace6 years ago

Your log still said INFO|18909/0|Service traccar|19-04-17 04:38:08|java.util.concurrent.TimeoutException: Idle timeout expired: 30002/30000 ms

Did you already increase it even more ??

Track-trace6 years ago

Increase it to 50000 ms just to try..

https://support.rackspace.com/how-to/how-to-change-the-mysql-timeout-on-a-server/

smsoousa6 years ago

Bernhard Ruimschoot, thanks for your feedback, my my.cnf configuration is now like this, is that correct?

open_files_limit = 50000
wait_timeout = 50000
interactive_timeout = 50000
set global wait_timeout=60
set session wait_timeout=3600

Track-trace6 years ago

you could try it.

Often is trial and error. Actually i was just looking at traccar myself when i read about you problems.
Always make sure that you keep a backup of your default config files.

Actually on linux you also could install tuning-primer.sh and execute it as ./tuning-primer.sh

https://github.com/BMDan/tuning-primer.sh

It wil give you tips howto optimise you mysql server.

I use it myself to optimize mysql. I did see a good increase of stability. But actually i use mysql for webshops. But basicly that is the same usage of a database.

smsoousa6 years ago

even with the configuration made, the system continues to give error.

INFO|10472/0|Service traccar|19-04-19 16:42:22|[qtp751432670-271] WARN org.eclipse.jetty.http.HttpParser - badMessage: 400 Illegal character 0x16 for HttpChannelOverHttp@1931c2dc{r=0,c=false,a=IDLE,uri=}
INFO|10472/0|Service traccar|19-04-19 16:42:25|[qtp751432670-304] WARN org.eclipse.jetty.http.HttpParser - Illegal character 0x16 in state=START for buffer HeapByteBuffer@5745854e[p=1,l=517,c=16384,r=516]={\x16<<<\x03\x01\x02\x00\x01\x00\x01\xFc\x03\x03R?T\x98\xD95H...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00>>> ext-show-live-ro...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
INFO|10472/0|Service traccar|19-04-19 16:42:25|[qtp751432670-304] WARN org.eclipse.jetty.http.HttpParser - badMessage: 400 Illegal character 0x16 for HttpChannelOverHttp@1532f0a5{r=0,c=false,a=IDLE,uri=}
INFO|10472/0|Service traccar|19-04-19 16:42:25|[qtp751432670-271] WARN org.eclipse.jetty.http.HttpParser - Illegal character 0x16 in state=START for buffer HeapByteBuffer@115e8b67[p=1,l=517,c=16384,r=516]={\x16<<<\x03\x01\x02\x00\x01\x00\x01\xFc\x03\x03"\x01\xD8u\xE4\xEa\xC1...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00>>>3.142.251.174:808...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
INFO|10472/0|Service traccar|19-04-19 16:42:25|[qtp751432670-271] WARN org.eclipse.jetty.http.HttpParser - badMessage: 400 Illegal character 0x16 for HttpChannelOverHttp@27d477cd{r=0,c=false,a=IDLE,uri=}
INFO|10472/0|Service traccar|19-04-19 16:42:26|[qtp751432670-304] WARN org.eclipse.jetty.http.HttpParser - Illegal character 0x16 in state=START for buffer HeapByteBuffer@253aca2b[p=1,l=209,c=16384,r=208]={\x16<<<\x03\x01\x00\xCc\x01\x00\x00\xC8\x03\x032?\xFb\xB3\x95\xFc\xAb...\x12\x00\x00\x00\x1b\x00\x03\x02\x00\x02\x1a\x1a\x00\x01\x00>>>ID=naytxiyyffn316...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
INFO|10472/0|Service traccar|19-04-19 16:42:26|[qtp751432670-304] WARN org.eclipse.jetty.http.HttpParser - badMessage: 400 Illegal character 0x16 for HttpChannelOverHttp@36aee025{r=0,c=false,a=IDLE,uri=}
INFO|10472/0|Service traccar|19-04-19 16:54:22|[qtp751432670-352] WARN org.eclipse.jetty.server.handler.ResourceHandler - org.eclipse.jetty.io.EofException
INFO|10472/0|Service traccar|19-04-19 16:54:22|[qtp751432670-356] WARN org.eclipse.jetty.server.handler.ResourceHandler - org.eclipse.jetty.io.EofException
INFO|wrapper|Service traccar|19-04-19 17:01:19|Shutting down Wrapper
...
INFO|13916/0|Service traccar|19-04-19 17:02:02|[main] INFO org.eclipse.jetty.util.log - Logging initialized @8038ms
INFO|13916/0|Service traccar|19-04-19 17:02:02|[main] INFO org.eclipse.jetty.server.Server - jetty-9.2.24.v20180105
INFO|13916/0|Service traccar|19-04-19 17:02:04|[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@35eb153f{/api,null,AVAILABLE}
INFO|13916/0|Service traccar|19-04-19 17:02:04|[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.t.w.@119d8d13{/,null,AVAILABLE}
INFO|13916/0|Service traccar|19-04-19 17:02:04|[main] INFO org.eclipse.jetty.server.ServerConnector - Started ServerConnector@367bbec2{HTTP/1.1}{0.0.0.0:8082}
INFO|13916/0|Service traccar|19-04-19 17:02:04|[main] INFO org.eclipse.jetty.server.Server - Started @9874ms
INFO|13916/0|Service traccar|19-04-19 18:05:42|[Scheduler-561601094] WARN org.eclipse.jetty.server.HttpChannel - Commit failed
INFO|13916/0|Service traccar|19-04-19 18:05:42|java.util.concurrent.TimeoutException: Idle timeout expired: 30001/30000 ms
INFO|13916/0|Service traccar|19-04-19 18:05:42|	at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:161)
INFO|13916/0|Service traccar|19-04-19 18:05:42|	at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
INFO|13916/0|Service traccar|19-04-19 18:05:42|	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473)
INFO|13916/0|Service traccar|19-04-19 18:05:42|	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
INFO|13916/0|Service traccar|19-04-19 18:05:42|	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
INFO|13916/0|Service traccar|19-04-19 18:05:42|	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
INFO|13916/0|Service traccar|19-04-19 18:05:42|	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
INFO|13916/0|Service traccar|19-04-19 18:05:42|	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
INFO|13916/0|Service traccar|19-04-19 18:05:42|	at java.lang.Thread.run(Thread.java:748)
INFO|13916/0|Service traccar|19-04-19 18:05:42|[Scheduler-561601094] WARN org.eclipse.jetty.server.handler.ResourceHandler - java.util.concurrent.TimeoutException: Idle timeout expired: 30001/30000 ms
INFO|13916/0|Service traccar|19-04-19 19:11:11|[Scheduler-561601094] WARN org.eclipse.jetty.server.HttpChannel - Commit failed
INFO|13916/0|Service traccar|19-04-19 19:11:11|java.util.concurrent.TimeoutException: Idle timeout expired: 30000/30000 ms
INFO|13916/0|Service traccar|19-04-19 19:11:11|	at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:161)
INFO|13916/0|Service traccar|19-04-19 19:11:11|	at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
INFO|13916/0|Service traccar|19-04-19 19:11:11|	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473)
INFO|13916/0|Service traccar|19-04-19 19:11:11|	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
INFO|13916/0|Service traccar|19-04-19 19:11:11|	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
INFO|13916/0|Service traccar|19-04-19 19:11:11|	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
INFO|13916/0|Service traccar|19-04-19 19:11:11|	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
INFO|13916/0|Service traccar|19-04-19 19:11:11|	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
INFO|13916/0|Service traccar|19-04-19 19:11:11|	at java.lang.Thread.run(Thread.java:748)
INFO|13916/0|Service traccar|19-04-19 19:11:11|[Scheduler-561601094] WARN org.eclipse.jetty.server.handler.ResourceHandler - java.util.concurrent.TimeoutException: Idle timeout expired: 30000/30000 ms