-
Notifications
You must be signed in to change notification settings - Fork 73
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
Can't cd to (unreachable)/: No such file or directory #55
Comments
Confirmed that if I revert the change made in 4e020cb to Perl.pm that needrestart works again. |
I'm unable to reproduce this issue. Could you please provide the output of |
The error occurs at
I'm running sudo needrestart $src is set to /usr/sbin/sqlgrey $cwd is set to /home/candrews (if I run from other directories, I get the same error, so I don't think $cwd is important)$pid is set to 15601
I'm using "dev-perl/Module-ScanDeps" version 1.230.0 sqlgrey is run as a systemd service. Here's that information:
I'm using systemd 232. |
Maybe the issue is triggered by the |
I removed I ran |
For starters I think there is a I have the same issue with sympa; with
This is debian stretch amd64, with another print for the chdir debug line, and the fixed chdir before return. |
@stbuehler can you please submit a pull request with your suggested change? |
I guess you misunderstood me; the missing cwd restore was a bug, but not this bug - the output I showed with the backtrace of the problem was done with #70 already applied. |
Did this fix work for everyone? We currently experience this on lxc host running debian stable (stretch). |
I got the same issue after yesterday's Debian update (Version 9.6). I have
and a
The error was:
I did tried this fix (8311453) but it did not work. Finally, I fixed it by switching back to system-v: |
I can confirm this,
Stopping munin-node allowed needrestart to continue |
This issue seems to be related to #125. |
This problem impacts version 2.11 (I did not have on any previous version).
Simply running
needrestart
yields this error:I suspect this problem was caused by 4e020cb
The text was updated successfully, but these errors were encountered: