WARN: DOS ALERT: Request delayed=100ms

smsoousa10 months ago

Hello everybody! I know there are topics related to this, however, I didn't find answers in any of them. We use a WhatsApp server to trigger notifications on traccar. Works well. However, we are having a recent problem, all devices go offline and only come back when we restart the traccar server. The error received is this:

2024-01-26 19:32:58  WARN: DOS ALERT: Request delayed=100ms, ip=201.8.70.67, overlimit=OverLimit@385ef239[type=AUTH, id=930, duration=PT0.979036398S, count=25], session=node0ze2h9s1oihlj1q24te34c3yht297.node0, user=null
2024-01-26 19:32:58  WARN: DOS ALERT: Request delayed=100ms, ip=201.8.70.67, overlimit=OverLimit@578d13ac[type=AUTH, id=930, duration=PT0.925531079S, count=25], session=node0ze2h9s1oihlj1q24te34c3yht297.node0, user=null
2024-01-26 19:32:58  WARN: DOS ALERT: Request delayed=100ms, ip=201.8.70.67, overlimit=OverLimit@65f20be2[type=AUTH, id=930, duration=PT0.923903396S, count=25], session=node0ze2h9s1oihlj1q24te34c3yht297.node0, user=null
2024-01-26 19:32:58  WARN: DOS ALERT: Request delayed=100ms, ip=201.8.70.67, overlimit=OverLimit@63ee9963[type=AUTH, id=930, duration=PT0.950483967S, count=25], session=node0ze2h9s1oihlj1q24te34c3yht297.node0, user=null
2024-01-26 19:32:58  WARN: DOS ALERT: Request delayed=100ms, ip=201.8.70.67, overlimit=OverLimit@2cc121de[type=AUTH, id=930, duration=PT0.930601874S, count=25], session=node0ze2h9s1oihlj1q24te34c3yht297.node0, user=null
2024-01-26 19:32:58  WARN: DOS ALERT: Request delayed=100ms, ip=201.8.70.67, overlimit=OverLimit@700fac5f[type=AUTH, id=930, duration=PT0.920518102S, count=25], session=node0ze2h9s1oihlj1q24te34c3yht297.node0, user=null
2024-01-26 19:32:58  WARN: DOS ALERT: Request delayed=100ms, ip=201.8.70.67, overlimit=OverLimit@80cad76[type=AUTH, id=930, duration=PT0.948348055S, count=25], session=node0ze2h9s1oihlj1q24te34c3yht297.node0, user=null
2024-01-26 19:32:58  WARN: DOS ALERT: Request delayed=100ms, ip=201.8.70.67, overlimit=OverLimit@24db1413[type=AUTH, id=930, duration=PT0.914625528S, count=25], session=node0ze2h9s1oihlj1q24te34c3yht297.node0, user=null
2024-01-26 19:32:58  WARN: DOS ALERT: Request delayed=100ms, ip=201.8.70.67, overlimit=OverLimit@7e4d763d[type=AUTH, id=930, duration=PT0.914007889S, count=25], session=node0ze2h9s1oihlj1q24te34c3yht297.node0, user=null

We use traccar standard SMS notifications. When we turn off notifications, the problem seems to go away. Can anyone help me with this? And know if this log information is a DDOS attack?

Anton Tananaev10 months ago

We use a WhatsApp server to trigger notifications on traccar.

What exactly do you mean by this?

smsoousa10 months ago

We have a service that looks like Telegram. When traccar notifies, the message is sent to the customer's Whatsapp. We use this configuration:

<entry key='notificator.sms.manager.class'>org.traccar.sms.HttpSmsClient</entry>
<entry key='sms.http.url'>http://my-ip:port/send-message</entry>
<entry key='sms.http.template'>{"number": "{phone}","message": "{message}"}</entry>
Anton Tananaev10 months ago

So you deliver notifications to WhatsApp, not trigger them from WhatsApp, right?

smsoousa10 months ago

Yes correct.

Anton Tananaev10 months ago

Then the logs you provided are completely unrelated to it.

Cristian10 months ago

smsoousa, if you use an api for WhatsApp notifications and the devices go to unknown status there can be 2 situations: that a notification is being sent to a client whose phone number is not registered in the traccar server client account or that the phone number is not authorized in the WhatsApp api.
If stopping the whatsapp api solves the problem then that's what I'm telling you.

but as Anton says, the records you provided have nothing to do with what you are talking about.