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
Perl 5.16.1 hangs on ./Configure on Debian in nfs file system #12507
Comments
From francis.nguyen@oicr.on.caCreated by francis.nguyen@oicr.on.caI am installing the latest version of perl (5.16.1) onto an nfs filesystem. Steps to reproduce: Perl Info
|
From @doughera88On Mon, 22 Oct 2012, Francis Nguyen wrote:
Configure definitely shouldn't hang, but I am unable to reproduce this If I had to guess, I'd guess your nfs client or server is having problems First, could please re-run Configure without the -s option? The -s option Next, if it hangs after printing "Checking if fcntl-based file locking /* Start of program */ /* end of program */ Even if the fcntl() call fails, this program is supposed to time out after Also helpful for debugging/reproducing this would be more information 1. uname -a output on the Debian client (The info in the original Thanks, -- |
The RT System itself - Status changed from 'new' to 'open' |
From francis.nguyen@oicr.on.ca(Sorry if this is a doublepost, but the message I sent to perlbug-followup@perl.org isn't showing up on https://rt-archive.perl.org/perl5/Public/Bug/Display.html?id=115416) Thank you very much for the quick response. The problem resolved itself this morning (post-restart) but then suddenly began giving the same problem again about an hour ago. After re-running configure without -s, I can confirm that it hangs after printing "Checking if fcntl-based file locking works...". I compiled and ran the C program (which is identical to try.c in the UU directory), and used gdb to figure out what was going on. The following is the output: Breakpoint 1, main () at test.c:19 Breakpoint 2, main () at test.c:20 At this point, the process hung, and could be viewed as being in uninterruptable sleep (D) under top. More information: 2) blabuser@clusterbuild:/.mounts/labs/boutroslab/private/users/blabuser/perl-5.16.1$ dpkg --status nfs-common 3) Unsure. I'm not an administrator, but I will get in contact with IT to tell you this. 4) As far as I know, the information in the perlbug report (gcc version 4.3.2, libc version 2.7) is correct. Thanks, Francis Nguyen Student Ontario Institute for Cancer Research Toll-free: 1-866-678-6427 This message and any attachments may contain confidential and/or privileged information for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this message in error, please contact the sender and delete all copies. Opinions, conclusions or other information contained in this message may not be that of the organization. ________________________________________ On Mon, 22 Oct 2012, Francis Nguyen wrote:
Configure definitely shouldn't hang, but I am unable to reproduce this If I had to guess, I'd guess your nfs client or server is having problems First, could please re-run Configure without the -s option? The -s option Next, if it hangs after printing "Checking if fcntl-based file locking /* Start of program */ /* end of program */ Even if the fcntl() call fails, this program is supposed to time out after Also helpful for debugging/reproducing this would be more information 1. uname -a output on the Debian client (The info in the original Thanks, -- |
From francis.nguyen@oicr.on.caAh -- the only reason it was working this morning was because I didn't have try.c in the same directory as that script. I've run a couple tests with the code you sent and figured out something interesting: the fcntl() call will run for 10 seconds like you said, but can still be ctrl+C'd out of. When the alarm hits after 10 seconds, the process becomes unresponsive to any sort of kill. Nonetheless, this does seem to be more of an issue on our side, and I will talk this over with our IT to try and resolve this issue. Thank you very much for your assistance, Francis Nguyen Student |
From francis.nguyen@oicr.on.caThank you very much for the quick response. The problem resolved itself this morning (post-restart) but then suddenly began giving the same problem again about an hour ago. After re-running configure without -s, I can confirm that it hangs after printing "Checking if fcntl-based file locking works...". I compiled and ran the C program (which is identical to try.c in the UU directory), and used gdb to figure out what was going on. The following is the output: Breakpoint 1, main () at test.c:19 Breakpoint 2, main () at test.c:20 At this point, the process hung, and could be viewed as being in uninterruptable sleep (D) under top. More information: 2) blabuser@clusterbuild:/.mounts/labs/boutroslab/private/users/blabuser/perl-5.16.1$ dpkg --status nfs-common 3) Unsure. I'm not an administrator, but I will get in contact with IT to tell you this. 4) As far as I know, the information in the perlbug report (gcc version 4.3.2, libc version 2.7) is correct. Thanks, Francis Nguyen Student Ontario Institute for Cancer Research Toll-free: 1-866-678-6427 This message and any attachments may contain confidential and/or privileged information for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this message in error, please contact the sender and delete all copies. Opinions, conclusions or other information contained in this message may not be that of the organization. ________________________________________ On Mon, 22 Oct 2012, Francis Nguyen wrote:
Configure definitely shouldn't hang, but I am unable to reproduce this If I had to guess, I'd guess your nfs client or server is having problems First, could please re-run Configure without the -s option? The -s option Next, if it hangs after printing "Checking if fcntl-based file locking /* Start of program */ /* end of program */ Even if the fcntl() call fails, this program is supposed to time out after Also helpful for debugging/reproducing this would be more information 1. uname -a output on the Debian client (The info in the original Thanks, -- |
From @ppisarOn 2012-10-24, Francis Nguyen <Francis.Nguyen@oicr.on.ca> wrote:
Maybe you are not running lock manager on NFS server and client or the -- Petr |
From francis.nguyen@oicr.on.ca--RESOLVED-- Thank you very much for your help, |
From francis.nguyen@oicr.on.caIf I figure out specifically caused this, I'll try to leave a comment |
From [Unknown Contact. See original ticket]If I figure out specifically caused this, I'll try to leave a comment |
francis.nguyen@oicr.on.ca - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#115416 (status was 'resolved')
Searchable as RT115416$
The text was updated successfully, but these errors were encountered: