readWorkerTask error logs

40 views
Skip to first unread message

Aravind Padmanabhan

unread,
Oct 16, 2023, 5:08:43 PM10/16/23
to iRODS-Chat
Hello,
Thank you for your continued support on our questions.

I am observing a lot of "readWorkerTask" errors on rodsServerlogs.

Like this, it's getting generated a lot
Oct 16 15:18:00 pid:49899 remote addresses: 192.168.108.102 ERROR: readWorkerTask - readStartupPack failed. -4000
Oct 16 15:18:00 pid:49899 remote addresses: 127.0.0.1, 192.168.108.102 ERROR: readWorkerTask - readStartupPack failed. -4000
Oct 16 15:18:00 pid:49899 remote addresses: 192.168.1.25, 192.168.7.57, 192.168.7.72, 192.168.7.77, 192.168.7.78, 192.168.7.79, 192.168.7.82, 192.168.7.84, 192.168.108.102 ERROR: readWorkerTask - readStartupPack failed. -4000
Oct 16 15:18:00 pid:49899 remote addresses: 192.168.1.25, 192.168.7.57, 192.168.7.67, 192.168.7.71, 192.168.7.72, 192.168.7.77, 192.168.7.79, 192.168.7.81, 192.168.7.82, 192.168.7.84, 192.168.7.86, 192.168.108.102 ERROR: readWorkerTask - readStartupPack failed. -4000
Oct 16 15:18:29 pid:49899 remote addresses: 192.168.108.102 ERROR: readWorkerTask - readStartupPack failed. -4000
Oct 16 15:18:29 pid:49899 remote addresses: 127.0.0.1, 192.168.108.102 ERROR: readWorkerTask - readStartupPack failed. -4000
Oct 16 16:45:00 pid:49899 remote addresses: 127.0.0.1, 192.168.108.102 ERROR: readWorkerTask - readStartupPack failed. -4000
Oct 16 16:45:00 pid:49899 remote addresses: 192.168.108.102 ERROR: readWorkerTask - readStartupPack failed. -4000
Oct 16 16:45:00 pid:49899 remote addresses: 192.168.108.102 ERROR: readWorkerTask - readStartupPack failed. -4000
Oct 16 16:45:00 pid:49899 remote addresses: 127.0.0.1, 192.168.108.102 ERROR: readWorkerTask - readStartupPack failed. -4000

How can get more info here.
Thank you

Kory Draughn

unread,
Oct 16, 2023, 5:18:05 PM10/16/23
to irod...@googlegroups.com
Hi Aravind,

I have a couple questions ...

What version of iRODS are you running?
Is the server responding and servicing requests?

Kory Draughn
Chief Technologist
iRODS Consortium


--
--
The Integrated Rule-Oriented Data System (iRODS) - https://irods.org
 
iROD-Chat: http://groups.google.com/group/iROD-Chat
---
You received this message because you are subscribed to the Google Groups "iRODS-Chat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to irod-chat+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/irod-chat/1ffacd53-a85a-4641-8dd4-0051aa94bcf5n%40googlegroups.com.

Aravind Padmanabhan

unread,
Oct 16, 2023, 10:44:10 PM10/16/23
to iRODS-Chat
Hi Kory,
Thank you for your reply.
We are on 4.2.7
We only have a single zone.

The resource servers are responding and serving data.
I was just searching the logs for something else, and stumbled on this.

Thank you

Aravind Padmanabhan

unread,
Oct 18, 2023, 1:50:34 PM10/18/23
to iRODS-Chat
Hi Kory,
Just an update.
The readWorker errors stopped after Oct16.
We did not make any changes though.
Thanks

Terrell Russell

unread,
Oct 18, 2023, 2:02:15 PM10/18/23
to irod...@googlegroups.com
Hi Aravind,

I believe those "readWorkerTask"s are related to failed parallel transfers (high ports).

I'd think you might have had (and maybe still have) a networking / hostname mismatch somewhere and the large file transfers weren't happy.

Terrell


Aravind Padmanabhan

unread,
Oct 18, 2023, 4:39:41 PM10/18/23
to iRODS-Chat
Hi Terrell,
Thank you
We will investigate as the errors are coming up again.
Thank you

Sietse Snel

unread,
Oct 19, 2023, 6:57:42 AM10/19/23
to iRODS-Chat
Hi all, 

I believe these messages can also be related to connections to port 1247 by software that doesn't use the iRODS protocol (e.g. port scans, load balancer probes, etc.)

You can reproduce this by connecting to port 1247 using a non-iRODS-protocol . Example command on provider: wget https://localhost:1247

Best,
Sietse

Aravind Padmanabhan

unread,
Oct 19, 2023, 9:55:08 AM10/19/23
to iRODS-Chat
Thank you all.
I will investigate / test and update here.
Thanks again
Reply all
Reply to author
Forward
0 new messages