| View previous topic :: View next topic |
| Author |
Message |
therealjrd
Tux's lil' helper
Joined: 18 May 2006
Posts: 122
|
 Posted: Thu Jul 25, 2024 6:55 pm Post subject: Net::DNS acting wierd |
 |
|
I've just built up a new server. Most stuff works, but one of my apps (qpsmtp) is croaking. A bit of debugging reveals the following, when something tries to connct to it:
| Code: |
*** FATAL PROGRAM ERROR!! Unknown instance method "udpsize"
*** which the program has attempted to call for the object:
***
. IN OPT ; no data
***
*** THIS IS A BUG IN THE CALLING SOFTWARE, which incorrectly assumes
*** that the object would be of a particular type. The type of an
*** object should be checked before calling any of its methods.
***
Net::DNS::RR 1910
Can't locate Net/DNS/RR/OPT.pm: lib/Net/DNS/RR/OPT.pm: Permission denied at (eval 34) line 1.
at /usr/lib64/perl5/vendor_perl/5.38/Net/DNS/Resolver/Base.pm line 983.
Net::DNS::Resolver::Base::_make_query_packet(Net::DNS::Resolver=HASH(0x5578b0cb8cd0), "192.168.2.6", "PTR") called at /usr/lib64/perl5/vendor_perl/5.38/Net/DNS/Resolver/Base.pm line 410
Net::DNS::Resolver::Base::send(Net::DNS::Resolver=HASH(0x5578b0cb8cd0), "192.168.2.6", "PTR") called at /usr/lib64/perl5/vendor_perl/5.38/Net/DNS/Resolver/Base.pm line 381
Net::DNS::Resolver::Base::query(Net::DNS::Resolver=HASH(0x5578b0cb8cd0), "192.168.2.6", "PTR") called at /usr/lib64/perl5/vendor_perl/5.38/Qpsmtpd/Base.pm line 108
Qpsmtpd::Base::resolve_ptr(Qpsmtpd::Base=HASH(0x5578b0b7db30), "192.168.2.6") called at /usr/lib64/perl5/vendor_perl/5.38/Qpsmtpd/TcpServer.pm line 198
Qpsmtpd::TcpServer::tcpenv(Qpsmtpd::TcpServer=HASH(0x5578b0c62470), "192.168.2.75", "192.168.2.6") called at /usr/bin/qpsmtpd-forkserver line 304
|
I'm running perl-5.38.2-r3 and Net-DNS-1.450.0
Does this ring any bells?
Thanks in advance. |
|
| Back to top |
|
 |
sMueggli
Guru
Joined: 03 Sep 2022
Posts: 489
|
| Posted: Fri Jul 26, 2024 4:45 pm Post subject: |
|
|
| Did you try ? |
|
| Back to top |
|
|
therealjrd
Tux's lil' helper
Joined: 18 May 2006
Posts: 122
|
| Posted: Sun Jul 28, 2024 6:24 pm Post subject: |
|
|
Yes. No effect.
I've found a few other references to this error, but no obvious solution. If the error is to be believed, it's a bug where upstream didn't dot and cross i's and t's. In that case I would expect it to fix itself eventually. In the meantime I've found a configuration workaround which doesn't tickle that path through the code. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
