Forum Discussion
hrelinho
Nimbostratus
NimbostratusUpdate OWASP score task failed.
Hello,
Just realized that my LTM is filling with restjavad logs, I'm getting error:
Update OWASP score task failed. OWASP Compliance Score generation task next iteration scheduled to run in 60 minutes from now.
It seems that it's connected with WAF module, which I'm not using currently. Also, just checked for network issues, and it seems everything is ok.
Does anyone have any idea? Thanks in advance!! (full log below).
LTM version: 16.0.0 0.0.12
[I][458273][05 Feb 2021 04:40:05 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] Update OWASP score task failed.
[I][458274][05 Feb 2021 04:40:05 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP Compliance Score generation task next iteration scheduled to run in 60 minutes from now.
[SEVERE][458275][05 Feb 2021 05:40:05 UTC][com.f5.rest.workers.asm.AsmConfigWorker] nanoTime:[15761351310149764] threadId:[21] Exception:[org.apache.thrift.transport.TTransportException: java.net.ConnectException: Connection refused (Connection refused)
at org.apache.thrift.transport.TSocket.open(TSocket.java:185)
at com.f5.asmconfig.client.AsmClient.<init>(AsmClient.java:42)
at com.f5.asmconfig.client.AsmClient.<init>(AsmClient.java:50)
at com.f5.rest.workers.asm.WrapAsmClient.getClient(AsmConfigWorker.java:306)
at com.f5.rest.workers.asm.AsmConfigWorker.restCallWithRetry(AsmConfigWorker.java:170)
at com.f5.rest.workers.asm.AsmConfigWorker.forwardCall(AsmConfigWorker.java:200)
at com.f5.rest.workers.asm.AsmConfigWorker$1.run(AsmConfigWorker.java:156)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:580)
at org.apache.thrift.transport.TSocket.open(TSocket.java:180)
... 13 more
]client:[7182705]
lixiaodongI mat the same question :
vious schedule of score generation.
[I][94450][08 Oct 2021 03:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP Compliance Score generation task next iteration sche
duled to run in 60 minutes from now.
[I][94451][08 Oct 2021 04:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP score generation: No policies found updated from pre
vious schedule of score generation.
[I][94452][08 Oct 2021 04:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP Compliance Score generation task next iteration sche
duled to run in 60 minutes from now.
[I][94453][08 Oct 2021 05:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP score generation: No policies found updated from pre
vious schedule of score generation.
[I][94454][08 Oct 2021 05:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP Compliance Score generation task next iteration sche
duled to run in 60 minutes from now.
[I][94455][08 Oct 2021 06:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP score generation: No policies found updated from pre
vious schedule of score generation.
[I][94456][08 Oct 2021 06:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP Compliance Score generation task next iteration sche
duled to run in 60 minutes from now.
[I][94457][08 Oct 2021 07:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP score generation: No policies found updated from pre
vious schedule of score generation.
[I][94458][08 Oct 2021 07:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP Compliance Score generation task next iteration sche
duled to run in 60 minutes from now.
[I][94459][08 Oct 2021 08:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP score generation: No policies found updated from pre
vious schedule of score generation.
[I][94460][08 Oct 2021 08:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP Compliance Score generation task next iteration sche
duled to run in 60 minutes from now.
[I][94461][08 Oct 2021 09:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP score generation: No policies found updated from pre
vious schedule of score generation.
[I][94462][08 Oct 2021 09:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP Compliance Score generation task next iteration sche
duled to run in 60 minutes from now.
[I][94463][08 Oct 2021 10:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskScheduleWorker] OWASP score generation: No policies found updated from pre
vious schedule of score generation.
[I][94464][08 Oct 2021 10:54:17 UTC][8100/tm/asm/owasp/task OWASPTaskSched
boneyardMVP
Also noticing that on 15.1.6.1.
Did either of you opened a F5 support ticket? lixiaodong hrelinho ?
- Mostafa_Elsayed
Cirrus
did u solve the issue?
- boneyard
No, didn't look at it further at that time, dont have access to the system now.
- Mostafa_Elsayed
As I can see it is related to Bug ID 991829 (https://cdn.f5.com/product/bugtracker/ID991829.html) which is Continuous connection refused errors in restjavad , The errors are observed regardless of asm provisioning
and no provided workaround until now.
- boneyard
Could be, if it really bothers you I would contact support to be sure.
- Mostafa_Elsayed
No Thanks bro, and something abnormal happended we have alot of security policies around 150 , and when we access OWASP Compliance, we disconnect from F5 GUI but if we leave page as it for 3 minutes we can press "Continue" and see OWASP compliance score normally 😂
and customer accepted that delay.
