[opensuse] Errors with 13.1 64 bit
I have recently been getting errors on the computer used as my firewall/router. When these errors occur, I cannot log into that computer, but it continues routing as normal. The software is up to date. -bash: fork: Cannot allocate memory -bash: fork: Cannot allocate memory -bash: fork: Cannot allocate memory -bash: fork: Cannot allocate memory -bash: fork: Cannot allocate memory -bash: fork: Cannot allocate memory -bash: fork: Cannot allocate memory -bash: fork: Cannot allocate memory -bash: fork: Cannot allocate memory -bash: fork: Cannot allocate memory -bash: fork: Cannot allocate memory -bash: fork: Cannot allocate memory -bash: fork: Cannot allocate memory -bash: cannot make pipe for command substitution: Too many open files Message from syslogd@firewall at Feb 21 20:24:22 ... kernel:[187950.234969] systemd[1]: segfault at a8 ip 000000000047912e sp 00007fffff09e060 error 4 in systemd[400000+ed000] -bash-4.2# reboot -bash: fork: Cannot allocate memory Any ideas? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/25/2015 05:30 PM, James Knott wrote:
-bash: cannot make pipe for command substitution: Too many open files
This sounds like it would be the reason ...
Any ideas?
Find out which of the processes has so many file descriptors open: if executing a command does not work anymore, then maybe enlarging the limit still works (ulimit -n), or find out by navigating thru /proc something like this (avoiding a subshell or spawning a process): $ cd /proc $ for pid in [1-9]*; do \ cd $pid/fd && { echo $pid: *; cd ../..; }; \ done Maybe there is a runaway process with an fd leak - or the default limit is too small for your use case. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/25/2015 11:51 AM, Bernhard Voelker wrote:
Find out which of the processes has so many file descriptors open: if executing a command does not work anymore, then maybe enlarging the limit still works (ulimit -n), or find out by navigating thru /proc something like this (avoiding a subshell or spawning a process):
$ cd /proc $ for pid in [1-9]*; do \ cd $pid/fd && { echo $pid: *; cd ../..; }; \ done
That sort of thing is difficult to do, if I can't log in or even use an existing session. Those captures were taken from existing ssh connections to the computer and, as you can see, I couldn't do anything. BTW, ulimit -n currently shows 1024 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/25/2015 05:57 PM, James Knott wrote:
That sort of thing is difficult to do, if I can't log in or even use an existing session. Those captures were taken from existing ssh connections to the computer and, as you can see, I couldn't do anything.
yes. I thought you'd have still one of these connections open. Well, then you probably have to do a hard reset. ;-/
BTW, ulimit -n currently shows 1024
it's still the same on 13.2, and that limit can be reached quite easily, e.g. if one uses Jboss and other java-based friends. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/25/2015 12:19 PM, Bernhard Voelker wrote:
On 02/25/2015 05:57 PM, James Knott wrote:
That sort of thing is difficult to do, if I can't log in or even use an existing session. Those captures were taken from existing ssh connections to the computer and, as you can see, I couldn't do anything.
yes. I thought you'd have still one of these connections open. Well, then you probably have to do a hard reset. ;-/
Yep, that's what I had to do.
BTW, ulimit -n currently shows 1024
it's still the same on 13.2, and that limit can be reached quite easily, e.g. if one uses Jboss and other java-based friends.
I'm not doing anything like that. I don't normally run any apps on that computer. I just boot it and let it run. It's just a router/firewall, with IPv6 tunnel software. I've been running that tunnel for almost 5 years without this sort of issue, which just started recently. I also ran a pass of memtest without error. I'm also planning on leaving it running overnight, to get a few passes. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 25 Feb 2015 19:04, James Knott
On 02/25/2015 12:19 PM, Bernhard Voelker wrote:
On 02/25/2015 05:57 PM, James Knott wrote:
That sort of thing is difficult to do, if I can't log in or even use an existing session. Those captures were taken from existing ssh connections to the computer and, as you can see, I couldn't do anything.
yes. I thought you'd have still one of these connections open. Well, then you probably have to do a hard reset. ;-/
Yep, that's what I had to do.
BTW, ulimit -n currently shows 1024
it's still the same on 13.2, and that limit can be reached quite easily, e.g. if one uses Jboss and other java-based friends.
I'm not doing anything like that. I don't normally run any apps on that computer. I just boot it and let it run. It's just a router/firewall, with IPv6 tunnel software. I've been running that tunnel for almost 5 years without this sort of issue, which just started recently. I also ran a pass of memtest without error. I'm also planning on leaving it running overnight, to get a few passes.
You might have been bitten by a systemd / dbus muck up. There where some, esp on 13.2 systemd the last weeks. Savest would be (reboot,) zypper patch, reboot (to be save). - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/25/2015 01:09 PM, Yamaban wrote:
I'm not doing anything like that. I don't normally run any apps on that computer. I just boot it and let it run. It's just a router/firewall, with IPv6 tunnel software. I've been running that tunnel for almost 5 years without this sort of issue, which just started recently. I also ran a pass of memtest without error. I'm also planning on leaving it running overnight, to get a few passes.
You might have been bitten by a systemd / dbus muck up. There where some, esp on 13.2 systemd the last weeks. Savest would be (reboot,) zypper patch, reboot (to be save).
A reboot (power switch) was necessary to recover from this. What would zypper get me that Yast online update wouldn't? I suspected the problem was caused by a recent update, but couldn't be sure. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Probably you are affected by this bug: https://bugzilla.suse.com/show_bug.cgi?id=918226 Best Regards, I. Petrov On 02/25/2015 08:15 PM, James Knott wrote:
On 02/25/2015 01:09 PM, Yamaban wrote:
I'm not doing anything like that. I don't normally run any apps on that computer. I just boot it and let it run. It's just a router/firewall, with IPv6 tunnel software. I've been running that tunnel for almost 5 years without this sort of issue, which just started recently. I also ran a pass of memtest without error. I'm also planning on leaving it running overnight, to get a few passes.
You might have been bitten by a systemd / dbus muck up. There where some, esp on 13.2 systemd the last weeks. Savest would be (reboot,) zypper patch, reboot (to be save).
A reboot (power switch) was necessary to recover from this. What would zypper get me that Yast online update wouldn't? I suspected the problem was caused by a recent update, but couldn't be sure.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJU7hS+AAoJEH8sJoKRFRU5gi8P/0Y0hj8P8mqZQQigKTTImjUE 06w2G9VD25Lc2BHxVgth3ZhKlItwnUNf3QgmLezjnLhbky3x0s3r0JU4A+iHRIOs DY3acXsVQKvA31r04HT1dtPQT2WJ1phPGEnDQ11AmAVeLbzKvz9EOhfD8u04gzDr 2tMqk4wu0bS/WfxSE1oMoAuc80BhPjbFab0YCoBitxxfQoB5aFDqzJdk6jLqrsYJ S/OEOT/6j/N1bA0Z+kgWWj3/QVQUtP/ACzZkQB+CYmZ0JmX0YuKnW9hPUys0yyv6 0rWCykZ5764lKKOHOJewo88Gga5LNXf8trKfKO0Zp0MYLJkljquDVey9k1mHgxgn I2kWlm5eh0bw46vByqWiZcZ43Lx5L5DtkOK0l9BHOVx/4eo3f/gAIjI2BHfucI5a BYkxNg1nVi//HXV/UGTBJ5ZhKIWRu/P3CEIjVCKWUKYdBF6Vxr5Fb5VPjv5o2lG4 cW6kc2tDKfmr61jMDJfL9/HyNcfPKbUILmIM+hQyp7Gg1gcWXaCW+MqaCeJstrtX 0xxHFKfXs07ygYZrifH+ry6LmlzsgJZStUOSZg9LPj85FzbSvwJQ9+KRxwUgscRm 2cTFSoTfmtigJRTxA8C7MKmmL7wHskW41iDV9V1y4tZnJqvh2SEP4zDjlc6fYJZH DcCtL2fT6DgptPJsYzAo =gOUg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/25/2015 01:30 PM, I.Petrov wrote:
Hello,
Probably you are affected by this bug:
That would be about the right time frame. I'll have to keep an eye on it. tnx -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 25 Feb 2015 19:15, James Knott
On 02/25/2015 01:09 PM, Yamaban wrote:
I'm not doing anything like that. I don't normally run any apps on that computer. I just boot it and let it run. It's just a router/firewall, with IPv6 tunnel software. I've been running that tunnel for almost 5 years without this sort of issue, which just started recently. I also ran a pass of memtest without error. I'm also planning on leaving it running overnight, to get a few passes.
You might have been bitten by a systemd / dbus muck up. There where some, esp on 13.2 systemd the last weeks. Savest would be (reboot,) zypper patch, reboot (to be save).
A reboot (power switch) was necessary to recover from this. What would zypper get me that Yast online update wouldn't? I suspected the problem was caused by a recent update, but couldn't be sure.
You spoke of using ssh, "zypper patch" is more friendly to that than "yast --ncurses online_update", but both do the same in the end. (yast does more if i rembember correctly, its more like "zypper ref; zypper patch; zypper up"). But lookin at it right now, "yast --ncurses" gives you also the possibility to go back to a prior version, in a easy way, with zypper its a few hops more. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/25/2015 02:38 PM, Yamaban wrote:
You spoke of using ssh, "zypper patch" is more friendly to that than "yast --ncurses online_update", but both do the same in the end. (yast does more if i rembember correctly, its more like "zypper ref; zypper patch; zypper up").
*DUH* ??? Why not just do 'zypper up'? it subsumes the first two. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/25/2015 02:38 PM, Yamaban wrote:
You spoke of using ssh, "zypper patch"
No, I didn't. I don't use zipper. Someone else mentioned that command. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Anton Aylward -
Bernhard Voelker -
I.Petrov -
James Knott -
Yamaban