Use of uninitialized value in subroutine entry

NCSC-NL / taranis3

Taranis

Other

59 stars 17 forks source link

Use of uninitialized value in subroutine entry #33

Open chandog opened 4 years ago

chandog commented 4 years ago

Am getting below message in taranis. Kindly assist/advise

Use of uninitialized value in subroutine entry at /home/taranis/taranis-3.6.2/perl5/Taranis/DB.pm line 207

Regards

markov2 commented 4 years ago

Can you reproduce the error message? Does it show often or only once? Did any functionality break?
Did you experience this message is a fresh installation, or in a set-up which already runs for some time?
What is your PostgreSQL version? (It uses a plugin which has changed over time)

chandog commented 4 years ago

We get the error often Please note we have been running the system with no error until last Friday. PostgreSQL version is 9.5.19

markov2 commented 4 years ago

Can you try to add this to /home/taranis/taranis-3.6.2/perl5/Taranis/DB.pm line 207

    my $lobj_fd  = $dbh->func($oid, $dbh->{pg_INV_WRITE}, 'lo_open' );
use Carp 'cluck';
defined $lobj_fd && defined $_[1] or cluck "addBlob(): $lobj_fd#";
    my $size     = $dbh->func($lobj_fd, $_[1], length $_[1], 'lo_write');

This will show a stack-trace. Probably addBlob is called with an "undef", but there are few of places where it is used: let's try to find where the empty blob is not caught.

ScorpionKing34 commented 4 years ago

We have same problem with our production server, I send my problem to taranis support mail. Use of uninitialized value in subroutine entry at /opt/taranis/taranis-3.6.2/perl5/Taranis/DB.pm line 207 my $size = $dbh->func($lobjfd, $[1], length $_[1], 'lo_write');

markov2 commented 4 years ago

To avoid slow response you can better directly send it to me at mark@overmeer.net

sosgasm commented 2 years ago

Was this problem ever solved? Same problem here under version 3.7.4.

It used to work. Error: Use of uninitialized value in subroutine entry at /home/taranis/taranis-3.7.4/perl5/Taranis/DB.pm line 207.

markov2 commented 2 years ago

Was this problem ever solved? Same problem here under version 3.7.4.

The issue did not get resolved, because I did not get the additional information I needed to make a good fix. See my response on April 14 2020. When people do not help me study the issue on their platform, I cannot fix it until it shows up on my own systems.