Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MSD: Deep recursion on subroutine #22

Open
boindil opened this issue Apr 7, 2021 · 2 comments
Open

MSD: Deep recursion on subroutine #22

boindil opened this issue Apr 7, 2021 · 2 comments

Comments

@boindil
Copy link

boindil commented Apr 7, 2021

Moin,
im Perl-Script kommt es zu Endlosschleifen, wenn die Logdateien nicht geschrieben werden können.

MySQLDumper - Perl CronDump [Version 1.24.4] started successfully (using perl v5.30.0)

[Wed Apr 7 18:30:12 2021] crondump.pl: Deep recursion on subroutine "main::PrintOut" at httpdocs/msd_cron/crondump.pl line 709.

[Wed Apr 7 18:30:12 2021] crondump.pl: Deep recursion on subroutine "main::err_trap" at httpdocs/msd_cron/crondump.pl line 770.

@r23
Copy link
Owner

r23 commented Apr 8, 2021

Here in the test environment, the backup with Perl works perfectly. If you are looking for support, describe your environment in a comprehensible way. And for reasons of politeness, use the English language.

grafik

@boindil
Copy link
Author

boindil commented Apr 9, 2021

Hi @r23,
I was using german, since this is an application with even a german documentation linked in this readme, however english is also fine ofc.

Yes, the dumper is working on my end now, too. The problem was a chroot environment with absolute - inaccessable - paths in chroot. Since I wasnt getting any useful error messages, I had to debug the code which was somewhat annoying.

This should not happen. If the log file is not accessable for any reason, this should not result in endless loops that are being detected by perl. Instead it should be resolved by print outs with appropriate error messages. The error messages in these lines were not printed out, as you can see.

I later noticed, that the autodelete method has a similar problem too, it seems that it cant handle relative paths. Note that I am in chroot.

Working:

path/to/log/file
/path/to/log/file
/path/to/work/folder

Not Working:

path/to/work/folder

The logging methods are able to use paths relative to the current directory, whilst the autodelete is not. Thats irritating to say the least.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants